linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: imx-drm: ldb and display power on sequence
Date: Thu, 06 Mar 2014 15:00:10 +0100	[thread overview]
Message-ID: <1394114410.3622.14.camel@paszta.hi.pengutronix.de> (raw)
In-Reply-To: <CAH9NwWcE=4OVHSMKCEuTrFA7JMGEdkxrbX_0OORZ96N1Roi2HQ@mail.gmail.com>

Hi Christian,

Am Donnerstag, den 06.03.2014, 13:34 +0100 schrieb Christian Gmeiner:
> Hi all.
> 
> On our custom board design (imx6d) we are using a TFT-display
> connceted via LVDS.
> The datasheet [0] says that the display needs a defined power up
> sequence. I need
> to control the following stuff:
> 
> - LCD_ON (gpio2 3)
> - Backlight ON (gpio2 0)
> - PMW for dimm
> 
> At the moment I have the backlight suff ready:
> 
>        backlight {
>                compatible = "pwm-backlight";
>                pwms = <&pwm4 0 50000>;
>                enable-gpios = <&gpio2 0 0>;
> 
>                brightness-levels = <0 1 2 3 4>;
>                default-brightness-level = <4>;
>        };
> 
> Now I only need to enable the LCD_ON and wait 40ms before turning on
> the LVDS clocks and data.

This can be done by adding a regulator-enable-ramp-delay property to the
gpio regulator.

> For this I tought to add a regulator support in
> imx_ldb_encoder_commit(..) of imx-ldb.c.
>That should give me the correct sequence for
> LVDS on to LVDS data/clock. Now I only need to get the pwm-backlight
> driver doing its work after ldb is ready.

We should rather add drm_panel support to imx-ldb. I have just sent a
patch for this.
The simple-panel driver already supports regulator and backlight.

regards
Philipp

  reply	other threads:[~2014-03-06 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 12:34 imx-drm: ldb and display power on sequence Christian Gmeiner
2014-03-06 14:00 ` Philipp Zabel [this message]
2014-03-07 11:18   ` Christian Gmeiner
2014-03-11  8:51     ` Christian Gmeiner
2014-03-13 13:04       ` Christian Gmeiner

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=1394114410.3622.14.camel@paszta.hi.pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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 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).