This patch series adds support for configuring the VMBus message connection-id through DeviceTree. The connection-id determines which hypervisor communication channel the guest should use to talk to the VMBus host.
Changes in v4: - Split the patch into two separate patches: * DeviceTree bindings documentation * Implementation changes - Fix warnings reported by checkpatch Changes in v3: - https://lore.kernel.org/all/6a92ca86-ad6b-4d49-af6e-1ed7651b8...@linux.microsoft.com/ Changes in v2: - https://lore.kernel.org/all/096edaf7-cc90-42b6-aff4-c5f088574...@linux.microsoft.com/ Changes in v1: - https://lore.kernel.org/all/6acee4bf-cb04-43b9-9476-e8d811d26...@linux.microsoft.com/ The series consists of two patches: 1. dt-bindings: microsoft: Add vmbus message-connection-id property 2. vmbus: retrieve connection-id from DeviceTree Testing: - Tested on Microsoft Hyper-V - Verified with and without the DeviceTree property - Confirmed proper fallback to default values - Validated binding documentation with dt_binding_check Hardik Garg (2): dt-bindings: microsoft: Add vmbus message-connection-id property vmbus: retrieve connection-id from DeviceTree Documentation/devicetree/bindings/bus/microsoft,vmbus.yaml | 9 +++++++++ drivers/hv/connection.c | 6 ++++-- drivers/hv/vmbus_drv.c | 13 +++++++++++++ 3 files changed, 26 insertions(+), 2 deletions(-) -- 2.40.4