diff options
author | Jeff LaBundy <jeff@labundy.com> | 2021-01-25 07:14:50 +0300 |
---|---|---|
committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2021-01-25 07:49:02 +0300 |
commit | 2539da6677b6355e124b99d1dbe15eb1066f1d46 (patch) | |
tree | 693acebec513121771874b0ca934c032ffb52c7b /crypto/asymmetric_keys | |
parent | 785a19d97cb072c748a310d558859853f8ba987b (diff) | |
download | linux-2539da6677b6355e124b99d1dbe15eb1066f1d46.tar.xz |
Input: iqs5xx - preserve bootloader errors
After user space writes the fw_file attribute to push new firmware
to the device, the driver calls iqs5xx_dev_init() to re-initialize
the device with the updated firmware or recover the device in case
the update failed.
In the case of the latter, however, iqs5xx_fw_file_write() returns
zero (success) so long as iqs5xx_dev_init() does not fail, and any
error encountered during the update process is lost. Solve this by
saving the error before calling iqs5xx_dev_init().
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Link: https://lore.kernel.org/r/1611002626-5889-3-git-send-email-jeff@labundy.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'crypto/asymmetric_keys')
0 files changed, 0 insertions, 0 deletions