development kernel tree: Changes to 'stable-tracking'
git at git.openmoko.org
git at git.openmoko.org
Sun Aug 3 22:00:28 CEST 2008
New branch 'stable-tracking' available with the following commits:
commit 851834ed52da8c60826a76db2ab36c95e6b0feaf
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:57:23 2008 +0100
remove-s3c24xx-serial-resume-dep-gsm-pm.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit a7839954acb31e2cd93cd8d616f09f88a2c3f382
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:57:03 2008 +0100
tracking-2.6.27-rc1-snd_soc_dapm_sync_endpoints.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit d5ac1b8d6c0f831203720bec3e09bc28a2ccb254
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:38:57 2008 +0100
tracking-2.6.27-rc1-snd_soc_dapm_set_endpoint.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 7c733627ccf53b336d2eec80af4350bcca94b520
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:38:55 2008 +0100
tracking-2.6.27-rc1-broken-cfg-uninit-nand.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit b6741dc3d1493b3c5238241a2832edc78ef07356
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:06 2008 +0100
tracking-2.6.27-rc1-s3c_lookup_cpu-mismatch.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit ca8ab7babd0d4d2b9cb168e65f12a40e4613a332
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:06 2008 +0100
tracking-2.6.27-rc1-gpio-redef.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit d01e67992e4ccf2efd130b9ed1da7452a8f6f35b
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:05 2008 +0100
tracking-2.6.27-rc1-debug-section-mismatch-build.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit f1893aa198e2ad434705b0a3096899286b57878b
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:05 2008 +0100
tracking-2.6.27-rc1-ar6000.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit dc12b5c5b4255699aa262392896146dbf822212e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:05 2008 +0100
tracking-2.6.27-rc1-last-2400-ordering.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit a81e9bc70ee35867bb6418a2004eef89396956c8
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:05 2008 +0100
tracking-2.6.27-rc1-borked-eth-gadget.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5e3f12ef11bceedcfe7bc662f9471e6eae09ab55
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:05 2008 +0100
tracking-2.6.27-rc1-tty-not-in-uart_port.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 8c2b82d8ccd92ff76f8bae2d38f32c356f4b1cc0
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-rc1-asm-semaphore-gone.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit ecc44617e9bc82e0904bcd515b24cc874a679014
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-mmc-ultiwrite-gone.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 51d677ac27f40d82e34152c9d292a030c4ef353a
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-rc1-irqtype-falling-glamo.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 4926b94ce8874207d07d3ca541270b2f3fcec77f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
fix-backlight-def-pcf50633.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit bd4cce646f315b298dbcf64d8550e79fa71fb911
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-rc1-pcf50306-defs.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 3f87160aae277c8fddba6a4b8648dc9cfec88758
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-gpio-redef-clean.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 9a3631993ddaf986061c18090587e6235466c13c
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:04 2008 +0100
tracking-2.6.27-irqtype-rename.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 9a9340c5f0b3c6748f047db1d03a004b5374e7be
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:03 2008 +0100
config-add-defconfig-2.6.27
Signed-off-by: Andy Green <andy at openmoko.com>
commit 58d61e1350148af861324fa32f917428a701c98f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:03 2008 +0100
config-usb-over-ethernet-modul
Signed-off-by: Andy Green <andy at openmoko.com>
commit 187446cdab7d4501b0b716268274e02bea2cde2f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:03 2008 +0100
fix-add-missing-include.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit bb3182411d71f8f439a0a8f0d53ace93ec899d19
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:03 2008 +0100
use-gta02-glamo-mci-sd-dynamic-clock.patch
This patch uses the new glamo-mci slow clock ratio
patch in order to dynamically reduce SD Card clock
rate when the GPS unit is powered on GTA02.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 8af2116976aa19e1da345b9f24dc2dc8a3873ff9
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:03 2008 +0100
add-glamo-mci-slower-clocking-dynamic-switching.patch
This patch gives glamo-mci a concept of a platform-defined
dynamic clock slowing callback. It means that platform code
can associate some completely external state to decide if
we run the SD clock at normal rate or a rate divided by a
module parameter "sd_slow_ratio", which you can set on
kernel commandline like this:
glamo_mci.sd_slow_ratio=8
you can also change it at runtime by
echo 8 > /sys/module/glamo_mci/parameters/sd_slow_ratio
If no platform callback is defined, then no slow mode
is used. If it is defined, then the default division
action is / 8, eg, 16MHz normal -> 2MHz slow mode.
Signed-off-by: Andy Green <andy at openmoko.com>
commit e028a77b983770fb4157fc58879f0a612435cf1d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 2008 +0100
fix-glamo-mci-dont-filter-voltage-change.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit a6764e60abae97fa9fcea3c52fbfd90e8536d875
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 2008 +0100
fix-allow-full-sd-voltage-range-selection.patch
Until now we just drove the SD Card at 3.3V all the time. But in
fact we can do better, and use a voltage negotiated with the
SD Card itself.
With the shipping 512MB Sandisk SD Card, 2.7V is negotiated which
gives 1.7dBm reduction in power on all the SD Card lines and should
further reduce GPS perturbation during SD Card usage.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 9742a7c881d6862be370ade1c503676cb49a4ec9
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 2008 +0100
tracking-2.6.26-rc9-dai-alsa.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 678c04455be3795f74392b3453f4185b7c75d92f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 2008 +0100
fix-glamo-mci-ensure-more-than-74-clocks-after-power.patch
We are meant to run SD_CLK a little while after power-on for the SD
Card, but with the no idle clock changes we didn't take care about it.
This makes us sleep a little bit before disabling clock if we just
powered up the SD Card.
Signed-off-by: Andy Green <andy at openmoko.com>
commit b88cc632f6a477fe8effd544c26c9e7ea8b09e9b
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 2008 +0100
fix-glamo-mci-possible-timeout-overflow.patch
The MMC stack hands us a timeout calibrated in SD_CLK clocks, but the
Glamo can only deal with up to 65520 clocks of timeout. If the stack
handed us a request bigger than this, it would just wrap and the
timeout we actually used would be way too short.
With this patch if that happens, we use the longest timeout we can,
65520 clocks and give it our best shot.
Signed-off-by: Andy Green <andy at openmoko.com>
commit d15669f4e6439428316de81418798e6a16c8e250
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:02 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 9daf467481145ad2d3c23acb154414de4963aad1
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:01 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 ef13d13b74990ea866f97521c96d303c299d2047
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:01 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 447dc8f3ded1dbddc4b76af2c2040a3059e71950
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:01 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 70a2a166e61049f17060fdc3503d4ef0e4a86983
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:00 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 456a5f0880e8c99957a85be11489ce8706ea0675
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:00 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 4d78573b2a54a153d54acaf692ae058ed1b7f97a
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:00 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 98ce0248c258b7186c46a3c0cd75fb9ec30f4c2a
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:26:00 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 f0656b2470c7b9808dc13bb00037d2e1875c8030
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 a22a4b7ce565ebe28d9cf6a568bb0d6ce84ace4f
Author: Jason Uhlenkott <jasonuhl at jasonuhl.org>
Date: Sun Aug 3 20:25:59 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 977e7a53345b7849f4f584d5042813587175810d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 e3df0e199e5ee647178c8e81298afd1e97a137a4
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 db08c8cdcff92b0428ac325dfe7caa8687d923bb
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 3184328b2fa682d2c432a91972c68b82fc12a49d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 17ba988f4d70f38a3acb1aa251fce55ef5591c20
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:59 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 6a4741d29fd6eecb6cf576b8bb716e20526d6ab3
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:58 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 95941d5960fd10a7751e57fa5c494708e28d4ce1
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:58 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 ef1c7d7188bbe408c982ccd34384e55e7a564fa7
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:58 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 3f85c445fc807ddbdeba624e3adf9a03b036b3d7
Author: Mike Westerhof <mwester at dls.net>
Date: Sun Aug 3 20:25:58 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 6ee3400a2878355575c5f9b8e6fb4f18fee9f1d4
Author: Mike Westerhof <mwester at dls.net>
Date: Sun Aug 3 20:25:58 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 421b822adadbcb1596e64e091c9a2b83afa33f28
Author: Matt <matt_hsu at openmoko.org>
Date: Sun Aug 3 20:25:58 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 4cdda326089d9cb4b8ca144155a64a9a977628bb
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:58 2008 +0100
change-remove-kernel-charging-led-drive.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit d124d2628e40f0b24033a758bc4033344504d086
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:57 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 8b76e28dcccd01af1902b0da17e56bd32b2c2392
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:57 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 5fa234932638c53f002639f08992aa0cd0d4b171
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:57 2008 +0100
From 000450f1ad2c713d2345a872fdf44f5dd3702e1b Mon Sep 17 00:00:00 2001
Subject: [PATCH] [janitor] make checkpatch.pl happy
commit a045bbac825d6e73672ed294e8ed804b1519a47e
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:57 2008 +0100
From 683ef8067815f6ba0ede73fa71973823726213a3 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [janitor] Make checkpatch happy on the header files
commit 58f6035670ce52732429e88b6fa69f47cc0217de
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:57 2008 +0100
From ae3f72fc608fcd0a98a980a335ac4dc7ad95b221 Mon Sep 17 00:00:00 2001
Subject: [PATCH] [bq27000] Make the checkpatch.pl happy
commit 102e6f513f86a0b989ac4da8b3b9c689fccee7d2
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Sun Aug 3 20:25:57 2008 +0100
From 119f4e02ba81cffe4dbc88d8ff667048ad28d925 Mon Sep 17 00:00:00 2001
Subject: [PATCH] Hacky CONFIG_NO_IDLE_HZ (dyn-tick) support for S3C24xx.
commit 66954cb9ca437f50768a9aec3d5231bfbcf8ed73
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:57 2008 +0100
tracking-2.6.26-rc7-repeat-cdev-removal-pcf50633.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit ed844242536ebcfc94a47c0ae5580488d384c5f2
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:56 2008 +0100
tracking-defconfig-2.6.26-rc7.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5a1d30fb0e2626698c218d994583f4b62ffb300e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:56 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 8c5148dc98fb6f1a5cd2d074aeff221b34332dbf
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:56 2008 +0100
fix-gsm-resume-problems.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 034566bb81a07bfda60c85f0e0365f1714149a43
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:55 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 7399543886d0c45af7694a96115bdcbe1408bba0
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:55 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 9a296c63b92952cb51f3dafbc88ae2d9495080d7
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:55 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 7459e64fe6814bd9e98bc5507c341322b99e2f47
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:55 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 a667777ef24fd9df514a87654927668030b24863
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Sun Aug 3 20:25:54 2008 +0100
Subject: [PATCH] glamo: Don't disable hwcursor for blinking and use vsync-wait.
commit fdeba4cec12b92f4b1b951dab531783059927cac
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:54 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 f27a0e0f52eb55e9a7b08fca619e5315d78e956e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:54 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 c15fb32e35f23a83931d78627a216d1a3a8c9881
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:54 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 e2d1715afd55998ea28e5e240050bc83718579f3
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:54 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 ea26d103be980d1f2296b21ec474d3d6317bf62c
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:54 2008 +0100
fix-pcf50633-platform-backlight-resume-ramp-setting.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 006b17f799b5f468b76ff0830c021c9a4910f201
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:54 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 440ef0e6ff9090a77adae34bc68464eb2354267d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 dbc422c219968b8647475b21c01be5f699903972
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 2008 +0100
debug-backtrace-not-choke-on-null-dev_blah.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 4b9e43cabf55f077adfb77ee565dd910eb4077f4
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 68b5078c0d0fd09d5bcf14f8db858acce4a8faf3
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 1aacd36cc4121e848d79cef574f1acea3b6cca65
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 2008 +0100
debug-i2c-s3c2410-dump-stack-on-suspended-tranfer.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit f35caf2d2016bf4fc6d4fdc4c7c8d46cbfad3762
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 bc72f163abc9b535ecd2d84fb0dc5e7cc770c4b9
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 4a6bbb380e54f43fe8e2a4ddd9f5cd276df864ea
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:53 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 9ffe4209615ce53d534008043f2398102fc6b308
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 2008 +0100
fix-pcf50633-require-resume-level-3-for-irq-work.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 71c46b222c204d10ba992beaea87853966096c9f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 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 6f711ef047b5bfd7abd8636054286b99e5efec8e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 2008 +0100
fix-gta02-mach-remove-gta01-lcd-reset.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 0c6116f68fbcaf6ff98f0040b8f25fb6d0ab228d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 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 450615d5212716112295722a5f6cb06dad0e5b5d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 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 4fe5033b87562a28a65dc3a7a3d9613965094b8e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:52 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 59cedd3d6915cdc9707a101947841ac4a52379ed
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:51 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 d9922a319ab4ea97a1c867351048f69834f936e9
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:51 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 d3621b9c5b6724869352761b90a8b70ac1c98fef
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:51 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 d2c0fe213c4274ec0dceb10095a4103d2246a93d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:50 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 b967efa9a25a55b3a082d3384720511d646fd224
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:50 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 ba670f6a663c884bd45f80b8c00a583deded5762
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:50 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 eefd5359db61437469761d5fa47e7858d464b683
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:50 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 5af8126772c16a8d903712bbba294169572fa585
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:49 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 e6fb194fe8b8996581fec2a394c807ae5d85b4fe
Author: Sean McNeil <sean at mcneil.com>
Date: Sun Aug 3 20:25:49 2008 +0100
The following is a minor cleanup of backlight resume:
commit 13d58a9ea54ee946b9fb9c5df7713aef661d5f85
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:49 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 be980893b95fd1c1597883b59033174f9c34e275
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:49 2008 +0100
introduce-pcf50633-resume-dependency-list.patch
Adds resume dependency support to pcf50633
Signed-off-by: Andy Green <andy at openmoko.com>
commit 7632d2b49f3f34a565d3554a1ba4ca00a39f285f
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:49 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 2a2a969cdcf3ab4bc392ad3643d401417bb203cc
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:49 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 34d3bb31e3b39ade2f87ca015712622137896b7e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:48 2008 +0100
Subject: config-defconfig-2.6.26.patch
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=7f52bae9664cbf006fe026d4dbbd5988137bd1cc
config-defconfig-2.6.26.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 4b8c5ac33a0c810be9aad8bfd303ec1883d80e7b
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Sun Aug 3 20:25:48 2008 +0100
Subject: [PATCH] Hardware glamo-fb cursor, some clean-up.
commit 2bf8f0c5f2d52142b1b030132d572d5799a0f3f6
Author: Andrzej Zaborowski <balrog at zabor.org>
Date: Sun Aug 3 20:25:48 2008 +0100
Subject: [PATCH] Build fixes.
commit 2a7fddca3183729649c811f34bdb77eb75e97e4b
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:46 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 71b5ca137ab3d6e0e682f0db6031cc5debc6381b
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:46 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 a57f6a4194e1b40a484b7851fbe17fe17578de77
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:46 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 5e3ecb04e57997cb20a0ab9d46cab0d1700066bc
Author: Andy Green <andy at opennoko.com>
Date: Sun Aug 3 20:25:45 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 fa7655a0ea8bbd563b0003d6ebf710dc14eae972
Author: SW.LEE <hitchcar at samsung.com>
Date: Sun Aug 3 20:25:45 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 051625cd1b6680f0f8295f93e3411cf01ab6f332
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:45 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 38586858e9b602c454320cb13531fb9bb6137bc8
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:45 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 d5de536d868aa9bed183aca61082016319f27e6d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:44 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 b8b39d6ced4f7cb411793fceda5bac35c2c8f165
Author: Andy Green <agreen at localhost.localdomain>
Date: Sun Aug 3 20:25:44 2008 +0100
fix-motion-sensor-corruption.patch
commit 4f847d6ce4e59bffe324a8903533552956a4a6f8
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:44 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 70c4ac475e31df5919eecd887714d5f733737bf7
Author: Sean McNeil <sean at mcneil.com>
Date: Sun Aug 3 20:25:44 2008 +0100
fix-wep-needs-keys-before-ap.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 232c0ee79c3fd268e18b866c141a00b6c01c2006
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:44 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 1b5c7a68f452a613fd7f7fb02baec953c46fed7b
Author: matt_hsu <matt_hsu at openmoko.org>
Date: Sun Aug 3 20:25:44 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 2628658b187496917bf341201a255d6855acacc6
Author: Sean McNeil <sean at mcneil.com>
Date: Sun Aug 3 20:25:44 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 2f5026808b54c14c57abf5cba56ed5b741704d4e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:43 2008 +0100
tracking-2.6.26-rc1-sdio-pnp-changes.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 31ad52a8a936eaf8cfbde988f15ae969e642c519
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:43 2008 +0100
tracking-2.6.26-rc1-remove-dupe-s3c2410_nand_update_chip.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit f810c9ff739f2ed04da01f4ee74ace692d412c81
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:43 2008 +0100
tracking-2.6.26-rc1-remove-input-dev-private-member.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit f5929e66d5460b812a6d27d58cbf8e716b9d01be
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:43 2008 +0100
config-update-2.6.21-rc1.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 2ee3ee57d3ef1c565343f08454c91904bd823e3a
Author: Andy Green <agreen at localhost.localdomain>
Date: Sun Aug 3 20:25:43 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 81fcf0455b3a858da4c80b84f8a6dac43982998d
Author: Matt Hsu <matt_hsu at openmoko.org>
Date: Sun Aug 3 20:25:43 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 46c620ec64b3fd68bd0141f0ca94d09e737a0dd0
Author: Reddog <reddog at mastersword.de>
Date: Sun Aug 3 20:25:43 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 4908d613213b9ee9f84f46d04a73d65863abc343
Author: Mike Westerhof <mwester at dls.net>
Date: Sun Aug 3 20:25:42 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 73ae7b20c31654f9605cc602575e9d1d83c4d889
Author: Mike Westerhof <mwester at dls.net>
Date: Sun Aug 3 20:25:42 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 ab7873193b1fb6d1bfc4a217a16bddfd2057f8e2
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:42 2008 +0100
tracking-2.6.25-changed-s3c2410_dma_request-reurn.patch
s3c2410_dma_request used to return 0 for OK and something else
for error, now it returns -ve error code or +ve dma channel index + flag
Signed-off-by: Andy Green <andy at openmoko.com>
commit 58f9e997d388b197a96cb1827faf9d45d0496a34
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:42 2008 +0100
tracking-2.6.25-deprecated-includefile-wm8753.patch
<linux/driver.h> is just empty and is deprecated now
Signed-off-by: Andy Green <andy at openmoko.com>
commit 16657d6dde8ac3490a936b01d718a315bd8c655d
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:42 2008 +0100
tracking-2.6.25-upstream-s3c2410_gpio_irq2pin.patch
Holger got beaten to it on mainline, they provide a
s3c2410_gpio_irq2pin() instead of the name he used.
Signed-off-by: Andy Green <andy at openmoko.com>
commit d845c7aa52b0b7a4cf7bbb06f953e6f90a35c085
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:42 2008 +0100
tracking-2.6.25-struct-bus-type-loses-devices-member.patch
I don't know what device the symlink should be linked
against on GTA01, somebody that does know needs to edit
it in where it says "FIXME"... I think the supplied method
can work OK otherwise.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5c1fb373a612bea4ccf5c8dac75deb9955c32011
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:42 2008 +0100
tracking-2.6.25-input_dev-cdev-union-removed.patch
struct input_dev in include/linux/input.h used to have a union
cdev which contained the associated device struct pointer. This
got simplified out in 2.6.25, so this patch removes cdev from
our drivers that used it before.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 6e630a0cae412a9531bc3887a35ea7cb590748c7
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:41 2008 +0100
add-defconfig-2.6.25
mostly built-in defconfig for 2.6.25
Signed-off-by: Andy Green <andy at openmoko.com>
commit 5bfe662d59871e86bec33bdbe48e90aeaf223ecf
Author: Mike Wester <mwester at dis.net>
Date: Sun Aug 3 20:25:41 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 b6c9ce96e7747f5453f797e2a1102c5073762c9c
Author: Mike Wester <mwester at dis.net>
Date: Sun Aug 3 20:25:41 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 9f429287fb25a14b66787d396b762fbe93758f9c
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:40 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 b714d3a10149e285efa3bc3652fa8030f377aca4
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:40 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 b8e360d20c2ccef651bd8b1dd8b26f5364a58bbf
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:39 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 3dcb3f82c1193bf50dc5b357a76232928bd5fe52
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:39 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 4d0d40d7522558d925466ce8112638022834e476
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:39 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 ddc3f01a8f5c4a73291c9f0451191a0f2f630972
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:39 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 3af19c2b459c5dd046a8568321b4ede0dee50180
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:39 2008 +0100
OpenMoko => Openmoko
Signed-Off-By: Holger Freyther <zecke at openmoko.org>
commit f1c7b3f9c9b887f51517c8a4cb0734b874fca20a
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:39 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 90f49f9b15f258d261e606a478b4eed6c8014c54
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:39 2008 +0100
debug-glamo-add-lcd-regs-to-dump.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 05cfecbe4875e89fa5791e9c481518183e636c3a
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:38 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 c55169a7ae31566a79e00cfb5e579a199330768c
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:38 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 d615e51f981ca52ce69bf3a4d6ee8a2f5c735992
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:38 2008 +0100
fix-gsm-download-irq-balance-issue.patch
Only enable or disable the interrupt if we see we are in the opposing state.
Also force that damn GSM download signal deasserted on probe at the time we
set the logical state for it to deasserted.
Signed-off-by: Andy Green <andy at openmoko.com>
commit 288b35b6bae4d843784574a36a1a73092bcdbd82
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:38 2008 +0100
defconfig-audio.patch
Add in some audio config needed
Signed-off-by: Andy Green <andy at openmoko.com>
commit 236152e6a7db598cd701ff65e5fced10289aab15
Author: Sameo <sameo at openedhand.com>
Date: Sun Aug 3 20:25:38 2008 +0100
fix-wlan-disable.patch
see
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1288
commit 65bd3be71ca2647a88093881c949c35256748357
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:38 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 576c3ae69c6672c6ecda4d584550578d09ba7a4c
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:38 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 96f42941ecd06c572c3c8775ed5648aaa1a39836
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 2008 +0100
Fix spelling. flaoting => floating
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 6486b46f232e0054ef7477986c868e6979031b8f
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 2008 +0100
This is gta02 and not gta01. Do not call the vibrator led.
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 0256b9e41d1fbe4c53187db40d92c62b474281e3
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 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 b2f92717dccade5917bffb6d81e5755d1384eb37
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 2008 +0100
Convert the driver to the generic GPIO framework
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 51b735329b45d409f8315a10b0ec96556a00e0fb
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 2008 +0100
Fix the FIXME, store the GPIO value for now
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit 180ff20b27bbd6c0c69a3cfa31d5cd551b7f980c
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 2008 +0100
Remove dead code
Signed-Off-by: Holger Freyther <zecke at openmoko.org>
commit de427e2db647a3016dbb8d0b55f0e9b9e5206edd
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:37 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 817a4d45ffcdbca77e10f1f07d4f67035b23ed92
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:36 2008 +0100
add-pcb-rev-sysfs.patch
Signed-off-by: Andy Green <andy at openmoko.com>
commit 888091e5429598e844820c98905a55b11fd0067c
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:36 2008 +0100
debug-glamo-dump-regs.patch
From: Andy Green <andy at openmoko.com>
Sigend-off-by: Andy Green <andy at openmoko.com>
commit e592c0b245153bc3cedcdc9f3e14cccf4094c4b2
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:36 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 24d69458e1e6bad685a53e61997b5be4bb736f30
Author: Holger Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:36 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 571c015ee61515a001fa705bec21f54797aa7312
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:36 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 b44dc41158de69f63cdfc8cd9e55b685f8ec3fb3
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:35 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 2605fba3861b95a7ea4536155815171d84f6bb3b
Author: Holger Hans Peter Freyther <zecke at openmoko.org>
Date: Sun Aug 3 20:25:35 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 a49095f79bf0eb5b8279406cda9983888cd1ab61
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:35 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 29bb939d596502a071c836f251d4180f9e011557
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:34 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 7e8be5190ecaaa9832eaafeb03b568232e79b329
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:34 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 4285ed271d7a0ff05b32978142a2992499f5c90e
Author: Willie <willie_chen at openmoko.com>
Date: Sun Aug 3 20:25:34 2008 +0100
use gpio control leds
commit 687831c11125b9ecdc4114cde127e38878a80c40
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:34 2008 +0100
fix-glamo-mci-fake-reset-opcode-in-suspend.patch
commit 0c9ae8421bd25858f883f766978d1aeba4809145
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:34 2008 +0100
fix-lcm-reinit-post-resume.patch
commit 27f0c94484f9029e299150a315f58c7ca11e9e14
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:34 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 59c8522feccca7fab693be6ab8917cec0d9d1245
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:33 2008 +0100
config-add-alsa.patch
commit 35f4c6eed680001786edf6e4a2ab36b4c1e81ccf
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:33 2008 +0100
fix-s3c2410_timer_setup-resume-BUG.patch
commit 449317c386969e00a5fe21bdaac3c16df648845b
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:33 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 77bf29a97a497be996fc08fd3e9534641d4962e7
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:33 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 f6409c2cdf0ce992960e11a087f9358024b02e6e
Author: Andy Green <andy at openmoko.com>
Date: Sun Aug 3 20:25:33 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 237f0cad6896b9decd5f3aeaf7896ab24a151a50
Author: warmcat <andy at openmoko.com>
Date: Sun Aug 3 20:25:33 2008 +0100
clean-snip-gpio-reinit.patch
These are initialized already
Signed-off-by: Andy Green <andy at openmoko.com>
commit cd5ade6e92617193165c0f01e1fae7395ed64c70
Author: warmcat <andy at openmoko.com>
Date: Sun Aug 3 20:25:33 2008 +0100
bugfix-deglitch-gpio-output-enable.patch
commit bb19155ca43a1520791f0da17078fd44dcc74b5c
Author: Mike Montour <mail at mmontour.net>
Date: Sun Aug 3 20:25:32 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 069d1061028e81837baec037c78a43cb0e84178b
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:32 2008 +0100
local-config-ext2.patch
commit debab2685c5ecfc8c4406d6cecec95a27a1d523f
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:32 2008 +0100
local-config-pmu.patch
commit aa53da13b12b5e2a7523f270688ec4af0bbb9484
Author: warmcat <andy at openmoko.com>
Date: Sun Aug 3 20:25:32 2008 +0100
local-config-defconfig-motion-sensor-gpio.patch
commit e6127c209cb4f47aeb032a5282edc69bc5d804da
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:32 2008 +0100
local-config-wlan-config-changes.patch
commit d2cd3102d43c893d4288686345005acdbecd0c59
Author: warmcat <andy at openmoko.com>
Date: Sun Aug 3 20:25:32 2008 +0100
local-config-add-bluetooth-monolithic.patch
Add Bluetooth in monolithic kernel
commit b6c3070425a50c2351089d7c27a802325c99c729
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:32 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 99596e8fc77df24e253d45d2f03512422ec50a98
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:31 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 11a2d493044432e114ab6becdfab730ad19adb1a
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:31 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 cd6a016f5d62a8b15d8f1ea3ba1b42151b4ddcca
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:31 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 59a9b075b0aaf4cc181df8d3ff1cbbf2213ec993
Author: warmcat <andy at warmcat.com>
Date: Sun Aug 3 20:25:30 2008 +0100
local-add-defconfig.patch
Adds svn defconfig
From: warmcat <andy at warmcat.com>
More information about the commitlog
mailing list