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/[email protected]/ 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/[email protected]/ Changes in v1: - Initial submission - https://lore.kernel.org/all/[email protected]/ 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
