Hi Laurent,
Thanks for looking at this!
On Mon, Jun 19, 2017 at 6:17 PM, Laurent Pinchart
<laurent.pinchart@xxxxxxxxxxxxxxxx> wrote:
> Hi Tomasz,
>
> On Friday 16 Jun 2017 17:35:52 Tomasz Figa wrote:
>> On Fri, Jun 16, 2017 at 5:25 PM, Sakari Ailus wrote:
>> > On Fri, Jun 16, 2017 at 02:52:07PM +0900, Tomasz Figa wrote:
>> >> On Tue, Jun 6, 2017 at 7:09 PM, Tomasz Figa wrote:
>> >>> On Tue, Jun 6, 2017 at 5:04 PM, Hans Verkuil wrote:
>> >>>> On 06/06/17 09:25, Sakari Ailus wrote:
>> >>>>> On Tue, Jun 06, 2017 at 01:30:41PM +0900, Tomasz Figa wrote:
>> >>>>>> On Tue, Jun 6, 2017 at 1:30 PM, Tomasz Figa wrote:
>> >>>>>>> On Tue, Jun 6, 2017 at 5:39 AM, Yong Zhi wrote:
>> >>>>>>>> Add the IPU3 specific processing parameter format
>> >>>>>>>> V4L2_META_FMT_IPU3_PARAMS and metadata formats
>> >>>>>>>> for 3A and other statistics:
>> >>>>>>>
>> >>>>>>> Please see my comments inline.
>> >>>>>>>
>> >>>>>>>> V4L2_META_FMT_IPU3_PARAMS
>> >>>>>>>> V4L2_META_FMT_IPU3_STAT_3A
>> >>>>>>>> V4L2_META_FMT_IPU3_STAT_DVS
>> >>>>>>>> V4L2_META_FMT_IPU3_STAT_LACE
>> >>>>>>>>
>> >>>>>>>> Signed-off-by: Yong Zhi <yong.zhi@xxxxxxxxx>
>> >>>>>>>> ---
>> >>>>>>>>
>> >>>>>>>> drivers/media/v4l2-core/v4l2-ioctl.c | 4 ++++
>> >>>>>>>> include/uapi/linux/videodev2.h | 6 ++++++
>> >>>>>>>> 2 files changed, 10 insertions(+)
>> >>>>>>>
>> >>>>>>> [snip]
>> >>>>>>>
>> >>>>>>>> +/* Vendor specific - used for IPU3 camera sub-system */
>> >>>>>>>> +#define V4L2_META_FMT_IPU3_PARAMS v4l2_fourcc('i', 'p', '3',
>> >>>>>>>> 'p') /* IPU3 params */
>> >>>>>>>> +#define V4L2_META_FMT_IPU3_STAT_3A v4l2_fourcc('i', 'p', '3',
>> >>>>>>>> 's') /* IPU3 3A statistics */
>> >>>>>>>> +#define V4L2_META_FMT_IPU3_STAT_DVS v4l2_fourcc('i', 'p', '3',
>> >>>>>>>> 'd') /* IPU3 DVS statistics */
>> >>>>>>>> +#define V4L2_META_FMT_IPU3_STAT_LACE v4l2_fourcc('i', 'p', '3',
>> >>>>>>>> 'l') /* IPU3 LACE statistics */
>
> This series is missing a documentation patch with a clear and detailed
> description of the buffer contents for each of these formats. I'm not very
> concerned about the three statistics formats (although that might change after
> reading the documentation), but the "IPU3 params" format makes me feel nervous
> already.
I guess this is a note addressed to patch authors. :)
>
>> >>>>>>> We had some discussion about this with Laurent and if I remember
>> >>>>>>> correctly, the conclusion was that it might make sense to define
>> >>>>>>> one FourCC for a vendor specific format, ('v', 'n', 'd', 'r') for
>> >>>>>>> example, and then have a V4L2-specific enum within the
>> >>>>>>> v4l2_pix_format(_mplane) struct that specifies the exact vendor data
>> >>>>>>> type.
>
> If I recall correctly, I mentioned that v4l2_format now has a struct
> v4l2_meta_format field that can be used to pass metadata-related parameters
> the same way that v4l2_pix_format passes image-related parameters. The only
> two metadata parameters currently defined are the data format (fourcc) and
> buffer size, and more can be added if needed. However, I don't think the
> v4l2_meta_format structure should be extended with vendor-specific fields.
Ah, then I got that wrong, sorry. But in general I believe we reached
exactly the same conclusion with Hans and Sakari after that.
Best regards,
Tomasz
