From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
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 15:58:44 +0200 [thread overview]
Message-ID: <8816374.onnX7s7R5d@avalon> (raw)
In-Reply-To: <20120924134453.GH12025@valkosipuli.retiisi.org.uk>
On Monday 24 September 2012 16:44:54 Sakari Ailus wrote:
> On Mon, Sep 24, 2012 at 03:26:53PM +0200, Sylwester Nawrocki wrote:
> > The s_rx_buffer callback allows the host to set buffer for non-image
> > (meta) data at a subdev. This callback can be implemented by an image
> > sensor or a MIPI-CSI receiver, allowing the host to retrieve the frame
> > embedded data from a subdev.
> >
> > Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > ---
> >
> > include/media/v4l2-subdev.h | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
> > index 22ab09e..28067ed 100644
> > --- a/include/media/v4l2-subdev.h
> > +++ b/include/media/v4l2-subdev.h
> > @@ -274,6 +274,10 @@ struct v4l2_subdev_audio_ops {
> >
> > s_mbus_config: set a certain mediabus configuration. This operation is
> > added>
> > for compatibility with soc-camera drivers and should not be used by
new
> > software.
> >
> > +
> > + s_rx_buffer: set a host allocated memory buffer for the subdev. The
> > subdev + can adjust @size to a lower value and must not write more data
> > to the + buffer starting at @data than the original value of @size.
> >
> > */
> >
> > struct v4l2_subdev_video_ops {
> >
> > int (*s_routing)(struct v4l2_subdev *sd, u32 input, u32 output, u32
> > config);>
> > @@ -327,6 +331,8 @@ struct v4l2_subdev_video_ops {
> >
> > struct v4l2_mbus_config *cfg);
> >
> > int (*s_mbus_config)(struct v4l2_subdev *sd,
> >
> > const struct v4l2_mbus_config *cfg);
> >
> > + int (*s_rx_buffer)(struct v4l2_subdev *sd, void *buf,
> > + unsigned int *size);
> >
> > };
> >
> > /*
>
> 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.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-09-24 13:58 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 [this message]
2012-09-24 17:05 ` Sylwester Nawrocki
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=8816374.onnX7s7R5d@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--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).