All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles-Antoine Couret <charles-antoine.couret@nexvision.fr>
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: [PATCH] V4L2: Add documentation for SDI timings and related flags
Date: Thu, 4 Aug 2016 17:21:42 +0200	[thread overview]
Message-ID: <58f6ea73-e54a-a0f7-305e-2740f5a8bfba@nexvision.fr> (raw)
In-Reply-To: <080c0d20-6268-f1a0-9120-d6e4909bdcd5@xs4all.nl>

Le 04/08/2016 à 12:11, Hans Verkuil a écrit :

>> --- a/Documentation/media/uapi/v4l/vidioc-g-dv-timings.rst
>> +++ b/Documentation/media/uapi/v4l/vidioc-g-dv-timings.rst
>> @@ -339,6 +339,13 @@ EBUSY
>>  
>>         -  The timings follow the VESA Generalized Timings Formula standard
>>  
>> +    -  .. row 7
>> +
>> +       -  ``V4L2_DV_BT_STD_SDI``
>> +
>> +       -  The timings follow the SDI Timings standard.
>> +	  There are no horizontal syncs/porches at all in this format.
>> +	  Total blanking timings must be set in hsync or vsync fields only.
> 
> Didn't you mention on irc that there are actually two blanking timings for
> vertical blanking? Something frontporch like? I can't remember the details,
> but if I remember correctly, then you should specify what goes where.


Yes, your're right about this.
In SMPTE 125M (I like this standard :D), some "frontporchs" or similar values are available.
So, I can precise that in the documentation and fix SMPTE 125M definition to take this into account.

Thank you very much.
Regards,
Charles-Antoine Couret

      reply	other threads:[~2016-08-04 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 15:04 [PATCH] V4L2: Add documentation for SDI timings and related flags Charles-Antoine Couret
2016-08-04 10:11 ` Hans Verkuil
2016-08-04 15:21   ` Charles-Antoine Couret [this message]

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=58f6ea73-e54a-a0f7-305e-2740f5a8bfba@nexvision.fr \
    --to=charles-antoine.couret@nexvision.fr \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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.