Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1481264 > unrolled thread

Re: [PATCH 01/26] dt-bindings: display: display-timing: Add property to configure sync drive edge

Started byRob Herring <robh@kernel.org>
First post2016-09-12 15:10 +0200
Last post2016-09-12 15:30 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 01/26] dt-bindings: display: display-timing: Add property  to configure sync drive edge Rob Herring <robh@kernel.org> - 2016-09-12 15:10 +0200
    Re: [PATCH 01/26] dt-bindings: display: display-timing: Add property  to configure sync drive edge Peter Ujfalusi <peter.ujfalusi@ti.com> - 2016-09-12 15:30 +0200

#1481264 — Re: [PATCH 01/26] dt-bindings: display: display-timing: Add property to configure sync drive edge

FromRob Herring <robh@kernel.org>
Date2016-09-12 15:10 +0200
SubjectRe: [PATCH 01/26] dt-bindings: display: display-timing: Add property to configure sync drive edge
Message-ID<sgz9M-3JB-61@gated-at.bofh.it>
On Thu, Sep 01, 2016 at 02:22:55PM +0300, Peter Ujfalusi wrote:
> There are display panels which demands that the sync signal is driven on
> different edge than the pixel data.
> With the syncclk-active property we can specify the clk edge to be used to
> drive the sync signal. When the property is missing it indicates that the
> sync is driven on the same edge as the pixel data.
> 
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> CC: Rob Herring <robh+dt@kernel.org>
> CC: Mark Rutland <mark.rutland@arm.com>
> CC: devicetree@vger.kernel.org
> ---
>  Documentation/devicetree/bindings/display/panel/display-timing.txt | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/display/panel/display-timing.txt b/Documentation/devicetree/bindings/display/panel/display-timing.txt
> index e1d4a0b59612..1436292e7a56 100644
> --- a/Documentation/devicetree/bindings/display/panel/display-timing.txt
> +++ b/Documentation/devicetree/bindings/display/panel/display-timing.txt
> @@ -32,6 +32,12 @@ optional properties:
>  			- active low  = drive pixel data on falling edge/
>  					sample data on rising edge
>  			- ignored     = ignored
> + - syncclk-active: with
> +			- active high = drive sync on rising edge/

rising edge of what? pixel clk?

> +					sample sync on falling edge
> +			- active low  = drive sync on falling edge/
> +					sample sync on rising edge
> +			- omitted     = same configuration as pixelclk-active
>   - interlaced (bool): boolean to enable interlaced mode
>   - doublescan (bool): boolean to enable doublescan mode
>   - doubleclk (bool): boolean to enable doubleclock mode
> -- 
> 2.9.3
> 

[toc] | [next] | [standalone]


#1481284

FromPeter Ujfalusi <peter.ujfalusi@ti.com>
Date2016-09-12 15:30 +0200
Message-ID<sgzt8-3QU-35@gated-at.bofh.it>
In reply to#1481264
On 09/12/16 16:05, Rob Herring wrote:
> On Thu, Sep 01, 2016 at 02:22:55PM +0300, Peter Ujfalusi wrote:
>> There are display panels which demands that the sync signal is driven on
>> different edge than the pixel data.
>> With the syncclk-active property we can specify the clk edge to be used to
>> drive the sync signal. When the property is missing it indicates that the
>> sync is driven on the same edge as the pixel data.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> CC: Rob Herring <robh+dt@kernel.org>
>> CC: Mark Rutland <mark.rutland@arm.com>
>> CC: devicetree@vger.kernel.org
>> ---
>>  Documentation/devicetree/bindings/display/panel/display-timing.txt | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/display/panel/display-timing.txt b/Documentation/devicetree/bindings/display/panel/display-timing.txt
>> index e1d4a0b59612..1436292e7a56 100644
>> --- a/Documentation/devicetree/bindings/display/panel/display-timing.txt
>> +++ b/Documentation/devicetree/bindings/display/panel/display-timing.txt
>> @@ -32,6 +32,12 @@ optional properties:
>>  			- active low  = drive pixel data on falling edge/
>>  					sample data on rising edge
>>  			- ignored     = ignored
>> + - syncclk-active: with
>> +			- active high = drive sync on rising edge/
> 
> rising edge of what? pixel clk?

Yes, pixel clk, I have copied and modified the 'pixelclk-active' option.
Probably it would be better to state it explicitly.

> 
>> +					sample sync on falling edge
>> +			- active low  = drive sync on falling edge/
>> +					sample sync on rising edge
>> +			- omitted     = same configuration as pixelclk-active
>>   - interlaced (bool): boolean to enable interlaced mode
>>   - doublescan (bool): boolean to enable doublescan mode
>>   - doubleclk (bool): boolean to enable doubleclock mode
>> -- 
>> 2.9.3
>>


-- 
Péter

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web