| Age | Commit message (Collapse) | Author |
|---|
|
Allow the GPS module to be powered during suspend so it can keep the fix.
This has to be enabled by writing 1 to .../neo1973-pm-gps.0/keep_on_in_suspend
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
Fix re-enabling of GPS on resume
The call to gps_pwron_set(0) during suspend would clear power_was_on
flag so the on/off status was always lost. Additionally when enabling/
disabling the regulator check its actual state, not power_was_on flag
(they don't match on resume).
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
This configuration (CONFIG_DISPLAY_L1K002) is GTA03 specific.
Let's disable it for GTA02.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
When in a kernel panic, we try to turn on the backlight. Because
of the panic, preempt is disabled at that time. Unfortunately,
operating the backlight requires access to I2C, and I2C likes to
sleep.
All this results in the kernel unleashing a nearly endless flood
of complaints complete with stack traces, etc., which often
obscures the real issue.
This patch is one way to improve the situation: it just skips
touching the backlight if we're in an atomic context. However, it
isn't perfect: it would be desirable if the backlight did get
turned on also on a panic. To do so, we would need to use I2C in
a way that doesn't sleep.
So I wonder if this is good enough or if someone has any plans to
make a better solution ?
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
-device-driv-1232448327
pending-tracking-hist top was MERGE-via-stable-tracking-add-tpo-l1k002-lcm-device-driv-1232448327 / 776c842e391a2fbc8e85cab38c90be2ce44e7cf7 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-add-tpo-l1k002-lcm-device-driv
stable-tracking-hist top was add-tpo-l1k002-lcm-device-driv / 738664a979e3fa43f3d53989390ce6212c818c92 ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
Add TPO L1K002 LCM device driver.
This device is adopted as LCM of gta03.
The patch provides the initialization for this LCM driver IC.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
lt-configura-1232397413
pending-tracking-hist top was MERGE-via-stable-tracking-update-gta02-default-configura-1232397413 / fdaef96a49003c3e907629757f489585ea6708ab ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-update-gta02-default-configura
stable-tracking-hist top was update-gta02-default-configura / ae4b4dc366b578f90cd85eda9348d3f7e585670c ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
update GTA02 default configurations
Add the settings introduced by the previous two patches to the default
configurations.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add the settings introduced by the previous two patches to the default
configurations.
(AG: this one is packaging config, the moredrivers one is on stable-tracking)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch cleans up the GTA02 WLAN power control platform device:
- remove misleading /sys/devices/platform/gta02-pm-wlan.0/power_on
Users really wishing to play with reset can just gpio j12=0
- rename gta02_wlan_power to gta02_wlan_reset, because that's what it
truly is
- remove handling of GTA02_CHIP_PWD because
- it's not used, say our schematics
- even if it is, it's sampled long before we could affect it
- move SDIO-specific conversion from "power switch" to "reset
button" logic from gta02_wlan_reset to gta02_s3c_mmc_set_power
- removed mutex protection because we now only have a single user
A note in passing: we can probably do away with gta02_pm_wlan
completely once upstream rfkill adds better support for type-based
control.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Here's a bunch of changes to neo1973_pm_gps.c. The thing I set out to
change was just the initial power state, but there's so much wrong in
there, I couldn't resist slaying some evil on the way:
- update the copyright year
- show slightly more confidence in operator precedence
- simplify #ifdef rat's nest a little
- rename "pwron" sysfs file to "power_on", to conform to all the rest
- wrap lines longer than 80 columns
- use PTR_ERR, not cast
- reduce redundancy and increase readability in code patching
gta01_gps_sysfs_entries
- on GTA02 and if booted by u-boot, GPS is powered on. Power it off,
like on GTA01 or with Qi.
It's still nasty, but slightly less painful to look at now. Tested on
GTA02 and tested that it still compiles for GTA01.
The name change from "pwron" to "power_on" may be controversial. If
this causes undue misery for distribution makers, please holler.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix suspend/resume dummy in mach-s3c2410/pwm.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
lter-include-1232325217
pending-tracking-hist top was MERGE-via-stable-tracking-fix-touchscreen-filter-include-1232325217 / d063e8c6d85c48de80b3d158bfa98d5a97149711 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-fix-touchscreen-filter-include
stable-tracking-hist top was fix-touchscreen-filter-include / bb151f28fc8e8923baad96e0f3e8f0ae57af95f5 ... parent commitmessage:
From: Nelson Castillo <arhuaco@freaks-unidos.net>
Fix touchscreen filter includes
Fix #includes to make the kernel compile again.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
-the-ar6000-1232104308
pending-tracking-hist top was MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308 / 09faeb511e9e6872c79b4d1ea2f3b5fefc16f3a1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-rfkill-support-for-the-ar6000-
stable-tracking-hist top was rfkill-support-for-the-ar6000- / e82f8ffa04ebcb05506c8e22268371c3c3b03173 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
rfkill support for the AR6000 driver
This patch adds rfkill support to the AR6000 driver. The driver does
not directly implement an rfkill device but uses the help of a special
platform device, such that the latter can retain rfkill state when the
AR6k driver is removed (e.g., because of suspend).
If an attempt is made to bring the driver up (module load, bind, or
resume) while rfkill is blocking, only the driver's data structures
are initialized, but function activation and most of the rest of the
setup is deferred until the rfkill block is removed.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch removes CONFIG_MD from gta02-moredrivers-defconfig, which
was dropped from the previous combined cleanup. It also removes
CONFIG_MMC_SDHCI from both GTA02 defconfigs, since this kind of
hardware doesn't exist in the S3C2442.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch changes the two GTA02 default configurations[1] to build
the AR6k driver and S3C MCI (which is used exclusively by AR6k)
as modules. This way, WLAN can be brought up only if we actually
need it.
The patch also disables CONFIG_MD, which served no clear purpose.
[1] andy removed the moredrivers part despite asking for it
because it can be useful to have it built in without syncing
the rootfs, so the packaging config alone has it as modules.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
pending-tracking-hist top was s3c64xx-fix-eint-group-macro-d / 2b782b2c91f8a43347d551f5a6cf0bb09243c27b ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
S3C64XX: Fix EINT group macro definition
EINT group macro produces an error.
Fix this by giving correct macro arguments.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Since we don't switch to PMU.standby, on suspend we should not
be defining these.
Btw, this fixes the WSOD I observed on andy-tracking and also
gets rid of the regulator related backtrace seen upon resume.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
This fixes the system-does-not-powerdown bug.
Reported-by: Michael Trimarchi <trimarchimichael@yahoo.it>
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
pending-tracking-hist top was this-patch-gets-the-linux-mci- / f45f6d893a0dc65a6041a2c0127e9970427a85da ... parent commitmessage:
From: Balaji Rao <balajirrao@openmoko.org>
This patch gets the Linux mci stack to use the voltage it negotiated before
with the uSD card on resume. Without this, it always reverts to and stays at
3.3V.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
This makes sure that charging status remains correct when currrent
limit is altered from userspace.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-MERGE-via-master-hist-1229249926-1229250322-1229250598
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-hist-1229249926-1229250322-1229250598 / 1231dc713a5825b92b6809aa417686c579e6a9f9 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-hist-1229249926-1229250322
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-hist-1229249926-1229250322 / 9c01cf722f0536f4827d76d36ee58c070b21c0da ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-hist-1229249926
mokopatches-tracking-hist top was MERGE-via-master-hist-1229249926 / 8f700d425b380707d4f2b7052c1b1f7e77c8b7d3 ... parent commitmessage:
From: merge <null@invalid>
MERGE-mokopatches-tracking-patchset-edits
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516-1229082771
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516-1229082771 / f410ecd0cc4642ae8b0f69c15fe349ea5639f5e2 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516 / 18f9a76ecc30ba8eee5de0627de3e7eb049775c3 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488
mokopatches-tracking-hist top was MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488 / 7eb66508f95eeebbd7ad3487c5183b76524d4765 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-master-MERGE-via-master-hist-1229078937
master top was MERGE-via-master-hist-1229078937 / ff0b5902f29135a782a3bfb68e3429b86669aea4 ... parent commitmessage:
From: merge <null@invalid>
MERGE-master-patchset-edits
|
|
patch-1229015794
pending-tracking-hist top was MERGE-via-stable-tracking-config-kill-evbug-patch-1229015794 / cf65aecd5f77e51a244ff4647afa409056c3d725 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-config-kill-evbug-patch
stable-tracking-hist top was config-kill-evbug-patch / 16e183d5b9b5e0bc6d14877a8815e91d9000792e ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
config-kill-evbug.patch
Reported-by: Klaus Kurzmann <mok@mnet-online.de>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
ckaging-defc-1228907217
pending-tracking-hist top was MERGE-via-stable-tracking-introduce-gta02-packaging-defc-1228907217 / 03583f856b4029f09b7aee17e1c743cd5d50062f ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-introduce-gta02-packaging-defc
stable-tracking-hist top was introduce-gta02-packaging-defc / 893e0396e11b1b697205262dd034a0420dbad0e1 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
introduce-gta02-packaging-defconfig
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
pat-patch-1228904021
pending-tracking-hist top was MERGE-via-stable-tracking-config-android-compat-patch-1228904021 / 73da33f3dea660b98727337d2e6e29bcf29fb419 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-config-android-compat-patch
stable-tracking-hist top was config-android-compat-patch / ff29cd711174bfe525a6cb9c9e37183f367f6558 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
config-android-compat.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
pending-tracking-hist top was MERGE-via-pending-tracking-hist-1228898320 / 75e06011b6a2ab443295941791f0e71913d837d5 ... parent commitmessage:
From: merge <null@invalid>
MERGE-pending-tracking-patchset-edits
|
|
pending-tracking-hist top was fix-s3c_irq_demux_extint8-to-h / e3a894b0f1fae0caa2224a5d1b3c409fcac9f5cc ... parent commitmessage:
From: Balaji Rao <balajirrao@openmoko.org>
Fix s3c_irq_demux_extint8 to handle masked but pending IRQs
Hi,
It was observed that even after the move to level irq on pcf50633, the
problem of 'the phone doesn't resume if POWER is pressed during
transition to standby' remains.
The original problem was due to a lost edge.
The present problem - When POWER is pressed during the transition,
handle_level_irq runs which looks at the IRQ_DISABLED flag set by
pcf50633_suspend and masks the irq on chip. Now when the cpu wakes up
(level keeps hitting us), s3c_irq_demux_extint8 runs, which tries to
handle all pending irqs. But before it does so, it applies the mask
and hence not all pending irqs were acked and hence, our pmu's irq
(level) caused an irq flood..
This patch clears those interrupts which are masked, but pending. Fixes
the problem for me. Mildly tested.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Whoops this is just reverting a couple of patches that
were not ready to be committed yet.
|
|
o-allocation-1228776491
pending-tracking-hist top was MERGE-via-stable-tracking-fix-s3c2410_ts-fifo-allocation-1228776491 / a85a8a282939b4f6800081f67e1d568e0b97bd7a ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-fix-s3c2410_ts-fifo-allocation
stable-tracking-hist top was fix-s3c2410_ts-fifo-allocation / 56a57ba0d4c1d60869250d5f89fae61544f01012 ... parent commitmessage:
From: Nelson Castillo <nelsoneci@gmail.com>
Fix s3c2410_ts FIFO allocation
When I added the FIFO improving the interrupts handlers I introduced a bug.
The FIFO is allocated after the interrupts are requested. This makes the kernel
crash if the touchscreen generates activity before the allocation takes place.
This patch fixes the bug. I reproduced it and tested the fix in a GTA02.
- Fix bug
- Fix a typo
Reported-by: Andy Green <andy@openmoko.com>
Signed-off-by: Nelson Castillo <nelsoneci@gmail.com>
|
|
pending-tracking-hist top was s3c24xx-needs-gpio_track / da546f30820208681442d98d29aadd2e6a909a09 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
S3C24xx needs GPIO_TRACK
s3c_gpiolib_getchip for 24xx assumes that, as far as addressing is
concerned, all ports have 32 pins. However, there are two flaws in
this logic:
1) gpiolib only assigns pin number for real pins (with the
exception of gaps added with CONFIG_S3C_GPIO_SPACE), and
2) not all ports have the same number of pins.
This patch makes 24xx use the more generic platform s3c_gpiolib_getchip,
like we do on 6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
S3C24xx: make GPIOs end at H10
At least on 2410 and 2442, GPIOs don't end at G10 but at H10 or
even J12.
Port J is treated as a special case throughout much of the S3C
code, so I'm not sure what the plan is for it now. However, it
seems safe to include port H.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
S3C24xx: GPIO G has 16 pins
At least on 2410 and 2442, GPIO port G has 16 pins.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
-group-patch-1228735176
pending-tracking-hist top was MERGE-via-stable-tracking-config-touchscreen-group-patch-1228735176 / b0d334ee992b56e9c97422bcb7d3d4fe239af53e ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-config-touchscreen-group-patch
stable-tracking-hist top was config-touchscreen-group-patch / 51c9b7258ee85644ada4b8bf1db4da2450585675 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
config-touchscreen-group.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
-1228733704
pending-tracking-hist top was MERGE-via-stable-tracking-remove-skip-filter-1228733704 / 552c6fdd4c644ab2618ad27564d159ed28bbd859 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-remove-skip-filter
stable-tracking-hist top was remove-skip-filter / 92bdef8636873a19efc05b2a19578a0aa93dba41 ... parent commitmessage:
From: Nelson Castillo <nelsoneci@gmail.com>
Remove skip filter
With more reliable points median and mean filters perform a better job.
We no longer need this filter.
Signed-off-by: Nelson Castillo <nelsoneci@gmail.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This fixes problems with not enough signals controlled by WLAN enable
and disable (it really does cycle the power) and adapts starting state
for Qi change that defaults it all to off. It saves about 50mW pulling
the power from it.
It also provokes the SDIO stack to go look for the card after power up
or down so it tracks presence by this power operation too.
Signed-off-by: Andy Green <andy@openmoko.com>
|
