From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Kate Hsuan <hpa@redhat.com>
Cc: tarang.raval@siliconsignals.io,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Serin Yeh <serin.yeh@intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] media: i2c: imx471: Add Sony IMX471 image sensor driver
Date: Wed, 27 May 2026 14:42:27 +0300 [thread overview]
Message-ID: <ahbYo3CSzkYI3jF9@kekkonen.localdomain> (raw)
In-Reply-To: <CAEth8oGWfYpC2umZ49g5qEp_QoZXNKNJ6vMu2EtmnOy6BxZGBg@mail.gmail.com>
Hi Kate,
On Wed, May 27, 2026 at 02:14:24PM +0800, Kate Hsuan wrote:
> > > +struct imx471 {
> > > + struct v4l2_subdev sd;
> > > + struct media_pad pad;
> > > +
> > > + struct v4l2_ctrl_handler ctrl_handler;
> > > + /* V4L2 Controls */
> > > + struct v4l2_ctrl *link_freq;
> > > + struct v4l2_ctrl *pixel_rate;
> > > + struct v4l2_ctrl *vblank;
> > > + struct v4l2_ctrl *hblank;
> > > + struct v4l2_ctrl *vflip;
> > > + struct v4l2_ctrl *hflip;
> > > + struct v4l2_ctrl *exposure;
> >
> > Do you need all these? At least link_freq remains effectively unused.
> I'll tweak these ctrl based on
> https://libcamera.org/sensor_driver_requirements.html.
I rather meant that you're assigning all of these fields but then not using
them. You could thus remove the fields and the assignments. But I can't say
which ones, apart from link_freq.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2026-05-27 11:42 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 " 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
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 [this message]
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=ahbYo3CSzkYI3jF9@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.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
Powered by JetHome