spi: differentiate between unsupported and invalid

Browse source

Merge series from Miquel Raynal <miquel.raynal@bootlin.com>:

I am working on spi-nand continuous read support, which lead me to check
what spi controllers were capable of.

>From a caller (and reviewer) point of view, distinguishing between error
cases has been proven useful, especially between two conditions:
- the request is totally unsupported and will never work
- the request is typically out of range somehow but a subsequent call
  with corrected parameters might work

So while I was statically reading the various drivers, I attempted to
clarify these situations and thought it might be nice to have this
upstream as well.

As ENOTSUPP is not a SUSV4 code and previous series have already been
merged to reduce its use, I also converted these few cases to EOPNOTSUP
instead, but if anybody doesn't like these changes, it can be dropped.

...

This commit is contained in:

Mark Brown 2024-05-29 11:08:05 +01:00

parent ab0b5a99d3 41b86b1455

commit b0d8c563f0

No known key found for this signature in database

GPG key ID: 24D68B725D5487D0

4 changed files with 16 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

10

drivers/spi/spi-dw-bt1.c

View file

2

drivers/spi/spi-mxic.c

View file

12

drivers/spi/spi-rpc-if.c

View file

6

drivers/spi/spi-wpcm-fiu.c

View file