Devicetree
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Robert Nelson <robertcnelson@gmail.com>,
	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>,
	Jason Kridner <jkridner@beagleboard.org>,
	afd@ti.com
Subject: Re: [PATCH V2 3/3] drm/bridge: it66121: Add it66122 support
Date: Thu, 14 Aug 2025 13:32:15 +0300	[thread overview]
Message-ID: <0c684542-aacb-4e8c-a1c0-7fc0da78c733@ideasonboard.com> (raw)
In-Reply-To: <20250813204106.580141-4-nm@ti.com>

Hi,

On 13/08/2025 23:41, Nishanth Menon wrote:
> 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

The intro letter said "practical purposes is drop in replacement for
IT66121". Here you say "with what we use of the IT66121".

What does that mean? Are they identical, except the IDs? Or are they
different, but the features and registers this driver uses are
identical? Or different, but only identical wrt. the driver's features
TI uses?

Assuming the first one of those, for the series:

Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>

 Tomi

> 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.
> 
> For new platforms that do explicitly use IT66122, they can use the
> appropriate compatible as well.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Changes since V1:
> - I think this is a more pragmatic approach with both compatibles
>   functional and the option of being able to split this up at a later
>   point if required in driver.
> 
> NOTE: I still retain the checkpatch --strict warning as v1 here.
> 
> V1: https://lore.kernel.org/all/20250813190835.344563-3-nm@ti.com/
> 
>  drivers/gpu/drm/bridge/ite-it66121.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/bridge/ite-it66121.c b/drivers/gpu/drm/bridge/ite-it66121.c
> index 208e118df0e2..dcbbf7578046 100644
> --- a/drivers/gpu/drm/bridge/ite-it66121.c
> +++ b/drivers/gpu/drm/bridge/ite-it66121.c
> @@ -1625,6 +1625,7 @@ static const struct it66121_chip_info it66121_chip_info = {
>  	.id = ID_IT66121,
>  	.device_id = {
>  		{.vid = 0x4954, .pid = 0x0612 },
> +		{.vid = 0x4954, .pid = 0x0622 },
>  		{ }
>  	},
>  };
> @@ -1639,6 +1640,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", &it66121_chip_info },
>  	{ .compatible = "ite,it6610", &it6610_chip_info },
>  	{ }
>  };
> @@ -1646,6 +1648,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) &it66121_chip_info },
>  	{ "it6610", (kernel_ulong_t) &it6610_chip_info },
>  	{ }
>  };


  reply	other threads:[~2025-08-14 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 20:41 [PATCH V2 0/3] drm/bridge: it66121: Add it66122 support Nishanth Menon
2025-08-13 20:41 ` [PATCH V2 1/3] dt-bindings: display: bridge: it66121: Add compatible string for IT66122 Nishanth Menon
2025-08-13 20:41 ` [PATCH V2 2/3] drm/bridge: it66121: Convert the vid/pid entries into a list Nishanth Menon
2025-08-13 20:41 ` [PATCH V2 3/3] drm/bridge: it66121: Add it66122 support Nishanth Menon
2025-08-14 10:32   ` Tomi Valkeinen [this message]
2025-08-14 11:06     ` Nishanth Menon
2025-08-13 22:41 ` [PATCH V2 0/3] " 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=0c684542-aacb-4e8c-a1c0-7fc0da78c733@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=afd@ti.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=nm@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox