From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Songhee Baek <sbaek@nvidia.com>,
Arun Shamanna Lakshmi <aruns@nvidia.com>,
alsa-devel@alsa-project.org, lars@metafoo.de,
swarren@wwwdotorg.org, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: dapm: Add support for multi register mux
Date: Thu, 3 Apr 2014 10:53:30 +0100 [thread overview]
Message-ID: <20140403095330.GS14763@sirena.org.uk> (raw)
In-Reply-To: <s5h4n2asq1o.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
On Thu, Apr 03, 2014 at 11:47:15AM +0200, Takashi Iwai wrote:
> I'm a bit late in the game, but I feel a bit uneasy through looking
> at the whole changes. My primary question is, whether do we really
> need to share the same struct soc_enum for the onehot type? What
> makes hard to use a struct soc_enum_onehot for them? You need
> different individual get/put for each type. We may still need to
> change soc_dapm_update stuff, but it's different from sharing
> soc_enum.
Indeed, I had thought this was where the discussion was heading - not
looked at this version of the patch yet.
[-- 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:[~2014-04-03 9:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 3:11 [PATCH] ASoC: dapm: Add support for multi register mux Arun Shamanna Lakshmi
2014-04-03 8:27 ` Lars-Peter Clausen
2014-04-03 9:40 ` Mark Brown
2014-04-03 20:11 ` Arun Shamanna Lakshmi
2014-04-04 7:31 ` Lars-Peter Clausen
2014-04-04 7:34 ` Arun Shamanna Lakshmi
2014-04-04 7:40 ` Lars-Peter Clausen
2014-04-03 9:47 ` Takashi Iwai
2014-04-03 9:53 ` Mark Brown [this message]
2014-04-03 13:31 ` Lars-Peter Clausen
2014-04-03 15:06 ` Takashi Iwai
2014-04-03 16:02 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-04-05 0:12 Arun Shamanna Lakshmi
2014-04-07 12:54 ` Lars-Peter Clausen
2014-04-07 14:24 ` Takashi Iwai
2014-04-09 15:56 ` Mark Brown
2014-04-01 6:21 [PATCH] ASoC: DAPM: " Arun Shamanna Lakshmi
2014-04-01 7:48 ` Lars-Peter Clausen
[not found] ` <781A12BB53C15A4BB37291FDE08C03F3A05CDCD63B@HQMAIL02.nvidia.com>
2014-04-01 18:26 ` Arun Shamanna Lakshmi
2014-04-02 6:00 ` Lars-Peter Clausen
2014-04-02 6:17 ` Songhee Baek
2014-04-02 6:47 ` Lars-Peter Clausen
2014-04-02 6:56 ` Songhee Baek
2014-04-02 7:01 ` Lars-Peter Clausen
2014-04-02 7:06 ` Songhee Baek
2014-04-02 15:26 ` Songhee Baek
2014-04-02 15:29 ` Lars-Peter Clausen
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=20140403095330.GS14763@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=aruns@nvidia.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbaek@nvidia.com \
--cc=swarren@wwwdotorg.org \
--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