Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1488734 > unrolled thread
| Started by | Peter Ujfalusi <peter.ujfalusi@ti.com> |
|---|---|
| First post | 2016-09-22 12:40 +0200 |
| Last post | 2016-09-29 13:00 +0200 |
| Articles | 3 — 3 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.
[PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge Peter Ujfalusi <peter.ujfalusi@ti.com> - 2016-09-22 12:40 +0200
Re: [PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge Rob Herring <robh@kernel.org> - 2016-09-23 22:10 +0200
Re: [PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-09-29 13:00 +0200
| From | Peter Ujfalusi <peter.ujfalusi@ti.com> |
|---|---|
| Date | 2016-09-22 12:40 +0200 |
| Subject | [PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge |
| Message-ID | <sk9A6-58y-25@gated-at.bofh.it> |
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 --- .../devicetree/bindings/display/panel/display-timing.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/display/panel/display-timing.txt b/Documentation/devicetree/bindings/display/panel/display-timing.txt index e1d4a0b59612..81a75893d1b8 100644 --- a/Documentation/devicetree/bindings/display/panel/display-timing.txt +++ b/Documentation/devicetree/bindings/display/panel/display-timing.txt @@ -32,6 +32,14 @@ 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/ + sample sync on falling edge of pixel + clock + - active low = drive sync on falling edge/ + sample sync on rising edge of pixel + clock + - 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.10.0
[toc] | [next] | [standalone]
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Date | 2016-09-23 22:10 +0200 |
| Subject | Re: [PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge |
| Message-ID | <skEXf-8mF-1@gated-at.bofh.it> |
| In reply to | #1488734 |
On Thu, Sep 22, 2016 at 01:35:24PM +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 > --- > .../devicetree/bindings/display/panel/display-timing.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) Acked-by: Rob Herring <robh@kernel.org>
[toc] | [prev] | [next] | [standalone]
| From | Tomi Valkeinen <tomi.valkeinen@ti.com> |
|---|---|
| Date | 2016-09-29 13:00 +0200 |
| Subject | Re: [PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge |
| Message-ID | <smHej-33A-65@gated-at.bofh.it> |
| In reply to | #1488734 |
[Multipart message — attachments visible in raw view] — view raw
On 22/09/16 13:35, 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 > --- > .../devicetree/bindings/display/panel/display-timing.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/panel/display-timing.txt b/Documentation/devicetree/bindings/display/panel/display-timing.txt > index e1d4a0b59612..81a75893d1b8 100644 > --- a/Documentation/devicetree/bindings/display/panel/display-timing.txt > +++ b/Documentation/devicetree/bindings/display/panel/display-timing.txt > @@ -32,6 +32,14 @@ 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/ > + sample sync on falling edge of pixel > + clock > + - active low = drive sync on falling edge/ > + sample sync on rising edge of pixel > + clock > + - omitted = same configuration as pixelclk-active I wonder if the "sample sync on..." should be left out here. It makes sense for the pixel data, but for sync... Do the panels "sample" it, or do they trigger on rising/falling edge? Well, maybe that's a bit on the nitpick side, so: Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Tomi
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web