From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: 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>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
goledhruva@gmail.com, m-chawdhry@ti.com,
daniel.baluta@gmail.com, simona.toaca@nxp.com,
j.bhargav.u@gmail.com, linux-omap@vger.kernel.org
Subject: [PATCH v4 0/3] dt-bindings: bus: omap-l3: Convert to DT schema
Date: Fri, 13 Nov 2026 00:24:01 +0530 [thread overview]
Message-ID: <20261113-ti-l3-noc-v4-0-5084dcf4ffb4@gmail.com> (raw)
This series converts the TI OMAP L3 binding from text to DT schema.
The text binding grouped OMAP3 (SMX IP) and OMAP4+ (Arteris NoC IP)
together. split into two schemas because OMAP3 (SMX) and OMAP4+ (Arteris
NoC) are different hardware IPs.
- patch 1 adds a missing unit address to the ABB regulator node in the
OMAP36xx devicetree to fix a validation warning.
- patch 2 converts OMAP3 L3 SMX interconnect.
- patch 3 converts the OMAP4+ L3 NoC interconnect.
Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
Changes in v4:
- Fix SMX example node.
- Link to v3: https://lore.kernel.org/r/20261112-ti-l3-noc-v3-0-7281b1af8030@gmail.com
Changes in v3:
- Split bidning into two SMX and NOC variants.
- Fix reg maxItems to 2 for ti,dra7-l3-noc L3_MAIN_2 is a submodule of
L3_MAIN_1.
- Link to v2: https://lore.kernel.org/r/20261109-ti-l3-noc-v2-0-509e8485a1f3@gmail.com
Changes in v2:
- Move binding to bindings/bus/
- Rebase to latest mainline rc
- Add unit address to regulator-abb-mpu node
- Link to v1: https://lore.kernel.org/r/20261003-ti-l3-noc-v1-1-9bd18cac33e9@gmail.com
---
Bhargav Joshi (3):
ARM: dts: omap36xx: Add unit address to ABB regulator node
dt-bindings: bus: ti,omap3-l3-smx: Convert to DT schema
dt-bindings: bus: ti,omap-l3-noc: Convert to DT schema
.../devicetree/bindings/arm/omap/l3-noc.txt | 23 -------
.../devicetree/bindings/bus/ti,omap-l3-noc.yaml | 71 ++++++++++++++++++++++
.../devicetree/bindings/bus/ti,omap3-l3-smx.yaml | 68 +++++++++++++++++++++
arch/arm/boot/dts/ti/omap/omap36xx.dtsi | 2 +-
4 files changed, 140 insertions(+), 24 deletions(-)
---
base-commit: fa4ad798f6f681031775266044ba1b0cf3c670bd
change-id: 20261002-ti-l3-noc-28dfca81fdc5
Best regards,
--
Bhargav
next reply other threads:[~2026-11-12 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 18:54 Bhargav Joshi [this message]
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 18:54 ` [PATCH v4 3/3] dt-bindings: bus: ti,omap-l3-noc: " Bhargav Joshi
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=20261113-ti-l3-noc-v4-0-5084dcf4ffb4@gmail.com \
--to=j.bhargav.u@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=goledhruva@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
all inboxes | Powered by JetHome®