On Wed, Apr 24, 2019 at 09:07:12AM +0200, Lukas Wunner wrote: > Indeed I'd prefer if another bit is added to "mode" in struct device > to represent the need for another clock cycle in-between bytes. > The SPI core could then reduce the clock speed based on this flag > and the problem would be solved for everyone. > Influencing this behavior with a module parameter feels a bit like a > kludge and I fear may stay indefinitely even if a better solution > is implemented later. This does feel like we know enough to have a more advanced function in the driver given a bit of information about the client device requireemnts. Though it's going to be complex to express them, especially with the ATMega case where we want fast individual clocks but lots of dead space in between bytes (is the controller capable of adding that dead space itself in DMA mode BTW?).
Attachment:
signature.asc
Description: PGP signature
