From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>,
horms@verge.net.au, magnus.damm@gmail.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
mchehab@osg.samsung.com
Cc: laurent.pinchart@ideasonboard.com, j.anaszewski@samsung.com,
kamil@wypas.org, sergei.shtylyov@cogentembedded.com,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] R-Car JPEG Processing Unit
Date: Wed, 22 Jul 2015 08:08:39 +0200 [thread overview]
Message-ID: <55AF3367.5040503@xs4all.nl> (raw)
In-Reply-To: <1437444022-28916-1-git-send-email-mikhail.ulyanov@cogentembedded.com>
Hi Mikhail,
Just one small thing, see below...
On 07/21/2015 04:00 AM, Mikhail Ulyanov wrote:
> This series of patches contains a driver for the JPEG codec integrated
> peripheral found in the Renesas R-Car SoCs and associated DT documentation.
>
> This series of patches is against the 'master' branch of
> linuxtv.org/media_tree.git
>
> v4l2-compliance -s
>
> Driver Info:
> Driver name : rcar_jpu
> Card type : rcar_jpu encoder
> Bus info : platform:fe980000.jpu
> Driver version: 4.2.0
> Capabilities : 0x84204000
> Video Memory-to-Memory Multiplanar
> Streaming
> Extended Pix Format
> Device Capabilities
> Device Caps : 0x04204000
> Video Memory-to-Memory Multiplanar
> Streaming
> Extended Pix Format
>
> Compliance test for device /dev/video0 (not using libv4l2):
>
> Required ioctls:
> test VIDIOC_QUERYCAP: OK
>
> Allow for multiple opens:
> test second video open: OK
> test VIDIOC_QUERYCAP: OK
> test VIDIOC_G/S_PRIORITY: OK
>
> Debug ioctls:
> test VIDIOC_DBG_G/S_REGISTER: OK
> test VIDIOC_LOG_STATUS: OK (Not Supported)
>
> Input ioctls:
> test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
> test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
> test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
> test VIDIOC_ENUMAUDIO: OK (Not Supported)
> test VIDIOC_G/S/ENUMINPUT: OK (Not Supported)
> test VIDIOC_G/S_AUDIO: OK (Not Supported)
> Inputs: 0 Audio Inputs: 0 Tuners: 0
>
> Output ioctls:
> test VIDIOC_G/S_MODULATOR: OK (Not Supported)
> test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
> test VIDIOC_ENUMAUDOUT: OK (Not Supported)
> test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
> test VIDIOC_G/S_AUDOUT: OK (Not Supported)
> Outputs: 0 Audio Outputs: 0 Modulators: 0
>
> Input/Output configuration ioctls:
> test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
> test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
> test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
> test VIDIOC_G/S_EDID: OK (Not Supported)
>
> Control ioctls:
> test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK
> test VIDIOC_QUERYCTRL: OK
> test VIDIOC_G/S_CTRL: OK
> test VIDIOC_G/S/TRY_EXT_CTRLS: OK
> test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK
> test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
> Standard Controls: 2 Private Controls: 0
>
> Format ioctls:
> test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
> test VIDIOC_G/S_PARM: OK (Not Supported)
> test VIDIOC_G_FBUF: OK (Not Supported)
> test VIDIOC_G_FMT: OK
> test VIDIOC_TRY_FMT: OK
> test VIDIOC_S_FMT: OK
> test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)
> test Cropping: OK (Not Supported)
> test Composing: OK (Not Supported)
> test Scaling: OK
>
> Codec ioctls:
> test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported)
> test VIDIOC_G_ENC_INDEX: OK (Not Supported)
> test VIDIOC_(TRY_)DECODER_CMD: OK (Not Supported)
>
> Buffer ioctls:
> warn: v4l2-test-buffers.cpp(542): VIDIOC_CREATE_BUFS not supported
> warn: v4l2-test-buffers.cpp(542): VIDIOC_CREATE_BUFS not supported
Can you add support for this? There is a v4l2_m2m_ioctl_create_bufs helper function,
so all you need to do is stick in that helper and have jpu_queue_setup verify and
user fmt->fmt.imagesize as the size if fmt is non-NULL.
Please run v4l2-compliance again after it's been added.
I plan on reviewing and hopefully making a pull request for this on Friday.
Regards,
Hans
next prev parent reply other threads:[~2015-07-22 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 2:00 [PATCH 0/3] R-Car JPEG Processing Unit Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH v5 1/3] V4L2: platform: Add Renesas R-Car JPEG codec driver Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH v3 2/3] devicetree: bindings: Document Renesas R-Car JPEG Processing Unit Mikhail Ulyanov
2015-07-21 2:00 ` [PATCH 3/3] MAINTAINERS: V4L2: PLATFORM: Add entry for Renesas JPEG Processing Unit driver Mikhail Ulyanov
2015-07-22 0:41 ` [PATCH 0/3] R-Car JPEG Processing Unit Simon Horman
2015-07-22 1:19 ` Mikhail Ulyanov
2015-07-22 1:40 ` Simon Horman
2015-07-22 6:08 ` Hans Verkuil [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-22 11:23 Mikhail Ulyanov
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=55AF3367.5040503@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=j.anaszewski@samsung.com \
--cc=kamil@wypas.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=mikhail.ulyanov@cogentembedded.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).