From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Alexandre Belloni <aleandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>, Takashi Iwai <tiwai@suse.com>,
devicetree@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: dt-bindings: simple-audio-mux: add mux-names property
Date: Thu, 27 Jun 2024 23:08:18 +0000 [thread overview]
Message-ID: <87tthe9e71.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <169aa3ed-8427-4832-b5e8-302a1ce0558e@sirena.org.uk>
Hi Krzysztof, Mark
> > > Current simple-audio-mux selects MUX by "Input 1" or "Input 2",
> > > it is not user friendly. Adds new "mux-names" property and enable to
> > > select MUX by own names.
>
> > > + mux-names:
> > > + description: |
> > > + Name of multiplexers. default is "Input 1", "Input 2"
>
> > I have troubles with this binding... It seems driver expects only one
> > GPIO, but the binding allows any number. Similarly mux-names...
>
> > Anyway, this does not look like hardware description but rather
> > configuration of driver. What's wrong with input 1 or mux 1 or whatever
> > is there for default?
>
> I would expect that when this driver is deployed it would mainly be for
> selecting between things like microphone inputs that are defined and
> labelled as part of the system hardware design. Using numbered inputs
> would *work* but it's not great for usability so I do see a use case for
> labels. Possibly we could figure something out by walking the graph but
> that seems quite hard, possibly unreasonably so.
Thank you for explaning, Mark
I noticed that the property naming is not so good.
I will fix property name and git-log, and re-post v2.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2024-06-27 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 3:51 [PATCH 0/2] ASoC: simple-audio-mux: add mux-name Kuninori Morimoto
2024-06-27 3:51 ` [PATCH 1/2] ASoC: simple-audio-mux: enable to select MUX names Kuninori Morimoto
2024-06-27 3:52 ` [PATCH 2/2] ASoC: dt-bindings: simple-audio-mux: add mux-names property Kuninori Morimoto
2024-06-27 7:46 ` Krzysztof Kozlowski
2024-06-27 11:45 ` Mark Brown
2024-06-27 23:08 ` 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=87tthe9e71.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=krzk@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