From: Hans de Goede <hdegoede@redhat.com>
To: Bard Liao <bardliao@realtek.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Takashi Iwai <tiwai@suse.com>
Subject: rt5645 Jack detect code on an Asus T100HA not being able to distinguish between headphones vs headset ?
Date: Fri, 27 Apr 2018 16:19:24 +0200 [thread overview]
Message-ID: <2cab6fb3-f5b0-948a-8d4f-2e42768d84e8@redhat.com> (raw)
Hi Bard,
I'm having some trouble with the rt5645.c codec code not
being able to distinguish between headphones vs headset
on an Asus T100HA laptop. It recognizes everything as
headphones. This statement in the jack-detect code:
dev_dbg(component->dev, "val = %d\n", val);
Always prints 4 for the value, no matter what I plug in.
Also the headset microphone input does not work, not
even if I select it manually.
The ACPI id for the device is 10EC3270, and I opened the
tablet and the marking on the codec says: ALC3270,
so I guess we may need some special handling for the
jack-detect (and headset microphone input) on this
variant, can you help?
I checked and the jack connector does seem to be of
the TRRS type.
Regards,
Hans
reply other threads:[~2018-04-27 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cab6fb3-f5b0-948a-8d4f-2e42768d84e8@redhat.com \
--to=hdegoede@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).