From: Lyude Paul <lyude@redhat.com>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] Input: synaptics-rmi4 - fix firmware update operations with bootloader v8
Date: Thu, 22 Sep 2022 16:06:48 -0400 [thread overview]
Message-ID: <3da8a0c9ae4e6d8a1d772498e4d4186bf969fd76.camel@redhat.com> (raw)
In-Reply-To: <20220608124808.51402-2-matthias.schiffer@ew.tq-group.com>
Would add a Cc: stable@vger.kernel.org for this
With that fixed: Reviewed-by: Lyude Paul <lyude@redhat.com>
On Wed, 2022-06-08 at 14:48 +0200, Matthias Schiffer wrote:
> Commit a6977d758fed ("Input: synaptics-rmi4 - support bootloader v8 in
> f34v7") allowed the F34v7 driver to probe with bootloader v8, but it did
> not update various other bootloader version checks in the F34 code.
>
> Fixes: a6977d758fed ("Input: synaptics-rmi4 - support bootloader v8 in f34v7")
> Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
> ---
> drivers/input/rmi4/rmi_f34.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/input/rmi4/rmi_f34.c b/drivers/input/rmi4/rmi_f34.c
> index e5dca9868f87..3afc94f679ed 100644
> --- a/drivers/input/rmi4/rmi_f34.c
> +++ b/drivers/input/rmi4/rmi_f34.c
> @@ -370,7 +370,7 @@ static int rmi_firmware_update(struct rmi_driver_data *data,
>
> f34 = dev_get_drvdata(&data->f34_container->dev);
>
> - if (f34->bl_version == 7) {
> + if (f34->bl_version >= 7) {
> if (data->pdt_props & HAS_BSR) {
> dev_err(dev, "%s: LTS not supported\n", __func__);
> return -ENODEV;
> @@ -382,7 +382,7 @@ static int rmi_firmware_update(struct rmi_driver_data *data,
> }
>
> /* Enter flash mode */
> - if (f34->bl_version == 7)
> + if (f34->bl_version >= 7)
> ret = rmi_f34v7_start_reflash(f34, fw);
> else
> ret = rmi_f34_enable_flash(f34);
> @@ -413,7 +413,7 @@ static int rmi_firmware_update(struct rmi_driver_data *data,
> f34 = dev_get_drvdata(&data->f34_container->dev);
>
> /* Perform firmware update */
> - if (f34->bl_version == 7)
> + if (f34->bl_version >= 7)
> ret = rmi_f34v7_do_reflash(f34, fw);
> else
> ret = rmi_f34_update_firmware(f34, fw);
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2022-09-22 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 12:47 [PATCH 0/9] Input: synaptics-rmi4 - Bootloader v7/v8 firmware update improvements Matthias Schiffer
2022-06-08 12:48 ` [PATCH 1/9] Input: synaptics-rmi4 - fix firmware update operations with bootloader v8 Matthias Schiffer
2022-09-22 20:06 ` Lyude Paul [this message]
2022-09-23 9:12 ` Matthias Schiffer
2022-09-23 19:13 ` Lyude Paul
2022-06-08 12:48 ` [PATCH 2/9] Input: synaptics-rmi4 - introduce rmi_f34v7_check_command_status() helper Matthias Schiffer
2022-06-08 12:48 ` [PATCH 3/9] Input: synaptics-rmi4 - fix command completion check for bootloader v7/v8 Matthias Schiffer
2022-06-08 12:48 ` [PATCH 4/9] Input: synaptics-rmi4 - rewrite partition table unconditionally Matthias Schiffer
2022-06-08 12:48 ` [PATCH 5/9] Input: synaptics-rmi4 - reset after writing partition table Matthias Schiffer
2022-06-08 12:48 ` [PATCH 6/9] Input: synaptics-rmi4 - make rmi_f34v7_erase_all() use the "erase all" command Matthias Schiffer
2022-06-08 12:48 ` [PATCH 7/9] Input: synaptics-rmi4 - remove unneeded struct register_offset Matthias Schiffer
2022-06-08 12:48 ` [PATCH 8/9] Input: synaptics-rmi4 - simplify rmi_f34v7_start_reflash() Matthias Schiffer
2022-06-08 12:48 ` [PATCH 9/9] Input: synaptics-rmi4 - drop useless gotos in rmi_f34v7_do_reflash() Matthias Schiffer
2022-06-27 8:31 ` [PATCH 0/9] Input: synaptics-rmi4 - Bootloader v7/v8 firmware update improvements Matthias Schiffer
2022-08-15 7:43 ` Matthias Schiffer
2022-09-15 8:02 ` Matthias Schiffer
2022-09-16 22:39 ` Lyude Paul
2022-09-16 22:50 ` Dmitry Torokhov
2022-09-16 22:51 ` Lyude Paul
2022-09-22 20:18 ` Lyude Paul
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=3da8a0c9ae4e6d8a1d772498e4d4186bf969fd76.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Jason@zx2c4.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
/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.