Hi Ryan and Jeevan,
On 18/09/26 21:40, Ryan Eatmon via lists.yoctoproject.org wrote:
On 9/17/2026 7:16 AM, Jeevan via lists.yoctoproject.org wrote:
On Wed, Sep 16, 2026 at 09:37 PM, Paresh Bhagat wrote:
Extend the PipeWire recipe to add platform-specific ALSA configuration
and service file. Service file added to start PipeWire as a system
service with proper socket dependency.
Add sink and source configuration for 8-channel audio playback and
capture on the AM62D2EVM as the default configuration is 2-channel.
Signed-off-by: Paresh Bhagat <[email protected]>
---
.../pipewire/pipewire-arago.inc | 28
+++++++++++++++++++
.../am62dxx-evm/90-pipewire-sink.conf | 17 +++++++++++
.../am62dxx-evm/91-pipewire-source.conf | 17 +++++++++++
.../pipewire/pipewire/pipewire.service | 26 +++++++++++++++++
.../pipewire/pipewire_%.bbappend | 4 +++
5 files changed, 92 insertions(+)
create mode 100644
meta-arago-distro/recipes-multimedia/pipewire/pipewire-arago.inc
create mode 100644
meta-arago-distro/recipes-multimedia/pipewire/pipewire/am62dxx-evm/90-pipewire-sink.conf
create mode 100644
meta-arago-distro/recipes-multimedia/pipewire/pipewire/am62dxx-evm/91-pipewire-source.conf
create mode 100644
meta-arago-distro/recipes-multimedia/pipewire/pipewire/pipewire.service
create mode 100644
meta-arago-distro/recipes-multimedia/pipewire/pipewire_%.bbappend
diff --git
a/meta-arago-distro/recipes-multimedia/pipewire/pipewire-arago.inc
b/meta-arago-distro/recipes-multimedia/pipewire/pipewire-arago.inc
new file mode 100644
index 00000000..6545c364
--- /dev/null
+++ b/meta-arago-distro/recipes-multimedia/pipewire/pipewire-arago.inc
@@ -0,0 +1,28 @@
+PR:append = ".arago1"
+
+FILESEXTRAPATHS:prepend := "${THISDIR}/pipewire:"
+SRC_URI:append = " file://pipewire.service"
+
+# AM62D-specific config files
+SRC_URI:append:am62dxx-evm = " \
+ file://90-pipewire-sink.conf \
+ file://91-pipewire-source.conf \
+"
Is it okay to have AM62D-specific PipeWire and WirePlumber
configuration files, scripts, and services
in meta-arago or set somewhere else? Ryan/Denys any thoughts?
My recommendation would be to have a more generic/runtime-detectable
configs that is device agnostic.
That's why I keep asking why we have something specific for am62d in
here. If there are other ways of doing it to make it more generic
then I am all for it.
Generally speaking, if this is required then it is ok. The other way
of doing this would be to have the distro add in pipewire support and
then move this specific change over to meta-ti-extras as a bbappend so
that the platform specific tweaks are in the BSP repo. That way if
someone wanted to use poky with pipewire then we would add in the
needed tweaks.
Denys? Thoughts?
Agreed. I could not find any variables, macros in pipewire doc which
could help generalize the pipewire configuration for all devices. Only
ways i see now see is to generate a config during build by either
specifying values in recipe or use a service/script and inherit whatever
alsa reports. But what if it needs modification (example AM62D).
Furthermore other devices do not need it as they work with default
configs (only support mono/stereo).
Since these are no doubt AM62d specific changes, I can move them to
meta-tisdk for now and keep only the pipewire package support in
meta-arago. Let me know if your thoughts.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17686):
https://lists.yoctoproject.org/g/meta-arago/message/17686
Mute This Topic: https://lists.yoctoproject.org/mt/121281282/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
