From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, David Airlie <airlied@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
Robert Nelson <robertcnelson@gmail.com>,
Jason Kridner <jkridner@beagleboard.org>, <afd@ti.com>,
<tomi.valkeinen@ideasonboard.com>, <devarsht@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH V3 0/4] drm/bridge: it66121: Add initial it66122 support
Date: Thu, 14 Aug 2025 22:41:01 -0500 [thread overview]
Message-ID: <20250815034105.1276548-1-nm@ti.com> (raw)
Hi,
Add initial support for IT66122, which seems to be compatible to it66121
but probably has additional functionality.
BeagleY-AI uses this it66122 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. Additionally, it also looks like
Revision D of BeagleBone Black switched over to it66122 as well.
Changes in V3:
Based on Tomi's and Devarsh's reviews, and searching online (and failing
to find) for a public data sheet, I have refactored the series to:
a) Detect the ID by matching vid/pid
b) Introduce it66122 basic support which seems to work based on
empirical testing evidence on BeagleY-AI. This allows incremental
patches in the future by someone who might have access to the data
sheet to add additional features for the chip.
c) Irritated by checkpatch --strict warnings, added a patch to fix
existing warnings as part of this series, but it could probably go
in independent of everything else.
d) Stopped claiming it66122 is drop in replacement of it66121 :)
Changes in V2:
* Picked up Krystoff's binding ack
* Switched over to a vid/pid list
V1: https://lore.kernel.org/all/20250813190835.344563-1-nm@ti.com/
V2: https://lore.kernel.org/all/20250813204106.580141-1-nm@ti.com/
Nishanth Menon (4):
dt-bindings: display: bridge: it66121: Add compatible string for
IT66122
drm/bridge: it66121: Drop ftrace like dev_dbg() prints
drm/bridge: it66121: Use vid/pid to detect the type of chip
drm/bridge: it66121: Add minimal it66122 support
.../bindings/display/bridge/ite,it66121.yaml | 1 +
drivers/gpu/drm/bridge/ite-it66121.c | 63 +++++++++----------
2 files changed, 32 insertions(+), 32 deletions(-)
--
2.47.0
next reply other threads:[~2025-08-15 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 3:41 Nishanth Menon [this message]
2025-08-15 3:41 ` [PATCH V3 1/4] dt-bindings: display: bridge: it66121: Add compatible string for IT66122 Nishanth Menon
2025-08-15 3:41 ` [PATCH V3 2/4] drm/bridge: it66121: Drop ftrace like dev_dbg() prints Nishanth Menon
2025-08-15 13:50 ` Andrew Davis
2025-08-16 19:23 ` Dmitry Baryshkov
2025-08-15 3:41 ` [PATCH V3 3/4] drm/bridge: it66121: Use vid/pid to detect the type of chip Nishanth Menon
2025-08-15 13:52 ` Andrew Davis
2025-08-15 15:22 ` Nishanth Menon
2025-08-16 19:55 ` Dmitry Baryshkov
2025-08-15 3:41 ` [PATCH V3 4/4] drm/bridge: it66121: Add minimal it66122 support Nishanth Menon
2025-08-15 13:54 ` Andrew Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250815034105.1276548-1-nm@ti.com \
--to=nm@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=afd@ti.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jkridner@beagleboard.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox