On 8/14/25 11:09, Krzysztof Kozlowski wrote:
> On Tue, Aug 12, 2025 at 03:49:00PM +0200, Raphael Gallais-Pou wrote:
>> Update the compatible to accept both "st,stm32mp255-lvds" and
>> st,stm32mp25-lvds" respectively. Default will fall back to
>> "st,stm32mp25-lvds".
>>
>> Signed-off-by: Raphael Gallais-Pou <raphael.gallais-...@foss.st.com>
>> ---
>> Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml | 8
>> +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
>> b/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
>> index
>> 6736f93256b5cebb558cda5250369ec4b1b3033c..b777c55626e4b322d77ef411ad9e4a3afb6c9131
>> 100644
>> --- a/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
>> +++ b/Documentation/devicetree/bindings/display/st,stm32mp25-lvds.yaml
>> @@ -31,7 +31,13 @@ description: |
>>
>> properties:
>> compatible:
>> - const: st,stm32mp25-lvds
>> + oneOf:
>> + - items:
>> + - enum:
>> + - st,stm32mp255-lvds
>> + - const: st,stm32mp25-lvds
>> + - items:
> Drop. This should be just enum or const, no need for items.
Why would items not be applicable in this case ? I want the compatible field to
be either:
compatible = "st,stm32mp255-lvds", "st,stm32mp25-lvds";
or
compatible = "st,stm32mp25-lvds";
example-schema.yaml states the same pattern.
Best regards,
Raphaël
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlow...@linaro.org>
>
> Best regards,
> Krzysztof
>
