Bug 218926 - Microphone does not work on the HP Victus 16-e1xxx
Summary: Microphone does not work on the HP Victus 16-e1xxx
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: AMD Linux
: P3 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-01 12:52 UTC by CuerdOS Dev Team
Modified: 2024-06-01 13:05 UTC (History)
0 users

See Also:
Kernel Version: 6.9.3
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description CuerdOS Dev Team 2024-06-01 12:52:12 UTC
Hello! This is the first time we report to bugzilla.

There was a user who reported us that his microphone was not working, either on our Linux distribution or any other.

This is the information about the laptop model:

01:00.1 Audio device: NVIDIA Corporation Device 2291 (rev a1)
06:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller
06:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 60)
06:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller

**** List of CAPTURE Hardware Devices ****
card 2: Generic_1 [HD-Audio Generic], device 0: ALC245 Analog [ALC245 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: acp6x [acp6x], device 0: DMIC capture dmic-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

The solution we found was to add these lines of code to the file sound/soc/amd/yc/acp6x-mach.c

	{
		.driver_data = &acp6x_card,
		.matches = {
			DMI_MATCH(DMI_BOARD_VENDOR, “HP”),
                        DMI_MATCH(DMI_PRODUCT_NAME, “Victus by HP Laptop 16-e1xxx”),
		}
	},

This way, the microphone works perfectly.

Attached is also the git repo where we have uploaded the Linux kernel 6.9.3 with the solution to the problem:
https://github.com/CuerdOS/linux-kernel-nhs/commit/b29ba27a0ed672664071b4b345e63b62a419d31d#diff-8e067272cb2534f01550437bb3397f9060df95024f779dd5572b308c0dd9e718

Note You need to log in before you can comment on or make changes to this bug.