All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	mchehab@redhat.com, linux-media@vger.kernel.org,
	linux-sh@vger.kernel.org, matsu@igel.co.jp
Subject: Re: [PATCH 1/5] V4L2: I2C: ML86V7667 video decoder driver
Date: Sun, 21 Apr 2013 10:23:07 +0000	[thread overview]
Message-ID: <5173BE0B.8090001@cogentembedded.com> (raw)
In-Reply-To: <51730324.8090403@gmail.com>

Hi Sylwester,

Thank you for the review.

Sylwester Nawrocki wrote
>
>> +static struct v4l2_subdev_video_ops ml86v7667_subdev_video_ops = {
>> +    .querystd = ml86v7667_querystd,
>> +    .g_input_status = ml86v7667_g_input_status,
>> +    .enum_mbus_fmt = ml86v7667_enum_mbus_fmt,
>> +    .try_mbus_fmt = ml86v7667_try_mbus_fmt,
>> +    .g_mbus_fmt = ml86v7667_g_mbus_fmt,
>> +    .s_mbus_fmt = ml86v7667_s_mbus_fmt,
>> +    .cropcap = ml86v7667_cropcap,
>> +    .g_mbus_config = ml86v7667_g_mbus_config,
>> +};
>
> Why do you need .cropcap when there is no s_crop/g_crop ops ? Is it
> only for pixel aspect ratio ?
Yes it is.
>
> Also, new drivers are supposed to use the selections API instead
> (set/get_selection ops). However this requires pad level ops support
> in your host driver, hence might be a bigger issue.
Yes, since the host driver (rcar_vin is already send for review) is 
designed for soc-camera layer that does not use the pad level ops but 
needs at least cropcap to get the pixel aspect ratio.
The soc-camera has it's own set/get_selection in soc_camera_host_ops and 
it is possible to use it like all i2c/soc_camera sensors can/do.
But we would not like to design the ml86v7667 as soc-camera device since 
it will not be available for all non soc-camera v4l2 hosts.

Regards,
Vladimir

WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	mchehab@redhat.com, linux-media@vger.kernel.org,
	linux-sh@vger.kernel.org, matsu@igel.co.jp
Subject: Re: [PATCH 1/5] V4L2: I2C: ML86V7667 video decoder driver
Date: Sun, 21 Apr 2013 14:23:07 +0400	[thread overview]
Message-ID: <5173BE0B.8090001@cogentembedded.com> (raw)
In-Reply-To: <51730324.8090403@gmail.com>

Hi Sylwester,

Thank you for the review.

Sylwester Nawrocki wrote
>
>> +static struct v4l2_subdev_video_ops ml86v7667_subdev_video_ops = {
>> +    .querystd = ml86v7667_querystd,
>> +    .g_input_status = ml86v7667_g_input_status,
>> +    .enum_mbus_fmt = ml86v7667_enum_mbus_fmt,
>> +    .try_mbus_fmt = ml86v7667_try_mbus_fmt,
>> +    .g_mbus_fmt = ml86v7667_g_mbus_fmt,
>> +    .s_mbus_fmt = ml86v7667_s_mbus_fmt,
>> +    .cropcap = ml86v7667_cropcap,
>> +    .g_mbus_config = ml86v7667_g_mbus_config,
>> +};
>
> Why do you need .cropcap when there is no s_crop/g_crop ops ? Is it
> only for pixel aspect ratio ?
Yes it is.
>
> Also, new drivers are supposed to use the selections API instead
> (set/get_selection ops). However this requires pad level ops support
> in your host driver, hence might be a bigger issue.
Yes, since the host driver (rcar_vin is already send for review) is 
designed for soc-camera layer that does not use the pad level ops but 
needs at least cropcap to get the pixel aspect ratio.
The soc-camera has it's own set/get_selection in soc_camera_host_ops and 
it is possible to use it like all i2c/soc_camera sensors can/do.
But we would not like to design the ml86v7667 as soc-camera device since 
it will not be available for all non soc-camera v4l2 hosts.

Regards,
Vladimir

  reply	other threads:[~2013-04-21 10:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 20:13 [PATCH 0/5] OKI ML86V7667 driver and R8A7778/BOCK-W VIN support Sergei Shtylyov
2013-04-20 20:13 ` Sergei Shtylyov
2013-04-20 20:13 ` Sergei Shtylyov
2013-04-20 20:16 ` [PATCH 1/5] V4L2: I2C: ML86V7667 video decoder driver Sergei Shtylyov
2013-04-20 20:16   ` Sergei Shtylyov
2013-04-20 21:05   ` Sylwester Nawrocki
2013-04-20 21:05     ` Sylwester Nawrocki
2013-04-21 10:23     ` Vladimir Barinov [this message]
2013-04-21 10:23       ` Vladimir Barinov
2013-04-20 21:50   ` Hans Verkuil
2013-04-20 21:50     ` Hans Verkuil
2013-04-20 21:59   ` Sergei Shtylyov
2013-04-20 21:59     ` Sergei Shtylyov
2013-04-20 20:28 ` [PATCH 3/5] ARM: shmobile: r8a7778: add VIN support Sergei Shtylyov
2013-04-20 20:28   ` Sergei Shtylyov
2013-04-20 20:28   ` Sergei Shtylyov
2013-04-20 20:36 ` [PATCH 4/5] ARM: shmobile: BOCK-W: add VIN and ML86V7667 support Sergei Shtylyov
2013-04-20 20:36   ` Sergei Shtylyov
2013-04-20 20:36   ` Sergei Shtylyov
2013-04-20 20:38 ` [PATCH 5/5] ARM: shmobile: BOCK-W: enable VIN and ML86V7667 in defconfig Sergei Shtylyov
2013-04-20 20:38   ` Sergei Shtylyov
2013-04-20 20:38   ` Sergei Shtylyov
2013-04-20 20:43 ` [PATCH 0/5] OKI ML86V7667 driver and R8A7778/BOCK-W VIN support Sergei Shtylyov
2013-04-20 20:43   ` Sergei Shtylyov
2013-04-20 20:43   ` Sergei Shtylyov
2013-04-22  4:21 ` Simon Horman
2013-04-22  4:21   ` Simon Horman
2013-04-22  4:21   ` Simon Horman

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=5173BE0B.8090001@cogentembedded.com \
    --to=vladimir.barinov@cogentembedded.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=matsu@igel.co.jp \
    --cc=mchehab@redhat.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=sylvester.nawrocki@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.