From: Jameson Thies <jthies@google.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: akuchynski@chromium.org, abhishekpandit@chromium.org,
krzk+dt@kernel.org, robh@kernel.org, bleung@chromium.org,
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: Wed, 8 Oct 2025 16:34:54 -0700 [thread overview]
Message-ID: <CAMFSARfn_ULu2+JXjGSjz4KPDOSD=MAcKS8XwZNqbHf7YL6JBg@mail.gmail.com> (raw)
In-Reply-To: <aOZUq6K8bZtciL6Q@kuha.fi.intel.com>
> If you are not using that for anything, then couldn't you just use
> acpi_dev_found("GOOG0021") ?
Thanks, this is a good suggestion. I'll switch to acpi_dev_found() in
the v3 update.
> Can there be multiple UCSI interfaces on these systems?
None of our devices will support multiple UCSI interfaces.
prev parent reply other threads:[~2025-10-08 23:35 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
2025-10-08 12:10 ` Heikki Krogerus
2025-10-08 23:34 ` Jameson Thies [this message]
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='CAMFSARfn_ULu2+JXjGSjz4KPDOSD=MAcKS8XwZNqbHf7YL6JBg@mail.gmail.com' \
--to=jthies@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=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).