From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Wolfram Sang <wsa@kernel.org>, Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
chrome-platform@lists.linux.dev, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Johan Hovold <johan@kernel.org>, Jiri Kosina <jikos@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v9 0/7] platform/chrome: Introduce DT hardware prober
Date: Thu, 17 Oct 2024 13:00:32 +0300 [thread overview]
Message-ID: <ZxDgQISmr_gn_aDF@smile.fi.intel.com> (raw)
In-Reply-To: <20241017094222.1014936-1-wenst@chromium.org>
On Thu, Oct 17, 2024 at 05:34:35PM +0800, Chen-Yu Tsai wrote:
> For the I2C component (touchscreens and trackpads) case from the
> original series, the hardware prober driver finds the particular
> class of device in the device tree, gets its parent I2C adapter,
> and tries to initiate a simple I2C read for each device under that
> I2C bus. When it finds one that responds, it considers that one
> present, marks it as "okay", and returns, letting the driver core
> actually probe the device.
>
> This works fine in most cases since these components are connected
> via a ribbon cable and always have the same resources. The prober
> will also grab these resources and enable them.
>
> The other case, selecting a display panel to use based on the SKU ID
> from the firmware, hit a bit of an issue with fixing the OF graph.
> It has been left out since v3.
>
> Patch 1 adds of_changeset_update_prop_string(), as requested by Rob.
>
> Patch 2 adds for_each_child_of_node_with_prefix(), as suggested by Andy.
> Patch 3 implements probing the I2C bus for presence of components as
> a hookable helper function in the I2C core.
>
> Patch 4 implements regulator supply support as a set of simple helpers
> for the I2C component prober.
>
> Patch 5 implements GPIO support for the I2C component prober simple
> helpers.
Not that I am really a fan of the idea, but I have nothing to counter propose.
Also my big concern about random msleep() calls seems to be addressed in a way
that it's now a caller's problem to supply the (correct) one.
Hence FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
for patches 3,4, and 5.
> Patch 6 adds a ChromeOS specific DT hardware prober. This initial
> version targets the Hana Chromebooks, probing its I2C trackpads and
> touchscreens.
>
> Patch 7 modifies the Hana device tree and marks the touchscreens
> and trackpads as "fail-needs-probe", ready for the driver to probe.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-17 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:34 [PATCH v9 0/7] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 1/7] of: dynamic: Add of_changeset_update_prop_string Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 2/7] of: base: Add for_each_child_of_node_with_prefix() Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 3/7] i2c: Introduce OF component probe function Chen-Yu Tsai
2024-10-17 9:52 ` Andy Shevchenko
2024-10-17 21:02 ` Doug Anderson
2024-10-17 9:34 ` [PATCH v9 4/7] i2c: of-prober: Add simple helpers for regulator support Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 5/7] i2c: of-prober: Add GPIO support to simple helpers Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 6/7] platform/chrome: Introduce device tree hardware prober Chen-Yu Tsai
2024-10-17 9:34 ` [PATCH v9 7/7] arm64: dts: mediatek: mt8173-elm-hana: Mark touchscreens and trackpads as fail Chen-Yu Tsai
2024-10-17 21:15 ` Doug Anderson
2024-10-28 9:13 ` Chen-Yu Tsai
2024-10-28 15:42 ` Doug Anderson
2024-10-17 10:00 ` Andy Shevchenko [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=ZxDgQISmr_gn_aDF@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jikos@kernel.org \
--cc=johan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=tzungbi@kernel.org \
--cc=wenst@chromium.org \
--cc=wsa@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