From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Shunqian Zheng <zhengsq@rock-chips.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] media: i2c: ov2685: Add controls from fwnode
Date: Sun, 29 Jan 2023 12:26:28 +0100 [thread overview]
Message-ID: <20230129112628.rb6h4xdfwvs3hbl7@uno.localdomain> (raw)
In-Reply-To: <20230129-ov2685-improvements-v1-3-f281bd49399c@z3ntu.xyz>
Hi Luca,
On Sun, Jan 29, 2023 at 10:42:37AM +0100, Luca Weiss wrote:
> Add V4L2_CID_CAMERA_ORIENTATION and V4L2_CID_CAMERA_SENSOR_ROTATION
> controls to the ov2685 driver by attempting to parse them from firmware.
>
> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> ---
> drivers/media/i2c/ov2685.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/media/i2c/ov2685.c b/drivers/media/i2c/ov2685.c
> index 844a91dbc8e5..bfced11b178b 100644
> --- a/drivers/media/i2c/ov2685.c
> +++ b/drivers/media/i2c/ov2685.c
> @@ -17,6 +17,7 @@
> #include <media/media-entity.h>
> #include <media/v4l2-async.h>
> #include <media/v4l2-ctrls.h>
> +#include <media/v4l2-fwnode.h>
> #include <media/v4l2-subdev.h>
>
> #define CHIP_ID 0x2685
> @@ -613,6 +614,7 @@ static int ov2685_initialize_controls(struct ov2685 *ov2685)
> const struct ov2685_mode *mode;
> struct v4l2_ctrl_handler *handler;
> struct v4l2_ctrl *ctrl;
> + struct v4l2_fwnode_device_properties props;
> u64 exposure_max;
> u32 pixel_rate, h_blank;
> int ret;
> @@ -661,6 +663,15 @@ static int ov2685_initialize_controls(struct ov2685 *ov2685)
> ARRAY_SIZE(ov2685_test_pattern_menu) - 1,
> 0, 0, ov2685_test_pattern_menu);
>
As the below function can register up to 2 controls, you should also
reserve space for them when initializing the control handler to avoid
relocations
- ret = v4l2_ctrl_handler_init(handler, 8);
+ ret = v4l2_ctrl_handler_init(handler, 10);
> + /* set properties from fwnode (e.g. rotation, orientation) */
> + ret = v4l2_fwnode_device_parse(&ov2685->client->dev, &props);
> + if (ret)
> + goto err_free_handler;
> +
> + ret = v4l2_ctrl_new_fwnode_properties(handler, &ov2685_ctrl_ops, &props);
> + if (ret)
> + goto err_free_handler;
> +
> if (handler->error) {
> ret = handler->error;
> dev_err(&ov2685->client->dev,
>
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-01-29 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 9:42 [PATCH 0/4] Improvements for OmniVision OV2685 driver Luca Weiss
2023-01-29 9:42 ` [PATCH 1/4] media: i2c: ov2685: Make reset gpio optional Luca Weiss
2023-01-29 11:22 ` Jacopo Mondi
2023-01-29 11:49 ` Luca Weiss
2023-01-29 13:05 ` Jacopo Mondi
2023-01-29 9:42 ` [PATCH 2/4] media: i2c: ov2685: Add print for power on write failed Luca Weiss
2023-01-29 11:24 ` Jacopo Mondi
2023-01-29 9:42 ` [PATCH 3/4] media: i2c: ov2685: Add controls from fwnode Luca Weiss
2023-01-29 11:26 ` Jacopo Mondi [this message]
2023-01-29 9:42 ` [PATCH 4/4] media: i2c: ov2685: Add .get_selection() support Luca Weiss
2023-01-29 11:29 ` Jacopo Mondi
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=20230129112628.rb6h4xdfwvs3hbl7@uno.localdomain \
--to=jacopo.mondi@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=zhengsq@rock-chips.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®