From: Valentine <valentine.barshak@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Phil Edworthy <phil.edworthy@renesas.com>
Cc: linux-media@vger.kernel.org, linux-sh@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH] media: soc_camera: rcar_vin: Add support for 10-bit YUV cameras
Date: Tue, 25 Feb 2014 13:40:07 +0000 [thread overview]
Message-ID: <530C9D37.8070909@cogentembedded.com> (raw)
In-Reply-To: <2516843.7QqJLHtUZT@avalon>
On 02/24/2014 10:38 PM, Laurent Pinchart wrote:
> Hi Phil,
>
> Thank you for the patch.
>
> On Monday 24 February 2014 15:49:05 Phil Edworthy wrote:
>> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
>> ---
>> drivers/media/platform/soc_camera/rcar_vin.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/media/platform/soc_camera/rcar_vin.c
>> b/drivers/media/platform/soc_camera/rcar_vin.c index 3b1c05a..9929375
>> 100644
>> --- a/drivers/media/platform/soc_camera/rcar_vin.c
>> +++ b/drivers/media/platform/soc_camera/rcar_vin.c
>> @@ -68,6 +68,8 @@
>> #define VNMC_YCAL (1 << 19)
>> #define VNMC_INF_YUV8_BT656 (0 << 16)
>> #define VNMC_INF_YUV8_BT601 (1 << 16)
>> +#define VNMC_INF_YUV10_BT656 (2 << 16)
>> +#define VNMC_INF_YUV10_BT601 (3 << 16)
>> #define VNMC_INF_YUV16 (5 << 16)
>> #define VNMC_VUP (1 << 10)
>> #define VNMC_IM_ODD (0 << 3)
>> @@ -275,6 +277,10 @@ static int rcar_vin_setup(struct rcar_vin_priv *priv)
>> /* BT.656 8bit YCbCr422 or BT.601 8bit YCbCr422 */
>> vnmc |= priv->pdata->flags & RCAR_VIN_BT656 ?
>> VNMC_INF_YUV8_BT656 : VNMC_INF_YUV8_BT601;
>
> Aren't you missing a break here ?
>
>> + case V4L2_MBUS_FMT_YUYV10_2X10:
>> + /* BT.656 10bit YCbCr422 or BT.601 10bit YCbCr422 */
>> + vnmc |= priv->pdata->flags & RCAR_VIN_BT656 ?
>> + VNMC_INF_YUV10_BT656 : VNMC_INF_YUV10_BT601;
>
> You should add one here as well. Although not strictly necessary, it would
> help to avoid making the same mistake again.
>
> The rest looks good to me, but I'm not familiar with the hardware, so I'll let
> Valentine have the last word.
Thanks, looks good to me.
>
>> default:
>> break;
>> }
>> @@ -1003,6 +1009,7 @@ static int rcar_vin_get_formats(struct
>> soc_camera_device *icd, unsigned int idx, switch (code) {
>> case V4L2_MBUS_FMT_YUYV8_1X16:
>> case V4L2_MBUS_FMT_YUYV8_2X8:
>> + case V4L2_MBUS_FMT_YUYV10_2X10:
>> if (cam->extra_fmt)
>> break;
>
next prev parent reply other threads:[~2014-02-25 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 20:28 [PATCH] media: soc_camera: rcar_vin: Add preliminary R-Car M2 support Valentine Barshak
2013-12-26 14:18 ` Laurent Pinchart
2013-12-26 14:31 ` Valentine
2014-02-24 15:49 ` [PATCH] media: soc_camera: rcar_vin: Add support for 10-bit YUV cameras Phil Edworthy
2014-02-24 18:38 ` Laurent Pinchart
2014-02-25 9:10 ` [PATCH v2] " Phil Edworthy
2014-02-25 13:40 ` Vladimir Barinov
2014-02-25 13:40 ` Valentine [this message]
2014-10-14 6:22 ` [PATCH] media: soc_camera: rcar_vin: Add BT.709 24-bit RGB888 input support Yoshihiro Kaneko
2014-10-16 5:23 ` Simon Horman
2014-10-18 14:55 ` Sergei Shtylyov
2014-10-14 6:24 ` [PATCH] media: soc_camera: rcar_vin: Add YUYV capture format support Yoshihiro Kaneko
2014-10-16 5:24 ` Simon Horman
2014-10-20 2:51 ` [PATCH] media: soc_camera: rcar_vin: Add DT support for r8a7793 and r8a7794 SoCs Yoshihiro Kaneko
2014-10-20 16:20 ` Simon Horman
2014-10-31 9:08 ` [PATCH] media: soc_camera: rcar_vin: Add BT.709 24-bit RGB888 input support Yoshihiro Kaneko
2014-10-31 13:00 ` Sergei Shtylyov
2015-12-13 15:27 ` [PATCH] media: soc_camera: rcar_vin: Add R-Car Gen3 support Yoshihiro Kaneko
2015-12-13 17:43 ` Sergei Shtylyov
2015-12-20 9:52 ` Yoshihiro Kaneko
2016-01-09 10:46 ` Guennadi Liakhovetski
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=530C9D37.8070909@cogentembedded.com \
--to=valentine.barshak@cogentembedded.com \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=magnus.damm@gmail.com \
--cc=phil.edworthy@renesas.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).