public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: g@valkosipuli.retiisi.org.uk, linux-media@vger.kernel.org
Subject: Re: [PATCH] v4l: omap3isp: Move code out of mutex-protected section
Date: Mon, 04 Nov 2013 14:17:53 +0100	[thread overview]
Message-ID: <3877980.gXG2nDA4fQ@avalon> (raw)
In-Reply-To: <20131104112010.GB21655@valkosipuli.retiisi.org.uk>

Hi Sakari,

On Monday 04 November 2013 13:20:11 Sakari Ailus wrote:
> Hi Laurent,
> 
> Thanks for the patch.
> 
> On Mon, Nov 04, 2013 at 11:07:48AM +0100, Laurent Pinchart wrote:
> > The pad::get_fmt call must be protected by a mutex, but preparing its
> > arguments doesn't need to be. Move the non-critical code out of the
> > mutex-protected section.
> > 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> > 
> >  drivers/media/platform/omap3isp/ispvideo.c | 7 ++-----
> >  1 file changed, 2 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/media/platform/omap3isp/ispvideo.c
> > b/drivers/media/platform/omap3isp/ispvideo.c index a908d00..f6304bb
> > 100644
> > --- a/drivers/media/platform/omap3isp/ispvideo.c
> > +++ b/drivers/media/platform/omap3isp/ispvideo.c
> > @@ -339,14 +339,11 @@ __isp_video_get_format(struct isp_video *video,
> > struct v4l2_format *format)> 
> >  	if (subdev == NULL)
> >  	
> >  		return -EINVAL;
> > 
> > -	mutex_lock(&video->mutex);
> > -
> > 
> >  	fmt.pad = pad;
> >  	fmt.which = V4L2_SUBDEV_FORMAT_ACTIVE;
> > 
> > -	ret = v4l2_subdev_call(subdev, pad, get_fmt, NULL, &fmt);
> > -	if (ret == -ENOIOCTLCMD)
> > -		ret = -EINVAL;
> 
> By removing these lines, you're also returning -ENOIOCTLCMD to the caller.
> Is this intentional?
> 
> That return value will end up to at least one place which seems to be
> isp_video_streamon() and, unless I'm mistaken, will cause
> ioctl(VIDIOC_STREAMON) also return ENOTTY.

I should have split this in two patches, or at least explained the rationale 
in the commit message. The remote subdev is always an internal ISP subdev, the 
pad::get_fmt operation is thus guaranteed to be implemented. There's no need 
to check for ENOIOCTLCMD.

> > +	mutex_lock(&video->mutex);
> > +	ret = v4l2_subdev_call(subdev, pad, get_fmt, NULL, &fmt);
> > 
> >  	mutex_unlock(&video->mutex);
> >  	
> >  	if (ret)
-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-11-04 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 10:07 [PATCH] v4l: omap3isp: Move code out of mutex-protected section Laurent Pinchart
2013-11-04 11:20 ` Sakari Ailus
2013-11-04 13:17   ` Laurent Pinchart [this message]
2013-11-04 13:21     ` Sakari Ailus

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=3877980.gXG2nDA4fQ@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=g@valkosipuli.retiisi.org.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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