linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
	linux-media@vger.kernel.org, a.hajda@samsung.com,
	hverkuil@xs4all.nl, kyungmin.park@samsung.com,
	sw0312.kim@samsung.com
Subject: Re: [PATCH RFC] V4L: Add s_rx_buffer subdev video operation
Date: Mon, 24 Sep 2012 19:05:27 +0200	[thread overview]
Message-ID: <506092D7.9040807@samsung.com> (raw)
In-Reply-To: <8816374.onnX7s7R5d@avalon>

Hi Laurent,

On 09/24/2012 03:58 PM, Laurent Pinchart wrote:
>> How about useing a separate video buffer queue for the purpose? That would
>> provide a nice way to pass it to the user space where it's needed. It'd also
>> play nicely together with the frame layout descriptors.
> 
> Beside, a void *buf wouldn't support DMA. Only subdevs that use PIO to 
> transfer meta data could be supported by this.

I guess most of MIPI-CSI2 receivers out there support data capture
from distinct Data Types into separate DMA buffers. But not this one.
In case of multi-context DMA engine I guess MIPI-CSI2 receiver driver
would expose video node anyway and it wouldn't need such a callback
at all ?

Perhaps using struct v4l2_subdev_core_ops::ioctl would be more
appropriate here ?

--

Regards,
Sylwester

  reply	other threads:[~2012-09-24 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 13:26 [PATCH RFC] V4L: Add s_rx_buffer subdev video operation Sylwester Nawrocki
2012-09-24 13:44 ` Sakari Ailus
2012-09-24 13:58   ` Laurent Pinchart
2012-09-24 17:05     ` Sylwester Nawrocki [this message]
2012-09-24 16:51   ` Sylwester Nawrocki
2012-09-24 18:26     ` Sakari Ailus
2012-09-25  9:48       ` Sylwester Nawrocki
2012-09-26 20:49         ` 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=506092D7.9040807@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=a.hajda@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kyungmin.park@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=sw0312.kim@samsung.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;
as well as URLs for NNTP newsgroup(s).