From: Saurabh Sengar <ssengar@linux.microsoft.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, daniel.lezcano@linaro.org,
tglx@linutronix.de, virtualization@lists.linux-foundation.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, mikelley@microsoft.com,
ssengar@microsoft.com
Subject: [PATCH v2 0/6] Device tree support for Hyper-V VMBus driver
Date: Tue, 31 Jan 2023 10:10:03 -0800 [thread overview]
Message-ID: <1675188609-20913-1-git-send-email-ssengar@linux.microsoft.com> (raw)
This set of patches expands the VMBus driver to include device tree
support.
The first two patches enable compilation of Hyper-V APIs in a non-ACPI
build.
The third patch converts the VMBus driver from acpi to more generic
platform driver.
Further to add device tree documentation for VMBus, it needs to club with
other virtualization driver's documentation. For this rename the virtio
folder to more generic hypervisor, so that all the hypervisor based
devices can co-exist in a single place in device tree documentation. The
fourth patch does this renaming.
The fifth patch introduces the device tree documentation for VMBus.
The sixth patch adds device tree support to the VMBus driver. Currently
this is tested only for x86 and it may not work for other archs.
[v2]
- Convert VMBus acpi device to platform device, and added device tree support
in separate patch. This enables using same driver structure for both the flows.
- In Device tree documentation, changed virtio folder to hypervisor and moved
VMBus documentation there.
- Moved bindings before Device tree patch.
- Removed stale ".data" and ".name" field from of_device match table.
- Removed debug print.
- Fix "make DT_CHECKER_FLAGS=-m dt_binding_check" warnings.
Saurabh Sengar (6):
drivers/clocksource/hyper-v: non ACPI support in hyperv clock
Drivers: hv: allow non ACPI compilation for
hv_is_hibernation_supported
Drivers: hv: vmbus: Convert acpi_device to platform_device
dt-bindings: hypervisor: Rename virtio to hypervisor
dt-bindings: hypervisor: Add dt-bindings for VMBus
Driver: VMBus: Add device tree support
.../bindings/{virtio => hypervisor}/mmio.yaml | 2 +-
.../bindings/hypervisor/msft,vmbus.yaml | 50 ++++++
.../{virtio => hypervisor}/pci-iommu.yaml | 2 +-
.../{virtio => hypervisor}/virtio-device.yaml | 2 +-
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 3 +-
drivers/clocksource/hyperv_timer.c | 15 +-
drivers/hv/hv_common.c | 4 +
drivers/hv/vmbus_drv.c | 153 ++++++++++++++----
9 files changed, 193 insertions(+), 40 deletions(-)
rename Documentation/devicetree/bindings/{virtio => hypervisor}/mmio.yaml (95%)
create mode 100644 Documentation/devicetree/bindings/hypervisor/msft,vmbus.yaml
rename Documentation/devicetree/bindings/{virtio => hypervisor}/pci-iommu.yaml (98%)
rename Documentation/devicetree/bindings/{virtio => hypervisor}/virtio-device.yaml (93%)
--
2.25.1
next reply other threads:[~2023-01-31 18:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:10 Saurabh Sengar [this message]
2023-01-31 18:10 ` [PATCH v2 1/6] drivers/clocksource/hyper-v: non ACPI support in hyperv clock Saurabh Sengar
2023-01-31 18:10 ` [PATCH v2 2/6] Drivers: hv: allow non ACPI compilation for hv_is_hibernation_supported Saurabh Sengar
2023-02-01 17:47 ` Michael Kelley (LINUX)
2023-02-02 14:48 ` Saurabh Singh Sengar
2023-02-02 15:33 ` Michael Kelley (LINUX)
2023-01-31 18:10 ` [PATCH v2 3/6] Drivers: hv: vmbus: Convert acpi_device to platform_device Saurabh Sengar
2023-02-01 18:32 ` Michael Kelley (LINUX)
2023-02-02 15:27 ` Saurabh Singh Sengar
2023-02-03 5:32 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 4/6] dt-bindings: hypervisor: Rename virtio to hypervisor Saurabh Sengar
2023-01-31 19:57 ` Rob Herring
2023-02-01 5:36 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 5/6] dt-bindings: hypervisor: Add dt-bindings for VMBus Saurabh Sengar
2023-01-31 18:51 ` Krzysztof Kozlowski
2023-02-01 1:39 ` Saurabh Singh Sengar
2023-01-31 18:54 ` Krzysztof Kozlowski
2023-02-01 1:57 ` Saurabh Singh Sengar
2023-02-01 7:23 ` Krzysztof Kozlowski
2023-02-01 8:05 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 6/6] Driver: VMBus: Add device tree support Saurabh Sengar
2023-01-31 20:12 ` Rob Herring
2023-02-01 16:51 ` Saurabh Singh Sengar
2023-02-01 17:46 ` Rob Herring
2023-02-01 18:31 ` Saurabh Singh Sengar
2023-02-03 17:36 ` Saurabh Singh Sengar
2023-02-07 17:38 ` Rob Herring
2023-02-08 2:30 ` Saurabh Singh Sengar
2023-01-31 20:27 ` [PATCH v2 0/6] Device tree support for Hyper-V VMBus driver Rob Herring
2023-02-01 2:04 ` Saurabh Singh Sengar
2023-02-01 14:51 ` Rob Herring
2023-02-01 16:34 ` Saurabh Singh Sengar
2023-02-01 17:15 ` Krzysztof Kozlowski
2023-02-06 17:40 ` Saurabh Singh Sengar
2023-02-07 17:53 ` Rob Herring
2023-02-08 2:44 ` Saurabh Singh Sengar
2023-02-07 18:37 ` Sudeep Holla
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=1675188609-20913-1-git-send-email-ssengar@linux.microsoft.com \
--to=ssengar@linux.microsoft.com \
--cc=daniel.lezcano@linaro.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=robh+dt@kernel.org \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).