On Sat, Nov 21, 2015 at 03:10:03PM +0100, Heiner Kallweit wrote: > As you say this visibility of the master structure is unfortunate: > What could be a (maybe long-term) better way to propagate restrictions > that can't be handled transparently in the core like max message size > and SPI NOR to protocol drivers? The point is that the spi_master structure is not opaque to users (with a consumer/provider split like modern APIs have). We'd have to reorganise the headers and provide accessors in the client API to handle this.
Attachment:
signature.asc
Description: PGP signature
