[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e096cc4-a012-8ef0-d5a2-1a32d1f6c83e@linaro.org>
Date: Wed, 10 Aug 2022 19:44:34 +0300
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Thierry Reding <thierry.reding@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Paul Cercueil <paul@...pouillou.net>,
Christophe Branchereau <cbranchereau@...il.com>,
Jonathan Bakker <xc-racer2@...e.ca>,
Pratyush Yadav <p.yadav@...com>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi/panel: dt-bindings: drop 3-wire from common
properties
On 10/08/2022 19:18, Mark Brown wrote:
> On Wed, Aug 10, 2022 at 04:13:11PM +0300, Krzysztof Kozlowski wrote:
>> The spi-3wire property is device specific and should be accepted only if
>> device really needs them. Drop it from common spi-peripheral-props.yaml
>> schema, mention in few panel drivers which use it and include instead in
>> the SPI controller bindings. The controller bindings will provide
>> spi-3wire type validation and one place for description. Each device
>> schema must list the property if it is applicable.
>
> What's the plan for getting this merged? I can just apply it at -rc1 if
> that works for people?
Ah, I should mention it before, my bad. There are no dependencies, no
stoppers. I hope this will go via your SPI tree.
Best regards,
Krzysztof
Powered by blists - more mailing lists