All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elliot Berman <quic_eberman@quicinc.com>
To: Alex Elder <elder@linaro.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Elliot Berman <quic_eberman@quicinc.com>,
	Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Murali Nalajala <quic_mnalajal@quicinc.com>,
	Trilok Soni <quic_tsoni@quicinc.com>,
	Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>,
	Carl van Schaik <quic_cvanscha@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	"Konrad Dybcio" <konrad.dybcio@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Will Deacon <will@kernel.org>, "Andy Gross" <agross@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	"Rob Herring" <robh@kernel.org>
Subject: [PATCH v12 02/25] dt-bindings: Add binding for gunyah hypervisor
Date: Mon, 24 Apr 2023 16:15:35 -0700	[thread overview]
Message-ID: <20230424231558.70911-3-quic_eberman@quicinc.com> (raw)
In-Reply-To: <20230424231558.70911-1-quic_eberman@quicinc.com>

When Linux is booted as a guest under the Gunyah hypervisor, the Gunyah
Resource Manager applies a devicetree overlay describing the virtual
platform configuration of the guest VM, such as the message queue
capability IDs for communicating with the Resource Manager. This
information is not otherwise discoverable by a VM: the Gunyah hypervisor
core does not provide a direct interface to discover capability IDs nor
a way to communicate with RM without having already known the
corresponding message queue capability ID. Add the DT bindings that
Gunyah adheres for the hypervisor node and message queues.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Elliot Berman <quic_eberman@quicinc.com>
---
 .../bindings/firmware/gunyah-hypervisor.yaml  | 82 +++++++++++++++++++
 1 file changed, 82 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml

diff --git a/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml b/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml
new file mode 100644
index 000000000000..3fc0b043ac3c
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml
@@ -0,0 +1,82 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/firmware/gunyah-hypervisor.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Gunyah Hypervisor
+
+maintainers:
+  - Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>
+  - Elliot Berman <quic_eberman@quicinc.com>
+
+description: |+
+  Gunyah virtual machines use this information to determine the capability IDs
+  of the message queues used to communicate with the Gunyah Resource Manager.
+  See also: https://github.com/quic/gunyah-resource-manager/blob/develop/src/vm_creation/dto_construct.c
+
+properties:
+  compatible:
+    const: gunyah-hypervisor
+
+  "#address-cells":
+    description: Number of cells needed to represent 64-bit capability IDs.
+    const: 2
+
+  "#size-cells":
+    description: must be 0, because capability IDs are not memory address
+                  ranges and do not have a size.
+    const: 0
+
+patternProperties:
+  "^gunyah-resource-mgr(@.*)?":
+    type: object
+    description:
+      Resource Manager node which is required to communicate to Resource
+      Manager VM using Gunyah Message Queues.
+
+    properties:
+      compatible:
+        const: gunyah-resource-manager
+
+      reg:
+        items:
+          - description: Gunyah capability ID of the TX message queue
+          - description: Gunyah capability ID of the RX message queue
+
+      interrupts:
+        items:
+          - description: Interrupt for the TX message queue
+          - description: Interrupt for the RX message queue
+
+    additionalProperties: false
+
+    required:
+      - compatible
+      - reg
+      - interrupts
+
+additionalProperties: false
+
+required:
+  - compatible
+  - "#address-cells"
+  - "#size-cells"
+
+examples:
+  - |
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+
+    hypervisor {
+        #address-cells = <2>;
+        #size-cells = <0>;
+        compatible = "gunyah-hypervisor";
+
+        gunyah-resource-mgr@0 {
+            compatible = "gunyah-resource-manager";
+            interrupts = <GIC_SPI 3 IRQ_TYPE_EDGE_RISING>, /* TX full IRQ */
+                         <GIC_SPI 4 IRQ_TYPE_EDGE_RISING>; /* RX empty IRQ */
+            reg = <0x00000000 0x00000000>, <0x00000000 0x00000001>;
+                  /* TX, RX cap ids */
+        };
+    };
-- 
2.40.0


WARNING: multiple messages have this Message-ID (diff)
From: Elliot Berman <quic_eberman@quicinc.com>
To: Alex Elder <elder@linaro.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Elliot Berman <quic_eberman@quicinc.com>,
	Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Murali Nalajala <quic_mnalajal@quicinc.com>,
	Trilok Soni <quic_tsoni@quicinc.com>,
	Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>,
	Carl van Schaik <quic_cvanscha@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	"Konrad Dybcio" <konrad.dybcio@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Will Deacon <will@kernel.org>, "Andy Gross" <agross@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	"Rob Herring" <robh@kernel.org>
Subject: [PATCH v12 02/25] dt-bindings: Add binding for gunyah hypervisor
Date: Mon, 24 Apr 2023 16:15:35 -0700	[thread overview]
Message-ID: <20230424231558.70911-3-quic_eberman@quicinc.com> (raw)
In-Reply-To: <20230424231558.70911-1-quic_eberman@quicinc.com>

When Linux is booted as a guest under the Gunyah hypervisor, the Gunyah
Resource Manager applies a devicetree overlay describing the virtual
platform configuration of the guest VM, such as the message queue
capability IDs for communicating with the Resource Manager. This
information is not otherwise discoverable by a VM: the Gunyah hypervisor
core does not provide a direct interface to discover capability IDs nor
a way to communicate with RM without having already known the
corresponding message queue capability ID. Add the DT bindings that
Gunyah adheres for the hypervisor node and message queues.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Elliot Berman <quic_eberman@quicinc.com>
---
 .../bindings/firmware/gunyah-hypervisor.yaml  | 82 +++++++++++++++++++
 1 file changed, 82 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml

diff --git a/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml b/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml
new file mode 100644
index 000000000000..3fc0b043ac3c
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml
@@ -0,0 +1,82 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/firmware/gunyah-hypervisor.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Gunyah Hypervisor
+
+maintainers:
+  - Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>
+  - Elliot Berman <quic_eberman@quicinc.com>
+
+description: |+
+  Gunyah virtual machines use this information to determine the capability IDs
+  of the message queues used to communicate with the Gunyah Resource Manager.
+  See also: https://github.com/quic/gunyah-resource-manager/blob/develop/src/vm_creation/dto_construct.c
+
+properties:
+  compatible:
+    const: gunyah-hypervisor
+
+  "#address-cells":
+    description: Number of cells needed to represent 64-bit capability IDs.
+    const: 2
+
+  "#size-cells":
+    description: must be 0, because capability IDs are not memory address
+                  ranges and do not have a size.
+    const: 0
+
+patternProperties:
+  "^gunyah-resource-mgr(@.*)?":
+    type: object
+    description:
+      Resource Manager node which is required to communicate to Resource
+      Manager VM using Gunyah Message Queues.
+
+    properties:
+      compatible:
+        const: gunyah-resource-manager
+
+      reg:
+        items:
+          - description: Gunyah capability ID of the TX message queue
+          - description: Gunyah capability ID of the RX message queue
+
+      interrupts:
+        items:
+          - description: Interrupt for the TX message queue
+          - description: Interrupt for the RX message queue
+
+    additionalProperties: false
+
+    required:
+      - compatible
+      - reg
+      - interrupts
+
+additionalProperties: false
+
+required:
+  - compatible
+  - "#address-cells"
+  - "#size-cells"
+
+examples:
+  - |
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+
+    hypervisor {
+        #address-cells = <2>;
+        #size-cells = <0>;
+        compatible = "gunyah-hypervisor";
+
+        gunyah-resource-mgr@0 {
+            compatible = "gunyah-resource-manager";
+            interrupts = <GIC_SPI 3 IRQ_TYPE_EDGE_RISING>, /* TX full IRQ */
+                         <GIC_SPI 4 IRQ_TYPE_EDGE_RISING>; /* RX empty IRQ */
+            reg = <0x00000000 0x00000000>, <0x00000000 0x00000001>;
+                  /* TX, RX cap ids */
+        };
+    };
-- 
2.40.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-04-24 23:16 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 23:15 [PATCH v12 00/25] Drivers for Gunyah hypervisor Elliot Berman
2023-04-24 23:15 ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 01/25] docs: gunyah: Introduce Gunyah Hypervisor Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` Elliot Berman [this message]
2023-04-24 23:15   ` [PATCH v12 02/25] dt-bindings: Add binding for gunyah hypervisor Elliot Berman
2023-04-24 23:15 ` [PATCH v12 03/25] gunyah: Common types and error codes for Gunyah hypercalls Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 04/25] virt: gunyah: Add hypercalls to identify Gunyah Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 05/25] virt: gunyah: msgq: Add hypercalls to send and receive messages Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 06/25] mailbox: Add Gunyah message queue mailbox Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-05-04  6:21   ` Jassi Brar
2023-05-04  6:21     ` Jassi Brar
2023-05-09 20:52     ` Elliot Berman
2023-05-09 22:52       ` Jassi Brar
2023-04-24 23:15 ` [PATCH v12 07/25] gunyah: rsc_mgr: Add resource manager RPC core Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 08/25] gunyah: rsc_mgr: Add VM lifecycle RPC Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 09/25] gunyah: vm_mgr: Introduce basic VM Manager Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 10/25] gunyah: rsc_mgr: Add RPC for sharing memory Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 11/25] gunyah: vm_mgr: Add/remove user memory regions Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 12/25] gunyah: vm_mgr: Add ioctls to support basic non-proxy VM boot Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 13/25] samples: Add sample userspace Gunyah VM Manager Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 14/25] gunyah: rsc_mgr: Add platform ops on mem_lend/mem_reclaim Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 15/25] firmware: qcom_scm: Register Gunyah platform ops Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 16/25] docs: gunyah: Document Gunyah VM Manager Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 17/25] virt: gunyah: Translate gh_rm_hyp_resource into gunyah_resource Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 18/25] gunyah: vm_mgr: Add framework for VM Functions Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 19/25] virt: gunyah: Add resource tickets Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 20/25] virt: gunyah: Add IO handlers Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 21/25] virt: gunyah: Add proxy-scheduled vCPUs Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 22/25] virt: gunyah: Add hypercalls for sending doorbell Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 23/25] virt: gunyah: Add irqfd interface Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 24/25] virt: gunyah: Add ioeventfd Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-24 23:15 ` [PATCH v12 25/25] MAINTAINERS: Add Gunyah hypervisor drivers section Elliot Berman
2023-04-24 23:15   ` Elliot Berman
2023-04-25 16:33 ` [PATCH v12 00/25] Drivers for Gunyah hypervisor Elliot Berman
2023-04-25 16:33   ` Elliot Berman
2023-05-24 14:57 ` Alex Bennée
2023-05-24 14:57   ` Alex Bennée

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=20230424231558.70911-3-quic_eberman@quicinc.com \
    --to=quic_eberman@quicinc.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bagasdotme@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=elder@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_cvanscha@quicinc.com \
    --cc=quic_mnalajal@quicinc.com \
    --cc=quic_pheragu@quicinc.com \
    --cc=quic_svaddagi@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.