From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 14/14] ASoC: wm9712/wm9713: Use shared controls
Date: Fri, 31 Oct 2014 18:55:21 +0100 [thread overview]
Message-ID: <5453CD09.9010906@metafoo.de> (raw)
In-Reply-To: <20141031174056.GM18557@sirena.org.uk>
On 10/31/2014 06:40 PM, Mark Brown wrote:
> On Thu, Oct 30, 2014 at 09:01:11PM +0100, Lars-Peter Clausen wrote:
>
>> Note: This changes the exposed controls, instead of having one "Left HP
>> Mixer ..." and one "Right HP Mixer ..." control for each input there will
>> only be a single "HP Mixer ..." control.
>
> This change would be a win except for the above - these devices were
> very widely deployed in fairly popular devices like the Sharp Zaurus
> devices so there's quite a bit of deployed distro config in things like
> Angstrom which would get broken if we updated, and some user community
> remaining too. On balance I'd say that the cleanup to use the new
> feature isn't worth the disruption it'd cause to userspace.
It was worth a try ;) We can still clean this up using custom put/get
handlers instead of virtual registers.
next prev parent reply other threads:[~2014-10-31 17:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 20:00 [PATCH 00/14] ASoC: AC'97 driver cleanups Lars-Peter Clausen
2014-10-30 20:00 ` [PATCH 01/14] ASoC: ad1980: Remove unused header Lars-Peter Clausen
2014-10-31 17:19 ` Mark Brown
2014-10-30 20:00 ` [PATCH 02/14] ASoC: ad1980: Cleanup printk usage Lars-Peter Clausen
2014-10-31 17:19 ` Mark Brown
2014-10-30 20:01 ` [PATCH 03/14] ASoC: ad1980: Use table based control setup Lars-Peter Clausen
2014-10-31 17:19 ` Mark Brown
2014-10-30 20:01 ` [PATCH 04/14] ASoC: stac9766: Cleanup printk usage Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 05/14] ASoC: stac9766: Use table based control setup Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 06/14] ASoC: wm9705: Cleanup printk usage Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 07/14] ASoC: wm9705: Use table based control setup Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 08/14] ASoC: wm9712: Cleanup printk usage Lars-Peter Clausen
2014-10-31 17:32 ` Mark Brown
2014-10-30 20:01 ` [PATCH 09/14] ASoC: wm9712: Use table based control setup Lars-Peter Clausen
2014-10-31 17:32 ` Mark Brown
2014-10-30 20:01 ` [PATCH 10/14] ASoC: wm9713: Cleanup printk usage Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 11/14] ASoC: wm9713: Use table based control setup Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 12/14] ASoC: wm9713: Move driver state struct allocation to driver probe Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 13/14] ASoC: wm9713: Use virtual control instead of virtual register Lars-Peter Clausen
2014-10-30 20:01 ` [PATCH 14/14] ASoC: wm9712/wm9713: Use shared controls Lars-Peter Clausen
2014-10-31 17:40 ` Mark Brown
2014-10-31 17:55 ` Lars-Peter Clausen [this message]
2014-10-31 10:35 ` [PATCH 00/14] ASoC: AC'97 driver cleanups Charles Keepax
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=5453CD09.9010906@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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