Devicetree
 help / color / mirror / Atom feed
From: Eduard Bostina <egbostina@gmail.com>
To: Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, Eduard Bostina <egbostina@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Rob Herring <robh@kernel.org>
Cc: daniel.baluta@nxp.com, simona.toaca@nxp.com,
	goledhruva@gmail.com, m-chawdhry@ti.com
Subject: [PATCH v2 0/5] dt-bindings: soc: ti: Convert OMAP DSP and IVA to DT schema
Date: Mon,  6 Jul 2026 08:59:12 +0000	[thread overview]
Message-ID: <20260706085917.835875-1-egbostina@gmail.com> (raw)

This series converts the Texas Instruments DSP and IVA
Device Tree bindings from text format to DT schema.

These conversions are grouped together because the IVA schema explicitly 
depends on the DSP schema. The DSP is defined as a child node within the
IVA subsystem.

Changes in v2:
- Expanded from a 2 patch to a 5 patch series.
- Moved both the DSP and IVA binding files from bindings/arm/omap/ 
  to bindings/soc/ti/
- Patches 1 and 3: 1:1 conversions of the old txt files.
- Patches 2 and 4: Make 'ti,hwmods' optional to fix dtbs_check warnings. 
  Reasoning described in the commit messages.
- Patch 5: Documents the DSP child node in the IVA schema to fix 
  dtbs_check warnings. Reasoning described in the commit message.

Eduard Bostina (5):
  dt-bindings: soc: ti: Convert DSP to DT schema
  dt-bindings: soc: ti: omap-dsp: Make ti,hwmods optional
  dt-bindings: soc: ti: Convert IVA to DT schema
  dt-bindings: soc: ti: omap-iva: Make ti,hwmods optional
  dt-bindings: soc: ti: omap-iva: Document DSP child node

 .../devicetree/bindings/arm/omap/dsp.txt      | 14 ------
 .../devicetree/bindings/arm/omap/iva.txt      | 19 --------
 .../devicetree/bindings/soc/ti/ti,iva.yaml    | 48 +++++++++++++++++++
 .../bindings/soc/ti/ti,omap3-c64.yaml         | 31 ++++++++++++
 4 files changed, 79 insertions(+), 33 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/arm/omap/dsp.txt
 delete mode 100644 Documentation/devicetree/bindings/arm/omap/iva.txt
 create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,iva.yaml
 create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,omap3-c64.yaml

-- 
2.43.0


             reply	other threads:[~2026-07-06  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  8:59 Eduard Bostina [this message]
2026-07-06  8:59 ` [PATCH v2 1/5] dt-bindings: soc: ti: Convert DSP to DT schema Eduard Bostina
2026-07-06  8:59 ` [PATCH v2 2/5] dt-bindings: soc: ti: omap-dsp: Make ti,hwmods optional Eduard Bostina
2026-07-06  8:59 ` [PATCH v2 3/5] dt-bindings: soc: ti: Convert IVA to DT schema Eduard Bostina
2026-07-06  8:59 ` [PATCH v2 4/5] dt-bindings: soc: ti: omap-iva: Make ti,hwmods optional Eduard Bostina
2026-07-06  9:26   ` sashiko-bot
2026-07-06  8:59 ` [PATCH v2 5/5] dt-bindings: soc: ti: omap-iva: Document DSP child node Eduard Bostina

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=20260706085917.835875-1-egbostina@gmail.com \
    --to=egbostina@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=goledhruva@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=robh@kernel.org \
    --cc=simona.toaca@nxp.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