From: Hui Wang <hui.wang@canonical.com>
To: Mark Pearson <mpearson@lenovo.com>,
Jaroslav Kysela <perex@perex.cz>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Elimar Riesebieter <riesebie@lxtec.de>
Subject: Re: [alsa-devel] [External] Re: alsa-lib: Add ucm support for whiskeylake sof-skl_hda_card audio
Date: Fri, 27 Sep 2019 16:21:30 +0800 [thread overview]
Message-ID: <4cb6bec8-1dac-9114-c230-c9196763e58d@canonical.com> (raw)
In-Reply-To: <153ba191eb3c4849b6e65db5fc8e8760@lenovo.com>
So far, the alsa-lib still depends on the card->name/long-name to find
the needed UCM, I know some Dell machines also uses sof driver (so the
card->name/long-name is also sof-skl_hda_card), so if this UCM is
merged, it will be shared with Dell machines. But on those Dell
machines, there is no BASS Speaker, and Dell machines have sth that
Lenovo machines don't have, like headset-mic and headphone-mic. How to
make this UCM work on both Lenovo and Dell machines?
Regards,
Hui.
On 2019/9/24 下午8:06, Mark Pearson wrote:
>>> I think the first order would be to have the file cleaned-up, with its
>>> Intel origin clearly stated with a signed-off-by tag.
>>>
>>> Then once this is done, the Debian package creation needs to be
>>> handled (using either the ALSA repo or the cloned version on SOF
>>> GitHub). I don't have any experience with Debian packages so can't
>>> really comment on the effort it would take.
>> I did some cleanups here:
>>
>> https://github.com/alsa-project/alsa-ucm-
>> conf/commit/f796f0852a097e238fa9f5efb174e95b5ee6c8b7
>>
>> Pierre, could you confirm the original source and are you ok with that?
>>
> I got confirmation from Intel that they are the original source - they provided me with the files (as an aside in case it is important, originally they were working with Canonical on getting Ubuntu working on one of our (Lenovo) platforms). I was following up with Canonical to just check what they had done but haven't heard back yet.
>
> Since Intel has provided the files to me directly - can I act as an original source confirmation?
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
_______________________________________________
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-09-27 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 14:23 [alsa-devel] alsa-lib: Add ucm support for whiskeylake sof-skl_hda_card audio Elimar Riesebieter
2019-09-19 14:44 ` Pierre-Louis Bossart
[not found] ` <f11c5347d8504148a47fdbc48d920f59@lenovo.com>
2019-09-19 15:15 ` [alsa-devel] [External] " Pierre-Louis Bossart
2019-09-24 11:53 ` Jaroslav Kysela
2019-09-24 12:06 ` Mark Pearson
2019-09-27 8:21 ` Hui Wang [this message]
2019-09-27 9:01 ` Jaroslav Kysela
2019-09-28 3:33 ` Hui Wang
2019-10-03 2:07 ` Hui Wang
2019-09-27 10:07 ` Jaska Uimonen
2019-09-27 10:57 ` Jaroslav Kysela
2019-09-27 14:00 ` Jaska Uimonen
2019-09-27 14:49 ` Jaroslav Kysela
2019-09-28 16:33 ` Jaska Uimonen
2019-09-19 14:49 ` [alsa-devel] " Jaroslav Kysela
2019-09-19 15:14 ` [alsa-devel] [External] " Mark Pearson
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=4cb6bec8-1dac-9114-c230-c9196763e58d@canonical.com \
--to=hui.wang@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=mpearson@lenovo.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=riesebie@lxtec.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.