From: Benson Leung <bleung@google.com>
To: Jameson Thies <jthies@google.com>
Cc: akuchynski@chromium.org, abhishekpandit@chromium.org,
krzk+dt@kernel.org, robh@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 3/3] mfd: cros_ec: Don't add cros_ec_ucsi if it is defined in OF or ACPI
Date: Tue, 7 Oct 2025 19:43:40 +0000 [thread overview]
Message-ID: <aOVtbDOl1w4RXEfi@google.com> (raw)
In-Reply-To: <20251001193346.1724998-4-jthies@google.com>
[-- Attachment #1: Type: text/plain, Size: 2920 bytes --]
On Wed, Oct 01, 2025 at 07:33:43PM +0000, Jameson Thies wrote:
> On devices with a UCSI PPM in the EC, check for cros_ec_ucsi to be
> defined in the OF device tree or an ACPI node. If it is defined by
> either OF or ACPI, it does not need to be added as a subdevice of
> cros_ec_dev.
>
> Signed-off-by: Jameson Thies <jthies@google.com>
Reviewed-by: Benson Leung <bleung@chromium.org>
> ---
> drivers/mfd/cros_ec_dev.c | 40 ++++++++++++++++++++++++++++++++++-----
> 1 file changed, 35 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/mfd/cros_ec_dev.c b/drivers/mfd/cros_ec_dev.c
> index dc80a272726b..b0523f6541d2 100644
> --- a/drivers/mfd/cros_ec_dev.c
> +++ b/drivers/mfd/cros_ec_dev.c
> @@ -5,6 +5,7 @@
> * Copyright (C) 2014 Google, Inc.
> */
>
> +#include <linux/acpi.h>
> #include <linux/dmi.h>
> #include <linux/kconfig.h>
> #include <linux/mfd/core.h>
> @@ -131,11 +132,6 @@ static const struct cros_feature_to_cells cros_subdevices[] = {
> .mfd_cells = cros_ec_rtc_cells,
> .num_cells = ARRAY_SIZE(cros_ec_rtc_cells),
> },
> - {
> - .id = EC_FEATURE_UCSI_PPM,
> - .mfd_cells = cros_ec_ucsi_cells,
> - .num_cells = ARRAY_SIZE(cros_ec_ucsi_cells),
> - },
> {
> .id = EC_FEATURE_HANG_DETECT,
> .mfd_cells = cros_ec_wdt_cells,
> @@ -177,6 +173,16 @@ static const struct mfd_cell cros_ec_vbc_cells[] = {
> { .name = "cros-ec-vbc", }
> };
>
> +static int ucsi_acpi_match(struct device *dev, const void *data)
> +{
> + struct acpi_device_id ucsi_acpi_device_ids[] = {
> + { "GOOG0021", 0 },
> + {"", 0},
> + };
> + return !!acpi_match_device(ucsi_acpi_device_ids, dev);
> +}
> +
> +
> static void cros_ec_class_release(struct device *dev)
> {
> kfree(to_cros_ec_dev(dev));
> @@ -264,6 +270,30 @@ static int ec_device_probe(struct platform_device *pdev)
> }
> }
>
> + /*
> + * FW nodes can load cros_ec_ucsi, but early PDC devices did not define
> + * the required nodes. On PDC systems without FW nodes for cros_ec_ucsi,
> + * the driver should be added as an mfd subdevice.
> + */
> + if (cros_ec_check_features(ec, EC_FEATURE_USB_PD) &&
> + cros_ec_check_features(ec, EC_FEATURE_UCSI_PPM)) {
> + struct device *acpi_dev = device_find_child(ec->ec_dev->dev,
> + NULL,
> + ucsi_acpi_match);
> +
> + if (!!acpi_dev) {
> + put_device(acpi_dev);
> + } else if (!of_find_compatible_node(NULL, NULL,
> + "google,cros-ec-ucsi")) {
> + retval = mfd_add_hotplug_devices(
> + ec->dev, cros_ec_ucsi_cells,
> + ARRAY_SIZE(cros_ec_ucsi_cells));
> + if (retval)
> + dev_warn(ec->dev,
> + "failed to add cros_ec_ucsi: %d\n", retval);
> + }
> + }
> +
> /*
> * UCSI provides power supply information so we don't need to separately
> * load the cros_usbpd_charger driver.
> --
> 2.51.0.618.g983fd99d29-goog
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-07 19:43 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
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 [this message]
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=aOVtbDOl1w4RXEfi@google.com \
--to=bleung@google.com \
--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=robh@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 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).