Rebased ref, commits from common ancestor:
commit ffebf2f8e5af956749d7bff4d1ba48dc24b2d406
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Jul 27 20:31:06 2008 +0200
[gta02] Disable hardware ECC unless we get instructed to enable it
This is restoring the old behavior in regard to ECC. Even if
hardware ECC was compiled in we didn't use it. Make this a runtime
option. If the bootloader passes hardware_ecc we will enable the
hardware ECC for real.
commit 79850664c8b68bb56568e45d5aac308eb60f4673
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Jul 27 18:44:51 2008 +0200
[bq2000] Be able to compile the kernel without bq2000 battery support
Signed-off-by: Holger Freyther <zecke at openmoko.org>
commit 67d278f16f4291816790dcd7716d9e8a73cb4e9d
Author: Holger Freyther <zecke at openmoko.org>
Date: Sat Jul 26 22:57:27 2008 +0200
[gta02] Disable the NAND debugging as it would print every hardware ECC
commit 42862206c5c586c0e92a1c3bb087bbcc7c9c4194
Author: Holger Freyther <zecke at openmoko.org>
Date: Thu Jul 24 18:37:49 2008 +0200
Revert "s3c2440-nand-disable-hwecc.patch"
This reverts commit 1d89da736ed33d3f7c398fb9f8dfddecb7c7c7a9.
commit 41cecdb10c99b47a856446b1440d32d8d9b03586
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 23 14:12:45 2008 +0200
[defconfig-2.6.24] Disable a whole set of kernel debugging
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit be0f111b3d1570dec174ff301d08bad995ccf1e6
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 22 22:17:15 2008 +0100
fix-pcf50633-only-do-platform-callback-once-per-event.patch
Reported-by: Holger Freyther <zecke at openmoko.org>
We harmlessly repeated PMU platform callbacks about charging state twice.
Clean it up and leave it to pcf50633_charge_enable() to report once.
Also tidies the sequencing so we set current limit before we enable
charger now.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 3574745cad910ce45db692baadf1fe233bc383b5
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 22 22:17:04 2008 +0100
fix-pcf50633-remove-charger-curlim-and-enable-apis-from-export.patch
Setting the current limit directly and enabling the charger
isn't anyone's business except pcf50633 driver itself, so these
two functions should not be exported and become static.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 66a83c97c4545ce4f07e0d90998f906fae49caf2
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 22 13:16:29 2008 +0100
fix-glamo-mci-set-default-drive-level-0.patch
Tests on access to SD Card with Glamo drive level "0" show
that it reduces SD_CLK energy at 1.5GHz by 24dBm compared to
drive level 3. This puts it only 6dB above the background
noise floor compared to 30dB and should make a solution for
GPS trouble with SD Card in.
SD card communication seems unaffected so far on the Sandisk
512MB card we ship.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 46159c9a3fba291d106625092fd62358548894e0
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 22 13:16:16 2008 +0100
fix-bq27000-charger-state-tracking.patch
Charger trigger stuff goes and asks for POWER_SUPPLY_PROP_STATUS
to figure out what the charger state is. But until now, we only
reported there what we found out from HDQ, and the HDQ registers
are not updated very often in the coulomb counter, it can be 4
or more second lag before it tells us about what it experiences.
When we react to USB insertion and only after 500ms debounce tell
power_supply stuff that something changed, it most times will
see old pre-USB-insertion state from bq27000 over HDQ at that time
and will report it ain't charging, buggering up the LED trigger
tracking.
This patch maintains distance between bq27000 and pcf50633 by
having platform callbacks in bq27000 that it can use to ask about
definitive charger "online" presence and "activity", whether the
charger says it is charging. If these callbacks are implemented
(and we implement them in this patch up in mach_gta02.c) then
this information is used in preference to what is found from
HDQ.
Result is if you set the LED trigger like this:
echo bat-charging > /sys/devices/platform/gta02-led.0/leds/gta02-aux:red/trigger
then it lights up properly on USB insertion now, goes away on
removal properly, as as far as I saw, when charging stops too.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 2eab6880861e27126d059251f88de92ac3e75eb1
Author: Andy Green <andy at openmoko.com>
Date: Tue Jul 22 13:16:07 2008 +0100
fix-pcf50633-move-charger-enable-decision-to-pcf50633_usb_curlim_set.patch
At the moment we ended up enabling and disabling the charger
at the time we service USBINS and USBREM events in the ISR.
We did that in machine specific code, but really it is PMU
specific decision, so this patch moves it into PMU code.
We enabled and disabled the charge immediately we saw the
interrupt event from PMU, yet we deferred setting charging
state based on ID and USB enumeration until at least after a
PMU ADC read that was handled in a second interrupt later.
Now the timing is unified to after we determined the charger
type and we enable and disable right there.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 1d04b142ffeaa15129f046751f1366b0f0614f47
Author: Andy Green <andy at openmoko.com>
Date: Mon Jul 21 00:51:30 2008 +0100
debug-add-glamo-drive-strength-module-param.patch
Suggested-by: Werner Almesberger <werner at openmoko.org>
This patch allows users to control two additional settings
in Glamo MCI driver from kernel commandline or module
parameters.
First is Glamo drive strength on SD IOs including CLK.
This ranges from 0 (weakest) to 3 (strongest).
echo 0 > /sys/module/glamo_mci/parameters/sd_drive
(Changes to this take effect on next SD Card transaction)
or, from kernel commandline
glamo_mci.sd_drive=0
On tests here with 0 strength, communication to SD card
(shipped 512MB Sandisk) seemed fine, and a dd of 10MB
urandom had the same md5 when written to cache as after
a reboot. I set the default to 2.
Second is whether we allow SD_CLK when the SD interface
is idle.
# stop the clock when we are idle (default)
echo 0 > /sys/module/glamo_mci/parameters/sd_idleclk
# run the SD clock all the time
echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk
(changes take effect on next SD Card transaction)
From kernel commandline, eg:
glamo_mci.sd_idleclk=1
Normally you don't want to run the SD Clock all the time.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 7588286c13ce04de9ce9b9a844033e07d0e71c93
Author: Andy Green <andy at openmoko.com>
Date: Mon Jul 21 00:51:15 2008 +0100
debug-move-dev-info-to-dbg.patch
Suggested-by: Sean McNeil <sean at mcneil.com>
To see if some subtle race is involved, Sean has tried
removing syslog traffic during resume and found he was
not seeing the resume crash any more. We're giving it
a try to see if it changes the behaviour for anyone
else. It would mean we have a pretty fine race in there
somewhere.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 6ec7d69f08cfb772fdf5d7c55ed9da2273677a4d
Author: Andy Green <andy at openmoko.com>
Date: Sun Jul 20 18:43:15 2008 +0100
fix-scard-stop-on-resume.patch
Reported-by: Ville-Pekka Vainio <vpivaini at cs.helsinki.fi>
The reporter noticed SD Card clock is running again after resume. After
looking at the code I saw I missed two tricks, this will force it off
after resume and will do better generally depending on what the last SD Card
packet was.
Since bulk read packet is normally last action (which set the clock off even
without this) the old patch worked for normal cases. But after resume, the last
packet on the wire was not a bulk transfer and we didn't take care about the
clock then.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 642cbda5f3b7e7a61512426e1d30a41ab4691123
Author: Andy Green <andy at openmoko.com>
Date: Thu Jul 17 12:21:53 2008 +0100
defconfig-enable-ext2-ext3-gtaxx.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit ef2376d29e996d9d21a9e5798cb88aa73f734c83
Author: Andy Green <andy at openmoko.com>
Date: Thu Jul 17 10:02:35 2008 +0100
add-limit-sdcard-clk-cmdline.patch
This patch allows you to control the maximum clock rate that will
be selected for SD Card access, from the kernel commandline using
glamo_mci.sd_max_clk=10000000
and also from
echo 10000000 > /sys/module/glamo_mci/parameters/sd_max_clk
although you have to suspend and resume to make the limit operational
on the actual SD_CLK line.
Clocks that are possible are divided down from ~50MHz, so 25000000,
16666666, 12500000, 10000000, etc. With Freerunner A5 revision that
has 100R series resistors in SD Card signals, I didn't get reliable
operation above 16MHz. With A6 revision the series resistors went
down to 75R, maybe it can work at 25MHz.
Reducing the clock rate is something to try if you find that your
SD Card is not communicating properly with the default speed.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5d70edcbe3ff5f6d5aef54ee9e278ad1ce431fd5
Author: Andy Green <andy at openmoko.com>
Date: Thu Jul 17 10:02:19 2008 +0100
fix-force-sdcard-clk-off-when-idle.patch
Existing Glamo bit for stopping SD Card Clock when there is no
transfer taking place does not work. This patch adds stuff around
the transfer code to force the SD clock up when something is going on
and down when it is idle. This'll save a little power and noise ;-)
I tested it briefly and was able to SD Boot normally on Sandisk 512M.
Wider testing is appreciated.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 287b292cf95edbd82dc63085ae5f0167a6e8141f
Author: Jason Uhlenkott <jasonuhl at jasonuhl.org>
Date: Tue Jul 15 11:37:45 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 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>
commit abb5807e67398d10a3014cc001897b11cc214ec9
Author: Andy Green <andy at openmoko.com>
Date: Sun Jul 13 20:31:04 2008 +0100
fix-no-uart-leak-when-gps-off.patch
During the suspend current reduction campaign on suspend I
forced the GPS UART to be GPIO and to drive 0 into the GPS
unit so we would not burn current there. On resume it lets
the pins act as UARTs again. But really, we should do this
all the time that the GPS unit is off, lest we leak it
enough power to hold internal state and make trouble.
Signed-off-by: Andy Green <andy at openmoko.com>
commit f96aab45a604cb0f46a6ca3aa286a821c2462fda
Author: Andy Green <andy at openmoko.com>
Date: Sun Jul 13 20:30:31 2008 +0100
add-pcf50633-allow-force-charger-type.patch
This patch adds a sysfs node:
/sys/class/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous
it allows to force the charging limit regardless of the one chosen
by pcf50633 kernel driver. As such, if you write a charging limit
here that is not suitable for the power source, and the power source
is not current limited on its side, it could draw more current than
your power source can handle, burn down you house, etc.
If you're certain that your power supply can handle it, you can use
this on your own responsibility to make the amount drawn by the
PMU match what you believed your power supply could handle.
Example usage, in case where you have a dumb 500mA USB charger that
does not have the ID resistor:
# cat /sys/class/i2c-adapter/i2c-0/0-0073/charger_type
host/500mA usb mode 100mA <=== dumb charger does not ennumerate us
# echo 500 > /sys/class/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous
# cat /sys/class/i2c-adapter/i2c-0/0-0073/charger_type
host/500mA usb mode 500mA
Signed-off-by: Andy Green <andy at openmoko.com>
commit 18ca5bd67840d6b2e21edb86057db10b2f21892d
Author: Andy Green <andy at openmoko.com>
Date: Sun Jul 13 20:30:20 2008 +0100
fix-aux-key-level-by-gtaxx.patch
Reported-by: Mickey Lauer <mickey at openmoko.org>
AUX level detection is inverted based on GTA01 or 02
Signed-off-by: Andy Green <andy at openmoko.com>
commit 691febd6e3dcf7b4e3fde786b1c6de2c1d978eb5
Author: Andy Green <andy at openmoko.com>
Date: Sun Jul 13 20:30:15 2008 +0100
fix-pcf50633-mask-second-on-resume.patch
We leave SECOND unmasked on resume, it's like the
situation at probe() time, but there it makes us
turn SECOND off after coldplug action. So we need
to act like after that has happened, not exactly
like what we do at probe / init time.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 9c058ff0d2641df3c36fc3300acb72078d2c41d4
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue Jul 8 18:38:19 2008 +0100
From 3a32be40f78404d5f1185f0b3d6b5632381cb33f Mon Sep 17 00:00:00 2001
Subject: [PATCH] [neo1973 leds] Move from mutex to spinlock because we may not use mutexes
The led triggers may call set_brightness from atomic contexts. As
mutex_lock calls might_sleep and sleeping is not allowed in atomic contexts
we have to switch to spinlocks here.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit e4b81c966e03ee280492e75cdd569f8495cb2a06
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue Jul 8 18:38:16 2008 +0100
From cede5c6c9b06ecbb0f7f2df7b7070092b87ddaf8 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [pcf50633] Avoid ooops on start with inserted usb cable
The pcf50633_global might not be initialized when we get the first
usb interrupt. We would oops inside the dev_err because we made up
a struct device.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 9af61cea8871d2303e06c5e71a121245d5fdc283
Author: Mike Westerhof <mwester at dls.net>
Date: Sun Jul 6 10:39:39 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 f5d2660aaa6b05397714ffb48e2e71c71cef0bdd
Author: Mike Westerhof <mwester at dls.net>
Date: Fri Jul 4 08:24:25 2008 +0100
Remove some bits of nspy + GSM flow control patches that leaked into stable
Signed-off-by: Mike Westerhof <mwester at dls.net>
commit 0f565eebf6f9a52a66053348aa710e05732f934e
Author: Matt <matt_hsu at openmoko.org>
Date: Wed Jul 2 23:02:14 2008 +0100
add-ar6k-wake-interrupt.patch
Signed-off-by: Matt Hsu <matt_hsu at openmoko.org>
- add an interrupt for ar6k wifi module
commit e86a397ab500cda75e7e0b7a27011f5dedee8338
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:45:15 2008 +0100
change-remove-kernel-charging-led-drive.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 618097c906c68f2df5fb03ace81e6295be6ded42
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:45:07 2008 +0100
From c221bb27c8e22daa451e26353140777223d397d2 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [pcf50633] Report more events to userspace using the default callback
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit d869fe11c6acbc3466abcdae741376b2c71bca69
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:44:59 2008 +0100
From 5718bde77ed1a75e0fd2cdf5e099e66121d10c0a Mon Sep 17 00:00:00 2001
Subject: [PATCH] [battery] Make the bq27000 send an uevent when the charging state possible changed
Remove the todo entries from the pcf50633, make the mach-gta02
call the bq27000 driver from the pmu callback.
commit b496d7ecfb1964a508f4aa2dfb8b27099e7777fc
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:44:49 2008 +0100
From 000450f1ad2c713d2345a872fdf44f5dd3702e1b Mon Sep 17 00:00:00 2001
Subject: [PATCH] [janitor] make checkpatch.pl happy
commit abd6565704cadc8d0968b6fede8d445f84c870d3
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:44:41 2008 +0100
From 683ef8067815f6ba0ede73fa71973823726213a3 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [janitor] Make checkpatch happy on the header files
commit 40581b00b3de51e2234e0e46a69287ab1e74bf75
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:44:32 2008 +0100
From ae3f72fc608fcd0a98a980a335ac4dc7ad95b221 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [bq27000] Make the checkpatch.pl happy
commit e2303161c93a90b966679b84c18838398b847d2c
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Wed Jul 2 22:44:22 2008 +0100
From 119f4e02ba81cffe4dbc88d8ff667048ad28d925 Mon Sep 17 00:00:00 2001
Subject: [PATCH] Hacky CONFIG_NO_IDLE_HZ (dyn-tick) support for S3C24xx.
commit 8e18a9db5f895f654b06000d7bd10528e6b795f3
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:44:11 2008 +0100
introduce-resume-exception-capture.patch
This patch introduces a new resume debugging concept: if we
get an OOPS inbetween starting suspend and finishing resume, it
uses a new "emergency spew" device similar to BUT NOT REQUIRING
CONFIG_DEBUG_LL to dump the syslog buffer and then the OOPS
on the debug device defined by the existing CONFIG_DEBUG_S3C_UART
index. But neither CONFIG_DEBUG_LL nor the S3C low level configs
are needed to use this feature.
Another difference between this feature and CONFIG_DEBUG_LL is that
it does not affect resume timing, ordering or UART traffic UNLESS
there is an OOPS during resume.
The patch adds three global exports, one to say if we are inside
suspend / resume, and two callbacks for printk() to use to init
and dump the emergency data. The callbacks are set in s3c serial
device init, but the whole structure is arch independent.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 6da7929da1b46bccaae0f53bf7a26cdd74a3b70a
Author: Mike Westerhof <mwester at dls.net>
Date: Wed Jul 2 22:44:01 2008 +0100
clean-gsm-flow-control.patch
Signed-off-by: Mike Westerhof <mwester at dls.net>
arch/arm/plat-s3c24xx/neo1973_pm_gsm.c | 52 +-------
drivers/serial/s3c2410.c | 204 +++-----------------------------
2 files changed, 24 insertions(+), 232 deletions(-)
commit 2a1042fc56273fac721207597968af313751c17b
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:43:53 2008 +0100
fix-gsm-resume-problems.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit b70bd0433a197f93f927f7b5720efe889aa4b430
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:43:45 2008 +0100
fix-lis302dl-resume-and-init-reload-boot-coefficients.patch
Reported-by: John Lee <john_lee at openmoko.com>
We don't reset the devices either at init or resume, where init
means use the BOOT bit to reload device calibration coefficients
from internal EEPROM. John Lee saw brain-damaged behaviour after
resume and sometimes after boot (since it may not have lost power
to force a BOOT itself that makes sense).
This patch
- adds a diagnostic dump feature down /sys
- forces BOOT action on init and resume, and waits for
completion
- makes sure XYZ capture is enabled on resume
- adds some constants in the .h and removes some magic numbers
in the code by using them
Signed-off-by: Andy Green <andy at openmoko.com>
commit e0dc30dfda233d4ebe6f88cd1162e5952fc69027
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:43:38 2008 +0100
fix-touchscreen-meddling-divde.patch
Reported-by: Holger Freyther <zecke at openmoko.org>
length can be zero... blowing a divide by zero exception...
which somehow I don't get (?) Anyway the code is wrong and
this should fix it.
Signed-off-by: Andy Green <andy at openmoko.com>
commit cf7096e6f6e24d8a362ad05f768d609a2921f479
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:43:31 2008 +0100
touchscreen-meddling.patch
Touchscreen on GTA01-02 experiences noise on the channel that serves the
"tall axis" of the LCM. The sample quality of the other axis is good.
The bad samples have a characteristic of one shot excursions that can
reach +/- 20% or more of the sample average.
Previously, we had a simple averaging scheme going in the touchscreen
driver that summed up 32 x and ys and then divided it by 32. This patch
first tidies up the existing code for style, then adds a new "running
average" concept with a FIFO. The running average is separate from the
summing average mentioned above, and is accurate for the last n samples
sample-by-sample, where n is set by 1 << excursion_filter_len_bits in the
machine / platform stuff.
The heuristic the patch implements for the filtering is to accept all
samples, but tag the *previous* sample with a flag if it differed from
the running average by more than reject_threshold_vs_avg in either
axis. The next sample time, a beauty contest is held if the flag was
set to decide if we think the previous sample was a one-shot excursion
(detected by the new sample being closer to the average than to the
flagged previous sample), or if we believe we are moving (detected by
the new sample being closer to the flagged previous sample than the
average. In the case that we believe the previous sample was an
excursion, we simply overwrite it with the new data and adjust the
summing average to use the new data instead of the excursion data.
I only tested this by eyeballing the output of ts_print_raw, but it
seemed to be quite a bit better. Gross movement appeared to be
tracked fine too. If folks want to try different heuristics on top
of this patch, be my guest; either way feedback on what it looks like
with a graphical app would be good.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 0e049b8ff8ad37e3749121519fe96d357e0754f4
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:43:20 2008 +0100
introduce-panic-blink-led-not-using-userspace-omfg.patch
A panic is silent on GTA02, it would be good if we got a little hint
if we are crashing (eg, in suspend / resume) from a panic instead of
a deadlock, etc. On a normal PC i8042 blinks the keyboard lights if
we panic, this patch causes AUX to flash at 5Hz in event of a panic.
Tested by giving kernel fake root= that didn't exist.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 57df1041409b50f2cc3137a820254fa982c49c45
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Wed Jul 2 22:43:11 2008 +0100
Subject: [PATCH] glamo: Don't disable hwcursor for blinking and use vsync-wait.
commit 84b639db4a4cd8e7a6f65956148256152bf1e348
Author: Holger Freyther <zecke at openmoko.org>
Date: Wed Jul 2 22:43:03 2008 +0100
Subject: [PATCH] [a6k] Everyone calls SET_NET_DEV and hald needs that too,
make it happy
Call SET_NET_DEV to set a parent device. All other net drivers
are doing this and hald needs a parent to add the network device.
commit edd4b9c7128495063fb529282ebbf165a20f7a23
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:42:56 2008 +0100
workaround-s3c24xx-i2s-stop-live-stream-stall-on-resume.patch
Reported-by: Graeme Gregory <graeme at openmoko.org>
Basically-solved-by: Graeme Gregory <graeme at openmoko.org>
Graeme found a while back that on resume, IISCON register in
s3c2442 does not show LRCK toggling in LRINDEX bit any more,
causing s3c24xx_snd_lrsync() to timeout and return an error,
aborting restart of any live stream that was playing at
suspend.
I confirmed it was true, meddled around for a bit looking
for some magic to restart LRCK or at least the reporting of
it, and in the end worked around it using the method noted
by Graeme: just ignore LRCK sync if it timed out. The worst
that could happen would be L and R swap for the duration of
stream that was suspended into but probably not even that.
Signed-off-by: Andy Green <andy at openmoko.com>
commit d67dac178e8f4badacb161ad9505a3fbd6a2246e
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:42:48 2008 +0100
fix-pcf50633-use-pcf-not-data-in-probe-for-context.patch
Everywhere in the sources except the probe function the context
pointer is called "pcf"... in there it's called "data" for some
reason. This stops confusion by changing it to be "pcf" in there
as well.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 80b4a26a51a75a92ddbb64b342068b741ef88416
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:42:39 2008 +0100
fix-pcf50633-migrate-gta02-peripherals-out.patch
pcf50633.c shouldn't know GTAxx at all. Move to using a
platform callback to allow definition of platform devices
with pcf50633 as parent device (good for enforcing suspend /
resume ordering). Remove all code references to GTAxx from
the sources (one string left for compatability).
Signed-off-by: Andy Green <andy at openmoko.com>
commit 31afa68418678eef1885db656a935b24d51dce9b
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:42:29 2008 +0100
fix-pcf50633-platform-backlight-resume-ramp-setting.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 0c734eb8a3a41ca9f9b452d0d1a7211de6c146dd
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:42:07 2008 +0100
fix-pcf50633-really-defer-backlight-on-resume.patch
Backlight wasn't off by default on resume, so it was never really
deferred (until LCM is initialized). This fixes that and so removes
the brief white screen between pcf50633 resume and LCM init.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 91edf710900c85d081f2f56ad23d85f65674d316
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:59 2008 +0100
debug-backtrace-not-choke-on-null-dev_blah.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit eaa55efc0b559abebbcf2acea6ce267cea4c26f2
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:52 2008 +0100
fix-pcf50633-disable-irq-from-suspend-until-resume.patch
Disable pcf interrupt (not for wake, just as interrupt) in
suspend, re-enable it again just before we force-call the
workqueue function at end of pcf resume, which leads to
pcf interrupt source registers getting cleared so it can
signal an interrupt normally again.
This change ends the uncontrolled appearance of pcf interrupts
during resume time which previously caused the work to attempt
to use the I2C stuff before i2c host device had itself resumed.
Now the isr work is only queued, and the isr work function called,
definitively after pcf resume completes.
In suspend time, the work function may have been queued some
time before and be pending, and it could still show up at a
bad time. Therefore if the work function sees that it is
coming since the start of pcf50633 suspend function, it
aborts without attempting to read the pcf interrupt regs,
leaving them for resume to take care of.
USB current limit and no battery work functions are also made
aware of suspend state and act accordingly.
Lastly I noticed that in early resume, i2c_get_clientdata(&pcf->client)
returns NULL, presumably because i2c device is still suspended. This
could easily make trouble for async events like interrupt work,
since pcf pointer is the client data. Disabling appearance of the
work until after pcf50633 resume will also avoid that.
Signed-off-by: Andy Green <andy at openmoko.com>
commit dd7ff306b150c36950fa0f9dd718a1745a984d38
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:38 2008 +0100
fix-pcf50633-suspend-state-as-enum.patch
Use an enum to define pcf50633 suspend / resume state.
Add PCF50633_SS_RESUMING_BUT_NOT_US_YET to be the state
early in resume: add platform driver resume function just
to set this state so we can differentiate between early
resume and late suspend.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 6588d2e1ca2092e37781cfa17aea741165e01f7e
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:30 2008 +0100
debug-i2c-s3c2410-dump-stack-on-suspended-tranfer.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 56cb6e3d90e4fea9cefe133a7b0e2ce0f29ea379
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:22 2008 +0100
fix-allow-core-1v3-to-go-down.patch
Whoops left it up in suspend
Signed-off-by: Andy Green <andy at openmoko.com>
commit 358429b39b6801f4856e7c80d2c58ac7be4bd0bc
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:14 2008 +0100
fix-pcf50633-kill-white-splash-of-death-on-suspend.patch
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 at openmoko.com>
commit 22669f5d3422bca55eb247759d570306c1d6f1ae
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:41:07 2008 +0100
cosmetic-checkpatch-complaints.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit b6aa20d6e44fccefba7ca933d11befba3611a68a
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:58 2008 +0100
fix-pcf50633-add-back-gratuitous-isr-work-call-in-resume.patch
Sean McNeil reports that he doesn't get pcf50633 interrupts any
more after resume. This adds back the call to ISR work in
the resume, removal of which is probably to do with it.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 2d0f061cbf1ae256c9c91ee45bc4d09c2a8b1cdf
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:51 2008 +0100
fix-pcf50633-require-resume-level-3-for-irq-work.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5007c46ae31856ddac45e0e59bb54cd37c51fe78
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:43 2008 +0100
add-remote-install-sdcard-script.patch
If you boot from SDCARD, this helper script for the build host
mounts SD card part 1, copies the new uImage.bin, umounts it and
then remounts SD card part 2 as ro, before doing a reboot all
in one step. Read the instructions inside the script for adding
your public key to the GTAxx rootfs for really really simple and
nice automatic update and reboot action.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 913b141d09400c05fa4a6e69f325a6504ce1fe40
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:36 2008 +0100
fix-gta02-mach-remove-gta01-lcd-reset.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 897135bb5ce881419ee6e7c97875293b3e74330c
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:28 2008 +0100
change-lcm-keep-power-faster-resume.patch
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 at openmoko.com>
commit 553cc686ad357fc169a95733c51f7ae3466bb248
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:21 2008 +0100
fix-pcf50633-usb-curlim-workqueue-migration.patch
pcf50633 needs to take responsibility for managing current limit
changes asycnhrnously, ie, from USB stack enumeration. It's a feature of
pcf50633 not mach-gta02.c, and we can do better with taking care about
keeping it from firing at a bad time in there too.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 8a2d04c222684e3278dd28d11f57a05fe0865183
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:12 2008 +0100
fix-pcf50633-use-i2c-bulk-autoincrement.patch
Simplify and speed up bulk sequential I2C actions in pcf50633
the time savings are pretty considerable and so is the simplification
Signed-off-by: Andy Green <andy at openmoko.com>
commit d22227eec7efd4b2f40e51ea3c3bc025299efc93
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:40:04 2008 +0100
fix-pcf50633-rtc-i2c-bulk-autoincrement-simplify.patch
More pcf50633 major time saving by using i2c bulk autoincrement. Code
reduction too by using array for time elements.
Signed-off-by: Andy Green <andy at openmoko.com>
commit ac949375c7ef5882e8d3ea4f4a165b2fce943f21
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:56 2008 +0100
fix-pcf50633-interrupt-work-enforce-wait-on-resume-completion.patch
Improve pcf50633 interrupt service scheduling to enforce only servicing
when resume action is completed
Signed-off-by: Andy Green <andy at openmoko.com>
commit b73e3db4efa3409bd3c559d848e71e1519960d07
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:48 2008 +0100
fix-glamo-mci-resume-dependency-on-pcf50633.patch
Glamo MCI has a resume order dependncy on pcf50633, it has to be able to
power the SD slot via it.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 8f4ffd81a902d5499228ce79fcf38c90df52f0e4
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:41 2008 +0100
fix-glamo-mci-power-setting-timeout-waiting-for-pcf50633.patch
Glamo MCI power setting stuff spins on pcf50633
but it won't hurt if it gives up after a second or
two instead of stalling the resume silently.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 2219855aa7835e082ec134fafd9ddba84589d345
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:33 2008 +0100
ASoC: Don't block system resume
On OpenMoko soc-audio resume is taking 700ms of the whole resume time of
1.3s, dominated by writes to the codec over I2C. This patch shunts the
resume guts into a workqueue which then is done asynchronously.
The "card" is locked using the ALSA power state APIs as suggested by
Mark Brown.
[Added fix for race with resume to suspend and fixed a couple of nits
from checkpatch -- broonie.]
Signed-off-by: Andy Green <andy at openmoko.com>
Signed-off-by: Mark Brown <broonie at opensource.wolfsonmicro.com>
commit 5917872c144260bd6d74f35b6dadf0a98a53df07
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:25 2008 +0100
fix-jbt6k74-force-reset-suspend.patch
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 at openmoko.com>
commit ecb5c96f7da9b081efe3c731a0c7b052c2411536
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:17 2008 +0100
fix-glamo-mci-relationship-with-pcf50633-suspend-resume.patch
After protecting pcf50633 read and write primitives against
operation after suspend or before resume (by blowing a
stack_trace()) I saw glamo-mci was trying to use pcf50633
at these bad times on its own suspend and resume. Since that
part was already done via platform callback, I added an
export in pcf50633 that tells you if it is ready or busy,
and used it to defer (resume power on case) or ignore
(suspend power off case, since pcf50633 already did it)
the mci power call.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 83636af17dab41d313411543c57984b5834cfcf2
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:10 2008 +0100
fix-pcf50633-suspend-resume-onehit-i2c-other-meddling.patch
- speed up suspend and resume by using one hit i2c bulk transactions
- don't bother storing int mask set on suspend, the default one is
what we use anyway
- put stack_trace() on pcf50633 low level access that fire if we
try to touch them before we resumed
- cosmetic source cleanup
- reduces resume time for pcf50633 from 450ms to 255ms
Signed-off-by: Andy Green <andy at openmoko.com>
commit 79b99f7d65cce0730998a84d2fb615ae5ad0cff5
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:39:01 2008 +0100
debug-codec-register-setting-sysfs.patch
Allow direct setting of codec registers for super mega meddling power
Signed-off-by: Andy Green <andy at openmoko.com>
commit 50ea11a2a5397c72427a153a1327c6c433754df8
Author: Sean McNeil <sean at mcneil.com>
Date: Wed Jul 2 22:38:54 2008 +0100
The following is a minor cleanup of backlight resume:
commit b058131775abbc1ceedb5ad537014e4f9beed5ac
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Wed Jul 2 22:38:46 2008 +0100
Subject: [PATCH] Hardware glamo-fb cursor, some clean-up.
commit 727d8f48ab606e44af8afee03b87f0cfdc1f8bf5
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Wed Jul 2 22:38:36 2008 +0100
Subject: [PATCH] Build fixes.
commit e2a0bda68cf6f2511f6faabf922183c2454f84fa
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:38:26 2008 +0100
fix-remove-unused-model-name-bq27000.patch
Model name isn't in the bq27000 register set, remove the
claim that we can deliver it
Signed-off-by: Andy Green <andy at openmoko.com>
commit de64d8449b10dc39eebdee6bc01409cd0197e38a
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:38:15 2008 +0100
add-use-pcf50633-resume-callback-jbt6k74.patch
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 at openmoko.com>
commit bf63ca6b17328413611a9d7594ca2c2f710a1def
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:38:06 2008 +0100
introduce-pcf50633-resume-dependency-list.patch
Adds resume dependency support to pcf50633
Signed-off-by: Andy Green <andy at openmoko.com>
commit f07f917faa2f85625277f4d2f5294a630a6b0fb1
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:37:58 2008 +0100
introduce-resume-dependency.patch
Defines a way for drivers to defer execution of resume callbacks
until one or more other driver they are dependent on has itself
resumed.
Signed-off-by: Andy Green <andy at openmoko.com>
commit bf74b8891e80dfceb72002f12c7d3c9978631dc0
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:37:47 2008 +0100
introduce-charging-led-behaviour.patch
Creates a new behaviour requested by Will that the red LED on GTA02
is lit during battery charging.and goes out when the battery is full.
This is done by leveraging the PMU interrupts, but in one scenario
there is no interrupt that occurs, when the battery is replaced after
being removed with the USB power in all the while. So a sleepy work
function is started under those circumstances to watch for battery
reinsertion or USB cable pull.
100mA limit was not being observed under some conditions so this was
fixed and tested with a USB cable with D+/D- disconnected. 1A
charger behaviour was also tested.
Showing the charging action exposes some inconsistency in pcf50633
charging action. If your battery is nearly full, it will keep
charging it at decreasing current even after it thinks it is at
100% capacity for a long while. But if you pull that same battery
and re-insert it, the charger state machine in pcf50633 believe it is
full and won't charge it.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 1ccc3052a80284d3d7fbdfc0badadf6ae4236f79
Author: Andy Green <andy at opennoko.com>
Date: Wed Jul 2 22:37:38 2008 +0100
uplevel-samsung-camera-unit.patch
Update this old code to clk API, I2C changes, official GPIO API
various struct changes, explicit readl() writel(), DMA API changes.
Still not ready for actual use (eg, I2C) but a LOT closer.
Compiles on 2.6.24 without errors or warnings now.
Use CONFIG_S3C2440_CAMERA=y in .config
Signed-off-by: Andy Green <andy at openmoko.com>
commit 8602650d636b32c01fd11337dffc1df310f024e6
Author: SW.LEE <hitchcar at samsung.com>
Date: Wed Jul 2 22:36:46 2008 +0100
introduce-samsung-camera-unit-driver.patch
This is the kernel side of an old (2004) samsung camera driver for 2440
It doesn't compile on modern kernel yet, this patch introduces it into the
kernel tree without gross mods, so it is broken code we can start to work on
commit 2a48642ac0347c70f105997392f50b1ce8df45a3
Author: Andy Green <andy at openmoko.com>
Date: Wed Jul 2 22:36:10 2008 +0100
add-gta01-resume-sysfs.patch
Adds the somewhat simpler resume source support for GTA01
since PMU is not a wake source
Signed-off-by: Andy Green <andy at openmoko.com>
commit 9250c1fc7d6f62075d14ad8f396748490a55d61e
Author: Holger Freyther <zecke at openmoko.org>
Date: Thu Jun 19 22:13:31 2008 +0100
Subject: [PATCH] [a6k] Everyone calls SET_NET_DEV and hald needs that too,
make it happy
Call SET_NET_DEV to set a parent device. All other net drivers
are doing this and hald needs a parent to add the network device.
commit 421ed0bdd5b468d9de3ba571f49e7b840a8032e3
Author: No Attribution <dunno at dunno.org>
Date: Tue Jun 3 10:49:55 2008 +0100
Remove GTA01 PM debug
commit de09d927ffcba8c9fc77608f0e71f889287580a1
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue Jun 3 10:46:59 2008 +0100
Make ar6k not print soooo much to my console
From 4cb4c308fde9c1f3598046ff98191d14b62bc609 Mon Sep 17 00:00:00 2001
From: Holger Freyther <zecke at openmoko.org>
Date: Thu, 29 May 2008 00:09:32 +0200
Subject: [PATCH] [ar6k] silent++, removing -DDEBUG from the Makefile does not
work
commit 7d34adf0df1f105c73c6ecdee50a7ad6a6dbfd2b
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue Jun 3 10:46:48 2008 +0100
Fix possible null pointer dereference in s3c24xx_i2c_resume
From 0b9bae6aed5268707b348e48a01411ba420844e1 Mon Sep 17 00:00:00 2001
From: Holger Freyther <zecke at openmoko.org>
Date: Tue, 27 May 2008 14:41:35 +0200
Subject: [PATCH] [janitor] Fix possible null pointer dereference
Judging by the control flow of the resume method i2c->suspended++ could
lead to a null pointer dereference.
commit 57351c5a1f03e9ae884b094ddbde27b1ad6ed8e0
Author: Andy Green <andy at openmoko.com>
Date: Mon May 26 12:39:29 2008 +0100
fix-reduce-wake-reasons-in-pcf50633.patch
Currently we are willing to wake from sleep from
pcf50633 interrupts we don't actually do anything about
even when we wake (somewhat puzzled).
Let's disable some of these wake sources.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 595053e2185b896afe50af6bb48c082e3adcdd31
Author: Andy Green <andy at openmoko.com>
Date: Mon May 26 12:39:29 2008 +0100
add-resume-reason-sysfs.patch
If you have U-Boot with uboot-add-find-wake-reason.patch, this
patch will get you a wake reason report from
cat /sys/devices/platform/neo1973-resume.0/resume_reason
it looks like this:
EINT00_ACCEL1
EINT01_GSM
EINT02_BLUETOOTH
EINT03_DEBUGBRD
EINT04_JACK
EINT05_WLAN
EINT06_AUXKEY
EINT07_HOLDKEY
EINT08_ACCEL2
* EINT09_PMU
adpins
adprem
usbins
usbrem
rtcalarm
second
onkeyr
onkeyf
exton1r
exton1f
exton2r
exton2f
exton3r
exton3f
* batfull
chghalt
thlimon
thlimoff
usblimon
usblimoff
adcrdy
onkey1s
lowsys
lowbat
hightmp
autopwrfail
dwn1pwrfail
dwn2pwrfail
ledpwrfail
ledovp
ldo1pwrfail
ldo2pwrfail
ldo3pwrfail
ldo4pwrfail
ldo5pwrfail
ldo6pwrfail
hcidopwrfail
hcidoovl
EINT10_NULL
EINT11_NULL
EINT12_GLAMO
EINT13_NULL
EINT14_NULL
EINT15_NULL
This shows a problem, false wake from suspend due to battery full
Signed-off-by: Andy Green <andy at openmoko.com>
commit e93ec75e2a9c85e5a92af9e1b754fa711bd864b6
Author: Andy Green <agreen at localhost.localdomain>
Date: Thu May 15 21:47:56 2008 +0100
fix-motion-sensor-corruption.patch
commit 7b7d70785f1b3c1421d56ee8140578fea3b90f9c
Author: Holger Freyther <zecke at openmoko.org>
Date: Thu May 15 21:47:56 2008 +0100
Fixup hang on resume caused by the s3c2410 touch screen driver
From dc6d335b467646d802a21ea6b925ee97e83e07be Mon Sep 17 00:00:00 2001
From: Holger Freyther <zecke at openmoko.org>
Date: Thu, 15 May 2008 01:16:23 +0200
Subject: [PATCH] Do not use msleep in the resume path of s3c2410_ts as it
might lockup
For some reason msleep might set the only task running into a suspended
state and no timer will ever wake it up. Use mdelay to avoid this. I was not
able to understand the reasoning of sleeping after enabling the clock. So we
might just remove the msleep/mdelay at all and be fine.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 123f9e43f721a11e1b70c49b05cacb8f6edd7eaf
Author: Sean McNeil <sean at mcneil.com>
Date: Tue May 13 18:54:41 2008 +0100
minor problem with LCD
Looking at wrong register to see if the LCD is turned off?
commit e9beab2f041679bac20ac3d66ae7e8efe03fcf66
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:54:28 2008 +0100
clean-remove-build-noise.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 6b346561de958cd995c920d998bc6429bff39ce8
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue May 13 18:54:13 2008 +0100
Disable low level debugging, make the s3c24xx PM debug code depend on DEBUG_LL
Hey,
where are slowly getting into the product state, low level debugging is
supposed to be turned off there. :)
z
From 6448f0a521c05c5ba6672f5908c55583974ce1ed Mon Sep 17 00:00:00 2001
From: Holger Freyther <zecke at openmoko.org>
Date: Fri, 9 May 2008 19:56:31 +0200
Subject: [PATCH] [debug] Disable low level debugging for the product
Disable low level debugging in the defconfig-gta02 and
the s3c pm code used printascii which is only available
with low level debugging, update the Kconfig entry for
this pm debugging support to depend on low level debugging
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 368be2e8a4290da9e49c5625ed207885d345cfcf
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue May 13 18:53:40 2008 +0100
[power] Use the bq27000 battery to provide charging values for apm
Built the apm emulation for gta02 and say that the gta02 battery
is supposed to be used for this apm emulation.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 946aaea37e36e9f9fe16981a0f20f5f545fcd3b4
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue May 13 18:53:40 2008 +0100
[pcf50633] Disable debugging statements as the driver is working well
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 32d41ab91e5844ad6df1eea353c61a8fefc0c81e
Author: Holger Freyther <ich at tamarin.(none)>
Date: Tue May 13 18:53:40 2008 +0100
[pcf50633] Assume that all gta02's have a battery with coulumb counter
For the gta02 and the bq27000 battery it does not make sense to use the
ADC to get the current voltage. Under the assumption that all mass
production gta02's have such batteries it does not make any sense to
forward this value to APM.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 555ac92637a4343511a38cd4ff70d1aab6284d60
Author: Holger Freyther <ich at tamarin.(none)>
Date: Tue May 13 18:53:40 2008 +0100
[pcf50633] Add exported symbol to the header file
Reading the battery volt using the ADC was an exported symbol
but not in the header file, add it.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 0a6457836918f0aba88f861b7be65bfb883e6780
Author: Holger Freyther <ich at tamarin.(none)>
Date: Tue May 13 18:53:40 2008 +0100
[pcf50633] Print less debugging messages
According to the comments in the code we have to read
INT1 - INT5 in case of any interrupt. So even if we have masked
out the periodic timer interrupt we were able to see that it
fired. Only print that we got a SECOND interrupt if we are actually
interested in the periodic tick. From a brief look at the datasheet there
is no way to stop the periodic tick.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 88d3c5010a207c651d1940856d0d26935434e3c2
Author: Holger Freyther <ich at tamarin.(none)>
Date: Tue May 13 18:53:40 2008 +0100
Explain why we want SECOND to kick.
We do not mask the SECOND interrupt to make sure that we get
a interrupt at the beginning. We use this for the coldplug_done
initisalisation.
So pcf->flags and INT1M is out of sync at the beginning but after the
first SECOND interrupt it will be put into sync.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 624dadf2c300d9e5e439c07e1244babcef2fedca
Author: Holger Freyther <zecke at openmoko.org>
Date: Tue May 13 18:53:40 2008 +0100
Re: [PATCH 6/7] fix-suppress-cpu-suspend-save-restore-messages.patch
Andy Green <andy at ...> writes:
I kind of dislike commenting out code. Is this any better?
commit c9d44c8b43d29dd500c1dd711e490bdcd47f2830
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:53:40 2008 +0100
fix-backlight-disable-on-zero-intensity.patch
It's never right to put 0 intensity into LEDOUT according to datasheet
But having a floor at intensity 2 means backlight isn't properly off
when "dimmed". So change to intensity 0 --> disable backlight.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 56ba558ac343476a19a360fe139a6896bfc0b9e3
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:53:39 2008 +0100
add-force-backlight-up-on-resume.patch
The backlight status is restored during resume action, if it was
off then it resumes like that.
This patch forces it on after resume.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 782e7e4ec713c4f3bde792b5dd26b720f1383aa3
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:53:39 2008 +0100
quench-glamofb-err-lock-and-mmc-debug.patch
Remove debugging noise
Signed-off-by: Andy Green <andy at openmoko.com>
commit dcb5fd2c195981557237e3f91598a6b19f7fe929
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:53:39 2008 +0100
fix-suspend-backlight-timing-pm-debug.patch
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 at openmoko.com>
commit 45366d2500116c0b745a5b97f20a15c624eedf11
Author: Andy Green <andy at openmoko.com>
Date: Tue May 13 18:53:39 2008 +0100
config-add-back-MMC_UNSAFE_RESUME.patch
After LL debug disable, "unsafe" resume allows resume from SD card
rootfs without corruption, WAH
Signed-off-by: Andy Green <andy at openmoko.com>
commit ada5962807036b786fee00fd4462009c179181b6
Author: Sean McNeil <sean at mcneil.com>
Date: Tue May 13 10:54:45 2008 +0100
fix-wep-needs-keys-before-ap.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 966a29020932751ba6a1a137b0e1e25ac0708be7
Author: matt_hsu <matt_hsu at openmoko.org>
Date: Thu May 8 10:23:07 2008 +0100
s3c24xx-pwm-platform-driver.patch
This patch is to register pwm as platform driver to keep the PWM-related
config when system is in suspend/resume. This could fix the following
issue after resume:
- HDQ read timeout
- LEDs blinked abnormally(if LEDs is driven by PWM)
Signed-off-by: Matt Hsu <matt_hsu at openmoko.org>
commit bb7abab607e71a3cc1e8a4ebfa7619d872827353
Author: Sean McNeil <sean at mcneil.com>
Date: Thu May 8 09:24:45 2008 +0100
fix-KEY_PHONE-up-down-inversion.patch
the KEY_PHONE is backwards. It returns up when pushed and down when
released. The following change fixes it:
Signed-off-by: Sean McNeil <sean at mcneil.com>
commit 32a457c1616086e434bab03c24920ff6bd39e15a
Author: Mike Westerhof <mwester at dls.net>
Date: Wed Apr 30 14:50:12 2008 +0100
Stop GTA01 MMC Debugging messages
Signed-off-by: Mike Westerhof <mwester at dls.net>
commit 401eb535cb94e53ba4ff1a04caafe96b7d4d1981
Author: Andy Green <agreen at localhost.localdomain>
Date: Wed Apr 30 13:34:14 2008 +0100
clean-sdio-hcd-suspend.patch
fix trailing whitespace and function args for suspend.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 463f236121c752e434de713f6b141ed885c5fc5b
Author: Matt Hsu <matt_hsu at openmoko.org>
Date: Wed Apr 30 13:33:58 2008 +0100
From cc08b5986dfd8d971ee46ce7045fb7863f99a92a Mon Sep 17 00:00:00 2001
Subject: [PATCH] - add suspend/resume function of s3c24xx_hcd driver
Signed-off-by: Matt Hsu <matt_hsu at openmoko.org>
commit 1796e3d226fd1b119b09130478c781e25b7f5770
Author: Tim Niemeyer <reddog at mastersword.de>
Date: Mon Apr 21 21:09:37 2008 +0100
This-adds-some-debug-messages-to-the-Neo1937-sound-d.patch
Subject: [PATCH] This adds some debug messages to the Neo1937 sound driver.
Signed-off-by: Tim Niemeyer <reddog at mastersword.de>
commit b22975802d893a8cc600757436d5dd4dcd5cf469
Author: Tim Niemeyer <reddog at mastersword.de>
Date: Mon Apr 21 21:08:40 2008 +0100
This-fixes-the-exit-function-so-that-the-module-can.patch
Subject: [PATCH] This fixes the exit function, so that the module can be removed.
Signed-off-by: Tim Niemeyer <reddog at mastersword.de>
commit 5ccaca2adb1c37b5955a4733f68ae08a755e3d78
Author: Mike Westerhof <mwester at dls.net>
Date: Wed Apr 16 20:51:31 2008 +0100
gta01-gps-power-state-resume-preserve.patch
Created an attachment (id=593) / from BZ#79
Updated patch to preserve the power state of the GPS on the GTA01
Currently the GPS is powered up after a suspend/resume occurs. This patch will
only power the GPS back up if it was powered up when the GTA01 suspended.
Signed-off-by: Mike Westerhof <mwester at dls.net>
commit 0e45ee0b0c6b165d0ceb60a30e2f3a83e9273c6f
Author: Reddog <reddog at mastersword.de>
Date: Wed Apr 16 20:51:25 2008 +0100
gta01-fix-resume-redo-par.patch
--> (http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=595&action=view)
fix resume of fbdev BZ#79
I played a bit with the fbdev resume. With this patch the neo doesn't get this
white screen on resume from console and from X.
Signed-off-by: Reddog <reddog at mastersword.de>
commit 64ec7be81097f2c02ecffadbb2eef22ccf4c7e7b
Author: Mike Westerhof <mwester at dls.net>
Date: Wed Apr 16 20:51:17 2008 +0100
gta01-fix-jbt-platform-missing-members.patch
Created an attachment (id=594) / BZ#79
Add missing platform_data that caused the GTA01 to crash on suspend/resume
The interface to the jbt6k74 driver changed slightly; this patch adds the
missing platform_data for the GTA01. This prevents a crash while suspending.
This patch also makes some minor changes to cleanup and clarify some debug
messages.
Signed-off-by: Mike Westerhof <mwester at dls.net>
commit f54af99850ae25da80e491b1864bb90e14c80b1f
Author: Mike Wester <mwester at dis.net>
Date: Sun Apr 13 07:25:59 2008 +0100
fix-gta01-pmu-irq-edge-lost-on-resume.patch
GTA01 -only
Restore power button functionality after resume operation
Per Werner's suggestion, run the PMU interrupt handler immediately after resume
to clear/handle any pending interrupts from that device. This appears to
resolve the dead-powerbutton-after-resume problem. This is not well-tested;
need feedback to see if there are any side-effects or other problems.
From BZ 1313
Signed-off-by: Mike Wester <mwester at dis.net>
commit 4c445577b8f471612389007e5265c7dbfb2c487b
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:59 2008 +0100
fix-jack-interrupt-debounce-loss-window.patch
Make sure we can't lose a jack interrupt in debounce, despite it is
a one-in-a-million thing that just needs replug to clear
Signed-off-by: Andy Green <andy at openmoko.com>
commit eb020c73e01bc31c9ae8500fa07ecfafcd35d2c8
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:58 2008 +0100
[neo] Every access to GPIO bank B has to go through the shadow code
- Any setting of any PIN on bank B will undo the LED setting.
Introduce neo1973_gpb_set_pin to set the PIN in a way not losing
the LED or any other shadowed setting.
- Update users of GPBXY for gta01 and gta02.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 3beacb9939b07b974a9150a0a5848e0fbdb07df9
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:58 2008 +0100
[neo bluetooth] GTA01_GPIO_MODEM_RST != GTA02_GPIO_MODEM_RST
The bluetooth enable and modem reset switched the order in
gta02. Do not poke the bluetooth dongle when we want to reset
the modem.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 218ecc6801019388f1856547875635bfbb671342
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:58 2008 +0100
[led] Misc fixes in the driver code
to_bundle returned the wrong data. The platform_device is the
parent of the class_device used by the LED device class. Return
the correct class.
num_leds was not set to the correct number of registered LEDs. All
loops using num_leds (e.g. module unloading) were not executed at
all.
On removal of the module disable all LEDs.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 5c701da7eb3f9fdd3d9cb410c6e1699f862277ea
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:57 2008 +0100
[leds] We would enable PWM for all four timers, disable it for all four as well
Currently we do not use the PWM code to drive the LEDS. We have enabled the PWM
for four timer sources but disable it only for three, fix that up.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit cab66f63cd7e36a576d3ae53fef466df4e3391d8
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:57 2008 +0100
Remove not needed #ifdef as machine_is_ is always defined.
If we build a kernel without gta01/gta02 the
machine_is_ macro will expand to (0) and the compiler will
optimize the if (0) {} away.
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit f8759e3c3b99e15d4b182e3240d0990590e6cc36
Author: Mike Wester <mwester at dis.net>
Date: Sun Apr 13 07:25:57 2008 +0100
fix-gta01-spi-resume-patch
Patch to register the SPI device and thus the save/resume for the display
This patch does *NOT* resolve this problem, but it does make things a bit
better. The SPI device name changed with 2.6.24, and the change was made for
the gta02 but never propagated to the gta01. With this change, you'll now see
the entries for the spi bus and the display controller in /sys; and the display
controller suspend/resume functions will be called.
(via BZ 79)
Signed-off-by: Mike Wester <mwester at dis.net>
commit f761294475ddac8ecb74b5ef6c7cb7b0e7f71e0b
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:57 2008 +0100
OpenMoko => Openmoko
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit 9a5d2d81c0bf5c8fe2ac58d267033876904ed925
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:57 2008 +0100
fix-jack-debounce.patch
Headphone jack detection is bouncy, it can trigger multiple interrupts
on insertion or removal. This patch adds a workqueue that waits out the
interrupt spew in 100ms units, and if it sees no more interrupts for 100ms
only then samples and reports the jack state. I was unable to get a bounce
after 20 or so tries after this.
Signed-off-by: Andy Green <andy at openmoko.com>
commit f2cf4e5f204e981a02a0edaccab4ca39f868ac0f
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:56 2008 +0100
fix-glamofb-cmd-mode-locking.patch
Glamo "cmd mode" is modal, but nothing took care about locking.
Also cmd mode was entered recursively in rotate_lcd().
Signed-off-by: Andy Green <andy at openmoko.com>
commit 2c96fcfe5037e1078c24f824a0c84050cf54532b
Author: Mike Wester <mwester at dis.net>
Date: Sun Apr 13 07:25:56 2008 +0100
fix-usb-ethernet-mwester.patch
This is a kernel bug affecting all platforms, introduced in some code cleanup in
2.6.23. Patch will be posted as soon as I test it.
NOTE: Do not submit upstream; this patch or something very similar is already
in process for 2.6.25.
commit e9c1588c44daa953240f7fedbf8100cf840414f5
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:56 2008 +0100
fix-glamofb-cmdqueue-timeout.patch
loglevl=9 can cause failure to init glamo-fb
problem seems to be too low timeout when text scrolling can
delay commandqueue going empty
Signed-off-by: Andy Green <andy at openmoko.com>
commit 1b5fe5baf3d57244221823402164bc6b016c0d5c
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:56 2008 +0100
add-modules-defconfig.patch
From: Andy Green <andy at openmoko.com>
Add in the svn "mostly modules" config and GTA01 / 02 split
Signed-off-by: Andy Green <andy at openmoko.com>
commit 129f349dc3ee75dfb0580436d82fd0d6633ba2c4
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:55 2008 +0100
fix-gsm-download-irq-balance-issue.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5d6f04132cb5bd8fa8f1c9c9c3dc337aeae18f4c
Author: Werner Almesberger <werner at openmoko.org>
Date: Sun Apr 13 07:25:55 2008 +0100
audio-tickless-timeout.patch
When we resume, we can end up in
sound/soc/s3c24xx/s3c24xx-i2s.c:s3c24xx_snd_lrsync
with the timer tick still disabled, and the LR signal never happening.
Thus, we loop forever.
The patch below changes the timeout mechanism to use udelay, which
doesn't need timer ticks.
Note that this code is in a module, so to get the fix, you have to
build the modules, and update them.
The kernel now resumes but does the ugly GSM modem ticking. I'll have
to find a good place to turn that one off ...
- Werner
---------------------------------- cut here -----------------------------------
- sound/soc/s3c24xx/s3c24xx-i2s.c (s3c24xx_snd_lrsync): in resume, we may
call s3c24xx_snd_lrsync with timer ticks disabled, thus jiffies never
change. Use udelay to avoid this problem.
commit 11264214bbe864fb6e55fe2ab988d6bd37f2f705
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:55 2008 +0100
defconfig-audio.patch
Add in some audio config needed
Signed-off-by: Andy Green <andy at openmoko.com>
commit e5b19d7219195af3496f3f3904e62d75d300156f
Author: Sameo <sameo at openedhand.com>
Date: Sun Apr 13 07:25:55 2008 +0100
fix-wlan-disable.patch
see
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1288
commit d685e208663ffc9bd454af6698cb2945e60a3ba8
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:55 2008 +0100
Enable GPS only if it was powered on before suspending the device
Similar to the neo1974_pm_gsm.c keep a static struct around. On suspend
we will save the current power state, on resume we will use this
information to enable power of the GPS only when it was powered on before.
This is passing basic tests with screen /dev/ttySAC1 on suspend and resume.
Only do this for the GTA02 as I don't have a gllin setup for the GTA01
I wonder why the suspend and resume code is not using gps_pwron_set and why
for the GTA02 we need to keep the state of the GPIOs, this should be done
by the s3c code.
Signed-Off-by: Holger Frether <zecke at openmoko.org>
commit d6c8d6b85864edd5bb616f9fda0d2e9c1f74de42
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:54 2008 +0100
Fix the firing of "Jack"-Interrupts after resume when the modem is powered on.
GTA02_GPIO_nDL_GSM defaults to high/1. On resume do not enable the DL_GSM if
it was not enabled before. This is stopping the storm of interrupts.
Fix the logic in the download file handling. Downloads are disabled (0) when
the GTA02_GPIO_nDL_GSM is high (1). To enable downloading set
GTA02_GPIO_nDL_GSM to low (0, !on). Disable the jack interrupt while download
the is active. When disabling download we will get a couple of jack interrupts
but this is hardly avoidable.
Avoid reading the GPIO value if we do not even have a console set.
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 69998884e413697ea6b57a1deedb7ca5fde520ac
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:54 2008 +0100
Fix spelling. flaoting => floating
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit ba854ad9250eca9dc665507f0a4a80cbc6449ff5
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:54 2008 +0100
This is gta02 and not gta01. Do not call the vibrator led.
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 5134afd82f568f1eae133069bc9298e731546bc1
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:54 2008 +0100
Add GPIO -> IRQ for the s3c2410 and add irq_to_gpio to the gpio.h of the Samsung SoC
Use this irq_to_gpio in the neo1973 keyboard driver
commit 382b211cbde80703444333900dbdc0cf63d3ffab
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:54 2008 +0100
Convert the driver to the generic GPIO framework
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 897d69be643b8a8616b1c912444993a54f095917
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:53 2008 +0100
Fix the FIXME, store the GPIO value for now
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 9f60f7625fe32037c9ce6467737cb510666b5a7a
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:53 2008 +0100
Remove dead code
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit d5964d963a8b486d3b78fd4a135ee400bbf93bd1
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:52 2008 +0100
Simplify the code, there is no need for a branch. The code for
GTA01_GPIO_AUX_KEY looks odd.
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit b20fa9e7d54d8dfc40be78ccb4c5bafdfaf2ad15
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:52 2008 +0100
add-pcb-rev-sysfs.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit dda4110e4b365da5a520e8c2e3964d556206881d
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:52 2008 +0100
debug-glamo-dump-regs.patch
From: Andy Green <andy at openmoko.com>
Sigend-off-by: Andy Green <andy at openmoko.com>
commit b8d251412bc4c420f33920c2d9492076fc7b9624
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:52 2008 +0100
add-gta02-pcb-revision-detect.patch
Add function
int gta02_get_pcb_revision(void)
which returns state of GTA02 PCB revision pins. It is also called
and logged during boot with KERN_INFO. The results look like:
b9 b8 b2 b1 b0
GPD4 GPD3 GPD0 GPC15 GPC13
GTA02 A5 and before: 0x000
GTA02 A6 : 0x001
Signed-off-by: Andy Green <andy at openmoko.com>
commit a178e6a9426d258926af1ef86108648a0a47b808
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:52 2008 +0100
Do not send low level debugging to the modem
Hey,
I see no reason to send LL debugging messages to the modem. This can happen if
we compile the Samsung SoC with PM debugging as in andy's git branch.
From 452c17990dfeb9c2eb2ffa7ded4d24ddb1bcd4b2 Mon Sep 17 00:00:00 2001
From: Holger Freyther <zecke at openmoko.org>
Date: Sun, 23 Mar 2008 00:57:28 +0100
Subject: [PATCH] Never ever send debug messages to the modem. The serial
console is
on UART2, send the messages for decompressing and low level debugging
there.
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 0df922c0e1c6cdbfb8b2d2d0f7b474d09d121510
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:51 2008 +0100
fix-suspend-gps-tx-level.patch
We used to drive output high into GPS unit in suspend
Signed-off-by: Andy Green <andy at openmoko.com>
commit b1f47a12474fdb7c00e2234a8a02a7e1a2031a1e
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:51 2008 +0100
fix-lis302dl-suspend-gpio.patch
Add platform stuff to deal with going in and out of suspend
so the motion sensor IO is not driving high into unpowered sensors
Signed-off-by: Andy Green <andy at openmoko.com>
commit 24df87afae6f246622251b8d6f326493bcc206bd
Author: Holger Hans Peter Freyther <zecke at openmoko.org>
Date: Sun Apr 13 07:25:51 2008 +0100
add-pcf50633-06-RTC_AIE-ioctl
Hey,
the legacy application 'atd' from Russ Nelson/Nils Faerber, used by Qtopia, to
schedule alarms currently fails to start as the the above ioctl is failing.
The other drivers in drivers/rtc implement the above ioctl and we can
implement it too.
The code to mask/unmask the RTC alarm is copied from the set_alarm routine and
adapted to use the reg_set_bit_mask and reg_set_clear_mask.
It is compiling, so it must work. Please welcome me the lkml way ;)
Signed-Off-by: Holger Hans Peter Freyther <zecke at openmoko.org>
commit b32caff43b040be34c206962402e881e4235c5a9
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:51 2008 +0100
fix-charging-deassert-host-power-1a-detect.patch
We don't take care to stop driving generated USB host power even
when we have a 1A charger connected on the same pins.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 20369a802d4df104489daeb85388554f79e7e281
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:51 2008 +0100
introduce-usb-host-power-control.patch
Unless I really really missed the point, there is no support for enabling
USB Host power for USB host mode. This patch adds a /sys node for GTA02
that allows control of the charge pump for 5V out on the USB mini connector
It doesn't change any logical mode in the CPU, just enables (1) and disables
(0) USB host power.
# cat /sys/devices/platform/neo1973-pm-host.0/hostmode
0
# echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode
Signed-off-by: Andy Green <andy at openmoko.com>
commit 565f2987435711c4ac154e7cc12a03eedce2bfdb
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:50 2008 +0100
fix-gpio-led-patch-still-pwm-t3.patch
Starting up all the PWMs seems to be needed for PWM3 operation
and FIQ / HDQ / VIB operation. But after starting, turn the
LEDs to GPIO-only.
Applies on top of Willie's patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit a320183ac1d4bd8a430ef9f3e3b957ed4177454b
Author: Willie <willie_chen at openmoko.com>
Date: Sun Apr 13 07:25:50 2008 +0100
use gpio control leds
commit a8ee32310d3ed6fe66e639314ccae72d2fbbc886
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:50 2008 +0100
fix-glamo-mci-fake-reset-opcode-in-suspend.patch
commit bcf06c774c2c55fbd05b74ea01f1a2a6b3de2dc7
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:50 2008 +0100
fix-lcm-reinit-post-resume.patch
commit 99fbe6e31e09c9000668b50a87b3bbb834a145d0
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:50 2008 +0100
fix-glamo-mci-defeat-ops-during-suspend.patch
We need to be able to use the config option CONFIG_MMC_UNSAFE_RESUME that allows the rootfs
to live on SD. But when we use this, it tries to send a reset command to the SD card during
suspend -- and unfortunately many things like Power have suspended by then.
This patch again rejects IO on the MMC device during suspend of the MMC device, and it
gives the result the rootfs on SD card works okay.
Signed-off-by: Andy Green <andy at openmoko.com>
commit f5cedbb7cda510235de0783fea77ad8e028d1002
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:49 2008 +0100
config-add-alsa.patch
commit 6ce7c9b239314f4ee9f86164da8aaf5f78c0d1f1
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:49 2008 +0100
fix-s3c2410_timer_setup-resume-BUG.patch
commit 475826b7d7ef66e80b64d97ea9e8aca56d97e313
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:49 2008 +0100
debug-suspend-dump-gpio-states-add-GPA.patch
Add support for GPA[] GPIO bus since we have some NCs
but they seem to output-only IO cells so no matter
Signed-off-by: Andy Green <andy at openmoko.com>
commit 7b70de51df68659d3789481cf2446f8bc01e5387
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:48 2008 +0100
introduce-bq27000-battery-driver.patch
This is a driver for the bq27000 found in the Highcell A5
battery, and the platform device stuff for it for GTA02. It
is a Power Supply Class battery device.
The driver doesn't contain an HDQ engine but accepts pointers
from the platform data to the HDQ action routines; our
platform data plugs it into the FIQ HDQ engine stuff.
The Power Supply class exposes the battery down /sys so you
can find out battery status by doing the equivalent of this
bash command
for i in capacity charge_full current_now present status technology temp time_to_empty_now time_to_full_now type voltage_now ; do echo -n "$i " ; cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/$i ; done
Here is the kind of result you get from a battery discharging
capacity 0
charge_full 1215585
current_now 183375
present 1
status Discharging
technology Li-ion
temp 276
time_to_empty_now 0
time_to_full_now 3932100
type Battery
voltage_now 2761000
Note that temp is in 1/10 degrees C, other values are in uV,
uA, uW. The time_to_* reported are bogus, but that is what
the battery actually reports.
We can make more mappings to entries in power_supply class
but this is enough to get started with.
Signed-off-by: Andy Green <andy at openmoko.com>
commit ab6e925546e3d3361ab59c2b090eccf0cb411c7b
Author: Andy Green <andy at openmoko.com>
Date: Sun Apr 13 07:25:48 2008 +0100
introduce-fiq-hdq.patch
This adds a platform driver and device which performs HDQ
battery protocol using a single GPIO pin which is set
through platform data.
HDQ has some hard latency requirements which can't
be met if interrupts are enabled, so normally using
a GPIO for this will require blocking out all other
interrupts and processes for several milliseconds
per register being read or written.
This HDQ protocol engine is a FSM implemented inside the
the FIQ ISR and regulated by timer interrupts happening
at 20us intervals. The path through the FSM on any
"clock" is very short and should be over with in ~
1us. Because FIQ has guaranteed latencies of <1us,
it means we can service the HDQ protocol without
blocking interrupts or any other process other than
the caller that is waiting for the result. It's pretty
cool performance from 1 GPIO ;-)
Due to it being hard to do locking from the FIQ ISR
the code simply sleeps 10ms or whatever the scheduler
gives it and checks if the transfer took place yet.
This platform driver doesn't have any knowledge about
the device it is talking to, it just knows it is a
HDQ device. It exports three functions for read, write
and confirming HDQ is initialized. It also exports two
/sys nodes that are usable by humans, one dumps the whole
127 register HDQ register space
# cat /sys/devices/platform/gta02-hdq.0/hdq/dump
00 44 55 00 00 00 ba 04 a2 0d 50 00 00 00 00 00
00 00 9a 1a 00 00 ff ff ff ff 29 00 00 00 80 2b
00 00 00 00 00 00 ff ff 00 00 00 00 00 32 af 06
a0 d8 37 4e 00 00 00 00 00 00 00 34 2e 03 b4 e7
00 00 06 00 41 00 4c 02 00 00 00 00 00 00 00 00
83 02 00 00 94 09 59 b9 a5 0d 7f 21 00 00 7a ff
df ff 62 ff a7 04 2e 05 00 00 00 01 00 07 00 00
2a 78 36 67 7b b5 1b a9 af 19 38 89 63 57 42 7c
#
and the other allows to set one register
# echo 2 170 > /sys/devices/platform/gta02-hdq.0/hdq/write
writes 0xAA into register 2.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 41b2c45d068da0467272ca843e05a13f0e262be6
Author: warmcat <andy at openmoko.com>
Date: Sun Apr 13 07:25:47 2008 +0100
clean-snip-gpio-reinit.patch
These are initialized already
Signed-off-by: Andy Green <andy at openmoko.com>
commit e05285e4b6a3fa1134d40e91c5a345392e7efba0
Author: warmcat <andy at openmoko.com>
Date: Sun Apr 13 07:25:47 2008 +0100
bugfix-deglitch-gpio-output-enable.patch
commit 293025ae0e971da194ecb58be304835f246b6c9e
Author: Mike Montour <mail at mmontour.net>
Date: Sun Apr 13 07:25:47 2008 +0100
contrib-fix-chgstate-array-bloat.patch
--- linux-2.6.22/drivers/i2c/chips/pcf50606.c.orig 2008-01-17 22:30:16.000000000 -0800
+++ linux-2.6.22/drivers/i2c/chips/pcf50606.c 2008-01-17 22:31:43.000000000 -0800
@@ -71,12 +71,19 @@
I2C_CLIENT_INSMOD_1(pcf50606);
-#define PCF50606_F_CHG_FAST 0x00000001 /* Charger Fast allowed */
-#define PCF50606_F_CHG_PRESENT 0x00000002 /* Charger present */
-#define PCF50606_F_CHG_FOK 0x00000004 /* Fast OK for battery */
-#define PCF50606_F_CHG_ERR 0x00000008 /* Charger Error */
-#define PCF50606_F_CHG_PROT 0x00000010 /* Charger Protection */
-#define PCF50606_F_CHG_READY 0x00000020 /* Charging completed */
+#define PCF50606_B_CHG_FAST 0 /* Charger Fast allowed */
+#define PCF50606_B_CHG_PRESENT 1 /* Charger present */
+#define PCF50606_B_CHG_FOK 2 /* Fast OK for battery */
+#define PCF50606_B_CHG_ERR 3 /* Charger Error */
+#define PCF50606_B_CHG_PROT 4 /* Charger Protection */
+#define PCF50606_B_CHG_READY 5 /* Charging completed */
+
+#define PCF50606_F_CHG_FAST (1<<PCF50606_B_CHG_FAST) /* Charger Fast allowed */
+#define PCF50606_F_CHG_PRESENT (1<<PCF50606_B_CHG_PRESENT) /* Charger present */
+#define PCF50606_F_CHG_FOK (1<<PCF50606_B_CHG_FOK) /* Fast OK for battery */
+#define PCF50606_F_CHG_ERR (1<<PCF50606_B_CHG_ERR) /* Charger Error */
+#define PCF50606_F_CHG_PROT (1<<PCF50606_B_CHG_PROT) /* Charger Protection */
+#define PCF50606_F_CHG_READY (1<<PCF50606_B_CHG_READY) /* Charging completed */
#define PCF50606_F_CHG_MASK 0x000000fc
#define PCF50606_F_PWR_PRESSED 0x00000100
@@ -1026,12 +1033,12 @@
static DEVICE_ATTR(chgmode, S_IRUGO | S_IWUSR, show_chgmode, set_chgmode);
static const char *chgstate_names[] = {
- [PCF50606_F_CHG_FAST] = "fast_enabled",
- [PCF50606_F_CHG_PRESENT] = "present",
- [PCF50606_F_CHG_FOK] = "fast_ok",
- [PCF50606_F_CHG_ERR] = "error",
- [PCF50606_F_CHG_PROT] = "protection",
- [PCF50606_F_CHG_READY] = "ready",
+ [PCF50606_B_CHG_FAST] = "fast_enabled",
+ [PCF50606_B_CHG_PRESENT] = "present",
+ [PCF50606_B_CHG_FOK] = "fast_ok",
+ [PCF50606_B_CHG_ERR] = "error",
+ [PCF50606_B_CHG_PROT] = "protection",
+ [PCF50606_B_CHG_READY] = "ready",
};
static ssize_t show_chgstate(struct device *dev, struct device_attribute *attr,
commit 9f90b78f834e3d18520c03af4644ff239a2e891b
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:46 2008 +0100
local-config-ext2.patch
commit 5c6c019690dac8b5f8d76732c8fd387ff7a27f2d
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:46 2008 +0100
local-config-pmu.patch
commit b0eec76126c38ed02f0af80ebf65801d46e6e261
Author: warmcat <andy at openmoko.com>
Date: Sun Apr 13 07:25:46 2008 +0100
local-config-defconfig-motion-sensor-gpio.patch
commit e1f4e75f4f146f534f659f2c9cf525387d4d734a
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:46 2008 +0100
local-config-wlan-config-changes.patch
commit 7eb5d3249a17af091630b6fa8392ed1e268962f6
Author: warmcat <andy at openmoko.com>
Date: Sun Apr 13 07:25:45 2008 +0100
local-config-add-bluetooth-monolithic.patch
Add Bluetooth in monolithic kernel
commit fb75c4b67418f06a86a1a8f07614c618e496bc14
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:45 2008 +0100
local-config-add-vfat-nls-to-kern.patch
SD Card / VFAT in monolithic kernel
Signed-off-by: Andy Green <andy at openmoko.com>
commit d7f185674ade4b1a152c1cc142d07d47f13ce9cd
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:45 2008 +0100
local-update-defconfig-for-2.6-dev.patch
Make a defconfig for 2.6.24 out of the current 2.6.22.5 one
From: warmcat <andy at warmcat.com>
commit 2f8f225597218a1b838f70dc8f7d9216c40cd4c0
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:44 2008 +0100
local-build-new-dfu-vid.patch
Update to new DFU VID for A5
Signed-off-by: Andy Green <andy at openmoko.com>
commit 3801eb47f3ce58d2f8b64089ab01d85edf19f441
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:44 2008 +0100
local-build-scripts.patch
Add a couple of handy scripts to crossmake and send over dfu
From: warmcat <andy at warmcat.com>
commit b58c89ed206269de1116a7b3f98f07bad902a566
Author: warmcat <andy at warmcat.com>
Date: Sun Apr 13 07:25:44 2008 +0100
local-add-defconfig.patch
Adds svn defconfig
From: warmcat <andy at warmcat.com>