[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c6a7db0-dc75-4ed1-aeae-418fa004ea53@ti.com>
Date: Wed, 13 Aug 2025 14:32:45 -0500
From: Andrew Davis <afd@...com>
To: Nishanth Menon <nm@...com>, Conor Dooley <conor+dt@...nel.org>,
Krzysztof
Kozlowski <krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>, David Airlie
<airlied@...il.com>,
Maxime Ripard <mripard@...nel.org>,
Laurent Pinchart
<Laurent.pinchart@...asonboard.com>,
Neil Armstrong
<neil.armstrong@...aro.org>
CC: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>,
Robert Nelson <robertcnelson@...il.com>,
Jason Kridner <jkridner@...gleboard.org>
Subject: Re: [PATCH 0/2] drm/bridge: it66121: Add it66122 support
On 8/13/25 2:08 PM, Nishanth Menon wrote:
> Hi,
>
> Add support for IT66122, which for all practical purposes is
> drop in replacement for IT66121 except for the ID register
> definition.
>
> BeagleY-AI uses this new part as the old part is no longer in production
> as far as I understand.
>
> Now, BeaglePlay uses it66121 at the moment, but at some point, it might
> end up flipping over to the new part.
>
> An alternate implementation could be to drop the revision check or make
> it66121 check include alternate ID check.. but that seems a little
> non-standard.. Anyways, I suppose mediatek platforms will face this
> problem as well at some point.
>
Hmmm, since these boards will probably have to switch parts mid-production
it would cause us to need to have a new DT with the updated compatible
just for a otherwise transparent revision. Might be better to just
loosen the PID check so the alternative part work just the same.
Andrew
> Nishanth Menon (2):
> dt-bindings: display: bridge: it66121: Add compatible string for
> IT66122
> drm/bridge: it66121: Add it66122 support
>
> .../devicetree/bindings/display/bridge/ite,it66121.yaml | 1 +
> drivers/gpu/drm/bridge/ite-it66121.c | 8 ++++++++
> 2 files changed, 9 insertions(+)
>
Powered by blists - more mailing lists