linux-sound.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wang, Sen" <sen@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	<linux-sound@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: sound: simple-card: add system-clock-id property
Date: Sat, 16 May 2026 05:17:57 -0500	[thread overview]
Message-ID: <7afd906e-a851-4cfb-ad4b-f0284cd84f67@ti.com> (raw)
In-Reply-To: <20260516-resilient-magenta-reindeer-4f0bcd@quoll>

On 5/16/2026 4:54 AM, Krzysztof Kozlowski wrote:
> On Fri, May 15, 2026 at 11:13:57AM -0500, Sen Wang wrote:
>> Document the new optional "system-clock-id" u32 property for cpu/codec
>> sub-nodes in simple-audio-card and audio-graph-card.

(snip)
> So now driver APIs are part of binding :/. No.
> 
> You should have built on top or use previous discussion instead of
> making new mistakes:
> https://lore.kernel.org/linux-devicetree/20221022162742.21671-2-aidanmacdonald.0x0@gmail.com/
> 

Thanks for your insight Krzysztof, definitely failed my due diligence in 
finding previous discussions :/.

Let me see if I can do some refactor in ASoC clks instead.

Best,
Sen Wang


  reply	other threads:[~2026-05-16 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 16:13 [PATCH v2 0/2] ASoC: simple-card-utils: support system-clock-id DT property Sen Wang
2026-05-15 16:13 ` [PATCH v2 1/2] dt-bindings: sound: simple-card: add system-clock-id property Sen Wang
2026-05-16  9:54   ` Krzysztof Kozlowski
2026-05-16 10:17     ` Wang, Sen [this message]
2026-05-15 16:13 ` [PATCH v2 2/2] ASoC: simple-card-utils: support system-clock-id DT property Sen Wang
2026-05-15 19:32 ` [PATCH v2 0/2] " Wang, Sen
2026-06-07 14:38 ` Andreas Kemnade
2026-06-16 21:14   ` Wang, Sen

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=7afd906e-a851-4cfb-ad4b-f0284cd84f67@ti.com \
    --to=sen@ti.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).