From: Michael Riesch <michael.riesch@wolfvision.net>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com,
Martin Hecht <martin.hecht@avnet.eu>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Sebastian Reichel <sre@kernel.org>,
Zhi Mao <zhi.mao@mediatek.com>,
Alain Volmat <alain.volmat@foss.st.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Umang Jain <umang.jain@ideasonboard.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Julien Massot <julien.massot@collabora.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Nicholas Roth <nicholas@rothemail.net>,
Paul Elder <paul.elder@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] media: i2c: imx415: Drop HAS_EVENTS flag
Date: Thu, 31 Oct 2024 22:38:35 +0100 [thread overview]
Message-ID: <02802b4a-af44-45ef-892d-870423fc8a38@wolfvision.net> (raw)
In-Reply-To: <20241029225632.3019083-3-tomm.merciai@gmail.com>
Hi all,
Sorry for the recent HTML mail. Let's try again -- hopefully it works now.
On 10/29/24 23:56, Tommaso Merciai wrote:
> v4l2_subdev_init_finalize() already sets the HAS_EVENTS flag if a
> control handler is set. Let's drop the HAS_EVENTS flag.
>
> Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
Thanks for the patch.
Acked-by: Michael Riesch <michael.riesch@wolfvision.net>
Best regards,
Michael
> ---
> drivers/media/i2c/imx415.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/media/i2c/imx415.c b/drivers/media/i2c/imx415.c
> index a20b0db330d3..3f7924aa1bd3 100644
> --- a/drivers/media/i2c/imx415.c
> +++ b/drivers/media/i2c/imx415.c
> @@ -1113,8 +1113,7 @@ static int imx415_subdev_init(struct imx415 *sensor)
> if (ret)
> return ret;
>
> - sensor->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE |
> - V4L2_SUBDEV_FL_HAS_EVENTS;
> + sensor->subdev.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
> sensor->pad.flags = MEDIA_PAD_FL_SOURCE;
> sensor->subdev.entity.function = MEDIA_ENT_F_CAM_SENSOR;
> ret = media_entity_pads_init(&sensor->subdev.entity, 1, &sensor->pad);
prev parent reply other threads:[~2024-10-31 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:56 [PATCH v2 0/2] media: i2c: Drop HAS_EVENTS and event handlers Tommaso Merciai
2024-10-29 22:56 ` [PATCH v2 1/2] " Tommaso Merciai
2024-10-29 22:56 ` [PATCH v2 2/2] media: i2c: imx415: Drop HAS_EVENTS flag Tommaso Merciai
2024-10-30 19:40 ` Laurent Pinchart
2024-10-31 21:38 ` Michael Riesch [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=02802b4a-af44-45ef-892d-870423fc8a38@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=alain.volmat@foss.st.com \
--cc=bingbu.cao@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=julien.massot@collabora.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.hecht@avnet.eu \
--cc=mchehab@kernel.org \
--cc=nicholas@rothemail.net \
--cc=paul.elder@ideasonboard.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tomm.merciai@gmail.com \
--cc=umang.jain@ideasonboard.com \
--cc=zhi.mao@mediatek.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®