From: "Rob Herring (Arm)" <robh@kernel.org>
To: Moteen Shah <m-shah@ti.com>
Cc: nm@ti.com, y-abhilashchandra@ti.com, vigneshr@ti.com,
gehariprasath@ti.com, kristo@kernel.org, u-kumar1@ti.com,
krzk+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ti,j721e-system-controller.yaml: Allow audio-refclk as clock-controller child
Date: Thu, 15 Jan 2026 11:31:32 -0600 [thread overview]
Message-ID: <176849829204.923576.6698326462461946997.robh@kernel.org> (raw)
In-Reply-To: <20260112104536.83309-2-m-shah@ti.com>
On Mon, 12 Jan 2026 16:15:34 +0530, Moteen Shah wrote:
> The ti,j721e-system-controller binding currently only allows
> clock-controller@ child nodes to reference the ti,am654-ehrpwm-tbclk
> schema. However, the system controller on J721S2 also contains audio
> reference clock controllers (ti,am62-audio-refclk) that use the same
> clock-controller@XXXX naming pattern.
>
> Hence, extend the clock-controller pattern to accept either ehrpwm-tbclk
> or audio-refclk schemas using a oneOf constraint.
>
> Signed-off-by: Moteen Shah <m-shah@ti.com>
> ---
> .../bindings/soc/ti/ti,j721e-system-controller.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-01-15 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:45 [PATCH 0/3] Enable analog audio support on J721S2 EVM Moteen Shah
2026-01-12 10:45 ` [PATCH 1/3] ti,j721e-system-controller.yaml: Allow audio-refclk as clock-controller child Moteen Shah
2026-01-15 17:31 ` Rob Herring (Arm) [this message]
2026-01-12 10:45 ` [PATCH 2/3] arm64: dts: ti: k3-j721s2-main: Add audio_refclk node Moteen Shah
2026-01-16 10:29 ` Hari Prasath
2026-01-12 10:45 ` [PATCH 3/3] arm64: dts: ti: k3-j721s2-common-proc-board: Enable analog audio support Moteen Shah
2026-01-16 11:52 ` Hari Prasath
2026-01-16 13:04 ` Nishanth Menon
2026-02-04 11:18 ` Moteen Shah
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=176849829204.923576.6698326462461946997.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gehariprasath@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@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
all inboxes | Powered by JetHome®