linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Pearson" <mpearson@squebb.ca>
To: "Kate Hsuan" <hpa@redhat.com>, "Damjan Georgievski" <gdamjan@gmail.com>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Hans de Goede" <johannes.goede@oss.qualcomm.com>,
	"Hans Verkuil" <hverkuil+cisco@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Serin Yeh" <serin.yeh@intel.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Chi-Wei Chen50" <cchen50@lenovo.com>
Subject: Re: [PATCH v3 1/3] media: ipu-bridge: Add DMI information of Lenovo X9 to the image upside-down list
Date: Tue, 02 Jun 2026 22:03:07 -0700	[thread overview]
Message-ID: <38ba48b4-35ec-4514-b805-74ebfc17b328@app.fastmail.com> (raw)
In-Reply-To: <CAEth8oGOEdN9wf15FZ_z73pDj9Hw0+zj_8fd_ZMbMwMkBHrUPA@mail.gmail.com>

Note - switched to my open-source friendly email account.

Hi Kate,

On Tue, Jun 2, 2026, at 2:35 AM, Kate Hsuan wrote:
> Hi Damjan,
>
> Thank you for your review.
>
> On Sat, May 30, 2026 at 6:33 AM Damjan Georgievski <gdamjan@gmail.com> wrote:
>>
>> On 5/22/26 05:11, Kate Hsuan wrote:
>> > The Lenovo X9 has an upside-down-mounted Sony IMX471 sensor so the image
>> > was displayed upside-down. Add the DMI information of Lenovo X9 to
>> > resolve the issue.
>> >
>> > Signed-off-by: Kate Hsuan <hpa@redhat.com>
>> > ---
>> >   drivers/media/pci/intel/ipu-bridge.c | 14 ++++++++++++++
>> >   1 file changed, 14 insertions(+)
>> >
>> > diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
>> > index 32cc95a766b7..1c3364451fa3 100644
>> > --- a/drivers/media/pci/intel/ipu-bridge.c
>> > +++ b/drivers/media/pci/intel/ipu-bridge.c
>> > @@ -118,6 +118,20 @@ static const struct dmi_system_id upside_down_sensor_dmi_ids[] = {
>> >               },
>> >               .driver_data = "OVTI02C1",
>> >       },
>> > +     {
>> > +             .matches = {
>> > +                     DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
>> > +                     DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad X9-14"),
>>
>> Isn't this going to be an issue in the future if/when a "Gen 2" appears?
>
> You can look into the v1 [1]. The DMI_BOARD_NAME is used to
> distinguish the types of X1.
> v3 covers wider ranges of X9-14 and 15. If we agree with v1, I can
> revert this patch to v1.
>
> [1] https://lore.kernel.org/linux-media/20260417083214.222189-2-hpa@redhat.com/
>
I happily defer to Hans on things like this as he has way more experience than me, but we usually use the BOARD_NAME for identifying platforms everywhere else in the kernel so that feels to me 'safer'.

If we do go ahead with PRODUCT_VERSION it should probably be DMI_MATCH_EXACT instead. I think that will work fine, but it is not commonly used and I would worry about the FW team doing weird versions for different markets (the two board names are very standard for Thinkpads)

Mark (currently on vacation - so replies may be delayed)

  reply	other threads:[~2026-06-03  5:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22  3:11 [PATCH v3 0/3] Add Sony IMX471 camera sensor driver Kate Hsuan
2026-05-22  3:11 ` [PATCH v3 1/3] media: ipu-bridge: Add DMI information of Lenovo X9 to the image upside-down list Kate Hsuan
2026-05-29 22:33   ` Damjan Georgievski
2026-06-02  9:35     ` Kate Hsuan
2026-06-03  5:03       ` Mark Pearson [this message]
2026-06-04  3:19         ` Kate Hsuan
2026-05-22  3:11 ` [PATCH v3 2/3] media: i2c: imx471: Add Sony IMX471 image sensor driver Kate Hsuan
2026-05-22 11:12   ` Tarang Raval
2026-05-22 22:38     ` Sakari Ailus
2026-05-27  6:24       ` Kate Hsuan
2026-05-27  6:01     ` Kate Hsuan
2026-05-22 22:48   ` Sakari Ailus
2026-05-27  6:14     ` Kate Hsuan
2026-05-27 11:42       ` Sakari Ailus
2026-06-05  8:43         ` Kate Hsuan
2026-06-05  9:32           ` Tarang Raval
2026-05-22  3:11 ` [PATCH v3 3/3] media: i2c: imx471: Naming the register Kate Hsuan
2026-05-22 22:49   ` Sakari Ailus

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=38ba48b4-35ec-4514-b805-74ebfc17b328@app.fastmail.com \
    --to=mpearson@squebb.ca \
    --cc=cchen50@lenovo.com \
    --cc=gdamjan@gmail.com \
    --cc=hpa@redhat.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=serin.yeh@intel.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;
as well as URLs for NNTP newsgroup(s).