From: russell.parker7@gmail.com
To: patch@alsa-project.org
Cc: alsa-devel@alsa-project.org
Subject: [PATCH ucm/conf: 0/5] Factor out rt5645 + rt5650 shared UCM sequences
Date: Sat, 5 Jan 2019 19:47:10 -0800 [thread overview]
Message-ID: <20190106034715.21045-1-russell.parker7@gmail.com> (raw)
Hi,
When I submitted a patch to create a UCM config for chtrt5650 it was
suggested that I also factor out command sequences that it shares with
chtrt5645. The following patchset introduces a new component directory
codecs/rt5645-common/ and refactors UCM profiles in:
- chtrt5645
- chtrt5645-mono-speaker-analog-mic
- chtrt5650
- ASUSTeKCOMPUTERINC.-T100HAN-1.0-T100HAN
- LENOVO-80XF-LenovoMIIX320_10ICR-LNVNB161216
I compiled and tested playback with the rt5650 configs but I don't
have the devices to test the other configurations. Suggestions and feedback
are welcome, I'm not very familiar with UCM configuration so there may
definitely be better approaches for some of these changes.
- Russell
next reply other threads:[~2019-01-06 3:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 3:47 russell.parker7 [this message]
2019-01-06 3:47 ` [PATCH ucm/conf: 1/5] Update chtrt5645 ucm variants to use bytcr/PlatformEnableSeq.conf component russell.parker7
2019-01-06 3:47 ` [PATCH ucm/conf: 2/5] Create shared {En, Dis}ableSeq.conf components for rt5645 variants russell.parker7
2019-01-06 3:47 ` [PATCH ucm/conf: 3/5] Factor out rt5645 variants Speaker+Headphones shared UCM enable sequences russell.parker7
2019-01-06 3:47 ` [PATCH ucm/conf: 4/5] Factor out rt5645 variants Headset+Digital Mic UCM shared {en, dis}able sequences russell.parker7
2019-01-06 3:47 ` [PATCH ucm/conf: 5/5] Create device comoponent for rt5645 Internal Analog Mic UCM russell.parker7
2019-01-07 10:32 ` [PATCH ucm/conf: 0/5] Factor out rt5645 + rt5650 shared UCM sequences Jaroslav Kysela
2019-01-07 15:42 ` Russell Parker
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=20190106034715.21045-1-russell.parker7@gmail.com \
--to=russell.parker7@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=patch@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