From: Andrzej Hajda <a.hajda@samsung.com>
To: Inki Dae <inki.dae@samsung.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/panel/ld9040: add power control sequence
Date: Thu, 17 Apr 2014 14:54:53 +0200 [thread overview]
Message-ID: <534FCF1D.3010004@samsung.com> (raw)
In-Reply-To: <1396954685-12803-1-git-send-email-a.hajda@samsung.com>
Hi Inki,
Could you pick up this patch into the fixes branch.
Regards
Andrzej
On 04/08/2014 12:58 PM, Andrzej Hajda wrote:
> Some ld9040 panels do not start without providing power control sequence
> during initialization. The patch fixes the driver by providing such
> sequence for all panels.
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/gpu/drm/panel/panel-ld9040.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/panel/panel-ld9040.c b/drivers/gpu/drm/panel/panel-ld9040.c
> index 1f1f837..db1601f 100644
> --- a/drivers/gpu/drm/panel/panel-ld9040.c
> +++ b/drivers/gpu/drm/panel/panel-ld9040.c
> @@ -27,6 +27,7 @@
> #define MCS_ELVSS_ON 0xb1
> #define MCS_USER_SETTING 0xf0
> #define MCS_DISPCTL 0xf2
> +#define MCS_POWER_CTRL 0xf4
> #define MCS_GTCON 0xf7
> #define MCS_PANEL_CONDITION 0xf8
> #define MCS_GAMMA_SET1 0xf9
> @@ -182,6 +183,8 @@ static void ld9040_init(struct ld9040 *ctx)
> ld9040_dcs_write_seq_static(ctx, MCS_DISPCTL,
> 0x02, 0x08, 0x08, 0x10, 0x10);
> ld9040_dcs_write_seq_static(ctx, MCS_MANPWR, 0x04);
> + ld9040_dcs_write_seq_static(ctx, MCS_POWER_CTRL,
> + 0x0a, 0x87, 0x25, 0x6a, 0x44, 0x02, 0x88);
> ld9040_dcs_write_seq_static(ctx, MCS_ELVSS_ON, 0x0d, 0x00, 0x16);
> ld9040_dcs_write_seq_static(ctx, MCS_GTCON, 0x09, 0x00, 0x00);
> ld9040_brightness_set(ctx);
next prev parent reply other threads:[~2014-04-17 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 10:58 [PATCH] drm/panel/ld9040: add power control sequence Andrzej Hajda
2014-04-17 12:54 ` Andrzej Hajda [this message]
2014-05-05 8:51 ` Andrzej Hajda
2014-05-05 10:42 ` Thierry Reding
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=534FCF1D.3010004@samsung.com \
--to=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.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