On Wed, Oct 16, 2019 at 11:30:51PM +0200, Noralf Trønnes wrote:
> As Andy mentioned, ->max_transfer_size is a callback:
> struct spi_controller {
> /*
> * on some hardware transfer / message size may be constrained
> * the limit may depend on device transfer settings
> */
> size_t (*max_transfer_size)(struct spi_device *spi);
> (I looked at its users and they all return a static or probe time value
> so not sure why it's a callback.)
Huh, I wonder why we did that... I can't find any clear record, and
like you say nothing is using it so we should probably fix it - however
that's best done separately to this :/ Sorry for the confusion, I
didn't register what Andy was saying as being pointing out the current
state of the code.
Attachment:
signature.asc
Description: PGP signature
