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>,
<dmitry.baryshkov@oss.qualcomm.com>, Nishanth Menon <nm@ti.com>
Subject: [PATCH V5 0/5] drm/bridge: it66121: Add initial it66122 support
Date: Wed, 27 Aug 2025 15:23:49 -0500 [thread overview]
Message-ID: <20250827202354.2017972-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.
Series is based on next-20250827
Bootlog: BeaglePlay: https://gist.github.com/nmenon/65afb917ee1818979d338cf25732a920
Changes in V5:
* Switched over to ARRAY_SIZE
* Picked up Andrew's Reviewed-by
Changes in V4:
* Added patch to sort the compatibles alpha-numerically
* vid/pid lookup is done without using the match_data.
* picked reviews
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
V4: https://lore.kernel.org/all/20250819130807.3322536-1-nm@ti.com/
V3: https://lore.kernel.org/all/20250815034105.1276548-1-nm@ti.com/
V2: https://lore.kernel.org/all/20250813204106.580141-1-nm@ti.com/
V1: https://lore.kernel.org/all/20250813190835.344563-1-nm@ti.com/
Nishanth Menon (5):
dt-bindings: display: bridge: it66121: Add compatible string for
IT66122
drm/bridge: it66121: Drop ftrace like dev_dbg() prints
drm/bridge: it66121: Sort the compatibles
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 | 68 +++++++++----------
2 files changed, 34 insertions(+), 35 deletions(-)
--
2.47.0
next reply other threads:[~2025-08-27 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 20:23 Nishanth Menon [this message]
2025-08-27 20:23 ` [PATCH V5 1/5] dt-bindings: display: bridge: it66121: Add compatible string for IT66122 Nishanth Menon
2025-08-27 20:23 ` [PATCH V5 2/5] drm/bridge: it66121: Drop ftrace like dev_dbg() prints Nishanth Menon
2025-08-27 20:23 ` [PATCH V5 3/5] drm/bridge: it66121: Sort the compatibles Nishanth Menon
2025-08-27 20:23 ` [PATCH V5 4/5] drm/bridge: it66121: Use vid/pid to detect the type of chip Nishanth Menon
2025-08-27 20:23 ` [PATCH V5 5/5] drm/bridge: it66121: Add minimal it66122 support Nishanth Menon
2025-09-15 14:03 ` [PATCH V5 0/5] drm/bridge: it66121: Add initial " Nishanth Menon
2025-09-16 11:36 ` Tomi Valkeinen
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=20250827202354.2017972-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=dmitry.baryshkov@oss.qualcomm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.