From: "Juho Hämäläinen" <juho.hamalainen@tieto.com>
To: alsa-devel@alsa-project.org
Subject: UCM {Supported,Conflicting}Device confusion
Date: Wed, 29 May 2013 13:55:38 +0300 [thread overview]
Message-ID: <51A5DEAA.4020007@tieto.com> (raw)
Hello,
Firstly as a sidenote, Supported/Conflicting is checked only one-way, if
say devices A and B are enabled and say B has ConflictingDevice "C", and
device C doesn't list anything, enabling of C is possible (and after
that disabling C is not possible before B is disabled first).
Now, looking at the way SupportedDevice and ConflictingDevice are
implemented in ucm and I came to following conclusion:
If no SupportedDevice or ConflictingDevice: All devices and combinations
are compatible, so implicit "SupportedDevice ALL".
If SupportedDevice is listed: Device can be enabled as long as at least
one enabled device is in SupportedDevice list.
If ConflictingDevice is listed: Device can be enabled if none of active
devices are in ConflictingDevice list (noting aforementioned limit in
checking this)
This is at least how I figured all combinations of multiple devices can
be defined with only zero or one either SupportedDevice or
ConflictingDevice entry per device.
Did I understand this right?
--
juho
next reply other threads:[~2013-05-29 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 10:55 Juho Hämäläinen [this message]
2013-05-29 15:12 ` UCM {Supported,Conflicting}Device confusion Stephen Warren
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=51A5DEAA.4020007@tieto.com \
--to=juho.hamalainen@tieto.com \
--cc=alsa-devel@alsa-project.org \
/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