From: Jaroslav Kysela <perex@perex.cz>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Rasmus Porsager <rasmus@beat.dk>,
alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH alsa-ucm-conf 1/2] bytcr-rt5640: Add support for devices without speakers and/or an internal mic
Date: Mon, 11 Jan 2021 19:59:40 +0100 [thread overview]
Message-ID: <d5d4d125-c838-0ef9-e8be-2adb77688904@perex.cz> (raw)
In-Reply-To: <20210109210252.159162-1-hdegoede@redhat.com>
Dne 09. 01. 21 v 22:02 Hans de Goede napsal(a):
> There are kernel patches pending upstream for the bytcr-rt5640 machine-driver
> to support devices without speakers and/or an internal mic.
>
> Since the UCM profile already conditionally loads the speaker and
> internal-mic codec include files, these will simply get skipped in this
> case, so this almost works with the current UCM profile without changes.
>
> The only troublesome part is the ConflictingDevice sections in the codec
> HeadPhones.conf and HeadsetMic.conf files, which refer to resp. a "Speaker"
> and a "Mic" device. Without any of the speaker or mic codec conf files
> being included there will not by any "Speaker" / "Mic" devices leading
> to an error while parsing the HeadPhones.conf / HeadsetMic.conf files.
>
> This commit makes the ConflictingDevice section conditional, fixing this.
Applied to the ucm repo. Thank you.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
prev parent reply other threads:[~2021-01-11 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 21:02 [PATCH alsa-ucm-conf 1/2] bytcr-rt5640: Add support for devices without speakers and/or an internal mic Hans de Goede
2021-01-09 21:02 ` [PATCH alsa-ucm-conf 2/2] rt5640: Move standard DAC setup to EnableSeq.conf Hans de Goede
2021-01-11 19:00 ` Jaroslav Kysela
2021-01-11 18:59 ` Jaroslav Kysela [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=d5d4d125-c838-0ef9-e8be-2adb77688904@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rasmus@beat.dk \
/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.