From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: dapm: Fix snd_soc_dapm_put_volsw() connect
Date: Fri, 29 Jun 2012 21:09:49 +0200 (CEST) [thread overview]
Message-ID: <2026346.354826.1340996989713.JavaMail.root@advansee.com> (raw)
In-Reply-To: <s5hzk7mulyz.wl%tiwai@suse.de>
On Fri, Jun 29, 2012 at 06:22:28PM +0200, Takashi Iwai wrote:
> At Fri, 29 Jun 2012 18:09:35 +0200 (CEST),
> Benoît Thébaudeau wrote:
> >
> > On Fri, Jun 29, 2012 at 05:44:41PM +0200, Takashi Iwai wrote:
> > > BTW, looking at snd_soc_dapm_vol_getsw(), I found that
> > > snd_soc_dapm_vol_putsw() doesn't handle a stereo case.
> > > This needs a fix, too...
> >
> > I saw that too. Is it the stereo case that should be added to put
> > or removed
> > from get, i.e. is it possible to handle a stereo case with only one
> > connect
> > flag?
>
> I would assume that connect should be up when either left or right is
> on. A stereo widget doesn't mean multiple connections.
I have started to look into that:
- Give a choice between reg and shift stereo for snd_soc_dapm_get_volsw(), like
in snd_soc_get_volsw().
- Add stereo to the first case of dapm_set_path_status().
- Add stereo to dapm_widget_update() and struct snd_soc_dapm_update.
- Then comes snd_soc_dapm_get_volsw(): What should we do with
"widget->value = val;"? Add an rvalue to struct snd_soc_dapm_widget? This
field does not seem to be read anywhere except for enums. There is also
saved_value and other fields that do not seem to be used anywhere.
Regards,
Benoît
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2012-06-29 19:05 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 [this message]
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
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=2026346.354826.1340996989713.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox