[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuFwF/sOk4svIlkK@ravnborg.org>
Date: Wed, 27 Jul 2022 19:04:23 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Thierry Reding <thierry.reding@...il.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
David Lechner <david@...hnology.com>,
Javier Martinez Canillas <javierm@...hat.com>,
Heiko Schocher <hs@...x.de>,
Maxime Ripard <mripard@...nel.org>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: display: use spi-peripheral-props.yaml
Hi Krzysztof,
On Wed, Jul 27, 2022 at 06:43:12PM +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>
Acked-by: Sam Ravnborg <sam@...nborg.org>
I assume this will be added to the same tree as the SPI CPHA and CPOL
patch.
Sam
Powered by blists - more mailing lists