From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>,
Jarkko Nikula <jarkko.nikula@linux.jf.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, broonie@kernel.org,
subhransu.s.prusty@intel.com, lgirdwood@gmail.com
Subject: Re: [PATCH v2 5/5] ASoC: Intel: add BYTCR machine driver with RT5640
Date: Wed, 05 Nov 2014 09:54:59 +0200 [thread overview]
Message-ID: <5459D7D3.3090501@linux.intel.com> (raw)
In-Reply-To: <20141104093244.GE1870@intel.com>
On 11/04/2014 11:32 AM, Vinod Koul wrote:
> On Tue, Nov 04, 2014 at 11:19:10AM +0200, Jarkko Nikula wrote:
>>
>> I think it's worth to have same kcontrol and card names than
>> byt-rt5640 in case this is going to replace byt-rt5640.c since then
>> users can continue to use the same asound.state file. E.g. speakers
>> won't mute because of "Speaker" changes to "Ext Spk".
> It would have helped if the DSP controls were not there. The DSP controls
> need to be routed too, so existing conf files would need to be updated.
>
> So, do you still recommend changing :)
>
Do new controls affect PCM pass through? I was thinking if they affect
only compressed streams then it'd be useful if existing state files
continue working for PCM pass through. It's always painful if kcontol
name changes render audio muted and user have to go through gazillions
of kcontrols :-(
--
Jarkko
next prev parent reply other threads:[~2014-11-05 7:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 5:31 [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Vinod Koul
2014-11-04 5:31 ` [PATCH v2 1/5] ASoC: Intel: mrfld - remove unnecessary check for pointer Vinod Koul
2014-11-04 5:31 ` [PATCH v2 2/5] ASoC: Intel: mrfld - create separate module for pci part Vinod Koul
2014-11-04 5:31 ` [PATCH v2 3/5] ASoC: Intel: mrfld - add shim save restore Vinod Koul
2014-11-04 5:31 ` [PATCH v2 4/5] ASoC: Intel: mrfld- add ACPI module Vinod Koul
2014-11-04 5:31 ` [PATCH v2 5/5] ASoC: Intel: add BYTCR machine driver with RT5640 Vinod Koul
2014-11-04 9:19 ` Jarkko Nikula
2014-11-04 9:32 ` Vinod Koul
2014-11-05 7:54 ` Jarkko Nikula [this message]
2014-11-05 8:44 ` Vinod Koul
2014-11-04 8:09 ` [PATCH v2 0/5] ASoC: Intel: ACPI support and machines Jarkko Nikula
2014-11-04 8:25 ` Vinod Koul
2014-11-04 9:05 ` Jarkko Nikula
2014-11-04 9:15 ` Liam Girdwood
2014-11-04 9:31 ` Vinod Koul
2014-11-04 9:33 ` Vinod Koul
2014-11-04 11:15 ` Mark Brown
2014-11-05 7:49 ` Jarkko Nikula
2014-11-05 8:43 ` Vinod Koul
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=5459D7D3.3090501@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.jf.intel.com \
--cc=lgirdwood@gmail.com \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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 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.