summaryrefslogtreecommitdiffstats
path: root/Documentation/kernel-hacking
diff options
context:
space:
mode:
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2018-05-15 16:14:43 +1000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2018-06-12 14:05:16 +1000
commit4e56828a5db19e2de8f8dc464c6df2e7e9ff4e13 (patch)
treeacc4c44cb01969f50279d7367cf57870cfefad6f /Documentation/kernel-hacking
parent0e82e5c1fad79ffe9d316296c7a4c1de539d0c48 (diff)
downloadlinux-4e56828a5db19e2de8f8dc464c6df2e7e9ff4e13.tar.bz2
fsi/fsi-master-gpio: Implement CRC error recovery
The FSI protocol defines two modes of recovery from CRC errors, this implements both: - If the device returns an ECRC (it detected a CRC error in the command), then we simply issue the command again. - If the master detects a CRC error in the response, we send an E_POLL command which requests a resend of the response without actually re-executing the command (which could otherwise have unwanted side effects such as dequeuing a FIFO twice). Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Reviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com> Tested-by: Joel Stanley <joel@jms.id.au> --- Note: This was actually tested by removing some of my fixes, thus causing us to hit occasional CRC errors during high LPC activity.
Diffstat (limited to 'Documentation/kernel-hacking')
0 files changed, 0 insertions, 0 deletions