From: Amit Sunil Dhamne via B4 Relay <devnull+amitsd.google.com@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Badhri Jagan Sridharan <badhri@google.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, Kyle Tso <kyletso@google.com>,
RD Babiera <rdbabiera@google.com>,
Amit Sunil Dhamne <amitsd@google.com>
Subject: [PATCH 0/2] Introduce Sink Cap Extended AMS
Date: Wed, 11 Feb 2026 23:25:34 +0000 [thread overview]
Message-ID: <20260211-skedb-v1-0-616340426cdc@google.com> (raw)
This patchset adds support for Sink Cap Extended AMS. This is a
"required" AMS for PD 3.1 compliance for Sink or DRP ports and a
pre-requisite for Battery Caps and Battery Status AMSes.
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
---
Amit Sunil Dhamne (2):
dt-bindings: connector: Add sink properties to comply with PD 3.1 spec
usb: typec: tcpm: add support for Sink Cap Extended msg response
.../bindings/connector/usb-connector.yaml | 34 +++
.../devicetree/bindings/usb/maxim,max33359.yaml | 4 +
drivers/usb/typec/tcpm/tcpm.c | 253 ++++++++++++++++++++-
include/dt-bindings/usb/pd.h | 18 ++
include/linux/usb/pd.h | 82 ++++++-
5 files changed, 388 insertions(+), 3 deletions(-)
---
base-commit: 8dfce8991b95d8625d0a1d2896e42f93b9d7f68d
change-id: 20260210-skedb-5aebb944c35f
Best regards,
--
Amit Sunil Dhamne <amitsd@google.com>
next reply other threads:[~2026-02-11 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 23:25 Amit Sunil Dhamne via B4 Relay [this message]
2026-02-11 23:25 ` [PATCH 1/2] dt-bindings: connector: Add sink properties to comply with PD 3.1 spec Amit Sunil Dhamne via B4 Relay
2026-02-23 17:44 ` Rob Herring (Arm)
2026-02-11 23:25 ` [PATCH 2/2] usb: typec: tcpm: add support for Sink Cap Extended msg response Amit Sunil Dhamne via B4 Relay
2026-02-12 3:56 ` kernel test robot
2026-02-12 4:30 ` Amit Sunil Dhamne
2026-02-12 5:09 ` kernel test robot
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=20260211-skedb-v1-0-616340426cdc@google.com \
--to=devnull+amitsd.google.com@kernel.org \
--cc=amitsd@google.com \
--cc=badhri@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.com \
--cc=robh@kernel.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