[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a45ac6da-8e29-9b2d-6172-8bc043afc415@pengutronix.de>
Date: Thu, 4 May 2023 09:35:59 +0200
From: Johannes Zink <j.zink@...gutronix.de>
To: Rob Herring <robh@...nel.org>
Cc: devicetree@...r.kernel.org, daniel@...ll.ch, sam@...nborg.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
thierry.reding@...il.com, krzysztof.kozlowski+dt@...aro.org,
airlied@...il.com, kernel@...gutronix.de,
patchwork-jzi@...gutronix.de
Subject: Re: [PATCH 1/2] dt-bindings: display: simple: support non-default
data-mapping
Hi Rob,
On 4/19/23 08:29, Johannes Zink wrote:
[snip]
>>
>> Why do you duplicate what's in display/lvds.yaml?
>
> I don't think any of the other properties from display/lvds.yaml
> currently make any sense to be put into simple-panel, thus I selectively
> picked this one.
>
> If there is a way to selectively pick only the data_mapping, please let
> me know and I send a V2
>
>>
>> This also just made 'data-mapping' valid on non-LVDS panels.
>
> what is the canonical way of restricting the data-mapping property to
> LVDS panels only? Or ist the proper way to go to move the panel I use
> (innolux,g101ice-l01) to its own yaml file, include panel-simple.yaml
> and leave the others alone? I think other LVDS panels might benefit from
> this series though, which is why I think it makes sense to add the
> property to all LVDS panels.
>
gentle ping. How do you suggest should I proceed here? Maybe pulling the
data-mapping definition in a separate file and include it in both files?
Can I enable the property selectively, e.g. only on the
innolux,g101ice-l01 panel, in order not to enable it on non-LVDS panels
or on LVDS-panels which might not support it?
Best regards
Johannes
[snip]
--
Pengutronix e.K. | Johannes Zink |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686| Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists