From: joaopeixoto@osyx.tech
To: linux-kernel@vger.kernel.org
Cc: ajd@linux.ibm.com, alex@ghiti.fr, aou@eecs.berkeley.edu,
bagasdotme@gmail.com, catalin.marinas@arm.com,
conor+dt@kernel.org, corbet@lwn.net, dan.j.williams@intel.com,
davidmcerdeira@osyx.tech, devicetree@vger.kernel.org,
dev@kael-k.io, gregkh@linuxfoundation.org, haren@linux.ibm.com,
heiko@sntech.de, joaopeixoto@osyx.tech, jose@osyx.tech,
kever.yang@rock-chips.com, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-riscv@lists.infradead.org, maddy@linux.ibm.com,
mani@kernel.org, nathan@kernel.org, neil.armstrong@linaro.org,
palmer@dabbelt.com, pjw@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, robh@kernel.org,
will@kernel.org
Subject: [PATCH 3/6] dt-bindings: Add Bao I/O dispatcher driver binding
Date: Wed, 7 Jan 2026 16:28:26 +0000 [thread overview]
Message-ID: <20260107162829.416885-4-joaopeixoto@osyx.tech> (raw)
In-Reply-To: <20260107162829.416885-1-joaopeixoto@osyx.tech>
From: João Peixoto <joaopeixoto@osyx.tech>
This patch introduces a device tree binding for the Bao I/O Dispatcher,
a device used in backend VMs running virtualized devices (e.g., VirtIO).
Signed-off-by: João Peixoto <joaopeixoto@osyx.tech>
---
.../bindings/bao/bao,io-dispatcher.yaml | 75 +++++++++++++++++++
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/bao/bao,io-dispatcher.yaml
diff --git a/Documentation/devicetree/bindings/bao/bao,io-dispatcher.yaml b/Documentation/devicetree/bindings/bao/bao,io-dispatcher.yaml
new file mode 100644
index 000000000000..8ca450e4b9d5
--- /dev/null
+++ b/Documentation/devicetree/bindings/bao/bao,io-dispatcher.yaml
@@ -0,0 +1,75 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bao/bao,io-dispatcher.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Bao I/O Dispatcher Device
+
+maintainers:
+ - João Peixoto <joaopeixoto@osyx.tech>
+ - José Martins <jose@osyx.tech>
+ - David Cerdeira <davidmcerdeira@osyx.tech>
+
+description: |
+ I/O Dispatcher device for Bao hypervisor guests that run virtualized
+ devices (e.g., VirtIO).
+
+ This device is only required in backend VMs, which are responsible for
+ performing the actual I/O operations on physical hardware. Frontend
+ VMs, which only consume I/O services, do not require this device.
+
+ The I/O Dispatcher provides access to one or more backend devices.
+ Each backend device is associated with a contiguous shared-memory
+ region used to exchange I/O buffers with the respective frontend
+ driver, and an interrupt used by the Bao hypervisor to notify the
+ backend VM of pending I/O requests.
+
+properties:
+ compatible:
+ const: bao,io-dispatcher
+
+ reg:
+ description: |
+ Contiguous memory-mapped regions for each VirtIO backend device
+ managed by the I/O Dispatcher.
+
+ Each region is used to exchange I/O buffers between the backend
+ and frontend devices. A single region corresponds to one
+ backend device.
+ minItems: 1
+ maxItems: 64
+
+ interrupts:
+ description: |
+ Interrupts associated with the VirtIO backend devices.
+
+ Each interrupt corresponds to a backend device and is used
+ by the Bao hypervisor to notify the backend VM of pending
+ I/O requests from the associated frontend driver.
+ minItems: 1
+ maxItems: 64
+
+required:
+ - compatible
+ - reg
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ bao-io-dispatcher@50000000 {
+ compatible = "bao,io-dispatcher";
+ reg = <0x0 0x50000000 0x0 0x01000000
+ 0x0 0x51000000 0x0 0x01000000
+ 0x0 0x52000000 0x0 0x01000000
+ 0x0 0x53000000 0x0 0x01000000
+ 0x0 0x54000000 0x0 0x01000000>;
+ interrupts = <0x0 0x08 0x1
+ 0x0 0x09 0x1
+ 0x0 0x0a 0x1
+ 0x0 0x0b 0x1
+ 0x0 0x0c 0x1>;
+ interrupt-parent = <&gic>;
+ };
--
2.43.0
next prev parent reply other threads:[~2026-01-07 16:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 13:52 [PATCH 0/5] virt: Add Bao hypervisor IPC and I/O dispatcher drivers joaopeixoto
2025-12-24 13:52 ` [PATCH 1/5] dt-bindings: Add Bao IPC shared memory driver binding joaopeixoto
2025-12-24 16:18 ` Rob Herring (Arm)
2025-12-25 8:57 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 2/5] virt: add Bao IPC shared memory driver joaopeixoto
2025-12-24 15:53 ` Greg KH
2025-12-24 15:54 ` Greg KH
2025-12-25 9:02 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 3/5] dt-bindings: Add Bao I/O dispatcher driver binding joaopeixoto
2025-12-24 16:18 ` Rob Herring (Arm)
2025-12-25 8:58 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 5/5] MAINTAINERS: Add entries for Bao hypervisor drivers, headers, and DT bindings joaopeixoto
2025-12-25 8:52 ` Krzysztof Kozlowski
2025-12-25 8:51 ` [PATCH 0/5] virt: Add Bao hypervisor IPC and I/O dispatcher drivers Krzysztof Kozlowski
[not found] ` <20251224135217.25350-5-joaopeixoto@osyx.tech>
2025-12-25 9:12 ` [PATCH 4/5] virt: add Bao I/O dispatcher driver Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH v2 0/6] virt: Add Bao hypervisor IPC and I/O dispatcher drivers joaopeixoto
2026-01-07 16:28 ` [PATCH 1/6] dt-bindings: Add Bao IPC shared memory driver binding joaopeixoto
2026-01-07 16:46 ` Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH 2/6] virt: bao: Add Bao IPC shared memory driver joaopeixoto
2026-01-07 18:54 ` Randy Dunlap
2026-01-14 20:37 ` Andrew Jones
2026-01-07 16:28 ` joaopeixoto [this message]
2026-01-07 16:47 ` [PATCH 3/6] dt-bindings: Add Bao I/O dispatcher driver binding Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH 4/6] virt: bao: Add Bao I/O dispatcher driver joaopeixoto
2026-01-14 20:32 ` Andrew Jones
2026-01-07 16:28 ` [PATCH 5/6] virt: bao: Move BAO_IPCSHMEM_HYPERCALL_ID to common header joaopeixoto
2026-01-07 19:36 ` Greg KH
2026-01-14 20:34 ` Andrew Jones
2026-01-07 16:28 ` [PATCH 6/6] MAINTAINERS: Add entries for Bao hypervisor drivers, headers, and DT bindings joaopeixoto
2026-01-07 19:37 ` [PATCH v2 0/6] virt: Add Bao hypervisor IPC and I/O dispatcher drivers Greg KH
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=20260107162829.416885-4-joaopeixoto@osyx.tech \
--to=joaopeixoto@osyx.tech \
--cc=ajd@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=davidmcerdeira@osyx.tech \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haren@linux.ibm.com \
--cc=heiko@sntech.de \
--cc=jose@osyx.tech \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maddy@linux.ibm.com \
--cc=mani@kernel.org \
--cc=nathan@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=will@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