occ: fsi and hwmon: Fixes for polling un-initialized OCC
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | fsi: occ: Don't accept response from un-initialized OCCdrivers/ | +1 | 1 reply | |
| 2/4 | fsi: occ: Log error for checksum failuredrivers/ | +7 | 1 reply | |
| 3/4 | hwmon: (occ) Start sequence number at onedrivers/ | +2 | 1 reply | |
| 4/4 | hwmon: (occ) Print response status in first poll error messagedrivers/ | +3 | 1 reply |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by.
| Patch | Guenter Roeck | Joel Stanley |
|---|---|---|
| 1/4 | R-b | |
| 2/4 | R-b | |
| 3/4 | A-b | |
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] occ: fsi and hwmon: Fixes for polling un-initialized OCC
In the event that the OCC is not initialized when the driver sends a poll command, the driver may receive an invalid response. This isn't an error condition unless there is no valid response before the timeout expires. So change the starting sequence number and check for the un-initialized OCC state before returning the response in order to detect this condition and continue waiting if necessary.
Eddie James (4):
fsi: occ: Don't accept response from un-initialized OCC
fsi: occ: Log error for checksum failure
hwmon: (occ) Start sequence number at one
hwmon: (occ) Print response status in first poll error message
drivers/fsi/fsi-occ.c | 11 ++++++++--- drivers/hwmon/occ/common.c | 7 +++++-- 2 files changed, 13 insertions(+), 5 deletions(-)
Signature · 1 line
2.27.0