This patch series adds support for reading the VMBus message
connection ID from DeviceTree. The connection-id determines which
hypervisor communication channel the guest should use to talk to
the VMBus host.

Changes in v5:
- Updated subject line and commit description to clarify what
  connection ID is and why DeviceTree support is required
- Addressed reviewer feedback about zero handling and binding
  constraints
- Revised binding description to clarify version-based selection
  instead of using "defaults" language
- Fixed checkpatch warnings (indentation and alignment)

Changes in v4:
- Split the patch into two separate patches:
  * DeviceTree bindings documentation
  * Implementation changes
- Fixed warnings reported by checkpatch

Changes in v3:
- Added documentation for the new property in DeviceTree bindings
-
https://lore.kernel.org/all/6a92ca86-ad6b-4d49-af6e-1ed7651b8ab8@linux.microsoft.com/

Changes in v2:
- Rebased on hyperv-next branch as requested by maintainers
- Added details about the property name format in the commit message
-
https://lore.kernel.org/all/096edaf7-cc90-42b6-aff4-c5f088574e1e@linux.microsoft.com/

Changes in v1:
- Initial submission
-
https://lore.kernel.org/all/6acee4bf-cb04-43b9-9476-e8d811d26dfd@linux.microsoft.com/

Testing:
- Tested on Microsoft Hyper-V
- Verified with and without the DeviceTree property
- Confirmed proper fallback to version-based connection ID selection
- Validated binding documentation with dt_binding_check

Hardik Garg (2):
  dt-bindings: microsoft: Add vmbus message-connection-id property
  Drivers: hv: vmbus: retrieve connection-id from DeviceTree

 .../devicetree/bindings/bus/microsoft,vmbus.yaml    | 12 ++++++++++++
 drivers/hv/connection.c                             |  7 +++++--
 drivers/hv/vmbus_drv.c                              |  8 ++++++++
 3 files changed, 25 insertions(+), 2 deletions(-)

-- 
2.34.1

Just a gentle ping on this patch in case it got lost. I want to
check if anyone had a chance to look at it, or if there is
anything I should update or clarify.

I’ve also noticed a formatting issue in patch 2/2, which I
will address when sending a v6 along with any feedback.



Thanks,
Hardik

On 12/23/2025 3:05 PM, Hardik Garg wrote:
> This patch series adds support for reading the VMBus message
> connection ID from DeviceTree. The connection-id determines which
> hypervisor communication channel the guest should use to talk to
> the VMBus host.
>
> Changes in v5:
> - Updated subject line and commit description to clarify what
>   connection ID is and why DeviceTree support is required
> - Addressed reviewer feedback about zero handling and binding
>   constraints
> - Revised binding description to clarify version-based selection
>   instead of using "defaults" language
> - Fixed checkpatch warnings (indentation and alignment)