All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: linux-media@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	kyungmin.park@samsung.com, m.szyprowski@samsung.com,
	g.liakhovetski@gmx.de, sw0312.kim@samsung.com,
	riverful.kim@samsung.com
Subject: Re: [PATCH v3 1/2] v4l2: Add the polarity flags for parallel camera bus FIELD signal
Date: Wed, 21 Sep 2011 16:51:12 +0200	[thread overview]
Message-ID: <4E79F9E0.4010700@samsung.com> (raw)
In-Reply-To: <4E79E588.4000608@samsung.com>

On 09/21/2011 03:24 PM, Sylwester Nawrocki wrote:
> Hi Laurent,
> 
> On 09/21/2011 01:12 AM, Laurent Pinchart wrote:
>> Hi Sylwester,
>>
>> Thanks for the patch.
>>
>> On Monday 19 September 2011 19:07:55 Sylwester Nawrocki wrote:
>>> FIELD is an Even/Odd field selection signal, as specified in ITU-R BT.601
>>> standard. Add corresponding flag for configuring the FIELD signal polarity.
>>> Also add a comment about usage of V4L2_MBUS_[HV]SYNC* flags for the
>>> hardware that uses [HV]REF signals.
>>
>> I like this approach better.
>>
> ...
>>> +/* Field selection signal for interlaced scan mode */
>>> +#define V4L2_MBUS_FIELD_ACTIVE_HIGH		(1 << 10)
>>> +#define V4L2_MBUS_FIELD_ACTIVE_LOW		(1 << 11)
>>
>> What does this mean ? The FIELD signal is used to select between odd and even 
>> fields. Does "active high" mean that the field is odd or even when the signal 
>> has a high level ? The comment should make it explicit, or we could even 
>> rename those two constants to FIELD_ODD_HIGH/FIELD_ODD_LOW (or 
>> FIELD_EVEN_HIGH/FIELD_EVEN_LOW).
> 
> Yes, certainly I didn't think enough about this. I silently assumed that for
> V4L2_MBUS_FIELD_ACTIVE_HIGH FIELD = 0 selects Field1 (odd) and FIELD = 1 selects
> Field2 (even).
> I think it would be good to construct the macro so it is possibly self-explanatory,
> rather than requiring often to dig in the documentation.
> 
> So I would go for V4L2_MBUS_FIELD_ODD_LOW/V4L2_MBUS_FIELD_ODD_HIGH.
> Unless someone proposes something different/better I'll send an amended version
> tomorrow. 

Thinking some more of it, V4L2_MBUS_FIELD_EVEN_HIGH/V4L2_MBUS_FIELD_EVEN_LOW
is perhaps more in line with other defines where *HIGH means standard,
non-inverted case. So it seems better to me.

  reply	other threads:[~2011-09-21 14:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 17:28 [PATCH 0/2] v4l: Add media bus polarity flags for HREF signal Sylwester Nawrocki
2011-09-16 17:28 ` [PATCH/RFC 1/2] v4l2: Add the parallel bus HREF signal polarity flags Sylwester Nawrocki
2011-09-17 10:54   ` Laurent Pinchart
2011-09-17 12:07     ` Sylwester Nawrocki
2011-09-17 12:34       ` Guennadi Liakhovetski
2011-09-17 16:06         ` Sylwester Nawrocki
2011-09-18 23:05           ` Laurent Pinchart
2011-09-19  8:48             ` Sylwester Nawrocki
2011-09-19 16:41         ` [PATCH v2 0/2] v4l: Add media bus polarity flags for FIELD signal Sylwester Nawrocki
2011-09-19 16:41           ` [PATCH v2 1/2] v4l2: Add the polarity flags for parallel camera bus " Sylwester Nawrocki
2011-09-19 16:41           ` [PATCH v2 2/2] s5p-fimc: Convert to use generic media bus polarity flags Sylwester Nawrocki
2011-09-19 17:07           ` [PATCH v3 1/2] v4l2: Add the polarity flags for parallel camera bus FIELD signal Sylwester Nawrocki
2011-09-20 23:12             ` Laurent Pinchart
2011-09-21 13:24               ` Sylwester Nawrocki
2011-09-21 14:51                 ` Sylwester Nawrocki [this message]
2011-09-18 23:02       ` [PATCH/RFC 1/2] v4l2: Add the parallel bus HREF signal polarity flags Laurent Pinchart
2011-09-19  8:37         ` Sylwester Nawrocki
2011-09-16 17:28 ` [PATCH 2/2] s5p-fimc: Convert to use generic bus " Sylwester Nawrocki

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=4E79F9E0.4010700@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=kyungmin.park@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=riverful.kim@samsung.com \
    --cc=sw0312.kim@samsung.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.