Bug 219345 - Builtin microphone doesn't work on ASUS Vivobook S 15 OLED M3502RA
Summary: Builtin microphone doesn't work on ASUS Vivobook S 15 OLED M3502RA
Status: RESOLVED CODE_FIX
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-10-03 09:51 UTC by luojun853
Modified: 2024-10-11 15:54 UTC (History)
1 user (show)

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


Attachments
acp6x-mach patch (451 bytes, patch)
2024-10-03 09:51 UTC, luojun853
Details | Diff

Description luojun853 2024-10-03 09:51:41 UTC
Created attachment 306953 [details]
acp6x-mach patch

acp6x-mach patch for ASUS Vivobook S 15 OLED M3502RA microphone to work

ASUS Vivobook S15 OLED M3502RA requires a quirk entry for its internal microphone to function.

arecord -l with fix:
**** List of CAPTURE Hardware Devices ****
card 1: Generic_1 [HD-Audio Generic], device 0: ALC294 Analog [ALC294 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 2: ALC294 Alt Analog [ALC294 Alt Analog]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
card 2: acp6x [acp6x], device 0: DMIC capture dmic-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
Comment 1 luojun853 2024-10-05 04:17:26 UTC
I'm not really a kernel developer, so if someone could submit it for me, I'd appreciate it!
Comment 2 Christian Heusel 2024-10-05 17:56:56 UTC
Hey luojun!

With which email/name would you like to be credited for your contribution?
I can also send it in my name, but since you wrote the patch ... :D
Comment 3 luojun853 2024-10-10 11:32:35 UTC
(In reply to Christian Heusel from comment #2)
> Hey luojun!
> 
> With which email/name would you like to be credited for your contribution?
> I can also send it in my name, but since you wrote the patch ... :D

Send it in your name if you can. Thank you.
Comment 5 Christian Heusel 2024-10-11 11:19:10 UTC
The related patch has been applied, this issue can therefore be closed :)

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