Hi, On Fri, May 10, 2019 at 11:05:48AM -0500, Rob Herring wrote: > > +description: | > > + SPI busses can be described with a node for the SPI controller device > > + and a set of child nodes for each SPI slave on the bus. The system SPI > > + controller may be described for use in SPI master mode or in SPI slave mode, > > + but not for both at the same time. > > + > > +properties: > > + $nodename: > > + pattern: "^spi(@.*)$" > > Doing some testing with spi-gpio schema I'm writing, this needs to be > "^spi(@.*)*$" so that just 'spi' is allowed. I guess "^spi(@.*)+$" would be enough then? > However, that's not enough for handling multiple instances of > spi-gpio. So maybe we need "^spi(@.*|-[0-9a-f])*$" to allow spi-1, > spi-2, etc. Really, we need to decide the larger issue of how we > handle multiple instances when there's no address space. That works for me, I'll change it. > Also, this schema will be applied to any matching node name as it is > used for automatic selection if compatible schema is not present. If > we want to prevent that and only apply it when explicitly included, > then we need to add a 'select: false'. Without it, we get more > coverage, but it could slow things down and we'll get double printing > of errors. I guess we can change that later if it becomes too slow and / or confusing? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Attachment:
signature.asc
Description: PGP signature
