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>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH 2/2] drm/bridge: it66121: Add it66122 support
Date: Wed, 13 Aug 2025 14:08:35 -0500 [thread overview]
Message-ID: <20250813190835.344563-3-nm@ti.com> (raw)
In-Reply-To: <20250813190835.344563-1-nm@ti.com>
The IT66122 is a drop in replacement for the IT66122. The part is
register compatible with what we use of the IT66121. The only relevant
change being the PID is now 0x0622 vs 0x0612. Add this extra PID so
probe does not fail during the PID check with these new parts.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Note: checkpatch --strict reports:
CHECK: No space is necessary after a cast
#45: FILE: drivers/gpu/drm/bridge/ite-it66121.c:1643:
+ { "it66122", (kernel_ulong_t) &it66122_chip_info },
I chose to retain existing style - let me know if we want to clean this
up as well.
NOTE: .id = ID_IT66121 is explicitly used as indication of reuse of
existing it66121 compatibility.
drivers/gpu/drm/bridge/ite-it66121.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/bridge/ite-it66121.c b/drivers/gpu/drm/bridge/ite-it66121.c
index aa7b1dcc5d70..329fa47a5701 100644
--- a/drivers/gpu/drm/bridge/ite-it66121.c
+++ b/drivers/gpu/drm/bridge/ite-it66121.c
@@ -1618,6 +1618,12 @@ static const struct it66121_chip_info it66121_chip_info = {
.pid = 0x0612,
};
+static const struct it66121_chip_info it66122_chip_info = {
+ .id = ID_IT66121,
+ .vid = 0x4954,
+ .pid = 0x0622,
+};
+
static const struct it66121_chip_info it6610_chip_info = {
.id = ID_IT6610,
.vid = 0xca00,
@@ -1626,6 +1632,7 @@ static const struct it66121_chip_info it6610_chip_info = {
static const struct of_device_id it66121_dt_match[] = {
{ .compatible = "ite,it66121", &it66121_chip_info },
+ { .compatible = "ite,it66122", &it66122_chip_info },
{ .compatible = "ite,it6610", &it6610_chip_info },
{ }
};
@@ -1633,6 +1640,7 @@ MODULE_DEVICE_TABLE(of, it66121_dt_match);
static const struct i2c_device_id it66121_id[] = {
{ "it66121", (kernel_ulong_t) &it66121_chip_info },
+ { "it66122", (kernel_ulong_t) &it66122_chip_info },
{ "it6610", (kernel_ulong_t) &it6610_chip_info },
{ }
};
--
2.47.0
next prev parent reply other threads:[~2025-08-13 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 19:08 [PATCH 0/2] drm/bridge: it66121: Add it66122 support Nishanth Menon
2025-08-13 19:08 ` [PATCH 1/2] dt-bindings: display: bridge: it66121: Add compatible string for IT66122 Nishanth Menon
2025-08-13 19:20 ` Krzysztof Kozlowski
2025-08-13 19:08 ` Nishanth Menon [this message]
2025-08-14 4:02 ` [PATCH 2/2] drm/bridge: it66121: Add it66122 support devarsh
2025-08-13 19:32 ` [PATCH 0/2] " Andrew Davis
2025-08-13 20:24 ` Nishanth Menon
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=20250813190835.344563-3-nm@ti.com \
--to=nm@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--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 \
/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.