From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: change 'HDMI/DP, pcm=' to 'HDMI/DP, pcm=' Jack control names
Date: Fri, 25 Oct 2019 09:35:47 -0500 [thread overview]
Message-ID: <432032a3-26f1-bd58-278b-54f4f6ebe3e4@linux.intel.com> (raw)
In-Reply-To: <6b59a565-faf7-2b70-4e04-546a5ba507c3@perex.cz>
On 10/25/19 9:04 AM, Jaroslav Kysela wrote:
> Dne 25. 10. 19 v 14:44 Kai Vehmanen napsal(a):
>> Hi,
>>
>> On Fri, 25 Oct 2019, Jaroslav Kysela wrote:
>>
>>> There is an inconsistency in the names for the HDMI/DP Jack control
>>> names between some ASoC drivers and the HDA HDMI driver which
>>> introduced this naming in 2011.
>>
>> this will break a lot of existing devices that are using out-of-tree UCM
>> files, so I'm not sure this is worth the effort.
>
> I don't agree. The out-of-tree UCMs should go to upstream anyway, except
> that they are unusable for the standard users.
Isn't there a problem due to UCM extensions as well? I vaguely recall
having to modify the Cherrytrail UCMs I took from the Chrome adhd
repository since the parsing wouldn't work with the standard alsa-lib.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-25 14:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:30 [alsa-devel] [PATCH] ASoC: change 'HDMI/DP, pcm=' to 'HDMI/DP, pcm=' Jack control names Jaroslav Kysela
2019-10-25 12:38 ` Takashi Iwai
2019-10-25 13:57 ` Jaroslav Kysela
2019-10-25 14:06 ` Takashi Iwai
2019-10-25 14:18 ` Jaroslav Kysela
2019-10-25 14:28 ` Takashi Iwai
2019-10-25 14:39 ` Jaroslav Kysela
2019-10-25 16:11 ` Takashi Iwai
2019-10-25 17:04 ` Jaroslav Kysela
2019-10-25 18:02 ` Kai Vehmanen
2019-10-25 21:03 ` Jaroslav Kysela
2019-10-26 7:37 ` Takashi Iwai
2019-10-26 17:11 ` Jaroslav Kysela
2019-10-28 14:23 ` Takashi Iwai
2019-10-25 14:49 ` Mark Brown
2019-10-25 12:44 ` Kai Vehmanen
2019-10-25 14:04 ` Jaroslav Kysela
2019-10-25 14:35 ` Pierre-Louis Bossart [this message]
2019-10-25 14:43 ` Jaroslav Kysela
2019-10-25 16:27 ` Peter Ujfalusi
2019-10-25 17:48 ` Kai Vehmanen
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=432032a3-26f1-bd58-278b-54f4f6ebe3e4@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=perex@perex.cz \
--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.