From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: david@ixit.cz
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Henrik Rydberg <rydberg@bitmath.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Petr Hodina <petr.hodina@protonmail.com>,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
phone-devel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v7 1/4] Input: stmfts - wait for controller ready after reset
Date: Fri, 25 Sep 2026 12:27:37 -0700 [thread overview]
Message-ID: <arbJrK9zfoO1dGzy@google.com> (raw)
In-Reply-To: <20260907-stmfts5-v7-1-4a53381cd038@ixit.cz>
Hi David,
On Mon, Sep 07, 2026 at 12:50:19PM +0200, David Heidelberg via B4 Relay wrote:
>
> -static void stmfts_reset(struct stmfts_data *sdata)
> +static int stmfts_reset(struct stmfts_data *sdata)
> {
> gpiod_set_value_cansleep(sdata->reset_gpio, 1);
> msleep(20);
>
> + reinit_completion(&sdata->cmd_done);
> gpiod_set_value_cansleep(sdata->reset_gpio, 0);
> - msleep(50);
> + enable_irq(sdata->client->irq);
> +
> + if (!wait_for_completion_timeout(&sdata->cmd_done,
> + msecs_to_jiffies(STMFTS_RESET_TIMEOUT_MS)))
> + return -ETIMEDOUT;
> +
> + return 0;
> }
>
> static int stmfts_configure(struct stmfts_data *sdata)
> {
> int err;
>
> err = stmfts_command(sdata, STMFTS_SYSTEM_RESET);
> if (err)
> @@ -593,42 +602,47 @@ static int stmfts_power_on(struct stmfts_data *sdata)
> return err;
>
> /*
> * The datasheet does not specify the power on time, but considering
> * that the reset time is < 10ms, I sleep 20ms to be sure
> */
> msleep(20);
>
> - if (sdata->reset_gpio)
> - stmfts_reset(sdata);
> + if (sdata->reset_gpio) {
> + err = stmfts_reset(sdata);
> + if (err) {
> + dev_err(&sdata->client->dev,
> + "controller not ready after reset: %d\n", err);
> + goto err_disable_irq;
> + }
> + } else {
> + enable_irq(sdata->client->irq);
> + msleep(50);
> + }
>
> err = stmfts_read_system_info(sdata);
> if (err)
> - goto err_disable_regulators;
> -
> - enable_irq(sdata->client->irq);
> -
> - msleep(50);
> + goto err_disable_irq;
I think the logic is becoming quite convoluted here, and factored out
stmfts_reset() does not help. How about we make it look like this:
static int stmfts_power_on(struct stmfts_data *sdata)
{
int err;
if (sdata->reset_gpio) {
gpiod_set_value_cansleep(sdata->reset_gpio, 1);
/* a short delay before powering up */
usleep_range(1000, 1500);
}
err = regulator_bulk_enable(ARRAY_SIZE(stmfts_supplies),
sdata->supplies);
if (err)
return err;
if (sdata->reset_gpio) {
reinit_completion(&sdata->cmd_done);
/*
* The datasheet does not specify the power on time, but
* considering that the reset time is < 10ms, sleep for 20ms
* to be sure before releasing reset line.
*/
msleep(20);
gpiod_set_value_cansleep(sdata->reset_gpio, 0);
enable_irq(sdata->client->irq);
if (!wait_for_completion_timeout(&sdata->cmd_done,
msecs_to_jiffies(STMFTS_RESET_TIMEOUT_MS))) {
dev_err(&sdata->client->dev, "controller not ready after reset");
err = -ETIMEDOUT;
goto err_disable_irq;
}
} else {
/*
* We do not know the real controller state (was it powered
* off or reset). Let's hope that this is enough time to
* initialize.
*/
msleep(70);
enable_irq(sdata->client->irq);
}
err = sdata->ops->configure(sdata);
if (err)
goto err_disable_irq;
/*
* At this point no one is using the touchscreen
* and I don't really care about the return value
*/
(void)i2c_smbus_write_byte(sdata->client, STMFTS_SLEEP_IN);
return 0;
err_disable_irq:
disable_irq(sdata->client->irq);
regulator_bulk_disable(ARRAY_SIZE(stmfts_supplies), sdata->supplies);
return err;
}
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-09-25 19:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:50 [PATCH v7 0/4] Input: support for STM FTS5 David Heidelberg via B4 Relay
2026-09-07 10:50 ` David Heidelberg
2026-09-07 10:50 ` [PATCH v7 1/4] Input: stmfts - wait for controller ready after reset David Heidelberg via B4 Relay
2026-09-07 10:50 ` David Heidelberg
2026-09-07 11:06 ` sashiko-bot
2026-09-25 19:27 ` Dmitry Torokhov [this message]
2026-09-25 20:20 ` David Heidelberg
2026-09-25 20:36 ` Dmitry Torokhov
2026-09-07 10:50 ` [PATCH v7 2/4] dt-bindings: input: touchscreen: st,stmfts: Introduce STM FTS5 David Heidelberg via B4 Relay
2026-09-07 10:50 ` David Heidelberg
2026-09-07 11:00 ` sashiko-bot
2026-09-25 19:19 ` Dmitry Torokhov
2026-09-25 19:48 ` David Heidelberg
2026-09-07 10:50 ` [PATCH v7 3/4] Input: stmfts - support FTS5 David Heidelberg via B4 Relay
2026-09-07 10:50 ` David Heidelberg
2026-09-07 11:04 ` sashiko-bot
2026-09-25 19:21 ` Dmitry Torokhov
2026-09-07 10:50 ` [PATCH v7 4/4] arm64: dts: qcom: sdm845-google: Add STM FTS touchscreen support David Heidelberg via B4 Relay
2026-09-07 10:50 ` David Heidelberg
2026-09-07 10:58 ` Abel Vesa
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=arbJrK9zfoO1dGzy@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=petr.hodina@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rydberg@bitmath.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.