[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bf204c54-a51b-21d0-9fbf-3729d277ef76@linaro.org>
Date: Tue, 30 May 2023 17:13:20 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Raphael Gallais-Pou <raphael.gallais-pou@...s.st.com>,
Alexandre TORGUE <alexandre.torgue@...s.st.com>
Cc: linux-stm32@...md-mailman.stormreply.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
David Airlie <airlied@...il.com>,
Yannick Fertre <yannick.fertre@...s.st.com>,
Daniel Vetter <daniel@...ll.ch>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Conor Dooley <conor.dooley@...rochip.com>,
kernel@...electronics.com, Marek Vasut <marex@...x.de>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, Rob Herring <robh+dt@...nel.org>,
Philippe Cornu <philippe.cornu@...s.st.com>,
linux-arm-kernel@...ts.infradead.org,
Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH v4 2/4] dt-bindings: display: st,stm32-dsi: Remove
unnecessary fields
On 30/05/2023 15:38, Raphael Gallais-Pou wrote:
>
> On 5/30/23 15:30, Alexandre TORGUE wrote:
>> On 5/30/23 14:27, Krzysztof Kozlowski wrote:
>>> On Mon, 29 May 2023 11:13:57 +0200, Raphael Gallais-Pou wrote:
>>>> "#address-cells" and "#size-cells" are two properties that are not
>>>> mandatory. For instance, the DSI could refer to a bridge outside the scope
>>>> of the node rather than include a 'panel@0' subnode. By doing so, address
>>>> and size fields become then unnecessary, creating a warning at build time.
>>>>
>>>> Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@...s.st.com>
>>>> Acked-by: Conor Dooley <conor.dooley@...rochip.com>
>>>> Reviewed-by: Marek Vasut <marex@...x.de>
>>>> ---
>>>> Documentation/devicetree/bindings/display/st,stm32-dsi.yaml | 2 --
>>>> 1 file changed, 2 deletions(-)
>>>>
>>>
>>> Running 'make dtbs_check' with the schema in this patch gives the
>>> following warnings. Consider if they are expected or the schema is
>>> incorrect. These may not be new warnings
>> I checked it before merging the series on stm32-next tree. I didn't get this
>> error. I didn't check commit per commit.
>>
>> Do you get this error after merging the whole series ?
>
>
> I think this is because of the order of the patches within the serie. The patch
> correcting the yaml is before those modifying the device-trees. This could
> explain warnings rise up when checking patch per patch. However I did not get
> any errors on top of the whole serie.
Yeah. Ignore the report if you tested it by yourself.
Best regards,
Krzysztof
Powered by blists - more mailing lists