From: Manfred Schlaegl <manfred.schlaegl@gmx.at>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-fbdev@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Deepak Das <deepak_das@mentor.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [RFC PATCH 1/2] drm: add support for for clk and de polarity
Date: Thu, 26 Nov 2015 15:20:51 +0100 [thread overview]
Message-ID: <56571543.20701@gmx.at> (raw)
In-Reply-To: <1448472141.3390.17.camel@pengutronix.de>
On 2015-11-25 18:22, Philipp Zabel wrote:
> Am Mittwoch, den 15.07.2015, 17:50 +0200 schrieb Manfred Schlaegl:
>> To get full support for parallel and LVDS displays with drm:
>> Add representation for clock and data enable polarity in drm_display_mode
>> flags (similar to HSYNC/VSYNC polarity) and update conversion functions
>> from/to videomode accordingly.
>>
>> This is especially important for embedded devices where parallel(RGB) and
>> LVDS displays are still widely used and drm already plays an important
>> role.
>>
>> Tested on Freescale i.MX53(parallel) and i.MX6(LVDS).
>>
>> Background:
>> There was the ability to set polarity of clock and data enable signals
>> in devicetree(display-timing), struct display_timing and struct videomode,
>> but there was no representation for this in struct drm_display_mode.
>> Example on Freescale i.MX53/i.MX6 SoC's:
>> * A parallel display using different clock polarity is set up using
>> display-timing in devicetree
>> * ipuv3 parallel outputs clock with wrong polarity
>>
>> Signed-off-by: Manfred Schlaegl <manfred.schlaegl@gmx.at>
>
> Any comments on whether data enable and pixel clock polarity flags can
> be added to the visible DRM_MODE_FLAGs, and if not, where else this
> information should be kept? struct drm_display_info?
>
> This patch and the following IPUv3 patch are useful and necessary for
> quite some panels connected to i.MX SoCs, but adding DRM_MODE_FLAGs is
> somewhat out of my jurisdiction.
>
> best regards
> Philipp
>
Good to see that this discussion is triggered.
State of the sent patches respective to git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (78c4a49)
* [RFC PATCH 1/2] drm: add support for for clk and de polarity
* applies unmodified
* [RFC PATCH 2/2] gpu: ipu-v3: use clock and de polarity from videomode
* does not apply -> but this can be fixed with corrections of line offsets (using patch)
From a code review I think the modifications must work, but I did no testing on kernel versions newer than 4.1.13.
On demand, I can redo tests on some of our i.MX53 (parallel) and i.MX6 (lvds) boards and send actual patches.
best regards,
Manfred
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Manfred Schlaegl <manfred.schlaegl@gmx.at>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-fbdev@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Deepak Das <deepak_das@mentor.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [RFC PATCH 1/2] drm: add support for for clk and de polarity
Date: Thu, 26 Nov 2015 14:20:51 +0000 [thread overview]
Message-ID: <56571543.20701@gmx.at> (raw)
In-Reply-To: <1448472141.3390.17.camel@pengutronix.de>
On 2015-11-25 18:22, Philipp Zabel wrote:
> Am Mittwoch, den 15.07.2015, 17:50 +0200 schrieb Manfred Schlaegl:
>> To get full support for parallel and LVDS displays with drm:
>> Add representation for clock and data enable polarity in drm_display_mode
>> flags (similar to HSYNC/VSYNC polarity) and update conversion functions
>> from/to videomode accordingly.
>>
>> This is especially important for embedded devices where parallel(RGB) and
>> LVDS displays are still widely used and drm already plays an important
>> role.
>>
>> Tested on Freescale i.MX53(parallel) and i.MX6(LVDS).
>>
>> Background:
>> There was the ability to set polarity of clock and data enable signals
>> in devicetree(display-timing), struct display_timing and struct videomode,
>> but there was no representation for this in struct drm_display_mode.
>> Example on Freescale i.MX53/i.MX6 SoC's:
>> * A parallel display using different clock polarity is set up using
>> display-timing in devicetree
>> * ipuv3 parallel outputs clock with wrong polarity
>>
>> Signed-off-by: Manfred Schlaegl <manfred.schlaegl@gmx.at>
>
> Any comments on whether data enable and pixel clock polarity flags can
> be added to the visible DRM_MODE_FLAGs, and if not, where else this
> information should be kept? struct drm_display_info?
>
> This patch and the following IPUv3 patch are useful and necessary for
> quite some panels connected to i.MX SoCs, but adding DRM_MODE_FLAGs is
> somewhat out of my jurisdiction.
>
> best regards
> Philipp
>
Good to see that this discussion is triggered.
State of the sent patches respective to git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (78c4a49)
* [RFC PATCH 1/2] drm: add support for for clk and de polarity
* applies unmodified
* [RFC PATCH 2/2] gpu: ipu-v3: use clock and de polarity from videomode
* does not apply -> but this can be fixed with corrections of line offsets (using patch)
From a code review I think the modifications must work, but I did no testing on kernel versions newer than 4.1.13.
On demand, I can redo tests on some of our i.MX53 (parallel) and i.MX6 (lvds) boards and send actual patches.
best regards,
Manfred
WARNING: multiple messages have this Message-ID (diff)
From: Manfred Schlaegl <manfred.schlaegl@gmx.at>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: David Airlie <airlied@linux.ie>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org,
Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Deepak Das <deepak_das@mentor.com>,
Jiada Wang <jiada_wang@mentor.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] drm: add support for for clk and de polarity
Date: Thu, 26 Nov 2015 15:20:51 +0100 [thread overview]
Message-ID: <56571543.20701@gmx.at> (raw)
In-Reply-To: <1448472141.3390.17.camel@pengutronix.de>
On 2015-11-25 18:22, Philipp Zabel wrote:
> Am Mittwoch, den 15.07.2015, 17:50 +0200 schrieb Manfred Schlaegl:
>> To get full support for parallel and LVDS displays with drm:
>> Add representation for clock and data enable polarity in drm_display_mode
>> flags (similar to HSYNC/VSYNC polarity) and update conversion functions
>> from/to videomode accordingly.
>>
>> This is especially important for embedded devices where parallel(RGB) and
>> LVDS displays are still widely used and drm already plays an important
>> role.
>>
>> Tested on Freescale i.MX53(parallel) and i.MX6(LVDS).
>>
>> Background:
>> There was the ability to set polarity of clock and data enable signals
>> in devicetree(display-timing), struct display_timing and struct videomode,
>> but there was no representation for this in struct drm_display_mode.
>> Example on Freescale i.MX53/i.MX6 SoC's:
>> * A parallel display using different clock polarity is set up using
>> display-timing in devicetree
>> * ipuv3 parallel outputs clock with wrong polarity
>>
>> Signed-off-by: Manfred Schlaegl <manfred.schlaegl@gmx.at>
>
> Any comments on whether data enable and pixel clock polarity flags can
> be added to the visible DRM_MODE_FLAGs, and if not, where else this
> information should be kept? struct drm_display_info?
>
> This patch and the following IPUv3 patch are useful and necessary for
> quite some panels connected to i.MX SoCs, but adding DRM_MODE_FLAGs is
> somewhat out of my jurisdiction.
>
> best regards
> Philipp
>
Good to see that this discussion is triggered.
State of the sent patches respective to git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (78c4a49)
* [RFC PATCH 1/2] drm: add support for for clk and de polarity
* applies unmodified
* [RFC PATCH 2/2] gpu: ipu-v3: use clock and de polarity from videomode
* does not apply -> but this can be fixed with corrections of line offsets (using patch)
>From a code review I think the modifications must work, but I did no testing on kernel versions newer than 4.1.13.
On demand, I can redo tests on some of our i.MX53 (parallel) and i.MX6 (lvds) boards and send actual patches.
best regards,
Manfred
next prev parent reply other threads:[~2015-11-26 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 15:44 [RFC PATCH 0/2] drm: add support for for clk and de polarity & gpu: ipu-v3: use clock and de polarity Manfred Schlaegl
2015-07-15 15:44 ` Manfred Schlaegl
2015-07-15 15:44 ` [RFC PATCH 0/2] drm: add support for for clk and de polarity & gpu: ipu-v3: use clock and de polarit Manfred Schlaegl
[not found] ` <55A67FDB.8010602-RbZlAiThDcE@public.gmane.org>
2015-07-15 15:50 ` [RFC PATCH 1/2] drm: add support for for clk and de polarity Manfred Schlaegl
2015-07-15 15:50 ` Manfred Schlaegl
2015-07-15 15:50 ` Manfred Schlaegl
2015-11-25 17:22 ` Philipp Zabel
2015-11-25 17:22 ` Philipp Zabel
2015-11-25 17:22 ` Philipp Zabel
2015-11-26 14:20 ` Manfred Schlaegl [this message]
2015-11-26 14:20 ` Manfred Schlaegl
2015-11-26 14:20 ` Manfred Schlaegl
2015-11-27 7:37 ` Tomi Valkeinen
2015-11-27 7:37 ` Tomi Valkeinen
2015-11-27 7:37 ` Tomi Valkeinen
2015-11-30 21:09 ` Philipp Zabel
2015-11-30 21:09 ` Philipp Zabel
2015-11-30 21:09 ` Philipp Zabel
2015-07-15 15:51 ` [RFC PATCH 2/2] gpu: ipu-v3: use clock and de polarity from videomode Manfred Schlaegl
2015-07-15 15:51 ` Manfred Schlaegl
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=56571543.20701@gmx.at \
--to=manfred.schlaegl@gmx.at \
--cc=deepak_das@mentor.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred.schlaegl@ginzinger.com \
--cc=p.zabel@pengutronix.de \
--cc=plagnioj@jcrosoft.com \
--cc=slongerbeam@gmail.com \
--cc=tomi.valkeinen@ti.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.