From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jameson Thies <jthies@google.com>
Cc: abhishekpandit@chromium.org, akuchynski@chromium.org,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
bleung@chromium.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, heikki.krogerus@linux.intel.com,
linux-usb@vger.kernel.org, krzk+dt@kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v1 1/2] dt-bindings: chrome: Add cros-ec-ucsi compatibility to typec binding
Date: Mon, 6 Apr 2026 17:49:48 -0500 [thread overview]
Message-ID: <177551578813.60654.5045933666200538178.robh@kernel.org> (raw)
In-Reply-To: <20260403223357.1896403-2-jthies@google.com>
On Fri, 03 Apr 2026 22:33:26 +0000, Jameson Thies wrote:
> Chrome OS devices with discrete power delivery controllers (PDCs) allow
> the host to read port status and control port behavior through a USB
> Type-C Connector System Software (UCSI) interface with the embedded
> controller (EC). This uses a separate interface driver than other
> Chrome OS devices with a Type-C port manager in the EC FW. Those use
> a host command interface supported by cros-ec-typec. Add a cros-ec-ucsi
> compatibility string to the existing cros-ec-typec binding.
>
> Additionally, update maintainer list to reflect cros-ec-ucsi and
> cros-ec-typec driver maintainers.
>
> Signed-off-by: Jameson Thies <jthies@google.com>
> ---
> .../bindings/chrome/google,cros-ec-typec.yaml | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-04-06 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 22:33 [PATCH v1 0/2] Load cros_ec_ucsi from OF and ACPI nodes Jameson Thies
2026-04-03 22:33 ` [PATCH v1 1/2] dt-bindings: chrome: Add cros-ec-ucsi compatibility to typec binding Jameson Thies
2026-04-03 22:45 ` Benson Leung
2026-04-06 22:49 ` Rob Herring (Arm) [this message]
2026-04-03 22:33 ` [PATCH v1 2/2] usb: typec: cros_ec_ucsi: Load driver from OF and ACPI definitions Jameson Thies
2026-04-03 22:47 ` Benson Leung
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=177551578813.60654.5045933666200538178.robh@kernel.org \
--to=robh@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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