Devicetree
 help / color / mirror / Atom feed
From: Moteen Shah <m-shah@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <krzk+dt@kernel.org>, <robh@kernel.org>, <conor+dt@kernel.org>,
	<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>,
	<gehariprasath@ti.com>, <y-abhilashchandra@ti.com>
Subject: Re: [PATCH v3 1/2] ti,j721e-system-controller.yaml: Allow audio-refclk as clock-controller child
Date: Tue, 5 May 2026 11:28:19 +0530	[thread overview]
Message-ID: <1f06c527-4806-47a9-aa3d-70a01c5390f9@ti.com> (raw)
In-Reply-To: <0c78744d-6bdb-4b0e-a0bc-039bb6527476@kernel.org>

Hey Krzysztof,

On 07/04/26 11:23, Krzysztof Kozlowski wrote:
> On 07/04/2026 07:46, Moteen Shah wrote:
>> Hey Krzysztof,
>>
>> On 31/03/26 12:39, Krzysztof Kozlowski wrote:
>>> On Mon, Mar 30, 2026 at 03:14:58PM +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
>>> J721S2 or AM62?
>>>
>>>> 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(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,j721e-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,j721e-system-controller.yaml
>>>> index f3bd0be3b279..d5d84a8f1257 100644
>>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,j721e-system-controller.yaml
>>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,j721e-system-controller.yaml
>>>> @@ -53,9 +53,11 @@ patternProperties:
>>>>    
>>>>      "^clock-controller@[0-9a-f]+$":
>>>>        type: object
>>>> -    $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
>>>> +    oneOf:
>>>> +      - $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
>>>> +      - $ref: /schemas/clock/ti,am62-audio-refclk.yaml#
>>> Alphanumerical order.
>>>
>>> There is no ti,am62 in the top level compatibles, so why am62 is here?
>>> Top level has j721s2 but this ti,am62-audio-refclk.yaml only am62.
>>>
>>> Best regards,
>>> Krzysztof
>> The "ti,am62-audio-refclk" compatible refers to a shared audio reference
>> clock IP block that was first introduced/named on AM62 but is present on
>> other TI K3 SoCs as well, including J721S2. The compatible string
>> identifies the IP block, not the SoC family.
>>
>> This is already an established pattern —
>> k3-j784s4-j742s2-main-common.dtsi uses the same compatible for the
>> J784S4/J742S2 audio refclk node.
> Please read carefully writing-bindings doc.
>

I am planning add another compatible for j721s2: "compatible = 
"ti,j721s2-audio-refclk", "ti,am62-audio-refclk""
This will eventually be falling back to am62-audio-refclk's compatible 
for now, since we require the same functionality as 
"ti,am62-audio-refclk" but if in future someone wants j721s2 specific 
change only they can use the new compatible for j721s2 specific usecase. 
Does that sounds okay?

Regards,
Moteen


> Best regards,
> Krzysztof

  reply	other threads:[~2026-05-05  5:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30  9:44 [PATCH v3 0/2] Enable audio support for J721S2 EVM Moteen Shah
2026-03-30  9:44 ` [PATCH v3 1/2] ti,j721e-system-controller.yaml: Allow audio-refclk as clock-controller child Moteen Shah
2026-03-31  7:09   ` Krzysztof Kozlowski
2026-04-07  5:46     ` Moteen Shah
2026-04-07  5:53       ` Krzysztof Kozlowski
2026-05-05  5:58         ` Moteen Shah [this message]
2026-03-30  9:44 ` [PATCH v3 2/2] arm64: dts: ti: Add audio overlay for k3-j721s2-evm Moteen Shah
2026-03-31  7:11   ` Krzysztof Kozlowski

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=1f06c527-4806-47a9-aa3d-70a01c5390f9@ti.com \
    --to=m-shah@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gehariprasath@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --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