From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Wolfram Sang <wsa@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
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>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c@vger.kernel.org,
Andrey Skvortsov <andrej.skvortzov@gmail.com>
Subject: Re: [PATCH v11 5/7] i2c: of-prober: Add GPIO support to simple helpers
Date: Thu, 14 Nov 2024 11:37:00 +0100 [thread overview]
Message-ID: <7d9abefa-6400-424f-9cf5-439f4400a168@collabora.com> (raw)
In-Reply-To: <20241106093335.1582205-6-wenst@chromium.org>
Il 06/11/24 10:33, Chen-Yu Tsai ha scritto:
> Add GPIO support to the simple helpers for the I2C OF component prober.
> Components that the prober intends to probe likely require their
> regulator supplies be enabled, and GPIOs be toggled to enable them or
> bring them out of reset before they will respond to probe attempts.
> Regulator supplies were handled in the previous patch.
>
> The assumption is that the same class of components to be probed are
> always connected in the same fashion with the same regulator supply
> and GPIO. The names may vary due to binding differences, but the
> physical layout does not change.
>
> This supports at most one GPIO pin. The user must specify the GPIO name,
> the polarity, and the amount of time to wait after the GPIO is toggled.
> Devices with more than one GPIO pin likely require specific power
> sequencing beyond what generic code can easily support.
>
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2024-11-14 10:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:33 [PATCH v11 0/7] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-11-06 9:33 ` [PATCH v11 1/7] of: dynamic: Add of_changeset_update_prop_string Chen-Yu Tsai
2024-11-14 10:37 ` AngeloGioacchino Del Regno
2024-11-06 9:33 ` [PATCH v11 2/7] of: base: Add for_each_child_of_node_with_prefix() Chen-Yu Tsai
2024-11-14 10:37 ` AngeloGioacchino Del Regno
2024-11-06 9:33 ` [PATCH v11 3/7] i2c: Introduce OF component probe function Chen-Yu Tsai
2024-11-14 10:37 ` AngeloGioacchino Del Regno
2024-11-06 9:33 ` [PATCH v11 4/7] i2c: of-prober: Add simple helpers for regulator support Chen-Yu Tsai
2024-11-14 10:37 ` AngeloGioacchino Del Regno
2024-11-06 9:33 ` [PATCH v11 5/7] i2c: of-prober: Add GPIO support to simple helpers Chen-Yu Tsai
2024-11-08 15:33 ` Andrey Skvortsov
2024-11-14 10:37 ` AngeloGioacchino Del Regno [this message]
2024-11-06 9:33 ` [PATCH v11 6/7] platform/chrome: Introduce device tree hardware prober Chen-Yu Tsai
2024-11-14 10:36 ` AngeloGioacchino Del Regno
2024-11-06 9:33 ` [PATCH v11 7/7] arm64: dts: mediatek: mt8173-elm-hana: Mark touchscreens and trackpads as fail Chen-Yu Tsai
2024-11-14 10:36 ` AngeloGioacchino Del Regno
2024-11-25 8:01 ` Chen-Yu Tsai
2024-11-25 9:52 ` AngeloGioacchino Del Regno
2024-11-27 3:49 ` [PATCH v11 0/7] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-11-27 11:16 ` Wolfram Sang
2024-11-28 4:57 ` Chen-Yu Tsai
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=7d9abefa-6400-424f-9cf5-439f4400a168@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=andrej.skvortzov@gmail.com \
--cc=andriy.shevchenko@linux.intel.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