From: "Rob Herring (Arm)" <robh@kernel.org>
To: Charan Pedumuru <charan.pedumuru@gmail.com>
Cc: linux-sound@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH] ASoC: dt-bindings: ti,omap4-dmic: Convert TI OMAP4+ DMIC binding to YAML
Date: Fri, 10 Jul 2026 16:59:07 -0500 [thread overview]
Message-ID: <178372074660.1412241.7384502507366665799.robh@kernel.org> (raw)
In-Reply-To: <20260630-ti-dmic-v1-1-9e4400230266@gmail.com>
On Tue, 30 Jun 2026 12:25:49 +0000, Charan Pedumuru wrote:
> Convert the ti,omap4-dmic text binding to DT schema format for
> validation with dt_binding_check and dtbs_check.
> Changes during conversion:
> - dtbs_check flagged reg-names, dmas, and dma-names as undocumented
> on all four in-tree omap5 boards using this compatible (cm-t54,
> igep0050, sbc-t54, uevm)
> - Add these as required properties to reflect actual hardware usage,
> since the original text binding was incomplete
> - Drop ti,hwmods from required, as it is a legacy property tied to
> the OMAP hwmod framework and is not mandatory for DT schema
> validation going forward
> - Update the example to exercise all newly documented properties so
> the schema validates cleanly against real board DTS files
>
> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
> ---
> .../devicetree/bindings/sound/omap-dmic.txt | 20 -------
> .../devicetree/bindings/sound/ti,omap4-dmic.yaml | 68 ++++++++++++++++++++++
> 2 files changed, 68 insertions(+), 20 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2026-07-10 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 12:25 [PATCH] ASoC: dt-bindings: ti,omap4-dmic: Convert TI OMAP4+ DMIC binding to YAML Charan Pedumuru
2026-07-10 21:59 ` Rob Herring (Arm) [this message]
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=178372074660.1412241.7384502507366665799.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=charan.pedumuru@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@ti.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