On 28/07/2022 17:18, Rob Herring wrote: > On Wed, 27 Jul 2022 18:41:29 +0200, Krzysztof Kozlowski wrote: >> Instead of listing directly properties typical for SPI peripherals, >> reference the spi-peripheral-props.yaml schema. This allows using all >> properties typical for SPI-connected devices, even these which device >> bindings author did not tried yet. >> >> Remove the spi-* properties which now come via spi-peripheral-props.yaml >> schema, except for the cases when device schema adds some constraints >> like maximum frequency. >> >> While changing additionalProperties->unevaluatedProperties, put it in >> typical place, just before example DTS. >> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> >> >> --- >> >> Technically, this depends on [1] merged to SPI tree, if we want to >> preserve existing behavior of not allowing SPI CPHA and CPOL in each of >> schemas in this patch. >> >> If this patch comes independently via different tree, the SPI CPHA and >> CPOL will be allowed for brief period of time, before [1] is merged. >> This will not have negative impact, just DT schema checks will be >> loosened for that period. > > I don't think these need to go via the same tree. Yeah, I wanted to express it that almost no impact is expected if it goes independently. I could be more explicit here. Best regards, Krzysztof
