Skip to contentSkip to conversation

ALSA: hda/realtek - Add support for Memeza EDL03 headset mic

PATCH In review Chris Chiu 2 participants 3 messages Dec 7, 2020 – Dec 8, 2020 Sound

lore
Share & tools
lore

Chris Chiu

author
#0 lore raw

PATCH 1/1 ALSA: hda/realtek - Add support for Memeza EDL03 headset mic

The Memeza laptop EDL03 with codec ALC256 can't detect the headset microphone. The headphone jack sensing works after we add a pin definition for it by ALC256_FIXUP_ASUS_MIC_NO_PRESENCE.

---
 sound/pci/hda/patch_realtek.c | 1 +
 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
index d5e4d0ba1008..8b9b94cfc67e 100644
@@ -7871,6 +7871,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
 	SND_PCI_QUIRK(0x10cf, 0x1629, "Lifebook U7x7", ALC255_FIXUP_LIFEBOOK_U7x7_HEADSET_MIC),
 	SND_PCI_QUIRK(0x10cf, 0x1845, "Lifebook U904", ALC269_FIXUP_LIFEBOOK_EXTMIC),
 	SND_PCI_QUIRK(0x10ec, 0x10f2, "Intel Reference board", ALC700_FIXUP_INTEL_REFERENCE),
+	SND_PCI_QUIRK(0x10ec, 0x115a, "Memeza EDL03", ALC256_FIXUP_ASUS_MIC_NO_PRESENCE),
 	SND_PCI_QUIRK(0x10ec, 0x1230, "Intel Reference board", ALC295_FIXUP_CHROME_BOOK),
 	SND_PCI_QUIRK(0x10f7, 0x8338, "Panasonic CF-SZ6", ALC269_FIXUP_HEADSET_MODE),
 	SND_PCI_QUIRK(0x144d, 0xc109, "Samsung Ativ book 9 (NP900X3G)", ALC269_FIXUP_INV_DMIC),
Signature · 1 line
2.20.1
#1 lore raw
Quoted 16 lines · Chris Chiu

The Memeza laptop EDL03 with codec ALC256 can't detect the headset microphone. The headphone jack sensing works after we add a pin definition for it by ALC256_FIXUP_ASUS_MIC_NO_PRESENCE.

---
 sound/pci/hda/patch_realtek.c | 1 +
 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +0 -0
index d5e4d0ba1008..8b9b94cfc67e 100644

sound/pci/hda/patch_realtek.c static const struct snd_pci_quirk alc269_fixup_tbl[] = { · line 7874

Quoted 4 lines
sound/pci/hda/patch_realtek.c +1 -0
@@ -7871,6 +7871,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
 	SND_PCI_QUIRK(0x10cf, 0x1629, "Lifebook U7x7", ALC255_FIXUP_LIFEBOOK_U7x7_HEADSET_MIC),
 	SND_PCI_QUIRK(0x10cf, 0x1845, "Lifebook U904", ALC269_FIXUP_LIFEBOOK_EXTMIC),
 	SND_PCI_QUIRK(0x10ec, 0x10f2, "Intel Reference board", ALC700_FIXUP_INTEL_REFERENCE),
+	SND_PCI_QUIRK(0x10ec, 0x115a, "Memeza EDL03", ALC256_FIXUP_ASUS_MIC_NO_PRESENCE),

This looks suspicious. 10ec is the vendor ID for Realtek, i.e. it implies that the BIOS on this machine didn't give the proper unique ID. As you can see, the other entries with 10ec are only reference boards.

If the newer BIOS still doesn't fix the PCI SSID, you can check the codec SSID instead.

thanks,

Takashi

author
#2 lore raw
Quoted 29 lines · Takashi Iwai
Quoted 16 lines · Chris Chiu

The Memeza laptop EDL03 with codec ALC256 can't detect the headset microphone. The headphone jack sensing works after we add a pin definition for it by ALC256_FIXUP_ASUS_MIC_NO_PRESENCE.

---
 sound/pci/hda/patch_realtek.c | 1 +
 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +0 -0
index d5e4d0ba1008..8b9b94cfc67e 100644

sound/pci/hda/patch_realtek.c static const struct snd_pci_quirk alc269_fixup_tbl[] = { · line 7874

Quoted 4 lines
sound/pci/hda/patch_realtek.c +1 -0
@@ -7871,6 +7871,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
      SND_PCI_QUIRK(0x10cf, 0x1629, "Lifebook U7x7", ALC255_FIXUP_LIFEBOOK_U7x7_HEADSET_MIC),
      SND_PCI_QUIRK(0x10cf, 0x1845, "Lifebook U904", ALC269_FIXUP_LIFEBOOK_EXTMIC),
      SND_PCI_QUIRK(0x10ec, 0x10f2, "Intel Reference board", ALC700_FIXUP_INTEL_REFERENCE),
+     SND_PCI_QUIRK(0x10ec, 0x115a, "Memeza EDL03", ALC256_FIXUP_ASUS_MIC_NO_PRESENCE),

This looks suspicious. 10ec is the vendor ID for Realtek, i.e. it implies that the BIOS on this machine didn't give the proper unique ID. As you can see, the other entries with 10ec are only reference boards.

Quoted 7 lines

If the newer BIOS still doesn't fix the PCI SSID, you can check the codec SSID instead.

thanks,

Takashi

Thanks for the feedback. This is a special case that the ODM didn't flash the DMI information
and assign a formal SSID. They simply ship with the current status w/o any BIOS customization.

I agree that we should push the vendor for a BIOS fix or figure out a generic solution for this
instead of a pin quirk. Please ignore this. Thanks

Chris