Rebased ref, commits from common ancestor:
commit 4b9a33e613c55fdd6a22ff246b22c45149a97dd6
Author: Jason Uhlenkott <jasonuhl at jasonuhl.org>
Date: Tue Jul 15 09:12:34 2008 +0100
sdio: use interruptible sleep in kthread main loops
My FreeRunner's load average was leveling off at 2.00 as a result of
these two kernel threads:
SDIO Helper D c02b4500 0 255 2
[<c02b4298>] (schedule+0x0/0x2d4) from [<c02b4040>] (__down+0x100/0x158)
[<c02b3f40>] (__down+0x0/0x158) from [<c02b3e2c>] (__down_failed+0xc/0x20)
r7:00000000 r6:c01fbd64 r5:c7cb7134 r4:c7d58000
[<c01fa6fc>] (CardDetectHelperFunction+0x0/0x1ac) from [<c01fbd80>] (HelperLaunch+0x1c/0x28)
r5:c7cb7134 r4:c7cb7134
[<c01fbd64>] (HelperLaunch+0x0/0x28) from [<c005bbd0>] (kthread+0x60/0x94)
r4:c7d58000
[<c005bb70>] (kthread+0x0/0x94) from [<c0048f7c>] (do_exit+0x0/0x744)
r6:00000000 r5:00000000 r4:00000000
SDIO Helper D c02b4500 0 259 2
[<c02b4298>] (schedule+0x0/0x2d4) from [<c02b4040>] (__down+0x100/0x158)
[<c02b3f40>] (__down+0x0/0x158) from [<c02b3e2c>] (__down_failed+0xc/0x20)
r7:c0382bb4 r6:c0382b34 r5:c7d5a000 r4:00000001
[<c01f9104>] (SDIOIrqHelperFunction+0x0/0x29c) from [<c01fbd80>] (HelperLaunch+0x1c/0x28)
r8:00000000 r7:00000000 r6:c01fbd64 r5:c0382bb4 r4:c0382bb4
[<c01fbd64>] (HelperLaunch+0x0/0x28) from [<c005bbd0>] (kthread+0x60/0x94)
r4:c7d5a000
[<c005bb70>] (kthread+0x0/0x94) from [<c0048f7c>] (do_exit+0x0/0x744)
r6:00000000 r5:00000000 r4:00000000
This fixes them to use interruptible sleep primitives while waiting in
their main loops, as is conventional for kernel threads. They can't
actually be interrupted since kernel threads ignore all signals, but
by sleeping this way they get classified as long term waiters, and
don't get counted as running for purposes of load average calculation.
This is intended as a minimal fix. In the longer term, it'd probably
make sense to replace the semaphores with completions or something,
and to do away with some of these StudlyCapped wrapper functions.
Signed-off-by: Jason Uhlenkott <jasonuhl at jasonuhl.org>
--
This is untested, but what could possibly go wrong? ;)
commit be7cbde703b99e9fbf5ee7e95f805ba29c67965f
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:12:34 2008 +0100
test-force-gps-voltage-3v6.patch
Allows you to control RF_3V between 3.0V and 3.3V; this increases the
phantom voltage at the internal antenna from 2.63V to 2.85V and may
or may not affect antenna gain and GPS behaviour.
You can read and set the GPS voltage by
# cat /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/power_mv
3300
# echo 3100 > /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/power_mv
Signed-off-by: Andy Green <andy at openmoko.com>
commit dd1abcc14ce89cc9ef74b60b5ac8e183028ac0b9
Author: Mike Westerhof <mwester at dls.net>
Date: Tue Jul 15 09:12:33 2008 +0100
commit 5f42e24d361cd83178fe8da9d68efbf41a011483
Add missing initialization for the touchscreen driver for the
gta01 platform.
Signed-off-by: Mike Westerhof <mwester at dls.net>
commit 8786070b544806a0f29f4dc685f243ec5b13d2b4
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:12:33 2008 +0100
test-touchscreen-median.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit cc09be1a2b498a42cea30507a441eb67c80da1e4
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:12:33 2008 +0100
config-touchscreen-filters.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit fd25f90517322fc6c07bfb8d34752d3cb41cb4b6
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:04:11 2008 +0100
introduce-BANKCON-meddling-sysfs.patch
A few questions have been flying around about how optimal
our waitstates are for various things including Glamo.
This patch introduces new sysfs nodes
/sys/devices/platform/neo1973-memconfig.0/BANKCON0
...
/sys/devices/platform/neo1973-memconfig.0/BANKCON7
If you cat them you get translated info about bus speed on
that chip select, eg,
# cat /sys/devices/platform/neo1973-memconfig.0/BANKCON1
BANKCON1 = 0x00000A40
Type = ROM / SRAM
PMC = normal (1 data)
Tacp = 2 clocks
Tcah = 0 clocks
Tcoh = 1 clock
Tacc = 3 clocks
Tcos = 1 clock
Tacs = 0 clocks
You can write them in hex too
# echo 0x200 > /sys/devices/platform/neo1973-memconfig.0/BANKCON1
The write format for BANKCON0 - 5 looks like this
b1..b0 PMC Page Mode Config
b3..b2 Tacp Page Mode Access Cycle
b5..b4 Tcah Address hold after CS deasserted
b7..b6 Tcoh CS hold after OE deasserted
b10..b8 Tacc Access Cycle Period
b12..b11 Tcos CS setup before OE asserted
b14..b13 Tacs Address setup before CS asserted
BANKCON 6 and 7 have two extra bits
b16..b15 MT Memory type (00=ROM/SRAM, 11=DRAM)
If it's ROM/SRAM, the rest of the bits are as described above.
For DRAM
b1..b0 SCAN Column address number
b3..b2 RAS to CAS delay
The patch is intended to let people experiement on their own. But
of course you will crash things for sure if the timing is wrong, and
you can also trash SD Card data if you make Glamo unstable, so remove
it or remount ro first. Other horrible things are possible, but
because the settings aren't sticky, you should always be able to
recover by either normal reboot usually or at worst NOR boot and then
dfu. Most likely you will just crash your session and have to reboot
if your settings are bad, but consider yourself warned bad things are
possible. :-)
Signed-off-by: Andy Green <andy at openmoko.com>
commit db07519c1dfe916bcf9644bfdc4d7c03707a979e
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:04:05 2008 +0100
change-backlight-level-not-forced-up-on-resume.patch
We at least always enabled backlight on resume, this patch
changes us to set backlight back to last requested backlight
brightness level on resume. Note it means that you can
resume with screen blanked, but it should come back if that
happened with touchscreen action as usual.
/sys/class/backlight/pcf50633-bl/actual_brightness
and
/sys/class/backlight/pcf50633-bl/brightness
seem to agree after resume when reportedly they didn't before.
Signed-off-by: Andy Green <andy at openmoko.com>
commit e1673170182af199be7c6a2a346d8bad7e4dc532
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 15 09:04:00 2008 +0100
fix-glamo-suspend-resume-dram-and-engines.patch
Two issues... we never took care to take down engines in suspend
and bring them back in resume. This was part of the display
corruption that could be seen briefly on resume. The other issue
that made the "noise" corruption was bad ordering of resume steps.
This patch simplifies (removing needless re-init) resume actions
and makes explicit the suspend and resume steps. It also adds
code to track which engines are up and push them down in suspend
and bring them back in resume.
The result is no more corruption of display buffer in suspend, it
comes back completely clean.
Signed-off-by: Andy Green <andy at openmoko.com>