From: Carlo Caione <carlo@caione.org>
To: linux@endlessm.com, bardliao@realtek.com, oder_chiou@realtek.com,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.com, albertchen@realtek.com, edgar_shen@realtek.com
Cc: Carlo Caione <carlo@endlessm.com>
Subject: [PATCH 0/2] rt5651: Enable jack detection
Date: Thu, 19 Oct 2017 12:03:21 +0100 [thread overview]
Message-ID: <20171019110323.23751-1-carlo@caione.org> (raw)
From: Carlo Caione <carlo@endlessm.com>
Small set of patches to enable jack detection for the rt5651 codec.
Please note that:
- The jack detection is restricted to the JD1_1 pin only (the only
hardware I have uses this pin for jack detection)
- AFAICT (reading the rt5651 datasheet) there is no way to detect
runtime the type of the jack inserted as done for the others rt56*
codecs, so in the driver I always assume that we are dealing with an
headset.
Carlo Caione (2):
ASoC: rt5651: Enable jack detection on JD1_1
ASoC: intel: byt: Add headset jack
include/sound/rt5651.h | 7 +++
sound/soc/codecs/rt5651.c | 91 ++++++++++++++++++++++++++++++++++-
sound/soc/codecs/rt5651.h | 3 ++
sound/soc/intel/boards/bytcr_rt5651.c | 24 +++++++++
4 files changed, 123 insertions(+), 2 deletions(-)
--
2.14.2
next reply other threads:[~2017-10-19 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 11:03 Carlo Caione [this message]
2017-10-19 11:03 ` [PATCH 1/2] ASoC: rt5651: Enable jack detection on JD1_1 Carlo Caione
2017-10-19 15:47 ` [alsa-devel] " Pierre-Louis Bossart
2017-10-19 15:54 ` Carlo Caione
2017-10-20 2:10 ` Bard Liao
2017-10-20 2:23 ` Bard Liao
2017-10-19 11:03 ` [PATCH 2/2] ASoC: intel: byt: Add headset jack Carlo Caione
2017-10-19 15:56 ` Pierre-Louis Bossart
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=20171019110323.23751-1-carlo@caione.org \
--to=carlo@caione.org \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=carlo@endlessm.com \
--cc=edgar_shen@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.intel.com \
--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
all inboxes | Powered by JetHome®