From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
"Tomi Valkeinen" <tomi.valkeinen+renesas@ideasonboard.com>
Subject: Re: [PATCH 1/4] media: v4l2-subdev: Add cleanup macros for active state
Date: Tue, 24 Sep 2024 20:17:36 +0300 [thread overview]
Message-ID: <20240924171736.GE30551@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20240917-scoped-state-v1-1-b8ba3fbe5952@ideasonboard.com>
Hi Tomi,
Thank you for the patch.
On Tue, Sep 17, 2024 at 05:09:29PM +0300, Tomi Valkeinen wrote:
> From: Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
>
> Add cleanup macros for active state. These can be used to call
> v4l2_subdev_lock_and_get_active_state() and manage the unlocking either
> in unscoped or scoped fashion:
>
> This locks the state, gets it to the 'state' variable, and unlocks when
> exiting the surrounding scope:
>
> CLASS(v4l2_subdev_lock_and_get_active_state, state)(subdev);
>
> This does the same, but inside the given scope:
>
> scoped_v4l2_subdev_lock_and_get_active_state(subdev) {
> }
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
> ---
> include/media/v4l2-subdev.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
> index bd235d325ff9..699007cfffd7 100644
> --- a/include/media/v4l2-subdev.h
> +++ b/include/media/v4l2-subdev.h
> @@ -8,6 +8,7 @@
> #ifndef _V4L2_SUBDEV_H
> #define _V4L2_SUBDEV_H
>
> +#include <linux/cleanup.h>
> #include <linux/types.h>
> #include <linux/v4l2-subdev.h>
> #include <media/media-entity.h>
> @@ -1854,6 +1855,15 @@ v4l2_subdev_lock_and_get_active_state(struct v4l2_subdev *sd)
> return sd->active_state;
> }
>
> +DEFINE_CLASS(v4l2_subdev_lock_and_get_active_state, struct v4l2_subdev_state *,
> + v4l2_subdev_unlock_state(_T),
> + v4l2_subdev_lock_and_get_active_state(sd), struct v4l2_subdev *sd);
> +
> +#define scoped_v4l2_subdev_lock_and_get_active_state(sd) \
> + for (CLASS(v4l2_subdev_lock_and_get_active_state, state)(sd), \
> + *done = NULL; \
> + !done; done = (void *)1)
That a very long name :-S Could this be done using the scoped_guard()
macro instead ? For instance, with spinlocks you can do
scoped_guard(spinlock_irqsave, &dev->lock) {
...
}
It would be nice to be able to write
scoped_guard(v4l2_subdev_state, sd) {
...
}
This being said, we would then end up with the state variable being
named scope, which wouldn't be great.
This is actually one of my issues with the above macros, and especially
scoped_v4l2_subdev_lock_and_get_active_state(). It creates a local state
variable in the scope, which makes the code less readable in my opinion.
We could keep the class and drop
scoped_v4l2_subdev_lock_and_get_active_state(). I think I would like to
shorten the class name then.
Another option is to use DEFINE_FREE() and __free() instead.
> +
> /**
> * v4l2_subdev_init - initializes the sub-device struct
> *
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-09-24 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 14:09 [PATCH 0/4] " Tomi Valkeinen
2024-09-17 14:09 ` [PATCH 1/4] " Tomi Valkeinen
2024-09-24 17:17 ` Laurent Pinchart [this message]
2024-09-24 17:53 ` Tomi Valkeinen
2024-09-25 16:35 ` Laurent Pinchart
2024-09-26 15:26 ` Tomi Valkeinen
2024-09-17 14:09 ` [PATCH 2/4] media: v4l2-subdev: Use state cleanup macros Tomi Valkeinen
2024-09-17 14:09 ` [PATCH 3/4] media: renesas: " Tomi Valkeinen
2024-09-22 10:15 ` Niklas Söderlund
2024-09-24 17:24 ` Laurent Pinchart
2024-09-17 14:09 ` [PATCH 4/4] media: i2c: ds90ub9xx: " Tomi Valkeinen
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=20240924171736.GE30551@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen+renesas@ideasonboard.com \
--cc=tomi.valkeinen@ideasonboard.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®