lkml.org 
[lkml]   [2022]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5/9] Input: synaptics-rmi4 - reset after writing partition table
    Date
    When recovering from a bad partition table (for example after an
    interrupted update), a reset is necessary for the new partition table to
    become effective. Without this reset, writing the core code partition
    will fail with status 0x03 (Invalid Command).

    Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
    ---
    drivers/input/rmi4/rmi_f34v7.c | 8 ++++++++
    1 file changed, 8 insertions(+)

    diff --git a/drivers/input/rmi4/rmi_f34v7.c b/drivers/input/rmi4/rmi_f34v7.c
    index 19b94b1c1a33..9b78f98bb21c 100644
    --- a/drivers/input/rmi4/rmi_f34v7.c
    +++ b/drivers/input/rmi4/rmi_f34v7.c
    @@ -1146,6 +1146,14 @@ int rmi_f34v7_do_reflash(struct f34_data *f34, const struct firmware *fw)
    goto fail;
    dev_info(&f34->fn->dev, "%s: Partition table programmed\n", __func__);

    + /*
    + * Reset to reload partition table - as the previous firmware has been
    + * erased, we remain in bootloader mode.
    + */
    + ret = rmi_scan_pdt(f34->fn->rmi_dev, NULL, rmi_initial_reset);
    + if (ret < 0)
    + dev_warn(&f34->fn->dev, "RMI reset failed!\n");
    +
    dev_info(&f34->fn->dev, "Writing firmware (%d bytes)...\n",
    f34->v7.img.ui_firmware.size);

    --
    2.25.1
    \
     
     \ /
      Last update: 2022-06-08 14:55    [W:8.327 / U:0.324 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site