From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-input@vger.kernel.org, Joe Hung <joe_hung@ilitek.com>,
Luca Hsu <luca_hsu@ilitek.com>
Subject: Re: [PATCH] Input: ili210x - Probe even if no resolution information
Date: Thu, 16 Feb 2023 14:44:08 -0800 [thread overview]
Message-ID: <Y+6xuOJwVpYYFW6H@google.com> (raw)
In-Reply-To: <20220715155905.219391-1-marex@denx.de>
Hi Marek,
On Fri, Jul 15, 2022 at 05:59:05PM +0200, Marek Vasut wrote:
> Probe the touch controller driver even if resolution information is not
> available. This can happen e.g. in case the touch controller suffered a
> failed firmware update and is stuck in bootloader mode.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Joe Hung <joe_hung@ilitek.com>
> Cc: Luca Hsu <luca_hsu@ilitek.com>
> ---
> drivers/input/touchscreen/ili210x.c | 27 ++++++++++++++++++---------
> 1 file changed, 18 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/input/touchscreen/ili210x.c b/drivers/input/touchscreen/ili210x.c
> index e9bd36adbe47d..ad25081e301c6 100644
> --- a/drivers/input/touchscreen/ili210x.c
> +++ b/drivers/input/touchscreen/ili210x.c
> @@ -370,22 +370,32 @@ static int ili251x_firmware_update_resolution(struct device *dev)
>
> /* The firmware update blob might have changed the resolution. */
> error = priv->chip->read_reg(client, REG_PANEL_INFO, &rs, sizeof(rs));
> - if (error)
> - return error;
> + if (!error) {
> + resx = le16_to_cpup((__le16 *)rs);
> + resy = le16_to_cpup((__le16 *)(rs + 2));
>
> - resx = le16_to_cpup((__le16 *)rs);
> - resy = le16_to_cpup((__le16 *)(rs + 2));
> + /* The value reported by the firmware is invalid. */
> + if (!resx || resx == 0xffff || !resy || resy == 0xffff)
> + error = -EINVAL;
> + }
>
> - /* The value reported by the firmware is invalid. */
> - if (!resx || resx == 0xffff || !resy || resy == 0xffff)
> - return -EINVAL;
> + /*
> + * In case of error, the firmware might be stuck in bootloader mode,
> + * e.g. after a failed firmware update. Set maximum resolution, but
> + * do not fail to probe, so the user can re-trigger the firmware
> + * update and recover the touch controller.
> + */
> + if (error) {
Do you want to maybe dev_warn() here to explain the weird values?
> + resx = 16384;
> + resy = 16384;
> + }
Thanks.
--
Dmitry
prev parent reply other threads:[~2023-02-16 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 15:59 [PATCH] Input: ili210x - Probe even if no resolution information Marek Vasut
2023-02-16 22:44 ` Dmitry Torokhov [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=Y+6xuOJwVpYYFW6H@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=luca_hsu@ilitek.com \
--cc=marex@denx.de \
/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.