From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Robert Mader <robert.mader@collabora.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
linux-kernel@vger.kernel.org, nicholas@rothemail.net,
javierm@redhat.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2] media: i2c: imx258: Parse and register properties
Date: Tue, 14 Mar 2023 14:33:13 +0200 [thread overview]
Message-ID: <ZBBpiUnKnRGTVPkZ@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <Y7WieRzn4p9NCwsg@paasikivi.fi.intel.com>
On Wed, Jan 04, 2023 at 03:59:53PM +0000, Sakari Ailus wrote:
> Hi Robert,
>
> On Wed, Jan 04, 2023 at 03:14:50PM +0100, Robert Mader wrote:
> > On 04.01.23 15:11, Jacopo Mondi wrote:
> > > Hi Robert
> > >
> > > On Wed, Jan 04, 2023 at 01:23:37PM +0100, Robert Mader wrote:
> > > > Analogous to e.g. the imx219. This enables propagating
> > > > V4L2_CID_CAMERA_ORIENTATION and V4L2_CID_CAMERA_SENSOR_ROTATION
> > > > values.
> > > > The motivation is to allow libcamera detect these values from the
> > > > device tree and propagate them further to e.g. Pipewire.
> > > >
> > > > While at it, reserve space for 3 additional controls even if
> > > > v4l2_ctrl_new_fwnode_properties() can only register 2 of
> > > > them, to fix the existing implementation which reserve space for 8
> > > > controls but actually registers 9.
> > > >
> > > > Changes in v2:
> > > > - Reserve 11 instead of 10 controls
> > > > - Change order of variable declaration
> > > > - Slightly extend description
> > > This part should go below, after ---, as it shouldn't be part of the commit
> > > message
> > >
> > > The patch looks good
> > >
> > > Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> > Thanks! And ops, right, make sense. Should I spin a v3 for that or is it
> > simple enough to fix when pulling?
>
> I can fix it while applying the patch.
No need for line breaks after period, just let your editor to break them
before 74 or so.
--
Sakari Ailus
prev parent reply other threads:[~2023-03-14 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 12:23 Robert Mader
2023-01-04 14:11 ` Jacopo Mondi
2023-01-04 14:14 ` Robert Mader
2023-01-04 15:59 ` Sakari Ailus
2023-03-14 12:33 ` Sakari Ailus [this message]
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=ZBBpiUnKnRGTVPkZ@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=jacopo.mondi@ideasonboard.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicholas@rothemail.net \
--cc=robert.mader@collabora.com \
--cc=sakari.ailus@linux.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
all inboxes | Powered by JetHome®