From: Mark Brown <broonie@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: robh+dt@kernel.org, KCHSU0@nuvoton.com,
thomas.fehrenbacher@siedle.de, kernel@pengutronix.de,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] ASoC: nau8810: add aux input control, available on NAU8812
Date: Fri, 15 Nov 2019 17:14:54 +0000 [thread overview]
Message-ID: <20191115171454.GC4210@sirena.co.uk> (raw)
In-Reply-To: <20191115162053.fgsd45seg526gafv@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Fri, Nov 15, 2019 at 05:20:53PM +0100, Marco Felsch wrote:
> On 19-11-15 16:12, Mark Brown wrote:
> > It'd still be better to only register these controls if the device isn't
> > a nau8812 so that userspace doesn't see them.
> That's the thing I tought about 10min.. Imagine that: You have an
> embedded device with a very good codec driver (all codec controlls are
> available) but the hw-guys didn't connect all the in-/outputs. So
> switching those controls are useless too. IMHO this is exactly the same
> thing here.
We do have the start of facilities to mask out unreachable controls
already (a machine driver could use them manually as things stand). If
we ever get the graph API done properly that work is more likely to get
finished.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-15 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 16:08 [PATCH 0/3] Add NAU8812 support Marco Felsch
2019-11-15 16:08 ` [PATCH 1/3] dt-bindings: ASoC: add nau8812 documentation Marco Felsch
2019-12-03 19:27 ` Rob Herring
2019-11-15 16:08 ` [PATCH 2/3] ASoC: nau8810: add support for nau8812 Marco Felsch
2019-11-15 16:08 ` [PATCH 3/3] ASoC: nau8810: add aux input control, available on NAU8812 Marco Felsch
2019-11-15 16:12 ` Mark Brown
2019-11-15 16:20 ` Marco Felsch
2019-11-15 17:14 ` Mark Brown [this message]
2019-11-16 1:43 ` AS50 KCHsu0
2019-11-18 6:46 ` Marco Felsch
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=20191115171454.GC4210@sirena.co.uk \
--to=broonie@kernel.org \
--cc=KCHSU0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=thomas.fehrenbacher@siedle.de \
/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).