From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Inki Dae <inki.dae@samsung.com>
Cc: FlorianSchandinat@gmx.de, linux-fbdev@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kyungmin.park@samsung.com
Subject: Re: [PATCH] FB: add early fb blank feature.
Date: Thu, 15 Sep 2011 09:53:13 +0000 [thread overview]
Message-ID: <1316080393.23214.12.camel@deskari> (raw)
In-Reply-To: <1315544581-16379-1-git-send-email-inki.dae@samsung.com>
Hi,
On Fri, 2011-09-09 at 14:03 +0900, Inki Dae wrote:
> this patch adds early fb blank feature that this is a callback of
> lcd panel driver would be called prior to fb driver's one.
> in case of MIPI-DSI based video mode LCD Panel, for lcd power off,
> the power off commands should be transferred to lcd panel with display
> and mipi-dsi controller enabled because the commands is set to lcd panel
> at vsync porch period. on the other hand, in opposite case, the callback
> of fb driver should be called prior to lcd panel driver's one because of
> same issue. now we could handle call order to fb blank properly.
>
> the order is as the following:
>
> at fb_blank function of fbmem.c
> -> fb_early_notifier_call_chain()
> -> lcd panel driver's early_set_power()
> -> info->fbops->fb_blank()
> -> fb driver's fb_blank()
> -> fb_notifier_call_chain()
> -> lcd panel driver's set_power()
I'm not familiar with the lcd.c, so I may be talking nonsense, but I
don't quite understand the need for this patch. If you have some kind of
panel driver, shouldn't the panel driver handle power off in just one
place?
With omapfb and omapdss, the omapfb's fb_blank function just calls power
off in the panel driver, which handles all necessary actions. Is your
model somehow totally different?
Tomi
next prev parent reply other threads:[~2011-09-15 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 5:03 [PATCH] FB: add early fb blank feature Inki Dae
2011-09-15 9:53 ` Tomi Valkeinen [this message]
2011-09-15 10:14 ` Inki Dae
2011-09-15 10:26 ` Tomi Valkeinen
2011-09-15 11:37 ` Lars-Peter Clausen
2011-09-26 10:36 ` Inki Dae
2011-09-26 11:15 ` Inki Dae
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=1316080393.23214.12.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).