From: Liam Girdwood <lrg@ti.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] UCM: Implement ConflictingDevices, add device list to devices
Date: Fri, 3 Jun 2011 11:20:46 +0100 [thread overview]
Message-ID: <4DE8B57E.2000701@ti.com> (raw)
In-Reply-To: <1307059431-4913-1-git-send-email-swarren@nvidia.com>
On 03/06/11 01:03, Stephen Warren wrote:
> Wherever SupportedDevice can appear, also allow ConflictingDevice. Only
> one or the other (or neither) may be specified. When neither is
> specified, allow anything. Sometimes, listing ConflictingDevices may
> result in a shorter list than explicitly listing all SupportedDevices.
>
> Add support for SupportedDevice and ConflictingDevice to SectionDevice.
> This allows representing devices which are mutually exclusive, e.g. due
> to a mux that switches between capturing from two different microphones,
> without the possibility of mixing.
>
> Enhance is_modifier_supported to allow ignoring SupportedDevice and
> ConflictingDevice. This is useful when querying values from a
> SectionModifier; there's no reason we shouldn't be able to query values
> just because the current configuration would prevent enabling that
> device. The new is_device_supported is implemented similarly.
>
> Enhance switch_device to remove the old device from the current device
> list before querying for the new device, and add it back immediately
> afterwards. This allows the query for the new device to ignore any
> conflicts caused solely by the old device.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Liam Girdwood <lrg@ti.com>
> ---
> Depending on decisions in the thread I recently started entitled
> "UCM modifier names", this patch may change, e.g. name_match may not
> be needed, or could be simpler.
>
> I should probably split some of this into separate patches, but I
> figured I'd get it out there for people to discuss first.
>
Code looks fine, but it maybe best to rework with the index changes discussed in your previous mail (at least so we can deprecate the index).
Liam
prev parent reply other threads:[~2011-06-03 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 0:03 [PATCH] UCM: Implement ConflictingDevices, add device list to devices Stephen Warren
2011-06-03 10:20 ` Liam Girdwood [this message]
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=4DE8B57E.2000701@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=swarren@nvidia.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.