| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Introduce a new generic HDQ gpio based bitbang driver
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Since the pwm code in mach-2410 can be reused for 6410, move it to plat-s3c.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
This patch moves the bulk transfer action outside of
interrupt context, along with the STOP transmission action
for multiblock transfers.
It's prompted by
https://docs.openmoko.org/trac/ticket/2180
But it can impact throughput to SD card, so it's for testing
currently.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
It looks like I made a mistake in the original pan implementation that
is now getting exercised. The following fixes pan again.
Cheers,
Sean
|
|
pending-tracking-hist top was claen-ledtrig-netdev-unused-va / 126536fc6ed26323103f941e7cf81e4b0ceaab7a ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
claen-ledtrig-netdev-unused-var-warn.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
pending-tracking-hist top was MERGE-via-pending-tracking-hist-1234930404 / 4a23c8aeedd5fb86009d290a41fc299e3965d8ec ... parent commitmessage:
From: merge <null@invalid>
MERGE-pending-tracking-patchset-edits
|
|
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Reported-by: Mickey Lauer <mickey@openmoko.org>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
-do the parameter check of setting operating mode.
-add device haeder file.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
The following two features are added as platform data.
- externel reset
- operating mode
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Hi.
The recent patch to fix a USB current limit violation when turning the
device off triggered a bug in setting the battery charge current limit. We
now get a charge current limit of 0 mA on the GTA02 when plugging in the
wall charger (just as when setting 1000 mA in /sys/class/[...]/chg_curlim).
This patch fixes it (and a comment typo). Tested on a GTA02 with a wall
charger.
Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
|
Move the regulator handling stuff away from s3cmci.c to mach-gta01.c.
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: Andy Green <andy@openmoko.com>
|
|
hes-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505 / 1c405b6ccee468298e7ccbfd9a3a3f4d123207b0 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414 / 71be0a45396066b1f8f27f8f4f87937247a129e1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011
mokopatches-tracking-hist top was MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011 / 1be1b01373f572a02c6f1f99863c8c11ed2f9f5b ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-master-MERGE-via-master-hist-1232625318
master top was MERGE-via-master-hist-1232625318 / dd4b117123ae66451695810017eb72fbdfc05df5 ... parent commitmessage:
From: merge <null@invalid>
MERGE-master-patchset-edits
|
|
Cedric noticed that when he turned his GTA02 OFF while hooked to
a "dumb" USB charger that should only be asked for 100mA, suddenly
much more current was demanded.
When PMU enters PMU standmy when we go OFF, its USB current limit
is reset to the variant default of 500mA. Since we previously had
the charging current limit fixed at 1A, it meant we immediately
charge at 500mA.
This patch makes the charging limit follow the USB current limit,
so that even when we go off, no more than the last authorized amount
of current will be taken, even if the USB current limit is later
broken by the variant default.
Reported-by: Cedric Berger <cedric.berger74@gmail.com>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
We need to clear down the wakeup source reg if we woke from
threshold.
Reported-by: Simon Kagstrom <simon.kagstrom@gmail.com>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
We shouldn't be resetting the highpass filter every sample.
It should be disabled if we don't use it or allowed to
work across multiple samples if we do.
Was this hiding some other problem?
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Level interrupts solve the sticky loss of service from accels issue.
But currently, we get two service actions per one interrupt, leading to
information getting read and sent to the input subsystem twice.
This patch makes the ISR confirm with the lis302dl status register
that there is fresh data before accepting it, it works around the
issue and allows use of the other information in the status reg by
another patch.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
People on bug
https://docs.openmoko.org/trac/ticket/2217
experiencing problems with default emmory settings on Glamo
reported that changing reg 0x200 <- 0xef0 as in 2.6.24 made
the problem not reproducible any more.
However this changes three bitfields, two are to do with
waitstates before sampling read and write cycles off the
bus, and the last is to do with which PLL provides the clock
to the memory interface unit logic. The old settings has
all three of these very conservative, 3 waitstates and using
the 50MHz PLL instead of the 90MHz one; the new default
setting has all of these at their fastest of 0 wait states
and the 90MHz PLL.
This patch adds some more granular tests to the same
glamo3362.slow_memory=
parameter to see if we can find some middle ground. For
example the issue may be the waitstates and not the PLL
source, in which case even users with the bad Glamo
behaviour can have the advantage of the faster PLL / bus
bandwidth.
0 90MHz PLL, no wait states (default)
1 50MHz PLL, 3 wait states
2 50MHz PLL, 2 wait states
3 50MHz PLL, 1 wait state
4 50MHz PLL, no wait states
5 90MHz PLL, 3 wait states
6 90MHz PLL, 2 wait states
7 90MHz PLL, 1 wait state
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This patch adds setting and clearing of the "pending" flag of the
RTC alarm. The semantics follow the UEFI specification 2.2 available
at http://www.uefi.org/specs/, i.e., the "pending" flag is cleared
by disabling the alarm, but not by any other condition (such as the
passing of time, a successful wakeup, or setting of a new alarm.)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Hi Balaji,
Mickey mentioned to me that he had trouble with the RTC wakeup interrupt.
I had a quick look at the problem and it seems that alrm->enable doesn't
get propagated when setting the alarm time with RTC_WKALM_SET.
Does something like my patch below look right ? We also don't handle
alrm->pending, but I'm not sure if we have to.
I tested this only very lightly since my current andy-tracking crashes
in soc_suspend. If nobody else beats me to it, I'll have a look at it
tomorrow.
- Werner
---------------------------------- cut here -----------------------------------
According to Documentation/rtc.txt, RTC_WKALM_SET sets the alarm time
and enables/disables the alarm. We implement RTC_WKALM_SET through
pcf50633_rtc_set_alarm. The enabling/disabling part was missing.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Michael 'Mickey' Lauer <mickey@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=3b09161ffa5f29870d1f2cab1442f79ff2017b69
glamo_fix_improper_xrandr_geometry_setting.patch
Switching to xrandr -o 3 from xrandr -o 1 caused the screen to look crazy
because of the way lcd geometry is set in glamo. This patch fixes it.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Introduces battery charging current control.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Remove compilation of the old android directory
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Change android makefile to compile all the platform
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Fix binder compilation problem in linux system and change the
mapping required for arm system. This fix a crash in binder process
that can't map the required memory
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Add new android files. They support:
- android power
- andorid console
- alarm driver
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Remove old android support.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
We were waiting 60ms before reporting a pen-up event to avoid
jitter. Now we wait 8ms (actually 5 with HZ == 200).
Thanks to Marco Trevisan for testing and pointing out that there was a
problem that could be spotted with the illume keyboard.
Note that I used the Terminal mode of the keyboard (no dictionary)
for tests.
I also used touch_test.py and the jitter doesn't seem to be an
issue when drawing lines with the finger.
Reported-by: Marco Trevisan (Treviño) <mail@3v1n0.net>
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=1bb6adaa6a59f52d616b5260cb776eafd40ef05e
pcf50633_introduce_charging_restart_interval.patch
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=94808ce02deeb78bb3728db416fd4b7544b6d232
pcf50633_remove_set_charger_status.patch
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=40fe0a30c75937a476ea50220814ca8b1fd81b45
fix_glamo_xrandr_bug.patch
This patch reintroduces the 2-cycle delay used when accessing glamo-fb
registers. This seems to be required even when the corresponding
registers in HOST_BUS are off.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=938eddf17625cce0307f7612a3ea2560384e2384
pcf50606_rebase_changes,patch
This patch brings into andy-tracking all changes related to pcf50606 from old
balaji-tracking.
|
|
If the filtering is switched off, we need a substitution for the two missing
functions. So simply define some placeholders.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
First, make the filtering switchable by the user.
Second, select all filters if filtering is switched on. This is required because
we predefine the filterchain in mach-gta02.c and thus need all filter functions.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
|
|
fix-ac-redefinition.patch
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
