public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-media@vger.kernel.org, linux-sh@vger.kernel.org,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Katsuya MATSUBARA <matsu@igel.co.jp>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Subject: Re: [PATCH v5 7/9] v4l: Renesas R-Car VSP1 driver
Date: Fri, 02 Aug 2013 13:16:35 +0200	[thread overview]
Message-ID: <85967578.E7nGVEdzp4@avalon> (raw)
In-Reply-To: <51FB9481.2090202@xs4all.nl>

On Friday 02 August 2013 13:14:09 Hans Verkuil wrote:
> On 08/02/2013 12:57 PM, Laurent Pinchart wrote:
> > On Friday 02 August 2013 11:23:46 Hans Verkuil wrote:
> >> On 08/02/2013 03:03 AM, Laurent Pinchart wrote:
> >>> The VSP1 is a video processing engine that includes a blender, scalers,
> >>> filters and statistics computation. Configurable data path routing logic
> >>> allows ordering the internal blocks in a flexible way.
> >>> 
> >>> Due to the configurable nature of the pipeline the driver implements the
> >>> media controller API and doesn't use the V4L2 mem-to-mem framework, even
> >>> though the device usually operates in memory to memory mode.
> >>> 
> >>> Only the read pixel formatters, up/down scalers, write pixel formatters
> >>> and LCDC interface are supported at this stage.
> >>> 
> >>> Signed-off-by: Laurent Pinchart
> >>> <laurent.pinchart+renesas@ideasonboard.com>
> >>> Acked-by: Sakari Ailus <sakari.ailus@iki.fi>
> >>> 
> >>> diff --git a/drivers/media/platform/vsp1/vsp1_uds.h
> >>> b/drivers/media/platform/vsp1/vsp1_uds.h new file mode 100644
> >>> index 0000000..972a285
> > 
> > [snip]
> > 
> >>> +int vsp1_video_init(struct vsp1_video *video, struct vsp1_entity *rwpf)
> >>> +{
> >>> +	const char *direction;
> >>> +	int ret;
> >>> +
> >>> +	switch (video->type) {
> >>> +	case V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE:
> >>> +		direction = "output";
> >>> +		video->pad.flags = MEDIA_PAD_FL_SINK;
> >>> +		break;
> >>> +
> >>> +	case V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE:
> >>> +		direction = "input";
> >>> +		video->pad.flags = MEDIA_PAD_FL_SOURCE;
> >>> +		video->video.vfl_dir = VFL_DIR_TX;
> >>> +		break;
> >>> +
> >>> +	default:
> >>> +		return -EINVAL;
> >>> +	}
> >>> +
> >>> +	video->rwpf = rwpf;
> >>> +
> >>> +	mutex_init(&video->lock);
> >>> +	spin_lock_init(&video->irqlock);
> >>> +	INIT_LIST_HEAD(&video->irqqueue);
> >>> +
> >>> +	mutex_init(&video->pipe.lock);
> >>> +	spin_lock_init(&video->pipe.irqlock);
> >>> +	INIT_LIST_HEAD(&video->pipe.entities);
> >>> +	init_waitqueue_head(&video->pipe.wq);
> >>> +	video->pipe.state = VSP1_PIPELINE_STOPPED;
> >>> +
> >>> +	/* Initialize the media entity... */
> >>> +	ret = media_entity_init(&video->video.entity, 1, &video->pad, 0);
> >>> +	if (ret < 0)
> >>> +		return ret;
> >>> +
> >>> +	/* ... and the format ... */
> >>> +	video->fmtinfo = vsp1_get_format_info(VSP1_VIDEO_DEF_FORMAT);
> >>> +	video->format.pixelformat = video->fmtinfo->fourcc;
> >>> +	video->format.colorspace = V4L2_COLORSPACE_SRGB;
> >>> +	video->format.field = V4L2_FIELD_NONE;
> >>> +	video->format.width = VSP1_VIDEO_DEF_WIDTH;
> >>> +	video->format.height = VSP1_VIDEO_DEF_HEIGHT;
> >>> +	video->format.num_planes = 1;
> >>> +	video->format.plane_fmt[0].bytesperline =
> >>> +		video->format.width * video->fmtinfo->bpp[0] / 8;
> >>> +	video->format.plane_fmt[0].sizeimage =
> >>> +		video->format.plane_fmt[0].bytesperline * video->format.height;
> >>> +
> >>> +	/* ... and the video node... */
> >>> +	video->video.v4l2_dev = &video->vsp1->v4l2_dev;
> >>> +	video->video.fops = &vsp1_video_fops;
> >>> +	snprintf(video->video.name, sizeof(video->video.name), "%s %s",
> >>> +		 rwpf->subdev.name, direction);
> >>> +	video->video.vfl_type = VFL_TYPE_GRABBER;
> >>> +	video->video.release = video_device_release_empty;
> >>> +	video->video.ioctl_ops = &vsp1_video_ioctl_ops;
> >>> +
> >>> +	video_set_drvdata(&video->video, video);
> >>> +
> >>> +	/* ... and the buffers queue... */
> >>> +	video->alloc_ctx = vb2_dma_contig_init_ctx(video->vsp1->dev);
> >>> +	if (IS_ERR(video->alloc_ctx))
> >>> +		goto error;
> >>> +
> >>> +	video->queue.type = video->type;
> >>> +	video->queue.io_modes = VB2_MMAP | VB2_USERPTR | VB2_DMABUF;
> >>> +	video->queue.drv_priv = video;
> >>> +	video->queue.buf_struct_size = sizeof(struct vsp1_video_buffer);
> >>> +	video->queue.ops = &vsp1_video_queue_qops;
> >>> +	video->queue.mem_ops = &vb2_dma_contig_memops;
> >>> +	video->queue.timestamp_type = V4L2_BUF_FLAG_TIMESTAMP_COPY;
> >> 
> >> If you set video->queue.lock to &video->lock, then you can drop all the
> >> vb2 ioctl and fop helper functions directly without having to make your
> >> own wrapper functions.
> > 
> > Right, I'll do so. I will also drop the manual lock handling from the
> > STREAMON and STREAMOFF handlers, as the core will use the queue lock for
> > those.
> >
> >> It saves a fair bit of code that way. The only place where there is a
> >> difference as far as I can see is in vb2_fop_mmap: there the queue.lock
> >> isn't taken whereas you do take the lock. It has never been 100% clear to
> >> me whether or not that lock should be taken. However, as far as I can
> >> tell vb2_mmap never calls any driver callbacks, so it seems to be me that
> >> there is no need to take the lock.
> > 
> > Couldn't mmap() race with for instance REQBUFS(0) if we don't lock it ?
> 
> Hmm, good point. It would require a very convoluted program, but yes, there
> is a possible race condition. The same is true for vb2_get_unmapped_area.
> 
> Can you prepare a patch adding locking for these two fops?

Sure, will do.


-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-08-02 11:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  1:03 [PATCH v5 0/9] Renesas VSP1 driver Laurent Pinchart
2013-08-02  1:03 ` [PATCH v5 1/9] media: Add support for circular graph traversal Laurent Pinchart
2013-08-02  9:44   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 2/9] Documentation: media: Clarify the VIDIOC_CREATE_BUFS format requirements Laurent Pinchart
2013-08-02  9:43   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 3/9] videobuf2: Clarify queue_setup() and buf_prepare() usage documentation Laurent Pinchart
2013-08-02  9:45   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 4/9] v4l: Fix V4L2_MBUS_FMT_YUV10_1X30 media bus pixel code value Laurent Pinchart
2013-08-02  9:45   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 5/9] v4l: Add media format codes for ARGB8888 and AYUV8888 on 32-bit busses Laurent Pinchart
2013-08-02  9:47   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 6/9] v4l: Add V4L2_PIX_FMT_NV16M and V4L2_PIX_FMT_NV61M formats Laurent Pinchart
2013-08-02  9:54   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 7/9] v4l: Renesas R-Car VSP1 driver Laurent Pinchart
2013-08-02  9:23   ` Hans Verkuil
2013-08-02 10:57     ` Laurent Pinchart
2013-08-02 11:14       ` Hans Verkuil
2013-08-02 11:16         ` Laurent Pinchart [this message]
2013-08-02  1:03 ` [PATCH v5 8/9] vsp1: Fix lack of the sink entity registration for enabled links Laurent Pinchart
2013-08-02  9:55   ` Hans Verkuil
2013-08-02  1:03 ` [PATCH v5 9/9] vsp1: Use the maximum number of entities defined in platform data Laurent Pinchart
2013-08-02  9:55   ` Hans Verkuil

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=85967578.E7nGVEdzp4@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=matsu@igel.co.jp \
    --cc=sakari.ailus@iki.fi \
    --cc=sylvester.nawrocki@gmail.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