From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: 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>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
Robert Nelson <robertcnelson@gmail.com>,
Jason Kridner <jkridner@beagleboard.org>,
<tomi.valkeinen@ideasonboard.com>, <devarsht@ti.com>
Subject: Re: [PATCH V3 3/4] drm/bridge: it66121: Use vid/pid to detect the type of chip
Date: Fri, 15 Aug 2025 10:22:38 -0500 [thread overview]
Message-ID: <20250815152238.culfazudi4le2ykt@gravy> (raw)
In-Reply-To: <e3416746-ee96-449d-8a17-28efcd391c55@ti.com>
On 08:52-20250815, Andrew Davis wrote:
> > This also allows for some future compatibility to be checked only
> > against a restricted set of vid/pid.
^^ See below
> > static const struct of_device_id it66121_dt_match[] = {
> > - { .compatible = "ite,it66121", &it66121_chip_info },
> > - { .compatible = "ite,it6610", &it6610_chip_info },
> > + { .compatible = "ite,it66121", &it66xx_chip_info },
> > + { .compatible = "ite,it6610", &it66xx_chip_info },
>
> If you will pass in the same data to all devices, just don't pass
> anything. Move the it66121_dt_match table up above probe, and just
> use it, no need for fetching it from i2c_get_match_data().
(rationale in commit messsage)
Yeah, I was going to do that, but this vendor has a bunch of devices and
I am not able to see all possible combinations.. so was thinking that
maybe some combination device will need different checks with a limited
vid/pid list.. just lack of public documentation makes me a bit
paranoid.
I am not tied to this that hard (it was a "meh"), so if folks feel this
can be thrown out, can respin.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
next prev parent reply other threads:[~2025-08-15 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 3:41 [PATCH V3 0/4] drm/bridge: it66121: Add initial it66122 support Nishanth Menon
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 [this message]
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=20250815152238.culfazudi4le2ykt@gravy \
--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