From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Yoshihiro Kaneko <ykaneko0929@gmail.com>, linux-media@vger.kernel.org
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/3] media: soc_camera: rcar_vin: Add capture width check for NV16 format
Date: Sat, 18 Oct 2014 15:05:39 +0000 [thread overview]
Message-ID: <544281C3.9030002@cogentembedded.com> (raw)
In-Reply-To: <1413439968-6349-3-git-send-email-ykaneko0929@gmail.com>
On 10/16/2014 10:12 AM, Yoshihiro Kaneko wrote:
> From: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> At the time of NV16 capture format, the user has to specify the
> capture output width of the multiple of 32 for H/W specification.
> At the time of using NV16 format by ioctl of VIDIOC_S_FMT,
> this patch adds align check and the error handling to forbid
> specification of the capture output width which is not a multiple of 32.
> Signed-off-by: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
> ---
> v2 [Yoshihiro Kaneko]
> * use u32 instead of unsigned long
> drivers/media/platform/soc_camera/rcar_vin.c | 24 ++++++++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
> diff --git a/drivers/media/platform/soc_camera/rcar_vin.c b/drivers/media/platform/soc_camera/rcar_vin.c
> index 34d5b80..ff5f80a 100644
> --- a/drivers/media/platform/soc_camera/rcar_vin.c
> +++ b/drivers/media/platform/soc_camera/rcar_vin.c
[...]
> @@ -1606,6 +1615,17 @@ static int rcar_vin_set_fmt(struct soc_camera_device *icd,
> dev_dbg(dev, "S_FMT(pix=0x%x, %ux%u)\n",
> pixfmt, pix->width, pix->height);
>
> + /* At the time of NV16 capture format, the user has to specify the
> + width of the multiple of 32 for H/W specification. */
> + if (priv->error_flag = false)
> + priv->error_flag = true;
> + else {
> + if ((pixfmt = V4L2_PIX_FMT_NV16) && (pix->width & 0x1F)) {
> + dev_err(icd->parent, "Specified width error in NV16 format.\n");
> + return -EINVAL;
> + }
> + }
Oh, and the kernel style dictates that {} should be used in all arms of
the *if* statement if they're used in at least one.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Yoshihiro Kaneko <ykaneko0929@gmail.com>, linux-media@vger.kernel.org
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/3] media: soc_camera: rcar_vin: Add capture width check for NV16 format
Date: Sat, 18 Oct 2014 19:05:39 +0400 [thread overview]
Message-ID: <544281C3.9030002@cogentembedded.com> (raw)
In-Reply-To: <1413439968-6349-3-git-send-email-ykaneko0929@gmail.com>
On 10/16/2014 10:12 AM, Yoshihiro Kaneko wrote:
> From: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> At the time of NV16 capture format, the user has to specify the
> capture output width of the multiple of 32 for H/W specification.
> At the time of using NV16 format by ioctl of VIDIOC_S_FMT,
> this patch adds align check and the error handling to forbid
> specification of the capture output width which is not a multiple of 32.
> Signed-off-by: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
> ---
> v2 [Yoshihiro Kaneko]
> * use u32 instead of unsigned long
> drivers/media/platform/soc_camera/rcar_vin.c | 24 ++++++++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
> diff --git a/drivers/media/platform/soc_camera/rcar_vin.c b/drivers/media/platform/soc_camera/rcar_vin.c
> index 34d5b80..ff5f80a 100644
> --- a/drivers/media/platform/soc_camera/rcar_vin.c
> +++ b/drivers/media/platform/soc_camera/rcar_vin.c
[...]
> @@ -1606,6 +1615,17 @@ static int rcar_vin_set_fmt(struct soc_camera_device *icd,
> dev_dbg(dev, "S_FMT(pix=0x%x, %ux%u)\n",
> pixfmt, pix->width, pix->height);
>
> + /* At the time of NV16 capture format, the user has to specify the
> + width of the multiple of 32 for H/W specification. */
> + if (priv->error_flag == false)
> + priv->error_flag = true;
> + else {
> + if ((pixfmt == V4L2_PIX_FMT_NV16) && (pix->width & 0x1F)) {
> + dev_err(icd->parent, "Specified width error in NV16 format.\n");
> + return -EINVAL;
> + }
> + }
Oh, and the kernel style dictates that {} should be used in all arms of
the *if* statement if they're used in at least one.
WBR, Sergei
next prev parent reply other threads:[~2014-10-18 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 6:12 [PATCH v2 0/3] media: soc_camera: rcar_vin: Add scaling support Yoshihiro Kaneko
2014-10-16 6:12 ` Yoshihiro Kaneko
2014-10-16 6:12 ` [PATCH v2 1/3] " Yoshihiro Kaneko
2014-10-16 6:12 ` Yoshihiro Kaneko
2014-10-16 6:12 ` [PATCH v2 2/3] media: soc_camera: rcar_vin: Add capture width check for NV16 format Yoshihiro Kaneko
2014-10-16 6:12 ` Yoshihiro Kaneko
2014-10-18 14:46 ` Sergei Shtylyov
2014-10-18 14:46 ` Sergei Shtylyov
2014-10-18 15:05 ` Sergei Shtylyov [this message]
2014-10-18 15:05 ` Sergei Shtylyov
2014-10-16 6:12 ` [PATCH v2 3/3] media: soc_camera: rcar_vin: Add NV16 horizontal scaling-up support Yoshihiro Kaneko
2014-10-16 6:12 ` Yoshihiro Kaneko
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=544281C3.9030002@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ykaneko0929@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.