From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chanwoo Choi (samsung.com)" <cw00.choi@samsung.com>,
"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for v5.2
Date: Tue, 23 Apr 2019 14:58:09 +0900 [thread overview]
Message-ID: <b3ff314f-194a-a8e1-b4f9-ef281cd9e577@samsung.com> (raw)
In-Reply-To: <CGME20190423055704epcas1p3698d02b077f2e75da943525437363840@epcas1p3.samsung.com>
Dear Greg,
This is extcon-next pull request for v5.2. I add detailed description of
this pull request on below. Please pull extcon with following updates.
[Detailed description for this pull request]
1. Add new extcon-intel-mrfld.c extcon provider driver
- On Intel Merrifield the Basin Cove PMIC provides a feature to detect
the USB connection type. This driver utilizes the feature in order
to support the USB dual role detection.
2. Update the extcon provider drivers
- For extcon-intel-cht-wc.c, make charger detection co-existed
with OTG host mode and enable external charger.
- For intel extcon driver, add common header file (extcon-intel.h)
in order to remove the duplicate definitions.
- For extcon-arizonal.c, disable microphone detection on driver removal.
3.
- Edit comment of extcon_unregister_notifer() to fix a build warning
- Add CONFIG_ACPI dependency to Kconfig to fix a build error for extcon-axp.c
Best Regards,
Chanwoo Choi
The following changes since commit 86baf800de84eb89615c138d368b14bff5ee7d8a:
extcon: ptn5150: fix COMPILE_TEST dependencies (2019-04-05 10:08:37 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-5.2
for you to fetch changes up to 00053de52231117ddc154042549f2256183ffb86:
extcon: arizona: Disable mic detect if running when driver is removed (2019-04-12 09:38:40 +0900)
----------------------------------------------------------------
Andy Shevchenko (2):
extcon: intel: Split out some definitions to a common header
extcon: mrfld: Introduce extcon driver for Basin Cove PMIC
Charles Keepax (1):
extcon: arizona: Disable mic detect if running when driver is removed
Valdis Kletnieks (1):
extcon: Fix build warning for extcon_unregister_notifier comment
Yauhen Kharuzhy (2):
extcon: intel-cht-wc: Make charger detection co-existed with OTG host mode
extcon: intel-cht-wc: Enable external charger
YueHaibing (1):
extcon: axp288: Add a depends on ACPI to the Kconfig entry
drivers/extcon/Kconfig | 9 +-
drivers/extcon/Makefile | 1 +
drivers/extcon/devres.c | 2 +-
drivers/extcon/extcon-arizona.c | 10 ++
drivers/extcon/extcon-intel-cht-wc.c | 81 ++++++++--
drivers/extcon/extcon-intel-mrfld.c | 284 +++++++++++++++++++++++++++++++++++
drivers/extcon/extcon-intel.h | 20 +++
7 files changed, 389 insertions(+), 18 deletions(-)
create mode 100644 drivers/extcon/extcon-intel-mrfld.c
create mode 100644 drivers/extcon/extcon-intel.h
next parent reply other threads:[~2019-04-23 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190423055704epcas1p3698d02b077f2e75da943525437363840@epcas1p3.samsung.com>
2019-04-23 5:58 ` Chanwoo Choi [this message]
2019-04-25 17:51 ` Greg KH
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=b3ff314f-194a-a8e1-b4f9-ef281cd9e577@samsung.com \
--to=cw00.choi@samsung.com \
--cc=chanwoo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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®