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>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
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 v7 08/10] i2c: of-prober: Add GPIO support to simple helpers
Date: Fri, 13 Sep 2024 13:52:46 +0300 [thread overview]
Message-ID: <ZuQZfvqGii9fcH-j@smile.fi.intel.com> (raw)
In-Reply-To: <20240911072751.365361-9-wenst@chromium.org>
On Wed, Sep 11, 2024 at 03:27:46PM +0800, 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.
...
> +static int i2c_of_probe_simple_get_gpiod(struct device *dev, struct device_node *node,
> + struct i2c_of_probe_simple_ctx *ctx)
> +{
> + struct fwnode_handle *fwnode = of_fwnode_handle(node);
> + struct gpio_desc *gpiod;
> + const char *con_id = NULL;
> +
> + /* NULL signals no GPIO needed */
> + if (!ctx->opts->gpio_name)
> + return 0;
> +
> + /* An empty string signals an unnamed GPIO */
> + if (strlen(ctx->opts->gpio_name))
You run for entire string in order to check the first byte only?
if (ctx->opts->gpio_name[0] == '\0')
con_id = NULL;
else
> + con_id = ctx->opts->gpio_name;
Also note, that comment is given in inverted condition to what you actually do
in the code. With my suggestion it looks better.
> + gpiod = fwnode_gpiod_get_index(fwnode, con_id, 0, GPIOD_ASIS, "i2c-of-prober");
> + if (IS_ERR(gpiod))
> + return PTR_ERR(gpiod);
> +
> + ctx->gpiod = gpiod;
> +
> + return 0;
> +}
...
> +static int i2c_of_probe_simple_set_gpio(struct device *dev, struct i2c_of_probe_simple_ctx *ctx)
> +{
> + int ret;
> +
> + if (!ctx->gpiod)
> + return 0;
> + dev_dbg(dev, "Setting GPIO\n");
> + ret = gpiod_direction_output_raw(ctx->gpiod, ctx->opts->gpio_high_to_enable ? 1 : 0);
Hmm... _raw() in use... Perhaps it's on a territory of Bart and Linus to review
and comment on this.
> + if (ret)
> + return ret;
> +
> + msleep(ctx->opts->post_reset_deassert_delay_ms);
> +
> + return 0;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-13 10:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 7:27 [PATCH v7 00/10] platform/chrome: Introduce DT hardware prober Chen-Yu Tsai
2024-09-11 7:27 ` [PATCH v7 01/10] of: dynamic: Add of_changeset_update_prop_string Chen-Yu Tsai
2024-09-11 7:27 ` [PATCH v7 02/10] of: base: Add for_each_child_of_node_with_prefix() Chen-Yu Tsai
2024-09-12 20:31 ` Rob Herring (Arm)
2024-09-11 7:27 ` [PATCH v7 03/10] regulator: Split up _regulator_get() Chen-Yu Tsai
2024-09-13 10:27 ` Andy Shevchenko
2024-09-11 7:27 ` [PATCH v7 04/10] regulator: Add of_regulator_get_optional() for pure DT regulator lookup Chen-Yu Tsai
2024-09-11 7:27 ` [PATCH v7 05/10] i2c: core: Remove extra space in Makefile Chen-Yu Tsai
2024-09-13 14:59 ` Andi Shyti
2024-09-11 7:27 ` [PATCH v7 06/10] i2c: Introduce OF component probe function Chen-Yu Tsai
2024-09-13 10:25 ` Andy Shevchenko
2024-09-15 10:44 ` Chen-Yu Tsai
2024-09-16 10:36 ` Andy Shevchenko
2024-09-16 10:55 ` Jonathan Cameron
2024-09-16 14:59 ` Chen-Yu Tsai
2024-09-16 15:22 ` Andy Shevchenko
2024-09-13 23:43 ` Doug Anderson
2024-09-15 11:32 ` Chen-Yu Tsai
2024-09-16 14:15 ` Doug Anderson
2024-09-16 14:31 ` Chen-Yu Tsai
2024-09-16 10:13 ` Andy Shevchenko
2024-09-15 10:09 ` Andrey Skvortsov
2024-09-11 7:27 ` [PATCH v7 07/10] i2c: of-prober: Add simple helpers for regulator support Chen-Yu Tsai
2024-09-13 10:46 ` Andy Shevchenko
2024-09-13 23:43 ` Doug Anderson
2024-09-11 7:27 ` [PATCH v7 08/10] i2c: of-prober: Add GPIO support to simple helpers Chen-Yu Tsai
2024-09-13 10:52 ` Andy Shevchenko [this message]
2024-09-13 23:43 ` Doug Anderson
2024-09-17 12:41 ` Chen-Yu Tsai
2024-09-23 19:11 ` Doug Anderson
2024-09-15 9:46 ` Andrey Skvortsov
2024-09-11 7:27 ` [PATCH v7 09/10] platform/chrome: Introduce device tree hardware prober Chen-Yu Tsai
2024-09-13 23:43 ` Doug Anderson
2024-09-16 14:58 ` Chen-Yu Tsai
2024-09-16 15:23 ` Andy Shevchenko
2024-09-11 7:27 ` [PATCH v7 10/10] arm64: dts: mediatek: mt8173-elm-hana: Mark touchscreens and trackpads as fail Chen-Yu Tsai
2024-09-13 18:08 ` (subset) [PATCH v7 00/10] platform/chrome: Introduce DT hardware prober Mark Brown
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=ZuQZfvqGii9fcH-j@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=broonie@kernel.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=lgirdwood@gmail.com \
--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