From: Andrey Skvortsov <andrej.skvortzov@gmail.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>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v10 5/7] i2c: of-prober: Add GPIO support to simple helpers
Date: Tue, 5 Nov 2024 19:13:59 +0300 [thread overview]
Message-ID: <ZypER5bqLAlH7VxK@skv.local> (raw)
In-Reply-To: <20241030072229.1013235-6-wenst@chromium.org>
On 24-10-30 15:22, Chen-Yu Tsai wrote:
> 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>
> ---
> diff --git a/include/linux/i2c-of-prober.h b/include/linux/i2c-of-prober.h
> index df95aa6ad90e..a232f3cbb252 100644
> --- a/include/linux/i2c-of-prober.h
> +++ b/include/linux/i2c-of-prober.h
> @@ -85,6 +85,7 @@ int i2c_of_probe_component(struct device *dev, const struct i2c_of_probe_cfg *cf
> *
> * The following helpers are provided:
> * * i2c_of_probe_simple_enable()
> + * * i2c_of_probe_simple_cleanup_early()
> * * i2c_of_probe_simple_cleanup()
> */
>
> @@ -92,14 +93,31 @@ int i2c_of_probe_component(struct device *dev, const struct i2c_of_probe_cfg *cf
> * struct i2c_of_probe_simple_opts - Options for simple I2C component prober callbacks
> * @res_node_compatible: Compatible string of device node to retrieve resources from.
> * @supply_name: Name of regulator supply.
> + * @gpio_name: Name of GPIO. NULL if no GPIO line is used. Empty string ("") if GPIO
> + * line is unnamed.
> * @post_power_on_delay_ms: Delay after regulators are powered on. Passed to msleep().
> + * @post_gpio_config_delay_ms: Delay after GPIO is configured. Passed to msleep().
> + * @gpio_assert_to_enable: %true if GPIO should be asserted, i.e. set to logical high,
> + * to enable the component.
> + *
> + * This describes power sequences common for the class of components supported by the
> + * simple component prober:
> + * * @gpio_name is configured to the non-active setting according to @gpio_assert_to_enable.
> + * * @supply_name regulator supply is enabled.
> + * * Wait for @post_power_on_delay_ms to pass.
> + * * @gpio_name is configured to the active setting according to @gpio_assert_to_enable.
> + * * Wait for @post_gpio_config_delay_ms to pass.
> */
> struct i2c_of_probe_simple_opts {
> const char *res_node_compatible;
> const char *supply_name;
> + const char *gpio_name;
> unsigned int post_power_on_delay_ms;
> + unsigned int post_gpio_config_delay_ms;
> + bool gpio_assert_to_enable;
This header is missing '#include <linux/types.h>' for bool
type. Otherwise compilation may fail with following error:
```
./include/linux/i2c-of-prober.h:117:9: error: unknown type name ‘bool’
117 | bool gpio_assert_to_enable;
| ^~~~
./include/linux/i2c-of-prober.h:12:1: note: ‘bool’ is defined in header ‘<stdbool.h>’; this is probably fixable by adding ‘#include <stdbool.h>’
11 | #include <linux/kconfig.h>
+++ |+#include <stdbool.h>
12 |
```
> };
>
> +struct gpio_desc;
> struct regulator;
>
> struct i2c_of_probe_simple_ctx {
> @@ -107,9 +125,11 @@ struct i2c_of_probe_simple_ctx {
> const struct i2c_of_probe_simple_opts *opts;
> /* private: internal fields for helpers. */
> struct regulator *supply;
> + struct gpio_desc *gpiod;
> };
>
> int i2c_of_probe_simple_enable(struct device *dev, struct device_node *bus_node, void *data);
> +void i2c_of_probe_simple_cleanup_early(struct device *dev, void *data);
> void i2c_of_probe_simple_cleanup(struct device *dev, void *data);
>
> extern struct i2c_of_probe_ops i2c_of_probe_simple_ops;
> --
> 2.47.0.163.g1226f6d8fa-goog
>
--
Best regards,
Andrey Skvortsov
next prev parent reply other threads:[~2024-11-05 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 7:22 [PATCH v10 0/7] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 1/7] of: dynamic: Add of_changeset_update_prop_string Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 2/7] of: base: Add for_each_child_of_node_with_prefix() Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 3/7] i2c: Introduce OF component probe function Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 4/7] i2c: of-prober: Add simple helpers for regulator support Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 5/7] i2c: of-prober: Add GPIO support to simple helpers Chen-Yu Tsai
2024-11-05 16:13 ` Andrey Skvortsov [this message]
2024-11-06 8:12 ` Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 6/7] platform/chrome: Introduce device tree hardware prober Chen-Yu Tsai
2024-10-30 7:22 ` [PATCH v10 7/7] arm64: dts: mediatek: mt8173-elm-hana: Mark touchscreens and trackpads as fail 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=ZypER5bqLAlH7VxK@skv.local \
--to=andrej.skvortzov@gmail.com \
--cc=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