Re: Subject: [PATCH v2] vmbus: retrieve connection-id from DeviceTree
From: Saurabh Singh Sengar
Date: Tue Jun 03 2025 - 23:27:32 EST
On Tue, Jun 03, 2025 at 02:01:00PM -0700, Hardik Garg wrote:
> The connection-id determines which hypervisor communication channel the
> guest should use to talk to the VMBus host. This patch adds support to
> read this value from the DeviceTree where it exists as a property under
> the vmbus node with the compatible ID "microsoft,message-connection-id".
> The property name follows the format <vendor>,<field> where
> "vendor": "microsoft" and "field": "message-connection-id"
>
> Reading from DeviceTree allows platforms to specify their preferred
> communication channel, making it more flexible. If the property is
> not found in the DeviceTree, use the default connection ID
> (VMBUS_MESSAGE_CONNECTION_ID or VMBUS_MESSAGE_CONNECTION_ID_4
> based on protocol version).
>
> Signed-off-by: Hardik Garg <hargar@xxxxxxxxxxxxxxxxxxx>
> ---
> v2:
> - Rebased on hyperv-next branch as requested by maintainers
> - Added details about the property name format in the commit message
Property need to be documented in Documentation/devicetree/bindings/bus/microsoft,vmbus.yaml
- Saurabh
>