From: Fletcher Woodruff <fletcherw@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Fletcher Woodruff <fletcherw@chromium.org>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Oder Chiou <oder_chiou@realtek.com>,
Takashi Iwai <tiwai@suse.com>,
Curtis Malainey <cujomalainey@chromium.org>,
Ross Zwisler <zwisler@chromium.org>,
alsa-devel@alsa-project.org
Subject: [PATCH v6 0/4] Fix jack detection for Chromebook Pixel
Date: Wed, 5 Jun 2019 16:24:15 -0600 [thread overview]
Message-ID: <20190605222419.54479-1-fletcherw@chromium.org> (raw)
In-Reply-To: <20190507220115.90395-1-fletcherw@chromium.org>
Headphone/mic jack detection doesn't work on the Chromebook Pixel 2015.
This patch changes the irq implementation to support polarity flipping
and fixes the configuration code so that correct GPIO pins are read
from ACPI.
With this series, plugging and unplugging the headphone jack switches
between headphones and speakers automatically, and headset microphones
are also detected.
v6:
- Move refactoring into its own patch
- Reorder patches so that DT property names patch is first
- Clarify commit message for patch which implements irq handler
- Remove unused work struct
- Make IRQ function return IRQ_HANDLED only if IRQs actually fire
v5:
- Fix void* parameter to devm_request_threaded_irq
v4:
- Fix incorrect void* cast in rt5677_irq()
v3:
- Update commit message for patch 1/3 to clarify why we implement
our own irq_chip.
v2:
- Split IRQ change into two patches: adding and fixing potential race
- Change config reading code to try both DT and ACPI style names
Ben Zhang (2):
ASoC: rt5677: clear interrupts by polarity flip
ASoC: rt5677: handle concurrent interrupts
Fletcher Woodruff (2):
ASoC: rt5677: fall back to DT prop names on error
ASoC: rt5677: move jack-detect init to i2c probe
sound/soc/codecs/rt5677.c | 317 ++++++++++++++++++++++++++------------
sound/soc/codecs/rt5677.h | 13 +-
2 files changed, 234 insertions(+), 96 deletions(-)
--
2.22.0.rc1.311.g5d7573a151-goog
next prev parent reply other threads:[~2019-06-05 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 22:01 [PATCH v5 0/3] Fix jack detection for Chromebook Pixel Fletcher Woodruff
2019-05-07 22:01 ` [PATCH v5 1/3] ASoC: rt5677: allow multiple interrupt sources Fletcher Woodruff
2019-05-08 7:36 ` Mark Brown
2019-05-08 21:39 ` Curtis Malainey
2019-05-09 2:32 ` Mark Brown
2019-05-09 21:25 ` Curtis Malainey
2019-05-07 22:01 ` [PATCH v5 2/3] ASoC: rt5677: handle concurrent interrupts Fletcher Woodruff
2019-05-07 22:01 ` [PATCH v5 3/3] ASoC: rt5677: fall back to DT prop names on error Fletcher Woodruff
2019-05-08 9:04 ` Mark Brown
2019-06-05 22:24 ` Fletcher Woodruff [this message]
2019-06-05 22:24 ` [PATCH v6 1/4] " Fletcher Woodruff
2019-06-05 22:24 ` [PATCH v6 2/4] ASoC: rt5677: move jack-detect init to i2c probe Fletcher Woodruff
2019-06-05 22:24 ` [PATCH v6 3/4] ASoC: rt5677: clear interrupts by polarity flip Fletcher Woodruff
2019-06-05 22:24 ` [PATCH v6 4/4] ASoC: rt5677: handle concurrent interrupts Fletcher Woodruff
2019-06-14 18:43 [PATCH v6 0/4] Fix jack detection for Chromebook Pixel Fletcher Woodruff
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=20190605222419.54479-1-fletcherw@chromium.org \
--to=fletcherw@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zwisler@chromium.org \
/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).