From: Krzysztof Kozlowski <krzk@kernel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Takashi Iwai <tiwai@suse.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Jaroslav Kysela <perex@perex.cz>, Frank Li <Frank.li@nxp.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-sound@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] ASoC: dt-bindings: audio-graph-card2: add widgets and hp-det-gpios support
Date: Mon, 13 Jan 2025 12:44:49 +0100 [thread overview]
Message-ID: <79672620-9bfa-4162-9555-3f7274914cbf@kernel.org> (raw)
In-Reply-To: <e5665b6a-c2ad-470f-8a36-b7adc05c1cf0@gmail.com>
On 08/01/2025 13:19, Laurentiu Mihalcea wrote:
>
>
>
> On 12/17/2024 9:07 AM, Krzysztof Kozlowski wrote:
>> On Mon, Dec 16, 2024 at 09:50:37AM -0500, Laurentiu Mihalcea wrote:
>>> From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>>>
>>> Introduce the 'widgets' property, allowing the creation of widgets from
>>> 4 template widgets: Microphone, Line, Headphone, and Speaker. Also
>>> introduce the 'hp-det-gpios' property, which allows using headphone
>>> detection using the specified GPIO.
>>>
>>> Signed-off-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>>> ---
>>> .../devicetree/bindings/sound/audio-graph-card2.yaml | 4 ++++
>> I have impression you are duplicating audio graph properties instead of
>> referencing proper schema, but considering that the bindings
>> audio-graph-card and audio-graph-card2 differ only by number "2" without
>> any description, not sure what is correct here.
>
> Please correct me if I'm wrong here.
>
> As things stand now and based on Kuninori Morimoto's comment on this
> (https://lore.kernel.org/lkml/87cyhw8lg5.wl-kuninori.morimoto.gx@renesas.com/) I'd say we can't
> (or, rather, shouldn't) directly reference audio-graph.yaml here.
Thanks
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Now, I wonder if the "proper" solution here would be to take the common properties
> of audio-graph.yaml and audio-graph-card2.yaml and create a new binding that can be
> referenced by both aforementioned bindings? Would that make things even more confusing
> (we'd probably end up with audio-graph.yaml, audio-graph-card.yaml, audio-graph-card2.yaml,
> and audio-graph-common.yaml)? Should this be addressed as part of this series?
Really not sure. Common bindings are often good choice but I already
struggle with grasping the differences between both audio-graph-cards,
so more of it might not help.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-13 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 14:50 [PATCH v3 0/5] add sof support on imx95 Laurentiu Mihalcea
2024-12-16 14:50 ` [PATCH v3 1/5] ASoC: dt-bindings: add common binding for NXP audio processors Laurentiu Mihalcea
2024-12-16 16:42 ` Frank Li
2025-01-08 11:41 ` Laurentiu Mihalcea
2024-12-16 14:50 ` [PATCH v3 2/5] ASoC: dt-bindings: support imx95's CM7 core Laurentiu Mihalcea
2024-12-16 16:39 ` Frank Li
2024-12-17 6:56 ` Krzysztof Kozlowski
2024-12-16 14:50 ` [PATCH v3 3/5] ASoC: dt-bindings: audio-graph-card2: add widgets and hp-det-gpios support Laurentiu Mihalcea
2024-12-17 7:07 ` Krzysztof Kozlowski
2025-01-08 12:19 ` Laurentiu Mihalcea
2025-01-13 11:44 ` Krzysztof Kozlowski [this message]
2024-12-16 14:50 ` [PATCH v3 4/5] ASoC: SOF: imx: add driver for imx95 Laurentiu Mihalcea
2024-12-16 16:48 ` Frank Li
2024-12-16 17:56 ` Mark Brown
2024-12-16 14:50 ` [PATCH v3 5/5] arm64: dts: imx: add imx95 dts for sof Laurentiu Mihalcea
2024-12-16 17:05 ` Frank Li
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=79672620-9bfa-4162-9555-3f7274914cbf@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurentiumihalcea111@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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