From: ChiYuan Huang <cy_huang@richtek.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Roy Chiu <roy_chiu@richtek.com>, <linux-sound@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: dt-bindings: Add Richtek RTQ9124
Date: Fri, 6 Jun 2025 17:19:12 +0800 [thread overview]
Message-ID: <aEKykANxE/v0UN1b@git-send.richtek.com> (raw)
In-Reply-To: <d923e0a2-acee-4e25-80e7-cdbc125408a4@kernel.org>
On Fri, Jun 06, 2025 at 10:50:14AM +0200, Krzysztof Kozlowski wrote:
> On 06/06/2025 10:43, ChiYuan Huang wrote:
> > On Fri, Jun 06, 2025 at 10:33:46AM +0200, Krzysztof Kozlowski wrote:
> >> On 06/06/2025 10:24, cy_huang@richtek.com wrote:
> >>> +
> >>> +allOf:
> >>> + - $ref: dai-common.yaml#
> >>> +
> >>> +properties:
> >>> + compatible:
> >>> + enum:
> >>> + - richtek,rtq9124
> >>
> >> Exactly the same as richtek,rt9123. Don't create same binding files for
> >> similar devices.
> >>
> > Do you mean to expand rtq9124 description in rt9123 binding file?
>
> Yes
>
Compared to write a similar file, this should be better.
Will use that way in next revision.
Thanks.
> > Any example that I
> > can refer to?
>
> Majority of bindings.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-06-06 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 8:24 [PATCH 0/2] ASoC: Add Richtek RTQ9124 support cy_huang
2025-06-06 8:24 ` [PATCH 1/2] ASoC: dt-bindings: Add Richtek RTQ9124 cy_huang
2025-06-06 8:33 ` Krzysztof Kozlowski
2025-06-06 8:43 ` ChiYuan Huang
2025-06-06 8:50 ` Krzysztof Kozlowski
2025-06-06 9:19 ` ChiYuan Huang [this message]
2025-06-06 8:24 ` [PATCH 2/2] ASoC: codecs: Add support for " cy_huang
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=aEKykANxE/v0UN1b@git-send.richtek.com \
--to=cy_huang@richtek.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=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=roy_chiu@richtek.com \
--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).