From: Rob Herring <robh@kernel.org>
To: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, ycliang@andestech.com,
prabhakar.mahadev-lad.rj@bp.renesas.com, peterlin@andestech.com,
samuel.holland@sifive.com, conor.dooley@microchip.com,
alexghiti@rivosinc.com, ruanjinjie@huawei.com,
takakura@valinux.co.jp, conor+dt@kernel.org,
jassisinghbrar@gmail.com, krzk+dt@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: mailbox: add binding for Microchip IPC mailbox controller
Date: Tue, 19 Nov 2024 08:12:36 -0600 [thread overview]
Message-ID: <20241119141236.GA1099946-robh@kernel.org> (raw)
In-Reply-To: <20241105183513.1358736-4-valentina.fernandezalanis@microchip.com>
On Tue, Nov 05, 2024 at 06:35:12PM +0000, Valentina Fernandez wrote:
> Add a dt-binding for the Microchip Inter-Processor Communication (IPC)
> mailbox controller.
>
> Signed-off-by: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
> ---
> .../bindings/mailbox/microchip,sbi-ipc.yaml | 117 ++++++++++++++++++
> 1 file changed, 117 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/microchip,sbi-ipc.yaml
>
> diff --git a/Documentation/devicetree/bindings/mailbox/microchip,sbi-ipc.yaml b/Documentation/devicetree/bindings/mailbox/microchip,sbi-ipc.yaml
> new file mode 100644
> index 000000000000..9e67c09e4bea
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/microchip,sbi-ipc.yaml
> @@ -0,0 +1,117 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mailbox/microchip,sbi-ipc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip Inter-processor communication (IPC) mailbox controller
> +
> +maintainers:
> + - Valentina Fernandez <valentina.fernandezalanis@microchip.com>
> +
> +description:
> + The Microchip Inter-processor Communication (IPC) facilitates
> + message passing between processors using an interrupt signaling
> + mechanism.
> +
> +properties:
> + compatible:
> + oneOf:
> + - description:
> + Intended for use by software running in supervisor privileged
> + mode (s-mode). This SBI interface is compatible with the Mi-V
> + Inter-hart Communication (IHC) IP.
> + items:
> + - const: microchip,sbi-ipc
> +
> + - description:
> + SoC-specific compatible, intended for use by the SBI
> + implementation in machine mode (m-mode).
> + items:
> + - const: microchip,miv-ihc-rtl-v2
Usually SoC specific compatibles don't have version numbers. And all
hardware in an SoC is RTL at some point. So microchip,miv-ihc should be
sufficient if 'miv' is an SoC.
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 1
> + maxItems: 5
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 5
> + items:
> + pattern: "^hart-[0-5]+$"
> +
> + "#mbox-cells":
> + description: >
> + For the SBI "device", the cell represents the global "logical" channel IDs.
> + The meaning of channel IDs are platform firmware dependent.
> +
> + For the SoC-specific compatible string, the cell represents the physical
> + channel and does not vary based on the platform firmware.
> + const: 1
> +
> + microchip,ihc-chan-disabled-mask:
> + description: >
> + Represents the enable/disable state of the bi-directional IHC
> + channels within the MIV-IHC IP configuration.
> +
> + The mask is a 16-bit value, but only the first 15 bits are utilized.
> + Each of the bits corresponds to one of the 15 IHC channels.
That can be expressed as a constraint:
maximum: 0x7fff
Then you can drop this paragraph.
> +
> + A bit set to '1' indicates that the corresponding channel is disabled,
> + and any read or write operations to that channel will return zero.
> +
> + A bit set to '0' indicates that the corresponding channel is enabled
> + and will be accessible through its dedicated address range registers.
> +
> + The remaining bit of the 16-bit mask is reserved and should be ignored.
And drop this one.
> +
> + The actual enable/disable state of each channel is determined by the
> + IP block’s configuration.
> + $ref: /schemas/types.yaml#/definitions/uint16
> + default: 0
> +
> +required:
> + - compatible
> + - interrupts
> + - interrupt-names
> + - "#mbox-cells"
> +
> +additionalProperties: false
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: microchip,sbi-ipc
> + then:
> + properties:
> + reg: false
> + microchip,ihc-chan-disabled-mask: false
> + else:
> + required:
> + - reg
> + - microchip,ihc-chan-disabled-mask
> +
> +examples:
> + - |
> + mailbox {
> + compatible = "microchip,sbi-ipc";
> + interrupt-parent = <&plic>;
> + interrupts = <180>, <179>, <178>;
> + interrupt-names = "hart-1", "hart-2", "hart-3";
> + #mbox-cells = <1>;
> + };
> + - |
> + mailbox@50000000 {
> + compatible = "microchip,miv-ihc-rtl-v2";
> + microchip,ihc-chan-disabled-mask = /bits/ 16 <0>;
> + reg = <0x50000000 0x1C000>;
> + interrupt-parent = <&plic>;
> + interrupts = <180>, <179>, <178>;
> + interrupt-names = "hart-1", "hart-2", "hart-3";
> + #mbox-cells = <1>;
> + };
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-11-19 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:35 [PATCH v3 0/4] Add Microchip IPC mailbox Valentina Fernandez
2024-11-05 18:35 ` [PATCH v3 1/4] riscv: sbi: vendorid_list: Add Microchip Technology to the vendor list Valentina Fernandez
2024-11-05 18:35 ` [PATCH v3 2/4] riscv: export __cpuid_to_hartid_map Valentina Fernandez
2024-11-11 21:52 ` Rob Herring
2024-11-19 20:32 ` Atish Patra
2024-11-05 18:35 ` [PATCH v3 3/4] dt-bindings: mailbox: add binding for Microchip IPC mailbox controller Valentina Fernandez
2024-11-19 14:12 ` Rob Herring [this message]
2024-11-05 18:35 ` [PATCH v3 4/4] mailbox: add Microchip IPC support Valentina Fernandez
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=20241119141236.GA1099946-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=ruanjinjie@huawei.com \
--cc=samuel.holland@sifive.com \
--cc=takakura@valinux.co.jp \
--cc=valentina.fernandezalanis@microchip.com \
--cc=ycliang@andestech.com \
/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