Hi Sakari, On 12/26/2011 01:53 PM, Sakari Ailus wrote: > On Wed, Dec 21, 2011 at 01:20:56AM +0100, Laurent Pinchart wrote: >> On Wednesday 14 December 2011 13:23:07 Sylwester Nawrocki wrote: >>> The purpose of the new field is to allow the video pipeline elements >>> to negotiate memory buffer size for compressed data frames, where >>> the buffer size cannot be derived from pixel width and height and >>> the pixel code. >>> >>> For VIDIOC_SUBDEV_S_FMT and VIDIOC_SUBDEV_G_FMT ioctls, the >>> framesamples parameter should be calculated by the driver from pixel >>> width, height, color format and other parameters if required and >>> returned to the caller. This applies to compressed data formats only. >>> >>> The application should propagate the framesamples value, whatever >>> returned at the first sub-device within a data pipeline, i.e. at the >>> pipeline's data source. >>> >>> For compressed data formats the host drivers should internally >>> validate the framesamples parameter values before streaming is >>> enabled, to make sure the memory buffer size requirements are >>> satisfied along the pipeline. >>> >>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> >>> Signed-off-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx> >>> -- >>> There is no changes in this patch comparing to v3. >>> --- >>> Documentation/DocBook/media/v4l/dev-subdev.xml | 10 ++++++++-- >>> Documentation/DocBook/media/v4l/subdev-formats.xml | 9 ++++++++- >>> include/linux/v4l2-mediabus.h | 4 +++- >>> 3 files changed, 19 insertions(+), 4 deletions(-) >>> >>> diff --git a/Documentation/DocBook/media/v4l/dev-subdev.xml >>> b/Documentation/DocBook/media/v4l/dev-subdev.xml index 0916a73..b9d24eb >>> 100644 >>> --- a/Documentation/DocBook/media/v4l/dev-subdev.xml >>> +++ b/Documentation/DocBook/media/v4l/dev-subdev.xml >> >>> @@ -160,7 +160,13 @@ >>> guaranteed to be supported by the device. In particular, drivers >>> guarantee that a returned format will not be further changed if passed to >>> an &VIDIOC-SUBDEV-S-FMT; call as-is (as long as external parameters, such >>> as >>> - formats on other pads or links' configuration are not changed). >>> </para> >>> + formats on other pads or links' configuration are not changed). When >>> + a device contains a data encoder, the <structfield> >>> + <link linkend="v4l2-mbus-framefmt-framesamples">framesamples</link> >>> + </structfield> field value may be further changed, if parameters of >>> the >>> + encoding process are changed after the format has been negotiated. In >>> + such situation applications should use &VIDIOC-SUBDEV-G-FMT; ioctl to >>> + query an updated format.</para> >> >> Sorry for answering so late. I've been thinking about this topic (as well as >> the proposed new pixelclock field) quite a lot, and one question strikes me >> here (please don't hate me): does userspace need to care about the >> framesamples field ? It looks like the value is only used inside the kernel, >> and we're relying on on userspace to propagate those values between subdevs. >> >> If that's the case, wouldn't it be better to have an in-kernel API to handle >> this ? I'm a bit concerned about forcing userspace to handle internal >> information to userspace if there's no reason to do so. > > I feel partly the same about pixelrate --- there are sound reasons to export > that to user space still, but the method to do that could be something else > than putting it to v4l2_mbus_framefmt. > > I could think of an in-kernel counterpart for v4l2_mbus_framefmt, say, > v4l2_mbus_framedesc. This could then be passed from subdev to another using > a new subdev op. That might be needed eventually. But I'm not a great fan in general of yet another set of callbacks for media bus frame format set up. > Something else that should probably belong there is information on the frame > format: contrary to what I've previously thought, the sensor metadata is > often sent as part of the same CSI-2 channel. There also can be other types > of data, such as dummy data and data for black level calibration. I wouldn't > want to export all this to the user space --- it shouldn't probably need to > care about it. > > The transmitter of the data (sensor) has this information and the CSI-2 > receiver needs it. Same for the framesamples, as far as I understand. We could try to design some standard data structure for frame metadata - that's how I understood the meaning of struct v4l2_mbus_framedesc. But I doubt such attempts will be sucessful. And how can we distinguish which data is valid and applicable when there is lots of weird stuff in one data structure ? Using media bus pixel code only ? > Pixelrate is also used to figure out whether a pipeline can do streaming or > not; the pixel rate originating from the sensor could be higher than the > maximum of the ISP. For this reason, as well as for providing timing > information, access to pixelrate is reequired in the user space. > > Configuring the framesamples could be done on the sensor using a control if > necessary. Sure, that could work. But as I mentioned before, the host drivers would have to be getting such control internally from subdevs. Not so nice IMHO. Although I'm not in big opposition to that too. Grepping for v4l2_ctrl_g_ctrl() all the drivers appear to use it locally only. > Just my 5 euro cents. Perhaps we could discuss the topic on #v4l-meeting > some time? I'm available any time this week. :) -- Thanks, Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
