From: Rob Herring <robh@kernel.org>
To: Jameson Thies <jthies@google.com>
Cc: akuchynski@chromium.org, abhishekpandit@chromium.org,
krzk+dt@kernel.org, bleung@chromium.org,
heikki.krogerus@linux.intel.com, ukaszb@chromium.org,
tzungbi@kernel.org, devicetree@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: chrome: Add Cros EC UCSI driver
Date: Wed, 8 Oct 2025 11:03:54 -0500 [thread overview]
Message-ID: <20251008160354.GA3764744-robh@kernel.org> (raw)
In-Reply-To: <20251001193346.1724998-2-jthies@google.com>
On Wed, Oct 01, 2025 at 07:33:41PM +0000, Jameson Thies wrote:
> Chrome OS devices with PDCs allow the host to read port status and
> control port behavior with UCSI commands sent to the embedded controller
> (EC). Add documentation for cros-ec-ucsi node which loads the Chrome OS
> UCSI driver.
What's PDC? What's UCSI?
>
> Signed-off-by: Jameson Thies <jthies@google.com>
> ---
> .../bindings/chrome/google,cros-ec-ucsi.yaml | 71 +++++++++++++++++++
> .../bindings/mfd/google,cros-ec.yaml | 4 +-
> 2 files changed, 74 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-ec-ucsi.yaml
>
> diff --git a/Documentation/devicetree/bindings/chrome/google,cros-ec-ucsi.yaml b/Documentation/devicetree/bindings/chrome/google,cros-ec-ucsi.yaml
> new file mode 100644
> index 000000000000..2121776e3ff0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/chrome/google,cros-ec-ucsi.yaml
> @@ -0,0 +1,71 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/chrome/google,cros-ec-ucsi.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Google Chrome OS EC(Embedded Controller) UCSI driver.
> +
> +maintainers:
> + - Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
> + - Andrei Kuchynski <akuchynski@chromium.org>
> + - Benson Leung <bleung@chromium.org>
> + - Jameson Thies <jthies@google.com>
> + - Łukasz Bartosik <ukaszb@chromium.org>
> +
> +description:
> + Chrome OS devices with PDC-based USB-C ports expose a UCSI interface
> + from the Embedded Controller (EC) which allows the host to request
> + port state and control limited port behavior (DR/PR swap). This node
> + allows the host UCSI driver to send and receive UCSI commands to a
> + Chrome OS EC. The node for this device should be under a cros-ec node
> + like google,cros-ec-spi.
> +
> +properties:
> + compatible:
> + const: google,cros-ec-ucsi
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> +patternProperties:
> + '^connector@[0-9a-f]+$':
> + $ref: /schemas/connector/usb-connector.yaml#
> + required:
> + - reg
This is the exact same binding as google,cros-ec-typec.yaml. Why are you
duplicating the whole thing rather than just adding a new compatible
string?
Rob
next prev parent reply other threads:[~2025-10-08 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 19:33 [PATCH v2 0/3] Load cros_ec_ucsi from OF and ACPI definitions Jameson Thies
2025-10-01 19:33 ` [PATCH v2 1/3] dt-bindings: chrome: Add Cros EC UCSI driver Jameson Thies
2025-10-07 19:23 ` Benson Leung
2025-10-08 16:03 ` Rob Herring [this message]
2025-10-08 20:25 ` Jameson Thies
2025-10-01 19:33 ` [PATCH v2 2/3] usb: typec: cros_ec_ucsi: Load driver from OF and ACPI definitions Jameson Thies
2025-10-07 19:24 ` Benson Leung
2025-10-08 11:51 ` Heikki Krogerus
2025-10-01 19:33 ` [PATCH v2 3/3] mfd: cros_ec: Don't add cros_ec_ucsi if it is defined in OF or ACPI Jameson Thies
2025-10-07 19:43 ` Benson Leung
2025-10-08 12:10 ` Heikki Krogerus
2025-10-08 23:34 ` Jameson Thies
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=20251008160354.GA3764744-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=devicetree@vger.kernel.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 \
--cc=tzungbi@kernel.org \
--cc=ukaszb@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.