diff mbox series

dt-bindings: mailbox: Convert omap-mailbox.txt binding to YAML

Message ID 20210518172022.10562-1-s-anna@ti.com (mailing list archive)
State New
Headers show
Series dt-bindings: mailbox: Convert omap-mailbox.txt binding to YAML | expand

Commit Message

Suman Anna May 18, 2021, 5:20 p.m. UTC
Convert the current OMAP Mailbox binding from text format to YAML
format/DT schema, and delete the legacy text binding file.

The new YAML binding conversion is an updated version compared to
the original. The descriptions for certain properties have been
improved to provide more clarity. Constraints are added to the
properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
The 'ti,hwmods' is a legacy property and is retained only to reflect
the existing usage on some older OMAP2 and OMAP3 platforms.

All the existing examples have also been updated to reflect the
latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
and interrupts value updated for AM65x SoCs).

Signed-off-by: Suman Anna <s-anna@ti.com>
---
Hi,

This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
nodes with the latest kernel. There are few left-over warnings when just
this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
series for OMAP2+ SoCs. The dts patches can be picked up independently
of this patch.

regards
Suman

[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210514212016.3153-1-s-anna@ti.com/

 .../bindings/mailbox/omap-mailbox.txt         | 184 -----------
 .../bindings/mailbox/ti,omap-mailbox.yaml     | 309 ++++++++++++++++++
 2 files changed, 309 insertions(+), 184 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
 create mode 100644 Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml

Comments

Suman Anna May 19, 2021, 3:14 p.m. UTC | #1
On 5/18/21 12:20 PM, Suman Anna wrote:
> Convert the current OMAP Mailbox binding from text format to YAML
> format/DT schema, and delete the legacy text binding file.
> 
> The new YAML binding conversion is an updated version compared to
> the original. The descriptions for certain properties have been
> improved to provide more clarity. Constraints are added to the
> properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> The 'ti,hwmods' is a legacy property and is retained only to reflect
> the existing usage on some older OMAP2 and OMAP3 platforms.
> 
> All the existing examples have also been updated to reflect the
> latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> and interrupts value updated for AM65x SoCs).
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> Hi,
> 
> This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> nodes with the latest kernel. There are few left-over warnings when just
> this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> series for OMAP2+ SoCs. The dts patches can be picked up independently
> of this patch.

FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
series [2].

> 
> regards
> Suman
> 
> [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210514212016.3153-1-s-anna@ti.com/

[2] https://patchwork.kernel.org/project/linux-omap/list/?series=484489

[snip]

regards
Suman
Rob Herring May 20, 2021, 12:08 a.m. UTC | #2
On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
> On 5/18/21 12:20 PM, Suman Anna wrote:
> > Convert the current OMAP Mailbox binding from text format to YAML
> > format/DT schema, and delete the legacy text binding file.
> > 
> > The new YAML binding conversion is an updated version compared to
> > the original. The descriptions for certain properties have been
> > improved to provide more clarity. Constraints are added to the
> > properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> > The 'ti,hwmods' is a legacy property and is retained only to reflect
> > the existing usage on some older OMAP2 and OMAP3 platforms.
> > 
> > All the existing examples have also been updated to reflect the
> > latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> > and interrupts value updated for AM65x SoCs).
> > 
> > Signed-off-by: Suman Anna <s-anna@ti.com>
> > ---
> > Hi,
> > 
> > This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> > nodes with the latest kernel. There are few left-over warnings when just
> > this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> > fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> > series for OMAP2+ SoCs. The dts patches can be picked up independently
> > of this patch.
> 
> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
> series [2].

Nice, though it is a moving target. :) Is that still true with the 
undocumented compatible checks that's been added? 

Rob
Rob Herring May 20, 2021, 12:14 a.m. UTC | #3
On Tue, May 18, 2021 at 12:20:22PM -0500, Suman Anna wrote:
> Convert the current OMAP Mailbox binding from text format to YAML
> format/DT schema, and delete the legacy text binding file.
> 
> The new YAML binding conversion is an updated version compared to
> the original. The descriptions for certain properties have been
> improved to provide more clarity. Constraints are added to the
> properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> The 'ti,hwmods' is a legacy property and is retained only to reflect
> the existing usage on some older OMAP2 and OMAP3 platforms.
> 
> All the existing examples have also been updated to reflect the
> latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> and interrupts value updated for AM65x SoCs).
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> Hi,
> 
> This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> nodes with the latest kernel. There are few left-over warnings when just
> this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> series for OMAP2+ SoCs. The dts patches can be picked up independently
> of this patch.
> 
> regards
> Suman
> 
> [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210514212016.3153-1-s-anna@ti.com/
> 
>  .../bindings/mailbox/omap-mailbox.txt         | 184 -----------
>  .../bindings/mailbox/ti,omap-mailbox.yaml     | 309 ++++++++++++++++++
>  2 files changed, 309 insertions(+), 184 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
>  create mode 100644 Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml


> +++ b/Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml
> @@ -0,0 +1,309 @@
> +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI OMAP2+ and K3 Mailbox devices
> +
> +maintainers:
> +  - Suman Anna <s-anna@ti.com>
> +
> +description: |
> +  The OMAP Mailbox hardware facilitates communication between different
> +  processors using a queued mailbox interrupt mechanism. The IP block is
> +  external to the various processor subsystems and is connected on an
> +  interconnect bus. The communication is achieved through a set of registers
> +  for message storage and interrupt configuration registers.
> +
> +  Each mailbox IP block/cluster has a certain number of h/w fifo queues and
> +  output interrupt lines. An output interrupt line is routed to an interrupt
> +  controller within a processor subsystem, and there can be more than one line
> +  going to a specific processor's interrupt controller. The interrupt line
> +  connections are fixed for an instance and are dictated by the IP integration
> +  into the SoC (excluding the SoCs that have an Interrupt Crossbar or an
> +  Interrupt Router IP). Each interrupt line is programmable through a set of
> +  interrupt configuration registers, and have a rx and tx interrupt source per
> +  h/w fifo. Communication between different processors is achieved through the
> +  appropriate programming of the rx and tx interrupt sources on the appropriate
> +  interrupt lines.
> +
> +  The number of h/w fifo queues and interrupt lines dictate the usable
> +  registers. All the current OMAP SoCs except for the newest DRA7xx SoC has a
> +  single IP instance. DRA7xx has multiple instances with different number of
> +  h/w fifo queues and interrupt lines between different instances. The interrupt
> +  lines can also be routed to different processor sub-systems on DRA7xx as they
> +  are routed through the Crossbar, a kind of interrupt router/multiplexer. The
> +  K3 AM65x, J721E and J7200 SoCs has each of these instances form a cluster and
> +  combine multiple clusters into a single IP block present within the Main
> +  NavSS. The interrupt lines from all these clusters are multiplexed and routed
> +  to different processor subsystems over a limited number of common interrupt
> +  output lines of an Interrupt Router. The AM64x SoCS also uses a single IP
> +  block comprising of multiple clusters, but the number of clusters are
> +  smaller, and the interrupt output lines are connected directly to various
> +  processors.
> +
> +  Mailbox Controller Nodes
> +  =========================
> +  A Mailbox device node is used to represent a Mailbox IP instance/cluster
> +  within a SoC. The sub-mailboxes (actual communication channels) are
> +  represented as child nodes of this parent node.
> +
> +  Mailbox Users
> +  ==============
> +  A device needing to communicate with a target processor device should specify
> +  them using the common mailbox binding properties, "mboxes" and the optional
> +  "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
> +  for details). Each value of the mboxes property should contain a phandle to
> +  the mailbox controller device node and an args specifier that will be the
> +  phandle to the intended sub-mailbox child node to be used for communication.
> +  The equivalent "mbox-names" property value can be used to give a name to the
> +  communication channel to be used by the client user.
> +
> +definitions:

$defs is preferred (as that's what newer json-schema spec versions 
defined).

> +  omap-mbox-descriptor:
> +    $ref: /schemas/types.yaml#/definitions/uint32-array
> +    description: |
> +      The omap-mbox-descriptor is made of up of 3 cells and represents a single
> +      uni-directional communication channel. A typical sub-mailbox device uses
> +      two such channels - one for transmitting (Tx) and one for receiving (Rx).
> +    items:
> +      - description: |
> +          mailbox fifo id used either for transmitting on ti,mbox-tx channel or
> +          for receiving on ti,mbox-rx channel (fifo_id). This is the hardware
> +          fifo number within a mailbox cluster.
> +      - description: |
> +          irq identifier index number to use from the parent's interrupts data.
> +          Should be 0 for most of the cases, a positive index value is seen only
> +          on mailboxes that have multiple interrupt lines connected to the MPU
> +          processor (irq_id). This is an index number in the listed interrupts
> +          property in the DT nodes.
> +      - description: |
> +          mailbox user id for identifying the interrupt line associated with
> +          generating a tx/rx fifo interrupt (usr_id). This is the hardware
> +          user id number within a mailbox cluster.
> +
> +  omap-sub-mailbox:
> +    type: object
> +    description: |
> +      The omap-sub-mailbox is a child node within a Mailbox controller device
> +      node and represents the actual communication channel used to send and
> +      receive messages between the host processor and a remote processor. Each
> +      child node should have a unique node name across all the different mailbox
> +      device nodes.
> +
> +    properties:
> +      ti,mbox-tx:
> +        $ref: "#/definitions/omap-mbox-descriptor"
> +        description: sub-mailbox descriptor property defining a Tx fifo.
> +
> +      ti,mbox-rx:
> +        $ref: "#/definitions/omap-mbox-descriptor"
> +        description: sub-mailbox descriptor property defining a Rx fifo.
> +
> +      ti,mbox-send-noirq:
> +        type: boolean
> +        description: |

Drop '|' if formatting is not important.

> +          Quirk flag to allow the client user of this sub-mailbox to send
> +          messages without triggering a Tx ready interrupt, and to control
> +          the Tx ticker. Should be used only on sub-mailboxes used to
> +          communicate with WkupM3 remote processor on AM33xx/AM43xx SoCs.
> +
> +    required:
> +      - ti,mbox-tx
> +      - ti,mbox-rx
> +
> +properties:
> +  compatible:
> +    enum:
> +      - ti,omap2-mailbox # for OMAP2420, OMAP2430 SoCs
> +      - ti,omap3-mailbox # for OMAP3430, OMAP3630 SoCs
> +      - ti,omap4-mailbox # for OMAP44xx, OMAP54xx, AM33xx, AM43xx and DRA7xx SoCs
> +      - ti,am654-mailbox # for K3 AM65x, J721E and J7200 SoCs
> +      - ti,am64-mailbox  # for K3 AM64x SoCs
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    description: |
> +      Contains the interrupt information for the mailbox device. The format is
> +      dependent on which interrupt controller the Mailbox device uses. The
> +      number of interrupts listed will at most be the value specified in
> +      ti,mbox-num-users property, but is usually limited by the number of
> +      interrupts reaching the main processor. An interrupt-parent property
> +      is required on SoCs where the interrupt lines are connected through a
> +      Interrupt Router before reaching the main processor's GIC.
> +
> +  "#mbox-cells":
> +    const: 1
> +    description: |
> +      Common mailbox binding property to identify the number of cells required
> +      for the mailbox specifier in a consumer node. The specifier is a phandle
> +      to a omap-sub-mailbox device.

Can drop the first sentence.

> +
> +  ti,mbox-num-users:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: |
> +      Number of targets (processor devices) that the mailbox device can
> +      interrupt.
> +
> +  ti,mbox-num-fifos:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: Number of h/w fifo queues within the mailbox IP block.
> +
> +  ti,hwmods:
> +    $ref: /schemas/types.yaml#/definitions/string
> +    description: |
> +      Name of the hwmod associated with the mailbox. This should be defined
> +      in the mailbox node only if the node is not defined as a child node of
> +      a corresponding sysc interconnect node.
> +
> +      This property is only needed on some legacy OMAP SoCs which have not
> +      yet been converted to the ti,sysc interconnect hierarachy, but is
> +      otherwise considered obsolete.

deprecated: true

> +
> +patternProperties:
> +  "^mbox-[a-z0-9-]+$":
> +    $ref: "#/definitions/omap-sub-mailbox"
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - "#mbox-cells"
> +  - ti,mbox-num-users
> +  - ti,mbox-num-fifos
> +
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          enum:
> +            - ti,am654-mailbox
> +    then:
> +      required:
> +        - interrupt-parent
> +
> +  - if:
> +      properties:
> +        compatible:
> +          enum:
> +            - ti,am654-mailbox
> +            - ti,am64-mailbox
> +    then:
> +      properties:
> +        ti,mbox-num-users:
> +          const: 4
> +        ti,mbox-num-fifos:
> +          const: 16
> +        interrupts:
> +          minItems: 1
> +          maxItems: 4
> +
> +  - if:
> +      properties:
> +        compatible:
> +          enum:
> +            - ti,omap4-mailbox
> +    then:
> +      properties:
> +        ti,mbox-num-users:
> +          enum: [3, 4]
> +        ti,mbox-num-fifos:
> +          enum: [8, 12]
> +        interrupts:
> +          minItems: 1
> +          maxItems: 4
> +
> +  - if:
> +      properties:
> +        compatible:
> +          enum:
> +            - ti,omap3-mailbox
> +    then:
> +      properties:
> +        ti,mbox-num-users:
> +          const: 2
> +        ti,mbox-num-fifos:
> +          const: 2
> +        interrupts:
> +          minItems: 1
> +          maxItems: 1
> +
> +  - if:
> +      properties:
> +        compatible:
> +          enum:
> +            - ti,omap2-mailbox
> +    then:
> +      properties:
> +        ti,mbox-num-users:
> +          const: 4
> +        ti,mbox-num-fifos:
> +          const: 6
> +        interrupts:
> +          minItems: 1
> +          maxItems: 2
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    /* OMAP4 */
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +    mailbox: mailbox@4a0f4000 {
> +        compatible = "ti,omap4-mailbox";
> +        reg = <0x4a0f4000 0x200>;
> +        interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
> +        #mbox-cells = <1>;
> +        ti,mbox-num-users = <3>;
> +        ti,mbox-num-fifos = <8>;
> +
> +        mbox_ipu: mbox-ipu {
> +            ti,mbox-tx = <0 0 0>;
> +            ti,mbox-rx = <1 0 0>;
> +        };
> +        mbox_dsp: mbox-dsp {
> +            ti,mbox-tx = <3 0 0>;
> +            ti,mbox-rx = <2 0 0>;
> +        };
> +    };
> +
> +    dsp {
> +        mboxes = <&mailbox &mbox_dsp>;
> +    };
> +
> +  - |
> +    /* AM33xx */
> +    mailbox1: mailbox@480c8000 {
> +        compatible = "ti,omap4-mailbox";
> +        reg = <0x480c8000 0x200>;
> +        interrupts = <77>;
> +        #mbox-cells = <1>;
> +        ti,mbox-num-users = <4>;
> +        ti,mbox-num-fifos = <8>;
> +
> +        mbox_wkupm3: mbox-wkup-m3 {
> +            ti,mbox-tx = <0 0 0>;
> +            ti,mbox-rx = <0 0 3>;
> +            ti,mbox-send-noirq;
> +        };
> +    };
> +
> +  - |
> +    /* AM65x */
> +    mailbox0_cluster0: mailbox@31f80000 {
> +        compatible = "ti,am654-mailbox";
> +        reg = <0x31f80000 0x200>;
> +        #mbox-cells = <1>;
> +        ti,mbox-num-users = <4>;
> +        ti,mbox-num-fifos = <16>;
> +        interrupt-parent = <&intr_main_navss>;
> +        interrupts = <436>;
> +
> +        mbox_mcu_r5fss0_core0: mbox-mcu-r5fss0-core0 {
> +            ti,mbox-tx = <1 0 0>;
> +            ti,mbox-rx = <0 0 0>;
> +        };
> +    };
> -- 
> 2.30.1
>
Suman Anna May 20, 2021, 4:45 p.m. UTC | #4
On 5/19/21 7:08 PM, Rob Herring wrote:
> On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
>> On 5/18/21 12:20 PM, Suman Anna wrote:
>>> Convert the current OMAP Mailbox binding from text format to YAML
>>> format/DT schema, and delete the legacy text binding file.
>>>
>>> The new YAML binding conversion is an updated version compared to
>>> the original. The descriptions for certain properties have been
>>> improved to provide more clarity. Constraints are added to the
>>> properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
>>> The 'ti,hwmods' is a legacy property and is retained only to reflect
>>> the existing usage on some older OMAP2 and OMAP3 platforms.
>>>
>>> All the existing examples have also been updated to reflect the
>>> latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
>>> and interrupts value updated for AM65x SoCs).
>>>
>>> Signed-off-by: Suman Anna <s-anna@ti.com>
>>> ---
>>> Hi,
>>>
>>> This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
>>> nodes with the latest kernel. There are few left-over warnings when just
>>> this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
>>> fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
>>> series for OMAP2+ SoCs. The dts patches can be picked up independently
>>> of this patch.
>>
>> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
>> series [2].
> 
> Nice, though it is a moving target. :) Is that still true with the 
> undocumented compatible checks that's been added? 

[1] is acked, so will definitely get picked up for the next merge window. Should
hit next sometime in the next couple of days.

I didn't exactly understand your second comment, but no new compatibles were
added. The existing nodes are already in compliance with the constraints I added
(so that's strictly binding enforcements). These constraints are almost all on
legacy SoCs, so these do not pose any issues.

Most of the generated warnings stem from me adding a pattern for the child nodes
in the binding, and [2] is mostly just renaming these node names.

Tony,
Do you have/foresee any concerns with the patches in [2]?

regards
Suman

[1]
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210514212016.3153-1-s-anna@ti.com/
[2] https://patchwork.kernel.org/project/linux-omap/list/?series=484489
Rob Herring May 20, 2021, 7:21 p.m. UTC | #5
On Thu, May 20, 2021 at 11:45 AM Suman Anna <s-anna@ti.com> wrote:
>
> On 5/19/21 7:08 PM, Rob Herring wrote:
> > On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
> >> On 5/18/21 12:20 PM, Suman Anna wrote:
> >>> Convert the current OMAP Mailbox binding from text format to YAML
> >>> format/DT schema, and delete the legacy text binding file.
> >>>
> >>> The new YAML binding conversion is an updated version compared to
> >>> the original. The descriptions for certain properties have been
> >>> improved to provide more clarity. Constraints are added to the
> >>> properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> >>> The 'ti,hwmods' is a legacy property and is retained only to reflect
> >>> the existing usage on some older OMAP2 and OMAP3 platforms.
> >>>
> >>> All the existing examples have also been updated to reflect the
> >>> latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> >>> and interrupts value updated for AM65x SoCs).
> >>>
> >>> Signed-off-by: Suman Anna <s-anna@ti.com>
> >>> ---
> >>> Hi,
> >>>
> >>> This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> >>> nodes with the latest kernel. There are few left-over warnings when just
> >>> this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> >>> fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> >>> series for OMAP2+ SoCs. The dts patches can be picked up independently
> >>> of this patch.
> >>
> >> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
> >> series [2].
> >
> > Nice, though it is a moving target. :) Is that still true with the
> > undocumented compatible checks that's been added?
>
> [1] is acked, so will definitely get picked up for the next merge window. Should
> hit next sometime in the next couple of days.
>
> I didn't exactly understand your second comment, but no new compatibles were
> added. The existing nodes are already in compliance with the constraints I added
> (so that's strictly binding enforcements). These constraints are almost all on
> legacy SoCs, so these do not pose any issues.

When you say 'All the dtbs_check warnings', you mean *all* or just all
the mailbox ones. I read as the former, but I guess from the prior
paragraph and the links you are talking about, it's just mailbox
warnings.

Overall, this is what TI 32-bit warnings look like:

Processing (am3|am4|am5|dra|keystone|omap|compulab|logicpd|elpida|motorola-cpcap|twl|da|dm):
warnings: 60358
undocumented compat: 3195

This comes from my CI job[1]. The warnings aren't deduplicated, so 1
SoC warning expands to N board warnings. Only 3879 unique warnings. :)

The top warnings are:

arch/arm/boot/dts/(am3|am4|am5|dra|keystone|omap|compulab|logicpd|elpida|motorola-cpcap|twl|da|dm):60358:3879:3195
    253  segment@0: 'anyOf' conditional failed, one must be fixed:
    253  segment@0: $nodename:0: 'segment@0' does not match '^bus(@[0-9a-f]+)?$'
    140  segment@200000: 'anyOf' conditional failed, one must be fixed:
    140  segment@200000: $nodename:0: 'segment@200000' does not match
'^bus(@[0-9a-f]+)?$'
    128 0:0: /ocp/target-module@56000000: failed to match any schema
with compatible: ['ti,sysc-omap4', 'ti,sysc']
    128 0:0: /ocp/target-module@50000000: failed to match any schema
with compatible: ['ti,sysc-omap2', 'ti,sysc']
    128 0:0: /ocp/interconnect@48000000/segment@0/target-module@60000:
failed to match any schema with compatible: ['ti,sysc-omap2',
'ti,sysc']
    114 0:0: /ocp@68000000/target-module@49032000: failed to match any
schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
    114 0:0: /ocp@68000000/target-module@48320000: failed to match any
schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
    114 0:0: /ocp@68000000/target-module@48318000: failed to match any
schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
    114 0:0: /ocp@68000000/target-module@48304000: failed to match any
schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
    114 0:0: /ocp@68000000/target-module@480a0000: failed to match any
schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
    114 0:0: /ocp@68000000/target-module@48056000: failed to match any
schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
    114 0:0: /ocp@68000000/l4@48000000/scm@2000/scm_conf@270/pbias_regulator@2b0:
failed to match any schema with compatible: ['ti,pbias-omap3',
'ti,pbias-omap']
    114 0:0: /ocp@68000000/l4@48000000/scm@2000/pinmux@a00: failed to
match any schema with compatible: ['ti,omap3-padconf',
'pinctrl-single']
    114 0:0: /ocp@68000000/l4@48000000/scm@2000/pinmux@30: failed to
match any schema with compatible: ['ti,omap3-padconf',
'pinctrl-single']
    112 0:0: /opp-table: failed to match any schema with compatible:
['operating-points-v2-ti-cpu']
    111  segment@100000: 'anyOf' conditional failed, one must be fixed:
    111  segment@100000: $nodename:0: 'segment@100000' does not match
'^bus(@[0-9a-f]+)?$'
    108 0:0: /soc: failed to match any schema with compatible: ['ti,omap-infra']

Rob

[1] https://gitlab.com/robherring/linux-dt/-/jobs/1261951514
Suman Anna May 20, 2021, 8:07 p.m. UTC | #6
On 5/20/21 2:21 PM, Rob Herring wrote:
> On Thu, May 20, 2021 at 11:45 AM Suman Anna <s-anna@ti.com> wrote:
>>
>> On 5/19/21 7:08 PM, Rob Herring wrote:
>>> On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
>>>> On 5/18/21 12:20 PM, Suman Anna wrote:
>>>>> Convert the current OMAP Mailbox binding from text format to YAML
>>>>> format/DT schema, and delete the legacy text binding file.
>>>>>
>>>>> The new YAML binding conversion is an updated version compared to
>>>>> the original. The descriptions for certain properties have been
>>>>> improved to provide more clarity. Constraints are added to the
>>>>> properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
>>>>> The 'ti,hwmods' is a legacy property and is retained only to reflect
>>>>> the existing usage on some older OMAP2 and OMAP3 platforms.
>>>>>
>>>>> All the existing examples have also been updated to reflect the
>>>>> latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
>>>>> and interrupts value updated for AM65x SoCs).
>>>>>
>>>>> Signed-off-by: Suman Anna <s-anna@ti.com>
>>>>> ---
>>>>> Hi,
>>>>>
>>>>> This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
>>>>> nodes with the latest kernel. There are few left-over warnings when just
>>>>> this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
>>>>> fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
>>>>> series for OMAP2+ SoCs. The dts patches can be picked up independently
>>>>> of this patch.
>>>>
>>>> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
>>>> series [2].
>>>
>>> Nice, though it is a moving target. :) Is that still true with the
>>> undocumented compatible checks that's been added?
>>
>> [1] is acked, so will definitely get picked up for the next merge window. Should
>> hit next sometime in the next couple of days.
>>
>> I didn't exactly understand your second comment, but no new compatibles were
>> added. The existing nodes are already in compliance with the constraints I added
>> (so that's strictly binding enforcements). These constraints are almost all on
>> legacy SoCs, so these do not pose any issues.
> 
> When you say 'All the dtbs_check warnings', you mean *all* or just all
> the mailbox ones. I read as the former, but I guess from the prior
> paragraph and the links you are talking about, it's just mailbox
> warnings.

Yeah, sorry about the confusion. It is indeed just the mailbox ones, whatever is
showing up in the build log for this patch on the devicetree patchworks.

https://gitlab.com/robherring/linux-dt-review/-/jobs/1274246349/artifacts/file/build-dtbs-1480365.log

> 
> Overall, this is what TI 32-bit warnings look like:
> 
> Processing (am3|am4|am5|dra|keystone|omap|compulab|logicpd|elpida|motorola-cpcap|twl|da|dm):
> warnings: 60358
> undocumented compat: 3195

Yeah, we have many derivative boards on each of the SoC families.

> 
> This comes from my CI job[1]. The warnings aren't deduplicated, so 1
> SoC warning expands to N board warnings. Only 3879 unique warnings. :)
> 
> The top warnings are:
> 
> arch/arm/boot/dts/(am3|am4|am5|dra|keystone|omap|compulab|logicpd|elpida|motorola-cpcap|twl|da|dm):60358:3879:3195
>     253  segment@0: 'anyOf' conditional failed, one must be fixed:
>     253  segment@0: $nodename:0: 'segment@0' does not match '^bus(@[0-9a-f]+)?$'
>     140  segment@200000: 'anyOf' conditional failed, one must be fixed:
>     140  segment@200000: $nodename:0: 'segment@200000' does not match
> '^bus(@[0-9a-f]+)?$'
>     128 0:0: /ocp/target-module@56000000: failed to match any schema
> with compatible: ['ti,sysc-omap4', 'ti,sysc']
>     128 0:0: /ocp/target-module@50000000: failed to match any schema
> with compatible: ['ti,sysc-omap2', 'ti,sysc']
>     128 0:0: /ocp/interconnect@48000000/segment@0/target-module@60000:
> failed to match any schema with compatible: ['ti,sysc-omap2',
> 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@49032000: failed to match any
> schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@48320000: failed to match any
> schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@48318000: failed to match any
> schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@48304000: failed to match any
> schema with compatible: ['ti,sysc-omap2-timer', 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@480a0000: failed to match any
> schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
>     114 0:0: /ocp@68000000/target-module@48056000: failed to match any
> schema with compatible: ['ti,sysc-omap2', 'ti,sysc']
>     114 0:0: /ocp@68000000/l4@48000000/scm@2000/scm_conf@270/pbias_regulator@2b0:
> failed to match any schema with compatible: ['ti,pbias-omap3',
> 'ti,pbias-omap']
>     114 0:0: /ocp@68000000/l4@48000000/scm@2000/pinmux@a00: failed to
> match any schema with compatible: ['ti,omap3-padconf',
> 'pinctrl-single']
>     114 0:0: /ocp@68000000/l4@48000000/scm@2000/pinmux@30: failed to
> match any schema with compatible: ['ti,omap3-padconf',
> 'pinctrl-single']
>     112 0:0: /opp-table: failed to match any schema with compatible:
> ['operating-points-v2-ti-cpu']
>     111  segment@100000: 'anyOf' conditional failed, one must be fixed:
>     111  segment@100000: $nodename:0: 'segment@100000' does not match
> '^bus(@[0-9a-f]+)?$'
>     108 0:0: /soc: failed to match any schema with compatible: ['ti,omap-infra']

Tony,

Any chance you can add a 'ti-sysc' binding and address the 'segment' warnings
for 5.14? Those alone should bring the warning numbers down drastically.

regards
Suman

> 
> Rob
> 
> [1] https://gitlab.com/robherring/linux-dt/-/jobs/1261951514
>
Tony Lindgren May 21, 2021, 9:21 a.m. UTC | #7
* Suman Anna <s-anna@ti.com> [210520 16:45]:
> Tony,
> Do you have/foresee any concerns with the patches in [2]?

Looks OK to me, will be picking them up.

Regards,

Tony

> [2] https://patchwork.kernel.org/project/linux-omap/list/?series=484489
Tony Lindgren May 25, 2021, 6:44 a.m. UTC | #8
* Suman Anna <s-anna@ti.com> [210520 23:07]:
> Tony,
> 
> Any chance you can add a 'ti-sysc' binding and address the 'segment' warnings
> for 5.14? Those alone should bring the warning numbers down drastically.

Sure I'll do that. However, from what I recall there are still tons of dts
clock warnings left for the legacy clocks.

Regards,

Tony
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt b/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
deleted file mode 100644
index 12371f5c6cd9..000000000000
--- a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
+++ /dev/null
@@ -1,184 +0,0 @@ 
-OMAP2+ and K3 Mailbox
-=====================
-
-The OMAP mailbox hardware facilitates communication between different processors
-using a queued mailbox interrupt mechanism. The IP block is external to the
-various processor subsystems and is connected on an interconnect bus. The
-communication is achieved through a set of registers for message storage and
-interrupt configuration registers.
-
-Each mailbox IP block/cluster has a certain number of h/w fifo queues and output
-interrupt lines. An output interrupt line is routed to an interrupt controller
-within a processor subsystem, and there can be more than one line going to a
-specific processor's interrupt controller. The interrupt line connections are
-fixed for an instance and are dictated by the IP integration into the SoC
-(excluding the SoCs that have a Interrupt Crossbar IP). Each interrupt line is
-programmable through a set of interrupt configuration registers, and have a rx
-and tx interrupt source per h/w fifo. Communication between different processors
-is achieved through the appropriate programming of the rx and tx interrupt
-sources on the appropriate interrupt lines.
-
-The number of h/w fifo queues and interrupt lines dictate the usable registers.
-All the current OMAP SoCs except for the newest DRA7xx SoC has a single IP
-instance. DRA7xx has multiple instances with different number of h/w fifo queues
-and interrupt lines between different instances. The interrupt lines can also be
-routed to different processor sub-systems on DRA7xx as they are routed through
-the Crossbar, a kind of interrupt router/multiplexer. The K3 AM65x and J721E
-SoCs has each of these instances form a cluster and combine multiple clusters
-into a single IP block present within the Main NavSS. The interrupt lines from
-all these clusters are multiplexed and routed to different processor subsystems
-over a limited number of common interrupt output lines of an Interrupt Router.
-The AM64x SoCS also uses a single IP block comprising of multiple clusters,
-but the number of clusters are smaller, and the interrupt output lines are
-connected directly to various processors.
-
-Mailbox Device Node:
-====================
-A Mailbox device node is used to represent a Mailbox IP instance/cluster within
-a SoC. The sub-mailboxes are represented as child nodes of this parent node.
-
-Required properties:
---------------------
-- compatible:		Should be one of the following,
-			    "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
-			    "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
-			    "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
-						   AM43xx and DRA7xx SoCs
-			    "ti,am654-mailbox" for K3 AM65x and J721E SoCs
-			    "ti,am64-mailbox" for K3 AM64x SoCs
-- reg:			Contains the mailbox register address range (base
-			address and length)
-- interrupts:		Contains the interrupt information for the mailbox
-			device. The format is dependent on which interrupt
-			controller the Mailbox device uses
-- #mbox-cells:		Common mailbox binding property to identify the number
-			of cells required for the mailbox specifier. Should be
-			1
-- ti,mbox-num-users:	Number of targets (processor devices) that the mailbox
-			device can interrupt
-- ti,mbox-num-fifos:	Number of h/w fifo queues within the mailbox IP block
-
-SoC-specific Required properties:
----------------------------------
-The following are mandatory properties for the OMAP architecture based SoCs
-only:
-- ti,hwmods:		Name of the hwmod associated with the mailbox. This
-			should be defined in the mailbox node only if the node
-			is not defined as a child node of a corresponding sysc
-			interconnect node.
-
-The following are mandatory properties for the K3 AM65x and J721E SoCs only:
-- interrupt-parent:	Should contain a phandle to the TI-SCI interrupt
-			controller node that is used to dynamically program
-			the interrupt routes between the IP and the main GIC
-			controllers. See the following binding for additional
-			details,
-			Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
-
-Child Nodes:
-============
-A child node is used for representing the actual sub-mailbox device that is
-used for the communication between the host processor and a remote processor.
-Each child node should have a unique node name across all the different
-mailbox device nodes.
-
-Required properties:
---------------------
-- ti,mbox-tx:		sub-mailbox descriptor property defining a Tx fifo
-- ti,mbox-rx:		sub-mailbox descriptor property defining a Rx fifo
-
-Sub-mailbox Descriptor Data
----------------------------
-Each of the above ti,mbox-tx and ti,mbox-rx properties should have 3 cells of
-data that represent the following:
-    Cell #1 (fifo_id) - mailbox fifo id used either for transmitting
-                        (ti,mbox-tx) or for receiving (ti,mbox-rx)
-    Cell #2 (irq_id)  - irq identifier index number to use from the parent's
-                        interrupts data. Should be 0 for most of the cases, a
-                        positive index value is seen only on mailboxes that have
-                        multiple interrupt lines connected to the MPU processor.
-    Cell #3 (usr_id)  - mailbox user id for identifying the interrupt line
-                        associated with generating a tx/rx fifo interrupt.
-
-Optional Properties:
---------------------
-- ti,mbox-send-noirq:   Quirk flag to allow the client user of this sub-mailbox
-                        to send messages without triggering a Tx ready interrupt,
-                        and to control the Tx ticker. Should be used only on
-                        sub-mailboxes used to communicate with WkupM3 remote
-                        processor on AM33xx/AM43xx SoCs.
-
-Mailbox Users:
-==============
-A device needing to communicate with a target processor device should specify
-them using the common mailbox binding properties, "mboxes" and the optional
-"mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
-for details). Each value of the mboxes property should contain a phandle to the
-mailbox controller device node and an args specifier that will be the phandle to
-the intended sub-mailbox child node to be used for communication. The equivalent
-"mbox-names" property value can be used to give a name to the communication channel
-to be used by the client user.
-
-
-Example:
---------
-
-1. /* OMAP4 */
-mailbox: mailbox@4a0f4000 {
-	compatible = "ti,omap4-mailbox";
-	reg = <0x4a0f4000 0x200>;
-	interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
-	ti,hwmods = "mailbox";
-	#mbox-cells = <1>;
-	ti,mbox-num-users = <3>;
-	ti,mbox-num-fifos = <8>;
-	mbox_ipu: mbox_ipu {
-		ti,mbox-tx = <0 0 0>;
-		ti,mbox-rx = <1 0 0>;
-	};
-	mbox_dsp: mbox_dsp {
-		ti,mbox-tx = <3 0 0>;
-		ti,mbox-rx = <2 0 0>;
-	};
-};
-
-dsp {
-	...
-	mboxes = <&mailbox &mbox_dsp>;
-	...
-};
-
-2. /* AM33xx */
-mailbox: mailbox@480c8000 {
-	compatible = "ti,omap4-mailbox";
-	reg = <0x480C8000 0x200>;
-	interrupts = <77>;
-	ti,hwmods = "mailbox";
-	#mbox-cells = <1>;
-	ti,mbox-num-users = <4>;
-	ti,mbox-num-fifos = <8>;
-	mbox_wkupm3: wkup_m3 {
-		ti,mbox-tx = <0 0 0>;
-		ti,mbox-rx = <0 0 3>;
-	};
-};
-
-3. /* AM65x */
-&cbass_main {
-	cbass_main_navss: interconnect0 {
-		mailbox0_cluster0: mailbox@31f80000 {
-			compatible = "ti,am654-mailbox";
-			reg = <0x00 0x31f80000 0x00 0x200>;
-			#mbox-cells = <1>;
-			ti,mbox-num-users = <4>;
-			ti,mbox-num-fifos = <16>;
-			interrupt-parent = <&intr_main_navss>;
-			interrupts = <164 0>;
-
-			mbox_mcu_r5fss0_core0: mbox-mcu-r5fss0-core0 {
-				ti,mbox-tx = <1 0 0>;
-				ti,mbox-rx = <0 0 0>;
-			};
-		};
-	};
-};
diff --git a/Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml b/Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml
new file mode 100644
index 000000000000..1b5d71df1d51
--- /dev/null
+++ b/Documentation/devicetree/bindings/mailbox/ti,omap-mailbox.yaml
@@ -0,0 +1,309 @@ 
+# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TI OMAP2+ and K3 Mailbox devices
+
+maintainers:
+  - Suman Anna <s-anna@ti.com>
+
+description: |
+  The OMAP Mailbox hardware facilitates communication between different
+  processors using a queued mailbox interrupt mechanism. The IP block is
+  external to the various processor subsystems and is connected on an
+  interconnect bus. The communication is achieved through a set of registers
+  for message storage and interrupt configuration registers.
+
+  Each mailbox IP block/cluster has a certain number of h/w fifo queues and
+  output interrupt lines. An output interrupt line is routed to an interrupt
+  controller within a processor subsystem, and there can be more than one line
+  going to a specific processor's interrupt controller. The interrupt line
+  connections are fixed for an instance and are dictated by the IP integration
+  into the SoC (excluding the SoCs that have an Interrupt Crossbar or an
+  Interrupt Router IP). Each interrupt line is programmable through a set of
+  interrupt configuration registers, and have a rx and tx interrupt source per
+  h/w fifo. Communication between different processors is achieved through the
+  appropriate programming of the rx and tx interrupt sources on the appropriate
+  interrupt lines.
+
+  The number of h/w fifo queues and interrupt lines dictate the usable
+  registers. All the current OMAP SoCs except for the newest DRA7xx SoC has a
+  single IP instance. DRA7xx has multiple instances with different number of
+  h/w fifo queues and interrupt lines between different instances. The interrupt
+  lines can also be routed to different processor sub-systems on DRA7xx as they
+  are routed through the Crossbar, a kind of interrupt router/multiplexer. The
+  K3 AM65x, J721E and J7200 SoCs has each of these instances form a cluster and
+  combine multiple clusters into a single IP block present within the Main
+  NavSS. The interrupt lines from all these clusters are multiplexed and routed
+  to different processor subsystems over a limited number of common interrupt
+  output lines of an Interrupt Router. The AM64x SoCS also uses a single IP
+  block comprising of multiple clusters, but the number of clusters are
+  smaller, and the interrupt output lines are connected directly to various
+  processors.
+
+  Mailbox Controller Nodes
+  =========================
+  A Mailbox device node is used to represent a Mailbox IP instance/cluster
+  within a SoC. The sub-mailboxes (actual communication channels) are
+  represented as child nodes of this parent node.
+
+  Mailbox Users
+  ==============
+  A device needing to communicate with a target processor device should specify
+  them using the common mailbox binding properties, "mboxes" and the optional
+  "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
+  for details). Each value of the mboxes property should contain a phandle to
+  the mailbox controller device node and an args specifier that will be the
+  phandle to the intended sub-mailbox child node to be used for communication.
+  The equivalent "mbox-names" property value can be used to give a name to the
+  communication channel to be used by the client user.
+
+definitions:
+  omap-mbox-descriptor:
+    $ref: /schemas/types.yaml#/definitions/uint32-array
+    description: |
+      The omap-mbox-descriptor is made of up of 3 cells and represents a single
+      uni-directional communication channel. A typical sub-mailbox device uses
+      two such channels - one for transmitting (Tx) and one for receiving (Rx).
+    items:
+      - description: |
+          mailbox fifo id used either for transmitting on ti,mbox-tx channel or
+          for receiving on ti,mbox-rx channel (fifo_id). This is the hardware
+          fifo number within a mailbox cluster.
+      - description: |
+          irq identifier index number to use from the parent's interrupts data.
+          Should be 0 for most of the cases, a positive index value is seen only
+          on mailboxes that have multiple interrupt lines connected to the MPU
+          processor (irq_id). This is an index number in the listed interrupts
+          property in the DT nodes.
+      - description: |
+          mailbox user id for identifying the interrupt line associated with
+          generating a tx/rx fifo interrupt (usr_id). This is the hardware
+          user id number within a mailbox cluster.
+
+  omap-sub-mailbox:
+    type: object
+    description: |
+      The omap-sub-mailbox is a child node within a Mailbox controller device
+      node and represents the actual communication channel used to send and
+      receive messages between the host processor and a remote processor. Each
+      child node should have a unique node name across all the different mailbox
+      device nodes.
+
+    properties:
+      ti,mbox-tx:
+        $ref: "#/definitions/omap-mbox-descriptor"
+        description: sub-mailbox descriptor property defining a Tx fifo.
+
+      ti,mbox-rx:
+        $ref: "#/definitions/omap-mbox-descriptor"
+        description: sub-mailbox descriptor property defining a Rx fifo.
+
+      ti,mbox-send-noirq:
+        type: boolean
+        description: |
+          Quirk flag to allow the client user of this sub-mailbox to send
+          messages without triggering a Tx ready interrupt, and to control
+          the Tx ticker. Should be used only on sub-mailboxes used to
+          communicate with WkupM3 remote processor on AM33xx/AM43xx SoCs.
+
+    required:
+      - ti,mbox-tx
+      - ti,mbox-rx
+
+properties:
+  compatible:
+    enum:
+      - ti,omap2-mailbox # for OMAP2420, OMAP2430 SoCs
+      - ti,omap3-mailbox # for OMAP3430, OMAP3630 SoCs
+      - ti,omap4-mailbox # for OMAP44xx, OMAP54xx, AM33xx, AM43xx and DRA7xx SoCs
+      - ti,am654-mailbox # for K3 AM65x, J721E and J7200 SoCs
+      - ti,am64-mailbox  # for K3 AM64x SoCs
+
+  reg:
+    maxItems: 1
+
+  interrupts:
+    description: |
+      Contains the interrupt information for the mailbox device. The format is
+      dependent on which interrupt controller the Mailbox device uses. The
+      number of interrupts listed will at most be the value specified in
+      ti,mbox-num-users property, but is usually limited by the number of
+      interrupts reaching the main processor. An interrupt-parent property
+      is required on SoCs where the interrupt lines are connected through a
+      Interrupt Router before reaching the main processor's GIC.
+
+  "#mbox-cells":
+    const: 1
+    description: |
+      Common mailbox binding property to identify the number of cells required
+      for the mailbox specifier in a consumer node. The specifier is a phandle
+      to a omap-sub-mailbox device.
+
+  ti,mbox-num-users:
+    $ref: /schemas/types.yaml#/definitions/uint32
+    description: |
+      Number of targets (processor devices) that the mailbox device can
+      interrupt.
+
+  ti,mbox-num-fifos:
+    $ref: /schemas/types.yaml#/definitions/uint32
+    description: Number of h/w fifo queues within the mailbox IP block.
+
+  ti,hwmods:
+    $ref: /schemas/types.yaml#/definitions/string
+    description: |
+      Name of the hwmod associated with the mailbox. This should be defined
+      in the mailbox node only if the node is not defined as a child node of
+      a corresponding sysc interconnect node.
+
+      This property is only needed on some legacy OMAP SoCs which have not
+      yet been converted to the ti,sysc interconnect hierarachy, but is
+      otherwise considered obsolete.
+
+patternProperties:
+  "^mbox-[a-z0-9-]+$":
+    $ref: "#/definitions/omap-sub-mailbox"
+
+required:
+  - compatible
+  - reg
+  - interrupts
+  - "#mbox-cells"
+  - ti,mbox-num-users
+  - ti,mbox-num-fifos
+
+allOf:
+  - if:
+      properties:
+        compatible:
+          enum:
+            - ti,am654-mailbox
+    then:
+      required:
+        - interrupt-parent
+
+  - if:
+      properties:
+        compatible:
+          enum:
+            - ti,am654-mailbox
+            - ti,am64-mailbox
+    then:
+      properties:
+        ti,mbox-num-users:
+          const: 4
+        ti,mbox-num-fifos:
+          const: 16
+        interrupts:
+          minItems: 1
+          maxItems: 4
+
+  - if:
+      properties:
+        compatible:
+          enum:
+            - ti,omap4-mailbox
+    then:
+      properties:
+        ti,mbox-num-users:
+          enum: [3, 4]
+        ti,mbox-num-fifos:
+          enum: [8, 12]
+        interrupts:
+          minItems: 1
+          maxItems: 4
+
+  - if:
+      properties:
+        compatible:
+          enum:
+            - ti,omap3-mailbox
+    then:
+      properties:
+        ti,mbox-num-users:
+          const: 2
+        ti,mbox-num-fifos:
+          const: 2
+        interrupts:
+          minItems: 1
+          maxItems: 1
+
+  - if:
+      properties:
+        compatible:
+          enum:
+            - ti,omap2-mailbox
+    then:
+      properties:
+        ti,mbox-num-users:
+          const: 4
+        ti,mbox-num-fifos:
+          const: 6
+        interrupts:
+          minItems: 1
+          maxItems: 2
+
+additionalProperties: false
+
+examples:
+  - |
+    /* OMAP4 */
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+    mailbox: mailbox@4a0f4000 {
+        compatible = "ti,omap4-mailbox";
+        reg = <0x4a0f4000 0x200>;
+        interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
+        #mbox-cells = <1>;
+        ti,mbox-num-users = <3>;
+        ti,mbox-num-fifos = <8>;
+
+        mbox_ipu: mbox-ipu {
+            ti,mbox-tx = <0 0 0>;
+            ti,mbox-rx = <1 0 0>;
+        };
+        mbox_dsp: mbox-dsp {
+            ti,mbox-tx = <3 0 0>;
+            ti,mbox-rx = <2 0 0>;
+        };
+    };
+
+    dsp {
+        mboxes = <&mailbox &mbox_dsp>;
+    };
+
+  - |
+    /* AM33xx */
+    mailbox1: mailbox@480c8000 {
+        compatible = "ti,omap4-mailbox";
+        reg = <0x480c8000 0x200>;
+        interrupts = <77>;
+        #mbox-cells = <1>;
+        ti,mbox-num-users = <4>;
+        ti,mbox-num-fifos = <8>;
+
+        mbox_wkupm3: mbox-wkup-m3 {
+            ti,mbox-tx = <0 0 0>;
+            ti,mbox-rx = <0 0 3>;
+            ti,mbox-send-noirq;
+        };
+    };
+
+  - |
+    /* AM65x */
+    mailbox0_cluster0: mailbox@31f80000 {
+        compatible = "ti,am654-mailbox";
+        reg = <0x31f80000 0x200>;
+        #mbox-cells = <1>;
+        ti,mbox-num-users = <4>;
+        ti,mbox-num-fifos = <16>;
+        interrupt-parent = <&intr_main_navss>;
+        interrupts = <436>;
+
+        mbox_mcu_r5fss0_core0: mbox-mcu-r5fss0-core0 {
+            ti,mbox-tx = <1 0 0>;
+            ti,mbox-rx = <0 0 0>;
+        };
+    };