Age | Commit message (Collapse) | Author |
|
This adds a stopgap measure to permit manipulation of the LCD controller
chip in the absence of an fb notifier chain. It also adds some messing
around with the DPMS stuff.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
issue""
This reverts commit aa2dbc74bed8cf60e591c654ba1882011b9a8ece.
Reverting the revert. Sorry for the noise.
Check:
http://lists.openmoko.org/pipermail/openmoko-kernel/2009-April/010023.html
|
|
This reverts commit bd4b7e8e84ab43a13a4620b001d52d373c2122b3 which brought
WSOD back for some devices.
It was reported that the problem does not happen with Qi and it
seem it is good news. See:
https://docs.openmoko.org/trac/ticket/2274
Conflicts:
drivers/video/display/jbt6k74.c
|
|
Cleaned unnecessary debugging output.
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
Space transition between sleep-in and sleep-out of at least
120 ms as mentionned in the spec. Also, made sure the LCM
is moved into sleep state before the pixel clock is turned off.
To do so, I've modified glamo-fb to send FB_BLANK_POWERDOWN before
turning off the pixel clock. Also fixed various violation of coding
style. This patch should reduce the risk of white screen.
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
Some registers where not set properly, or at the right time (thanks to Balaji
for his patch).
Weak locking could lead to corruption when using sysfs to switch state from
multiple threads or processes. The state transitions are now all atomic.
The driver attribute 'last_state' was used for same purpose of 'normal_state'.
Kept only 'normal_state' and used it in 'init_regs' instead of custom qvga
parameter.
This patch should fix bug #2235.
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
Hi Andy,
Here's the fix for the qvga-normal bug we observed the other day
here - when the screen is powered up again after a blanking, in
qvga-normal mode, we see a WSOD(kind of!)
|
|
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-fix-stray-endmenu-patch-1232632040-1232632141
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040-1232632141 / fdf777a63bcb59e0dfd78bfe2c6242e01f6d4eb9 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040
stable-tracking-hist top was MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 / 90463bfd2d5a3c8b52f6e6d71024a00e052b0ced ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-fix-stray-endmenu-patch
mokopatches-tracking-hist top was fix-stray-endmenu-patch / 3630e0be570de8057e7f8d2fe501ed353cdf34e6 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-stray-endmenu.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
-device-driv-1232448327
pending-tracking-hist top was MERGE-via-stable-tracking-add-tpo-l1k002-lcm-device-driv-1232448327 / 776c842e391a2fbc8e85cab38c90be2ce44e7cf7 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-add-tpo-l1k002-lcm-device-driv
stable-tracking-hist top was add-tpo-l1k002-lcm-device-driv / 738664a979e3fa43f3d53989390ce6212c818c92 ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
Add TPO L1K002 LCM device driver.
This device is adopted as LCM of gta03.
The patch provides the initialization for this LCM driver IC.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Fix resume dummy in jbt6k74.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
_deep_sleep-1228475349
pending-tracking-hist top was MERGE-via-stable-tracking-jbt6k74_cleanup_no_deep_sleep-1228475349 / 7e4328b084323f8c35918bc2cb7a3afcf0ddf180 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-jbt6k74_cleanup_no_deep_sleep-
stable-tracking-hist top was jbt6k74_cleanup_no_deep_sleep- / f5213710553fe7a94cc0b47740162b8a745fa277 ... parent commitmessage:
From: nicolas dufresne <nicolas.dufresne@gmail.com>
jbt6k74_cleanup_no_deep_sleep.patch
Improve jbt6k74 driver changes to avoid WSOD so they don't stomp
on QVGA / VGA mode situation
|
|
eep-patch-0-1228473838
pending-tracking-hist top was MERGE-via-stable-tracking-jbt6k74_no_deep_sleep-patch-0-1228473838 / 5e9cdd03594ab072a42751e25d1aa2c08d65f13c ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-jbt6k74_no_deep_sleep-patch-0
stable-tracking-hist top was jbt6k74_no_deep_sleep-patch-0 / f2b6b0b0b2d235457e0c69cfdbf4f66a12dc2c4e ... parent commitmessage:
From: Nicolas Dufresne <nicolas.dufresne@gmail.com>
jbt6k74_no_deep_sleep.patch
This patch from
https://docs.openmoko.org/trac/ticket/1841
defeats deep sleep on the LCM ASIC and is reported to stop the WSOD
behaviour on LCMs that exhibit it.
|
|
racking-hist-1228427992-1228428064
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-stable-tracking-hist-1228427992-1228428064 / a02b19a9e543d49f2217ebd7f743a4082ecc0290 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-stable-tracking-hist-1228427992
stable-tracking-hist top was MERGE-via-stable-tracking-hist-1228427992 / 5fa26c730284f8aaa399f0a034988e786f383bda ... parent commitmessage:
From: merge <null@invalid>
MERGE-stable-tracking-patchset-edits
|
|
eep-patch-1228416934
pending-tracking-hist top was MERGE-via-stable-tracking-jbt6k74_no_deep_sleep-patch-1228416934 / 2920ea8e9a869e224ec22dea02c85def3910ff57 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-jbt6k74_no_deep_sleep-patch
stable-tracking-hist top was jbt6k74_no_deep_sleep-patch / 8e318ae8cab52b85323a36ac7808bf33e7a98797 ... parent commitmessage:
From: Nicolas Dufresne <nicolas.dufresne@gmail.com>
jbt6k74_no_deep_sleep.patch
This patch from
https://docs.openmoko.org/trac/ticket/1841
defeats deep sleep on the LCM ASIC and is reported to stop the WSOD
behaviour on LCMs that exhibit it.
|
|
Move backlight support out of pcf50633 driver. backlight
support now uses corgibl aka generic backlight support.
Set
CONFIG_BACKLIGHT_CORGI=y to use it.
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Weeks of frantic effort to control Glamo, traced the issue to two outcomes:
nWAIT is forced down and the device is hard locked, or we survive immediate
Glamo resume and die again with nWAIT forced down when the framebuffer driver
tries to flash the soft cursor.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
All that stuff should be enforced by device tree now, out with it
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
FB_BLANK events and switch the JBT6K74 LCM controller into
its power saving mode.
This has the potential of saving something like 50mW during screen blank.
Signed-off-by: Harald Welte <laforge@openmoko.org>
|
|
mach-gta02 meddles with the regulator platform struct after
it is defined, leading to LCM power getting lost in suspend
despite I set it to be left up. Fixing this finally removes
the incredibly stubborn white LCM on suspend "flash".
This is also going to be implicated in Sean McNeil's
experience of monochromatic LCM after resume, which was
previously attacked by resetting and re-initing the LCM
from scratch.
In addition, I realized that we take down core_1v3 in
pcf50633 suspend action, this is happening near the
start of suspend, so we are in a meta-race to finish
suspend in a controlled way before the caps on core_1v3
run out (I only saw 23.3uF total). If it's true, this
is where the weirdo sensitivity to timing during
suspend is coming from.
Therefore in this patch we also remove sleeps and
dev_info() etc (which have to flush on serial console)
from the pc50633 isr workqueue if we are in pcf50633
driver suspend state 1, ie, suspending... because we
don't have time for it.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
The LCM spins for 100ms during resume for not much reason. Leave it powered
(it is meant to pull uA when suspended) and get nice fast resume to video.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Sean McNeil reports that without the reset for LCM in suspend, he
gets a monochromatic mode on it somehow.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Adds the resume callback stuff to glamo, then changes
jbt6k74 to no longer use a sleeping workqueue, but to
make its resume actions dependent on pcf50633 and
glamo resume (for backlight and communication to LCM
respectively)
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This patch improves the smoothness of suspend and resume action.
Taking out CONFIG_PM_DEBUG allows much more rapid resume (the low level
serial traffic appears to be synchronous)
Added a platform callback in jbt driver and support in pcf50633 so we
can defer bringing up the backlight until the LCM is able to process
video again (which must happen after the glamo is up and producing
video beacuse the LCM is hooked to glamo SPI)
GTA01 should not be affected by all this as the callback will default
to null and it is on pcf50606
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-Off-By: Holger Freyther <zecke@openmoko.org>
|
|
|
|
This driver adds support for the SPI-based control interface of the LCM (LCD
Panel) found on the FIC GTA01 hardware.
The specific panel in this hardware is a TPO TD028TTEC1, but the driver should
be able to drive any other diplay based on the JBT6K74-AS controller ASIC.
Signed-off-by: Harald Welte <laforge@openmoko.org>
|
|
Now that device_create() has been audited, rename things back to the
original call to be sane.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
There is a race from when a device is created with device_create() and
then the drvdata is set with a call to dev_set_drvdata() in which a
sysfs file could be open, yet the drvdata will be NULL, causing all
sorts of bad things to happen.
This patch fixes the problem by using the new function,
device_create_drvdata().
Cc: Kay Sievers <kay.sievers@vrfy.org>
Cc: James Simmons <jsimmons@infradead.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Cc: James Simmons <jsimmons@infradead.org>
Cc: "Antonino A. Daplas" <adaplas@pol.net>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|
|
Add the new display class. This is meant to unite the various solutions to
display units ie acpi output device, auxdisplay and the defunct lcd class
in the backlight directory.
Signed-off-by: James Simmons <jsimmons@infradead.org>
Cc: "Antonino A. Daplas" <adaplas@pol.net>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|