Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Sricharan R <r.sricharan@ti.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Kevin Hilman <khilman@baylibre.com>,
	Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	goledhruva@gmail.com, m-chawdhry@ti.com, daniel.baluta@gmail.com,
	simona.toaca@nxp.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: bus: ti,omap3-l3-smx: Convert to DT schema
Date: Sat, 21 Nov 2026 10:14:24 +0100	[thread overview]
Message-ID: <20261121101424.22e24149@kemnade.info> (raw)
In-Reply-To: <20261113-ti-l3-noc-v4-2-5084dcf4ffb4@gmail.com>

On Fri, 13 Nov 2026 00:24:03 +0530
Bhargav Joshi <j.bhargav.u@gmail.com> wrote:

> Convert TI OMAP3 L3 interconnect from text to DT schema. In text binding
> this was grouped with omap4+ L3 noc interconnect but since it uses
> different hardware IP (SMX). Add SMX variant in new schema.
> 
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
Reviewed-by: Andreas Kemnade <andreas@kemnade.info>
> ---
>  .../devicetree/bindings/arm/omap/l3-noc.txt        |  5 +-
>  .../devicetree/bindings/bus/ti,omap3-l3-smx.yaml   | 68 ++++++++++++++++++++++
>  2 files changed, 70 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/omap/l3-noc.txt b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt
> index 161448da959d2..66548395fbdeb 100644
> --- a/Documentation/devicetree/bindings/arm/omap/l3-noc.txt
> +++ b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt
> @@ -4,10 +4,9 @@ This version is an implementation of the generic NoC IP
>  provided by Arteris.
>  
>  Required properties:
> -- compatible : Should be "ti,omap3-l3-smx" for OMAP3 family
> -               Should be "ti,omap4-l3-noc" for OMAP4 family
> +- compatible : Should be "ti,omap4-l3-noc" for OMAP4 family
>                 Should be "ti,omap5-l3-noc" for OMAP5 family
> -	       Should be "ti,dra7-l3-noc" for DRA7 family
> +	           Should be "ti,dra7-l3-noc" for DRA7 family
>                 Should be "ti,am4372-l3-noc" for AM43 family
>  - reg:	Contains L3 register address range for each noc domain.
>  - ti,hwmods: "l3_main_1", ... One hwmod for each noc domain.
> diff --git a/Documentation/devicetree/bindings/bus/ti,omap3-l3-smx.yaml b/Documentation/devicetree/bindings/bus/ti,omap3-l3-smx.yaml
> new file mode 100644
> index 0000000000000..3fc5fae7b37ba
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/ti,omap3-l3-smx.yaml
> @@ -0,0 +1,68 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/ti,omap3-l3-smx.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI OMAP3 L3 (SMX) Interconnect
> +
> +maintainers:
> +  - Santosh Shilimkar <santosh.shilimkar@ti.com>
> +  - Sricharan R <r.sricharan@ti.com>
> +
> +description:
> +  The L3 interconnect for OMAP3 is based on the SonicsMX (SMX) architecture.
> +
> +properties:
> +  compatible:
> +    items:
> +      - const: ti,omap3-l3-smx
> +      - const: simple-bus
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    items:
> +      - description: l3-dbg-irq
> +      - description: l3-app-irq
> +
> +  ti,hwmods:
> +    description: hwmod names for each domain.
> +    $ref: /schemas/types.yaml#/definitions/string
> +    const: l3_main
> +    deprecated: true
> +
> +  "#address-cells":
> +    const: 1
> +
> +  "#size-cells":
> +    const: 1
> +
> +  ranges: true
> +
> +patternProperties:
> +  "^.*@[0-9a-f]+$":
> +    type: object
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - "#address-cells"
> +  - "#size-cells"
> +  - ranges
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    bus@68000000 {
> +        compatible = "ti,omap3-l3-smx", "simple-bus";
> +        reg = <0x68000000 0x10000>;
> +        ranges;
> +        #address-cells = <1>;
> +        #size-cells = <1>;
> +        interrupts = <9>, <10>;
> +        ti,hwmods = "l3_main";
> +    };
> 


  parent reply	other threads:[~2026-11-21  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 18:54 [PATCH v4 0/3] dt-bindings: bus: omap-l3: Convert to DT schema Bhargav Joshi
2026-11-12 18:54 ` [PATCH v4 1/3] ARM: dts: omap36xx: Add unit address to ABB regulator node Bhargav Joshi
2026-11-12 18:54 ` [PATCH v4 2/3] dt-bindings: bus: ti,omap3-l3-smx: Convert to DT schema Bhargav Joshi
2026-11-12 23:04   ` Rob Herring (Arm)
2026-11-21  9:14   ` Andreas Kemnade [this message]
2026-11-12 18:54 ` [PATCH v4 3/3] dt-bindings: bus: ti,omap-l3-noc: " Bhargav Joshi
2026-11-12 23:04   ` Rob Herring (Arm)
2026-11-21  9:13   ` Andreas Kemnade

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=20261121101424.22e24149@kemnade.info \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=goledhruva@gmail.com \
    --cc=j.bhargav.u@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=r.sricharan@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=simona.toaca@nxp.com \
    --cc=tony@atomide.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