From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Alexandre Belloni <aleandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH v3 2/2] ASoC: dt-bindings: simple-audio-mux: add mux-names property
Date: Fri, 28 Jun 2024 01:44:04 +0000 [thread overview]
Message-ID: <87ikxtaljw.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <171953773961.1035497.12432679100328649698.robh@kernel.org>
Hi
> > simple-audio-mux is designed to be used generally, thus "Input 1" or
> > "Input 2" are used to selecting MUX input. This numbered inputs would
> > work, but might be not user friendly in some case, for example in case
> > of system hardware design has some clear labels.
> > Adds new "state-labels" property and enable to select MUX by own state
> > names.
> >
> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > ---
> > .../devicetree/bindings/sound/simple-audio-mux.yaml | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
>
> My bot found errors running 'make dt_binding_check' on your patch:
Grr. Thank you for pointing it. will post v4 patch
Thank you for your help !!
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2024-06-28 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 0:20 [PATCH v3 0/2] ASoC: simple-audio-mux: add state-labels Kuninori Morimoto
2024-06-28 0:20 ` [PATCH v3 1/2] ASoC: simple-audio-mux: enable to select MUX names Kuninori Morimoto
2024-06-28 0:22 ` [PATCH v3 2/2] ASoC: dt-bindings: simple-audio-mux: add mux-names property Kuninori Morimoto
2024-06-28 1:22 ` Rob Herring (Arm)
2024-06-28 1:44 ` Kuninori Morimoto [this message]
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=87ikxtaljw.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=aleandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--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