[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fciyxaedvyqeppldl26rsy7hogoi2zks6tq6m2yu5xerfjxo3g@u6vzsiicv5ke>
Date: Sat, 11 Oct 2025 04:22:09 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Jameson Thies <jthies@...gle.com>
Cc: akuchynski@...omium.org, abhishekpandit@...omium.org, krzk+dt@...nel.org,
robh@...nel.org, bleung@...omium.org, heikki.krogerus@...ux.intel.com,
ukaszb@...omium.org, tzungbi@...nel.org, devicetree@...r.kernel.org,
chrome-platform@...ts.linux.dev, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/3] usb: typec: cros_ec_ucsi: Load driver from OF and
ACPI definitions
On Fri, Oct 10, 2025 at 05:10:13PM -0700, Jameson Thies wrote:
> Hi Dmitry,
> on early ChromeOS devices using this driver it gets added as a
> subdevice of the cros_ec_dev mfd. But, we want to change this to load
> the device from OF/ACPI nodes. The issue here is that older devices
> which don't define the OF/ACPI nodes to load cros_ec_ucsi will still
> need to add the device through cros_ec_dev.
IIRC, MFD devices support binding subdevices to the OF nodes. Do you
plan to use it? Could you possibly point out the example DTs?
>
> So cros_ec_ucsi needs to support multiple methods of being
> instantiated, and going through cros_ec_dev creates an intermediary
> device in the path which doesn't exist when the driver is loaded
> through OF/ACPI. I'll add a comment explaining this in the v4 series.
--
With best wishes
Dmitry
Powered by blists - more mailing lists