linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	cw00.choi@samsung.com, chanwoo@kernel.org, cwchoi00@gmail.com,
	함명주 <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for v5.13
Date: Thu, 8 Apr 2021 15:44:35 +0900	[thread overview]
Message-ID: <6b1dea1d-331c-e349-6ff4-14585826cc52@samsung.com> (raw)
In-Reply-To: CGME20210408062703epcas1p22b2d793d4c5f7231964ff258e2ba40e5@epcas1p2.samsung.com

Dear Greg,

This is extcon-next pull request for v5.13. I add detailed description of
this pull request on below. Please pull extcon with following updates.

Best Regards,
Chanwoo Choi


The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:

  Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-5.13

for you to fetch changes up to 7b1222b224aff41739319ae81cd266825464ad8f:

  extcon: qcom-spmi: Add support for VBUS detection (2021-04-08 13:10:16 +0900)

----------------------------------------------------------------

Detailed description for this pull request:

1. Update extcon provider driver
- Add the support of charging interrupt to detect charger connector
for extcon-max8997.c

- Detect OTG when USB_ID pin is connected to ground for extcon-sm5502.c

- Add the support for VBUS detection for extcon-qcom-spmi-misc.c
and replace qcom,pm8941-misc binding document with yaml style.

----------------------------------------------------------------
Anirudh Ghayal (1):
      extcon: qcom-spmi: Add support for VBUS detection

Guru Das Srinagesh (2):
      bindings: pm8941-misc: Convert bindings to YAML
      bindings: pm8941-misc: Add support for VBUS detection

Nikita Travkin (1):
      extcon: sm5502: Detect OTG when USB_ID is connected to ground

Timon Baetz (1):
      extcon: max8997: Add CHGINS and CHGRM interrupt handling

 .../bindings/extcon/qcom,pm8941-misc.txt           | 41 ---------
 .../bindings/extcon/qcom,pm8941-misc.yaml          | 62 ++++++++++++++
 drivers/extcon/extcon-max8997.c                    |  4 +
 drivers/extcon/extcon-qcom-spmi-misc.c             | 99 +++++++++++++++++-----
 drivers/extcon/extcon-sm5502.c                     | 22 ++++-
 5 files changed, 166 insertions(+), 62 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/extcon/qcom,pm8941-misc.txt
 create mode 100644 Documentation/devicetree/bindings/extcon/qcom,pm8941-misc.yaml

       reply	other threads:[~2021-04-08  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210408062703epcas1p22b2d793d4c5f7231964ff258e2ba40e5@epcas1p2.samsung.com>
2021-04-08  6:44 ` Chanwoo Choi [this message]
2021-04-08  6:45   ` [GIT PULL] extcon next for v5.13 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=6b1dea1d-331c-e349-6ff4-14585826cc52@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=chanwoo@kernel.org \
    --cc=cwchoi00@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).