linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Ajay kumar <ajaynumb@gmail.com>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	Ajay Kumar <ajaykumar.rs@samsung.com>,
	linux-samsung-soc@vger.kernel.org, linux-fbdev@vger.kernel.org,
	jg1.han@samsung.com, devicetree-discuss@lists.ozlabs.org,
	FlorianSchandinat@gmx.de, tomasz.figa@gmail.com,
	thomas.ab@samsung.com
Subject: Re: [PATCH V4 2/2] video: exynos_dp: device tree documentation
Date: Thu, 11 Oct 2012 10:01:13 +0000	[thread overview]
Message-ID: <507698E9.7050007@samsung.com> (raw)
In-Reply-To: <CAEC9eQO5s5VG_qwRbH4K7TD_Z_rYbks=s_GEOfY3TxDMk7gPzw@mail.gmail.com>

On 10/11/2012 08:50 AM, Ajay kumar wrote:
>>> +     -samsung,interlaced:
>>> +             Interlace scan mode.
>>> +                     Progressive if defined, Interlaced if not defined
>>> +     -samsung,v_sync_polarity:
>>> +             VSYNC polarity configuration.
>>> +                     High if defined, Low if not defined
>>> +     -samsung,h_sync_polarity:
>>> +             HSYNC polarity configuration.
>>> +                     High if defined, Low if not defined
>>
>> So there is no common video bindings for things like these two ?
>> In V4L2 we decided to use vsync-active, hsync-active [1], the video
>> timings bindings [2] use hsync-active-high, hsync-active-high boolean
>> properties. Perhaps it is worth to pick some of those standard
>> definitions and use instead of the vendor specific ones ?

> hsync-active-high and vsync-active-high seems to hold good in our case.
> Also, are you asking us to just use only the standard names or use standard
> helper functions as well? Since we use only hsync and vsync polarity and no
> other LCD timing properties, I think we need not use standard helper functions
> for parsing display timings!

My point was just to use common property names where possible. Any parsing
helpers could be created afterwards, if you would rather avoid doing that
right now. BTW, it seems 'interlaced' could also be reused.

...
>> [1] http://www.mail-archive.com/linux-media@vger.kernel.org/msg52743.html
>> [2] http://www.mail-archive.com/linux-media@vger.kernel.org/msg53323.html

Thanks,
Sylwester


      reply	other threads:[~2012-10-11 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 14:04 [PATCH V4 0/2] video: exynos_dp: Add device tree support to DP driver Ajay Kumar
2012-10-09 14:04 ` [PATCH V4 1/2] " Ajay Kumar
2012-10-09 14:05 ` [PATCH V4 2/2] video: exynos_dp: device tree documentation Ajay Kumar
2012-10-09 21:29   ` Sylwester Nawrocki
2012-10-11  6:50     ` Ajay kumar
2012-10-11 10:01       ` Sylwester Nawrocki [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=507698E9.7050007@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=ajaykumar.rs@samsung.com \
    --cc=ajaynumb@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jg1.han@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sylvester.nawrocki@gmail.com \
    --cc=thomas.ab@samsung.com \
    --cc=tomasz.figa@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 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).