From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ASoC: dt-bindings: tlv320aic32x4: convert to DT schema format
Date: Fri, 16 Jun 2023 14:17:40 +0200 [thread overview]
Message-ID: <4930994.QJadu78ljV@steina-w> (raw)
In-Reply-To: <5a562bbc-9bba-4829-8998-af12041a434c@sirena.org.uk>
Hi Mark,
Am Freitag, 16. Juni 2023, 13:54:49 CEST schrieb Mark Brown:
> On Fri, Jun 16, 2023 at 10:35:49AM +0200, Alexander Stein wrote:
> > Convert the binding to DT schema format.
> > Since commit 514b044cba667 ("ASoC: tlv320aic32x4: Model PLL in CCF")
> > clocks & clock-names = "mclk" is mandatory, it has been added to required
> > properties as well. '#sound-dai-cells' is added for reference from
> > simple-audio-card.
>
> This doesn't apply against current code, please check and resend. This
> should be an incremental patch perhaps?
Is there any change to original .txt file I am not aware of? The to be created
.yaml file is new, so there is no increment.
To which base/branch/tag should I rebase this?
Thanks and best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-06-16 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 8:35 [PATCH v2 1/1] ASoC: dt-bindings: tlv320aic32x4: convert to DT schema format Alexander Stein
2023-06-16 9:34 ` Krzysztof Kozlowski
2023-06-16 11:54 ` Mark Brown
2023-06-16 12:17 ` Alexander Stein [this message]
2023-06-16 12:21 ` Mark Brown
2023-06-16 12:24 ` Alexander Stein
2023-06-16 12:30 ` Mark Brown
2023-06-16 13:22 ` Alexander Stein
2023-06-16 13:37 ` Mark Brown
2023-06-16 16:17 ` Mark Brown
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=4930994.QJadu78ljV@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=robh+dt@kernel.org \
/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