diff options
| author | Bin Meng <[email protected]> | 2019-09-09 06:00:00 -0700 |
|---|---|---|
| committer | Jagan Teki <[email protected]> | 2019-10-25 00:48:31 +0530 |
| commit | 4dd520b36bce9b35f7a12f3ffd9a95269d425170 (patch) | |
| tree | 5fa8faec8ebd54460c5ca96c88278f3ea053daba /doc | |
| 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 <[email protected]>
Tested-by: Jagan Teki <[email protected]> # SoPine
Reviewed-by: Jagan Teki <[email protected]>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/driver-model/spi-howto.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/driver-model/spi-howto.rst b/doc/driver-model/spi-howto.rst index 5540eb7d38e..44eab3947e7 100644 --- a/doc/driver-model/spi-howto.rst +++ b/doc/driver-model/spi-howto.rst @@ -634,8 +634,8 @@ method for cs_info() to deal with this. If you don't provide it, then the device tree will be used to determine what chip selects are valid. Return -ENODEV if the supplied chip select is invalid, or 0 if it is valid. -If you don't provide the cs_info() method, -ENODEV is assumed for all -chip selects that do not appear in the device tree. +If you don't provide the cs_info() method, 0 is assumed for all chip selects +that do not appear in the device tree. Test it |