From: Hardik Garg <hargar@linux.microsoft.com>
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, krzk+dt@kernel.org, robh@kernel.org,
conor+dt@kernel.org, mhklinux@outlook.com
Cc: devicetree@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, ssengar@linux.microsoft.com,
longli@microsoft.com, Naman Jain <namjain@linux.microsoft.com>,
hargar@microsoft.com
Subject: [PATCH v5 0/2] Add VMBus message connection ID support via DeviceTree
Date: Tue, 23 Dec 2025 15:05:47 -0800 [thread overview]
Message-ID: <58cb22cb-b0c8-4694-b9e4-971aa7f0f972@linux.microsoft.com> (raw)
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
next reply other threads:[~2025-12-23 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 23:05 Hardik Garg [this message]
2025-12-23 23:07 ` [PATCH v5 1/2] dt-bindings: microsoft: Add vmbus message-connection-id property Hardik Garg
2025-12-23 23:09 ` [PATCH v5 2/2] Drivers: hv: vmbus: retrieve connection-id from DeviceTree Hardik Garg
2026-01-27 0:12 ` [PATCH v5 0/2] Add VMBus message connection ID support via DeviceTree Hardik Garg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58cb22cb-b0c8-4694-b9e4-971aa7f0f972@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--cc=conor+dt@kernel.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hargar@microsoft.com \
--cc=krzk+dt@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=robh@kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®