diff options
author | Bin Meng <bmeng.cn@gmail.com> | 2019-09-09 06:00:00 -0700 |
---|---|---|
committer | Jagan Teki <jagan@amarulasolutions.com> | 2019-10-25 00:48:31 +0530 |
commit | 4dd520b36bce9b35f7a12f3ffd9a95269d425170 (patch) | |
tree | 5fa8faec8ebd54460c5ca96c88278f3ea053daba /drivers | |
parent | 0c8e605670fac186f225a957eb8e1a774cb17c41 (diff) |
dm: spi: Return 0 if driver does not implement ops->cs_info
If an SPI controller driver does not implement ops->cs_info, that
probably means any chip select number could be valid, hence let's
return 0 for spi_cs_info().
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Jagan Teki <jagan@amarulasolutions.com> # SoPine
Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
Diffstat (limited to 'drivers')
-rw-r--r-- | drivers/spi/spi-uclass.c | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/drivers/spi/spi-uclass.c b/drivers/spi/spi-uclass.c index a4d1b65682..947516073e 100644 --- a/drivers/spi/spi-uclass.c +++ b/drivers/spi/spi-uclass.c @@ -261,11 +261,10 @@ int spi_cs_info(struct udevice *bus, uint cs, struct spi_cs_info *info) return ops->cs_info(bus, cs, info); /* - * We could assume there is at least one valid chip select, but best - * to be sure and return an error in this case. The driver didn't - * care enough to tell us. + * We could assume there is at least one valid chip select. + * The driver didn't care enough to tell us. */ - return -ENODEV; + return 0; } int spi_find_bus_and_cs(int busnum, int cs, struct udevice **busp, |