Linux Media Controller development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: dave.stevenson@raspberrypi.com, linux-media@vger.kernel.org,
	mchehab@kernel.org, sakari.ailus@linux.intel.com,
	hverkuil-cisco@xs4all.nl
Subject: Re: [PATCH v2] media: i2c: imx219: Implement get_selection
Date: Tue, 28 Apr 2020 16:41:53 +0300	[thread overview]
Message-ID: <20200428134153.GF5859@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200428134036.askdjybit2lq47t6@uno.localdomain>

Hi Jacopo,

On Tue, Apr 28, 2020 at 03:40:36PM +0200, Jacopo Mondi wrote:
> On Mon, Apr 27, 2020 at 12:05:48AM +0300, Laurent Pinchart wrote:
> > Hi Jacopo,
> >
> > Thank you for the patch.
> >
> 
> [snip]
> 
> > > +
> > > +static int imx219_get_selection(struct v4l2_subdev *sd,
> > > +				struct v4l2_subdev_pad_config *cfg,
> > > +				struct v4l2_subdev_selection *sel)
> > > +{
> > > +	struct imx219 *imx219 = to_imx219(sd);
> > > +	const struct v4l2_rect *__crop;
> > > +
> > > +	if (sel->pad != 0)
> > > +		return -EINVAL;
> > > +
> > > +	mutex_lock(&imx219->mutex);
> > > +
> > > +	switch (sel->target) {
> > > +	case V4L2_SEL_TGT_NATIVE_SIZE:
> > > +		sel->r.top = 0;
> > > +		sel->r.left = 0;
> > > +		sel->r.width = IMX219_NATIVE_WIDTH;
> > > +		sel->r.height = IMX219_NATIVE_HEIGHT;
> > > +		mutex_unlock(&imx219->mutex);
> > > +
> > > +		return 0;
> > > +
> > > +	case V4L2_SEL_TGT_CROP_DEFAULT:
> > > +		sel->r.top = IMX219_PIXEL_ARRAY_TOP;
> > > +		sel->r.left = IMX219_PIXEL_ARRAY_LEFT;
> > > +		sel->r.width = IMX219_PIXEL_ARRAY_WIDTH;
> > > +		sel->r.height = IMX219_PIXEL_ARRAY_HEIGHT;
> > > +		mutex_unlock(&imx219->mutex);
> > > +
> > > +		return 0;
> > > +
> > > +	case V4L2_SEL_TGT_CROP:
> > > +		__crop = __imx219_get_pad_crop(imx219, cfg, sel->pad,
> > > +					       sel->which);
> > > +		sel->r = *__crop;
> > > +		mutex_unlock(&imx219->mutex);
> >
> > I should have thought about it before, but only this case requires
> > locking. Maybe
> 
> I should have thought it better, yes
> 
> >
> > 		__crop = __imx219_get_pad_crop(imx219, cfg, sel->pad,
> > 					       sel->which);
> > 		mutex_lock(&imx219->mutex);
> 
> Actually, retreiveing __crop should be protected too, as the crop
> rectangle is part of the imx219->mode, which is updated by the set_fmt
> operation.

__crop is a pointer, retrieving the pointer doesn't need protection.
Accessing its contents does. No big deal though, it's cheap, as long as
we don't lock for the bounds and default cases.

> I'll wrap the whole case content in a critical session.
> 
> > 		sel->r = *__crop;
> > 		mutex_unlock(&imx219->mutex);
> >
> > and removing the mutex_lock() at the beginning ?
> >
> > > +
> > > +		return 0;
> > > +	}
> > > +
> > > +	mutex_unlock(&imx219->mutex);
> > > +
> > > +	return -EINVAL;
> > > +}
> > > +
> > >  static int imx219_start_streaming(struct imx219 *imx219)
> > >  {
> > >  	struct i2c_client *client = v4l2_get_subdevdata(&imx219->sd);
> > > @@ -1152,6 +1248,7 @@ static const struct v4l2_subdev_pad_ops imx219_pad_ops = {
> > >  	.enum_mbus_code = imx219_enum_mbus_code,
> > >  	.get_fmt = imx219_get_pad_format,
> > >  	.set_fmt = imx219_set_pad_format,
> > > +	.get_selection = imx219_get_selection,
> > >  	.enum_frame_size = imx219_enum_frame_size,
> > >  };
> > >

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-04-28 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 20:52 [PATCH v2] media: i2c: imx219: Implement get_selection Jacopo Mondi
2020-04-26 21:05 ` Laurent Pinchart
2020-04-28 13:40   ` Jacopo Mondi
2020-04-28 13:41     ` Laurent Pinchart [this message]
2020-04-28 14:12       ` Jacopo Mondi
2020-04-26 21:11 ` [PATCH v2.1] " 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=20200428134153.GF5859@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --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