[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <58cb22cb-b0c8-4694-b9e4-971aa7f0f972@linux.microsoft.com>
Date: Tue, 23 Dec 2025 15:05:47 -0800
From: Hardik Garg <hargar@...ux.microsoft.com>
To: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, krzk+dt@...nel.org, robh@...nel.org,
conor+dt@...nel.org, mhklinux@...look.com
Cc: devicetree@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, ssengar@...ux.microsoft.com,
longli@...rosoft.com, Naman Jain <namjain@...ux.microsoft.com>,
hargar@...rosoft.com
Subject: [PATCH v5 0/2] Add VMBus message connection ID support via DeviceTree
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
Powered by blists - more mailing lists