- Alsa-devel - mailman.alsa-project.org

how do I create configure a ucm2 conf file for my card just like an acp file
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #475 was opened from beh-10257: 1_ how do I know if my card is using acp or ucm profile 2_ can ucm config file be availble in user directories 3_ how do i test a ucm profile 4_ if my card is using ucm is there a way to cooverride that file 5_ for more context https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4421 6_ as a tldr I want to take advanatage of indep_hp=yes (IDK why this is not enabled by default its a great feature compared to other platforms after all) either way I want to make hw:0,0 as speaker and hw:0,2 as headphones can a ucm profile replace the indep_hp hint and udev rule and just porceed to seperate them directly also indep_hp seperates speaker and headphones output is there a way to seperate internal mic and headphone speaker also is there a way to put priority for headphones when the jack port is actually put or even disable it entirely and just default back to speaker automatically thats all thanks thats all and thanks further editing will be filled once I have more questions and thanks Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/475 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

ALC225 update depop procedure
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, ALC225 update depop procedure. Many Thanks. BR, Kailang

2 1

Enable speaker pins for Medion E15443 platform
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, Attach was fixed speaker no sound issue. BR, Kailang

2 1

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp . Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was opened from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

RE: Set pcbeep to default value
by Kailang 26 Nov '24

26 Nov '24

OK. > -----Original Message----- > From: Takashi Iwai <tiwai(a)suse.de> > Sent: Monday, November 25, 2024 10:45 PM > To: Kailang <kailang(a)realtek.com> > Cc: Takashi Iwai <tiwai(a)suse.de> > Subject: Re: Set pcbeep to default value > > > External mail. > > > > On Mon, 25 Nov 2024 03:00:26 +0100, > Kailang wrote: > > > > > > > > > -----Original Message----- > > > From: Takashi Iwai <tiwai(a)suse.de> > > > Sent: Friday, November 22, 2024 5:34 PM > > > To: Kailang <kailang(a)realtek.com> > > > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org> > > > Subject: Re: Set pcbeep to default value > > > > > > > > > External mail. > > > > > > > > > > > > On Fri, 22 Nov 2024 08:29:56 +0100, > > > Kailang wrote: > > > > > > > > Hi Takashi, > > > > > > > > Attach patch will set pcbeep to default value for ALC274. > > > > > > Could you resubmit with your Signed-off-by tag? > > > > Sorry! Attach again. > > You seem to have dropped Cc to alsa-devel ML. > Also, nowadays we use linux-sound(a)vger.kernel.org for the main ML for kernel > patches. Care to resubmit to there? > > > thanks, > > Takashi

1 0

[PATCH] soundwire: amd: clear wake enable register for power off mode
by Vijendar Mukunda 26 Nov '24

26 Nov '24

As per design for power off mode, clear the wake enable register during resume sequence. Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda(a)amd.com> --- drivers/soundwire/amd_manager.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/soundwire/amd_manager.c b/drivers/soundwire/amd_manager.c index 5a4bfaef65fb..96a3aa6da711 100644 --- a/drivers/soundwire/amd_manager.c +++ b/drivers/soundwire/amd_manager.c @@ -1190,6 +1190,7 @@ static int __maybe_unused amd_resume_runtime(struct device *dev) if (amd_manager->power_mode_mask & AMD_SDW_CLK_STOP_MODE) { return amd_sdw_clock_stop_exit(amd_manager); } else if (amd_manager->power_mode_mask & AMD_SDW_POWER_OFF_MODE) { + writel(0x00, amd_manager->acp_mmio + ACP_SW_WAKE_EN(amd_manager->instance)); val = readl(amd_manager->mmio + ACP_SW_CLK_RESUME_CTRL); if (val) { val |= AMD_SDW_CLK_RESUME_REQ; -- 2.34.1

2 1

GoXLR not working in 1.2.13
by GitHub issues - opened 25 Nov '24

25 Nov '24

alsa-project/alsa-ucm-conf issue #473 was opened from AruAki: GoXLR not splitting into multiple channels. `alsaucm -c hw:1 dump text` returns ``` ALSA lib parser.c:270:(parse_syntax_field) Incompatible syntax 7 in USB-Audio.conf ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -22 alsaucm: error failed to open sound card hw:1: Invalid argument ``` Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/473 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[RFC PATCH 0/2] Add support for stacked and parallel memories
by Amit Kumar Mahapatra 25 Nov '24

25 Nov '24

Hello Everyone, Following an email discussion with Miquel regarding the binding changes and overall architecture for implementing support for stacked and parallel memories, I’m sharing this RFC to initiate a discussion on the proposed updates to current bindings and to finalize the implementation architecture. Before diving into the main topic, here is some background on stacked and parallel memories. The AMD QSPI controller supports two advanced connection modes(Stacked and Parallel) which allow the controller to treat two different flashes as one storage. Stacked: Flashes share the same SPI bus, but different CS line, controller driver asserts the CS of the flash to which it needs to communicate. Stacked mode is a software abstraction rather than a controller feature or capability. At any given time, the controller communicates with one of the two connected flash devices, as determined by the requested address and data length. If an operation starts on one flash and ends on the other, the core needs to split it into two separate operations and adjust the data length accordingly. Parallel(Multi-CS): Both the flashes have their separate SPI bus, CS of both the flashes will be asserted/de-asserted at the same time. In this mode data will be split across both the flashes by enabling the STRIPE setting in the controller. Parallel mode is a controller feature where if the STRIPE bit is set then the controller internally handles the data split during data write to the flashes and while reading data from the flash the controller internally merges data from both the flashes before writing to the controller FIFO. If STRIPE is not enabled, then same data will be sent to both the devices. In parallel mode both the flashes should be identical. For more information on the modes please feel free to go through the controller flash interface below [1]. Mirochip QSPI controller[2] also supports "Dual Parallel 8-bit IO mode", but they call it "Twin Quad Mode". Initially in [3] [4] [5] Miquel had tried to extend MTD-CONCAT driver to support Stacked mode, but the bindings were not accepted. So, the MTD-CONCAT approach was dropped and the DT bindings that got accepted [6] [7] [8] that describes the two flash devices as being one. SPI core changes to support the above bindings were added [9]. While adding the support in SPI-NOR Tudor provided additional feedback, leading to a discussion on updating the current stacked and parallel DT bindings. Proposed Solution: The solution has two parts: 1. Update MTD-CONCAT Update MTD-CONCAT to create virtual concatinated mtd devices as defined in the device tree. 2. Add a New Layer Add a new layer between the SPI-NOR and MTD layers to support stacked and parallel configurations. This new layer will be part of spi-nor, located in mtd/spi-nor/, can be included/excluded via Kconfig, will be maintained by AMD and will: - During probing, store information from all connected flashes in stacked or parallel mode and present them as a single device to the MTD layer. - Register callbacks and manage MTD device registration within the new layer instead of spi-nor/core.c. - Make minimal changes in spi-nor/core.c, as stacked and parallel handling will be managed by the new layer on top of SPI-NOR. - Handle odd byte count requests from the MTD layer during flash operations in parallel mode. [1] https://docs.amd.com/r/en-US/am011-versal-acap-trm/QSPI-Flash-Device-Interf… [2] https://ww1.microchip.com/downloads/aemDocuments/documents/MPU32/ProductDoc… [3] https://lore.kernel.org/all/20191113171505.26128-4-miquel.raynal@bootlin.co… [4] https://lore.kernel.org/all/20191127105522.31445-5-miquel.raynal@bootlin.co… [5]https://lore.kernel.org/all/20211112152411.818321-1-miquel.raynal@bootlin… [6] https://github.com/torvalds/linux/commit/f89504300e94524d5d5846ff8b728592ac… [7] https://github.com/torvalds/linux/commit/eba5368503b4291db7819512600fa014ea… [8] https://github.com/torvalds/linux/commit/e2edd1b64f1c79e8abda365149ed62a2a9… [9]https://github.com/torvalds/linux/commit/4d8ff6b0991d5e86b17b235fc46ec62e… Thanks, Amit Amit Kumar Mahapatra (2): dt-bindings: mtd: Add bindings for describing concatinated MTD devices dt-bindings: spi: Update stacked and parallel bindings .../mtd/partitions/fixed-partitions.yaml | 18 +++++++++++++++ .../bindings/mtd/partitions/partitions.yaml | 6 +++++ .../bindings/spi/spi-controller.yaml | 23 +++++++++++++++++-- .../bindings/spi/spi-peripheral-props.yaml | 9 +++----- 4 files changed, 48 insertions(+), 8 deletions(-) -- 2.34.1

6 15