f72ddbe1d7
On a functioning FSI link there is not need to retry a write when doing a scom in the driver. Allow the higher layers (eg. userspace) to attempt a retry if they want, or to accept that the address they are talking to is not accessible. By removing the retries we can separate the error handling from retry logic. In particular -EBUSY was used to force the get/put scom logic to retry. Signed-off-by: Joel Stanley <joel@jms.id.au> Link: https://lore.kernel.org/r/20210527070109.225198-1-joel@jms.id.au Signed-off-by: Joel Stanley <joel@jms.id.au> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| cf-fsi-fw.h | ||
| fsi-core.c | ||
| fsi-master-aspeed.c | ||
| fsi-master-ast-cf.c | ||
| fsi-master-gpio.c | ||
| fsi-master-hub.c | ||
| fsi-master.h | ||
| fsi-occ.c | ||
| fsi-sbefifo.c | ||
| fsi-scom.c | ||