lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 29 Jul 2022 17:22:47 -0600 From: Rob Herring <robh@...nel.org> To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> Cc: David Airlie <airlied@...ux.ie>, Javier Martinez Canillas <javierm@...hat.com>, Heiko Schocher <hs@...x.de>, David Lechner <david@...hnology.com>, Sam Ravnborg <sam@...nborg.org>, dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Thierry Reding <thierry.reding@...il.com>, Maxime Ripard <mripard@...nel.org>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Daniel Vetter <daniel@...ll.ch> Subject: Re: [PATCH] dt-bindings: display: use spi-peripheral-props.yaml On Wed, 27 Jul 2022 18:43:12 +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. > > The sitronix,st7735r references also panel-common.yaml and lists > explicitly allowed properties, thus here reference only > spi-peripheral-props.yaml for purpose of documenting the SPI slave > device and bringing spi-max-frequency type validation. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> > > --- > > 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. > > [1] https://lore.kernel.org/all/20220722191539.90641-2-krzysztof.kozlowski@linaro.org/ > --- > .../devicetree/bindings/display/panel/lg,lg4573.yaml | 2 +- > .../devicetree/bindings/display/sitronix,st7735r.yaml | 1 + > .../devicetree/bindings/display/solomon,ssd1307fb.yaml | 7 +++---- > 3 files changed, 5 insertions(+), 5 deletions(-) > Applied, thanks!
Powered by blists - more mailing lists