From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tarang Raval <tarang.raval@siliconsignals.io>
Cc: Kate Hsuan <hpa@redhat.com>, Serin Yeh <serin.yeh@intel.com>,
Damjan Georgievski <gdamjan@gmail.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v5 3/3] media: i2c: imx471: Add Sony IMX471 image sensor driver
Date: Wed, 24 Jun 2026 13:01:34 +0300 [thread overview]
Message-ID: <ajuq_pDnirv1NvKg@kekkonen.localdomain> (raw)
In-Reply-To: <PN3P287MB1829B3B10DBA560A46BC96038BED2@PN3P287MB1829.INDP287.PROD.OUTLOOK.COM>
On Wed, Jun 24, 2026 at 09:58:11AM +0000, Tarang Raval wrote:
> > So, avdd is necessary.
>
> Could you please try adding a mapping for SONY471A in
> int3472_gpio_map[] in drivers/platform/x86/intel/int3472/discrete.c?
>
> Not fully sure, I have to check, but hopefully it will work.
That's the intent, yes.
--
Sakari Ailus
next prev parent reply other threads:[~2026-06-24 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 3:35 [PATCH v5 0/3] Add Sony IMX471 camera " Kate Hsuan
2026-06-24 3:35 ` [PATCH v5 1/3] media: ipu-bridge: Add DMI information of Lenovo X9 to the image upside-down list Kate Hsuan
2026-06-24 3:35 ` [PATCH v5 2/3] media: ipu-bridge: Add Sony IMX471 for Lenovo X1 Carbon G14 Kate Hsuan
2026-06-24 3:35 ` [PATCH v5 3/3] media: i2c: imx471: Add Sony IMX471 image sensor driver Kate Hsuan
2026-06-24 8:43 ` Tarang Raval
2026-06-24 9:08 ` Kate Hsuan
2026-06-24 9:58 ` Tarang Raval
2026-06-24 10:01 ` Sakari Ailus [this message]
2026-06-25 3:55 ` Kate Hsuan
2026-06-24 8:55 ` Sakari Ailus
2026-06-24 9:30 ` Kate Hsuan
2026-06-24 10:02 ` Sakari Ailus
2026-06-24 10:12 ` Vladimir Zapolskiy
2026-06-25 5:36 ` Kate Hsuan
2026-06-24 13:08 ` Kieran Bingham
2026-06-24 14:06 ` Tarang Raval
2026-06-25 5:46 ` Kate Hsuan
2026-06-26 18:10 Anis TALBI
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=ajuq_pDnirv1NvKg@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.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=serin.yeh@intel.com \
--cc=tarang.raval@siliconsignals.io \
/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
all inboxes | Powered by JetHome®