From: Badhri Jagan Sridharan <badhri@google.com>
To: Guenter Roeck <linux@roeck-us.net>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Thierry Reding <treding@nvidia.com>,
Prashant Malani <pmalani@chromium.org>,
Badhri Jagan Sridharan <badhri@google.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [PATCH v12 00/10] TCPM support for FRS and AutoDischarge Disconnect
Date: Wed, 28 Oct 2020 23:31:28 -0700 [thread overview]
Message-ID: <20201029063138.1429760-1-badhri@google.com> (raw)
Hi all,
Addressed two comments in the series
1. From Rob Herring: Maxim parts are generally named 'maxim,max[0-9]+'
https://lkml.org/lkml/2020/10/26/503
Changed all occurences of maxim,33359 to maxim,max33359.
2. Added a new patch to address warnings reported by Kernel test robot.
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2354139.html
usb: typec: tcpci_maxim: Fix smatch warnings
Heikki, now that Rob has reviewed the dts patches, the following patches
are ready to be reviewed as well:
usb: typec: tcpci_maxim: Fix the compatible string
usb: typec: tcpm: Refactor logic for new-source-frs-typec-current
Greatly appreciate all of your support reviewing the code.
Thanks,
Badhri.
Badhri Jagan Sridharan (10):
dt-bindings: usb: Maxim type-c controller device tree binding document
usb: typec: tcpci_maxim: Fix the compatible string
usb: typec: tcpm: Refactor logic for new-source-frs-typec-current
usb: typec: tcpm: frs sourcing vbus callback
usb: typec: tcpci: frs sourcing vbus callback
usb: typec: tcpci_maxim: Fix vbus stuck on upon diconnecting sink
usb: typec: tcpm: Implement enabling Auto Discharge disconnect support
usb: typec: tcpci: Implement Auto discharge disconnect callbacks
usb: typec: tcpci_maxim: Enable auto discharge disconnect
usb: typec: tcpci_maxim: Fix smatch warnings
.../bindings/usb/maxim,max33359.yaml | 75 ++++++++++++++++
drivers/usb/typec/tcpm/tcpci.c | 72 ++++++++++++++-
drivers/usb/typec/tcpm/tcpci.h | 18 +++-
drivers/usb/typec/tcpm/tcpci_maxim.c | 35 ++++----
drivers/usb/typec/tcpm/tcpm.c | 87 ++++++++++++++++---
include/linux/usb/tcpm.h | 19 ++++
6 files changed, 274 insertions(+), 32 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/maxim,max33359.yaml
base-commit: aee9ddb1d3718d3ba05b50c51622d7792ae749c9
--
2.29.1.341.ge80a0c044ae-goog
next reply other threads:[~2020-10-29 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 6:31 Badhri Jagan Sridharan [this message]
2020-10-29 6:31 ` [PATCH v12 01/10] dt-bindings: usb: Maxim type-c controller device tree binding document Badhri Jagan Sridharan
2020-10-29 15:33 ` Rob Herring
2020-10-29 20:01 ` Badhri Jagan Sridharan
2020-11-06 10:45 ` Greg Kroah-Hartman
2020-10-29 6:31 ` [PATCH v12 02/10] usb: typec: tcpci_maxim: Fix the compatible string Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 03/10] usb: typec: tcpm: Refactor logic for new-source-frs-typec-current Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 04/10] usb: typec: tcpm: frs sourcing vbus callback Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 05/10] usb: typec: tcpci: " Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 06/10] usb: typec: tcpci_maxim: Fix vbus stuck on upon diconnecting sink Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 07/10] usb: typec: tcpm: Implement enabling Auto Discharge disconnect support Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 08/10] usb: typec: tcpci: Implement Auto discharge disconnect callbacks Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 09/10] usb: typec: tcpci_maxim: Enable auto discharge disconnect Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 10/10] usb: typec: tcpci_maxim: Fix uninitialized return variable Badhri Jagan Sridharan
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=20201029063138.1429760-1-badhri@google.com \
--to=badhri@google.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mripard@kernel.org \
--cc=pmalani@chromium.org \
--cc=robh+dt@kernel.org \
--cc=treding@nvidia.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