From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: dapm: Fix snd_soc_dapm_put_volsw() connect
Date: Sat, 30 Jun 2012 12:54:25 +0100 [thread overview]
Message-ID: <20120630115424.GX28922@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <71354327.345161.1340985944186.JavaMail.root@advansee.com>
[-- Attachment #1.1: Type: text/plain, Size: 1390 bytes --]
On Fri, Jun 29, 2012 at 06:05:44PM +0200, Benoît Thébaudeau wrote:
> On Fri, Jun 29, 2012 at 05:43:09PM +0200, Takashi Iwai wrote:
> > That's a valid assumption. Usually get and put callbacks must be
> > paired well.
> What is the point of having customizable get/put callbacks if
> dapm_set_path_status() ignores them and duplicates their core behavior?
Nobody needed to do that yet.
> In the aic3x example, the bit-field is actually a mixer volume control, and not
> only a boolean, so I was planning to post a fix for that. The issue is that the
> encoding of register values for this volume has holes that should not be
> duplicated in userspace raw values, so custom get and put callbacks have to be
> used here that will not be compatible with snd_soc_dapm_get_volsw(), which will
> be blocking for dapm_set_path_status(). Do you have a simple solution for that?
Clearly the driver is just buggy and should implement get for itself
too. As far as reading back the path status is concerned so long as
the mapping looks OK as a boolean we're fine, it doesn't matter what the
individual volumes are as all the code is interested in is on/off.
> In the meantime, please find below a quick patch for the consistency issue.
Stop doing this, send patches for review rather than burying them in the
middle of e-mails where they're at best a pain to apply.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-06-30 11:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 20:41 [PATCH] ASoC: dapm: Fix snd_soc_dapm_put_volsw() connect Benoît Thébaudeau
2012-06-19 11:36 ` Mark Brown
2012-06-29 6:25 ` Takashi Iwai
2012-06-29 7:23 ` Mark Brown
2012-06-29 7:26 ` Takashi Iwai
2012-06-29 11:53 ` Benoît Thébaudeau
2012-06-29 12:03 ` Takashi Iwai
2012-06-29 14:29 ` Benoît Thébaudeau
2012-06-29 15:43 ` Takashi Iwai
2012-06-29 15:44 ` Takashi Iwai
2012-06-29 16:09 ` Benoît Thébaudeau
2012-06-29 16:22 ` Takashi Iwai
2012-06-29 19:09 ` Benoît Thébaudeau
2012-06-29 20:18 ` Benoît Thébaudeau
2012-06-30 11:39 ` Mark Brown
2012-06-30 13:03 ` Benoît Thébaudeau
2012-06-30 18:24 ` Mark Brown
2012-07-02 11:46 ` [RFC/PATCH] ASoC: dapm: Fix/add support for stereo widgets Benoît Thébaudeau
2012-07-02 12:27 ` Mark Brown
2012-07-03 6:57 ` [PATCH] ASoC: dapm: Fix snd_soc_dapm_put_volsw() connect Takashi Iwai
2012-06-30 11:38 ` Mark Brown
2012-06-29 16:05 ` Benoît Thébaudeau
2012-06-29 16:11 ` Takashi Iwai
2012-06-30 11:54 ` Mark Brown [this message]
2012-06-30 13:03 ` Benoît Thébaudeau
2012-07-02 11:45 ` [PATCH] ASoC: dapm: Fix dapm_set_path_status() connect Benoît Thébaudeau
2012-07-03 19:08 ` Mark Brown
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=20120630115424.GX28922@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=benoit.thebaudeau@advansee.com \
--cc=lrg@ti.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.