Bug 220054 - A fixup for front speakers and mute LED on HP Spectre x360 Convertible 15-df1xxx/863E
Summary: A fixup for front speakers and mute LED on HP Spectre x360 Convertible 15-df1...
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: Intel Linux
: P3 enhancement
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-24 20:47 UTC by sergey.v.dolgov
Modified: 2025-04-27 08:11 UTC (History)
1 user (show)

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


Attachments
patch_realtek.c patch (3.40 KB, patch)
2025-04-24 20:47 UTC, sergey.v.dolgov
Details | Diff

Description sergey.v.dolgov 2025-04-24 20:47:55 UTC
Created attachment 308016 [details]
patch_realtek.c patch

My HP laptop is equipped with a 0x863E board which has a mute LED only, no micmute LEDs, and its ALC285 codec misses the front speakers, in contrast to similar other bug reports. Therefore, none of the existing quirks in sound/pci/hda/patch_realtek.c are entirely suitable. The attached combination enables all speakers and the LED on this board.
Comment 1 Takashi Iwai 2025-04-25 08:39:02 UTC
Thanks for the report and the patch.  The code change looks OK at a quick glance.

Would you submit your patch to the upstream for merging?  Just put the patch description, your Signed-off-by tag, and set a subject with "ALSA: hda/realtek: ....", and submit to linux-sound@vger.kernel.org and put maintainer (me) to Cc.
See Documentation/process/submitting-patches.rst for details.

If you don't want to do it by yourself, I can pick up this and submit from my side, too.
Comment 2 sergey.v.dolgov 2025-04-25 19:25:47 UTC
Err, it may be better if you submit it. I never used git send-email before, and gmail PWA tends to scramble tab symbols which would break the patch. Thanks a lot!
Comment 3 Takashi Iwai 2025-04-27 08:11:58 UTC
OK, now submitted to the upstream:
  https://lore.kernel.org/20250427081035.11567-1-tiwai@suse.de

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