From: GitHub pull_request - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: WIP: Add UCM for PinePhone
Date: Mon, 7 Feb 2022 12:54:55 +0100 (CET) [thread overview]
Message-ID: <20220207115455.0A07FF80482@alsa1.perex.cz> (raw)
In-Reply-To: <1644234888718647003-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #134 was edited from tomfitzhenry:
Fixes https://github.com/alsa-project/alsa-ucm-conf/issues/124.
The DTS configuration has had a unique audio card name since 5.14:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi?h=v5.14#n436
This UCM config is copied from https://gitlab.com/pine64-org/pine64-alsa-ucm/, which is BSD-3-Clause licensed.
This UCM has been tested via Pulseaudio's ALSA_CONFIG_UCM2 environment variable, but I've not yet tested that this UCM, when included in this package, is correctly recognised on a PinePhone as part of this
Todo:
* [x] Test that this UCM is correctly recognised on a PinePhone. **Done**. This testing found that the `File` directive in `SectionUseCase` needs to be absolute (for the symlink to work). I've fixed this in https://github.com/alsa-project/alsa-ucm-conf/pull/134/commits/5059e57a2197bb38848bbec10f589637df64679e.
See also:
* https://gitlab.com/pine64-org/pine64-alsa-ucm/-/merge_requests/1
* https://gitlab.com/pine64-org/pine64-alsa-ucm/-/issues/3
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2022-02-07 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1644234888718647003-webhooks-bot@alsa-project.org>
2022-02-07 11:54 ` GitHub pull_request - edited [this message]
[not found] <1644234869328393936-webhooks-bot@alsa-project.org>
2022-02-07 11:54 ` WIP: Add UCM for PinePhone GitHub pull_request - edited
[not found] <1644234768117971897-webhooks-bot@alsa-project.org>
2022-02-07 11:52 ` GitHub pull_request - edited
[not found] <1642372328656722069-webhooks-bot@alsa-project.org>
2022-01-16 22:32 ` GitHub pull_request - edited
[not found] <1642366418671698093-webhooks-bot@alsa-project.org>
2022-01-16 20:53 ` GitHub pull_request - opened
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=20220207115455.0A07FF80482@alsa1.perex.cz \
--to=github@alsa-project.org \
--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;
as well as URLs for NNTP newsgroup(s).