From: Robert Mader <robert.mader@collabora.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: 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] media: i2c: imx258: Parse and register properties
Date: Wed, 4 Jan 2023 13:47:00 +0100 [thread overview]
Message-ID: <62b0d46f-7962-ad5f-dd4e-5820d76964b4@collabora.com> (raw)
In-Reply-To: <Y7Uo3JlOoGJAoorz@paasikivi.fi.intel.com>
Sure, makes sense!
Send out v2 now.
On 04.01.23 08:21, Sakari Ailus wrote:
> Hi Jacopo, Robert,
>
> On Tue, Jan 03, 2023 at 06:16:24PM +0100, Jacopo Mondi wrote:
>> Hi Robert
>>
>> On Tue, Jan 03, 2023 at 03:11:44PM +0100, Robert Mader wrote:
>>> On 02.01.23 15:06, Jacopo Mondi wrote:
>>>> Hi Robert
>>>>
>>>> On Sun, Dec 25, 2022 at 04:42:34PM +0100, Robert Mader wrote:
>>>>> Analogous to e.g. the imx219. This enables propagating
>>>>> V4L2_CID_CAMERA_SENSOR_ROTATION values so that libcamera
>>>>> can detect the correct rotation from the device tree
>>>>> and propagate it further to e.g. Pipewire.
>>>>>
>>>>> Signed-off-by: Robert Mader <robert.mader@collabora.com>
>>>>> ---
>>>>> drivers/media/i2c/imx258.c | 13 ++++++++++++-
>>>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/media/i2c/imx258.c b/drivers/media/i2c/imx258.c
>>>>> index eab5fc1ee2f7..85819043d1e3 100644
>>>>> --- a/drivers/media/i2c/imx258.c
>>>>> +++ b/drivers/media/i2c/imx258.c
>>>>> @@ -9,6 +9,7 @@
>>>>> #include <linux/pm_runtime.h>
>>>>> #include <media/v4l2-ctrls.h>
>>>>> #include <media/v4l2-device.h>
>>>>> +#include <media/v4l2-fwnode.h>
>>>>> #include <asm/unaligned.h>
>>>>>
>>>>> #define IMX258_REG_VALUE_08BIT 1
>>>>> @@ -1149,6 +1150,7 @@ static int imx258_init_controls(struct imx258 *imx258)
>>>>> {
>>>>> struct i2c_client *client = v4l2_get_subdevdata(&imx258->sd);
>>>>> struct v4l2_ctrl_handler *ctrl_hdlr;
>>>>> + struct v4l2_fwnode_device_properties props;
>>>> Might be nicer to move this one line up
>>> Can you say what's your reasoning? I personally slightly prefer
>>> alphabetical order, but no strong opinion :)
>>>
>> I've often been instructed to try to respect the inverse-xmas-tree
> I'd advise the same, unless there are other reasons to arrange the lines
> differently.
>
prev parent reply other threads:[~2023-01-04 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 15:42 Robert Mader
2023-01-02 14:06 ` Jacopo Mondi
2023-01-03 14:11 ` Robert Mader
2023-01-03 17:16 ` Jacopo Mondi
2023-01-04 7:21 ` Sakari Ailus
2023-01-04 12:47 ` Robert Mader [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=62b0d46f-7962-ad5f-dd4e-5820d76964b4@collabora.com \
--to=robert.mader@collabora.com \
--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=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®