On Mon, Aug 01, 2022 at 06:04:10PM +0200, Lukas Wunner wrote: > On Mon, Aug 01, 2022 at 05:45:07PM +0200, Krzysztof Kozlowski wrote: > > On 31/07/2022 00:46, Lukas Wunner wrote: > > > On Wed, Jul 27, 2022 at 06:46:36PM +0200, Krzysztof Kozlowski wrote: > > >> 78 files changed, 324 insertions(+), 249 deletions(-) > > > > > > Pardon me for being dense, but what is the benefit of this series > > > that justifies inflating the schema definitions by a total of 75 lines? > > > > The commits were explaining rationale, so let me bring it here. The > > benefits are: > > This allows using all properties typical for SPI-connected devices, even > > these which device bindings author did not tried yet. > > How do you know these untested properties work with the devices to which > you're adding them? How do we know anything DT works? We don't without testing on h/w. That's not what the schemas provide. The spi-peripheral-props.yaml reference is needed in order to allow controller specific timing properties and to prevent random other undocumented properties from being present. There is not another way to do both of those. Do I wish we didn't have these controller specific timing parameters, yes! But that ship has sailed. Rob
