| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
This was posted to the linux-usb list in Dec 2008
Signed-off-by: Minkyu Kang <mk7.kang@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
include/linux/sched.h has two copies of these credentials now... real
and effective held in two struct creds. I chose real cred but I am uncertain
it's the desired one.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=445395c9fcfb78ea62ab5a69b84c2c12efe01cff
pcf50606_rebase_changes,patch
This patch brings into andy-tracking all changes related to pcf50606 from old
balaji-tracking.
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-fix-stray-endmenu-patch-1232632040-1232632141
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040-1232632141 / fdf777a63bcb59e0dfd78bfe2c6242e01f6d4eb9 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040
stable-tracking-hist top was MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 / 90463bfd2d5a3c8b52f6e6d71024a00e052b0ced ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-fix-stray-endmenu-patch
mokopatches-tracking-hist top was fix-stray-endmenu-patch / 3630e0be570de8057e7f8d2fe501ed353cdf34e6 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-stray-endmenu.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
kernel-build-1232567797
pending-tracking-hist top was MERGE-via-stable-tracking-glamo-don-t-break-kernel-build-1232567797 / d9aa2ec4d0f11979eb9894dbcf0c1639e73a7587 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-glamo-don-t-break-kernel-build
stable-tracking-hist top was glamo-don-t-break-kernel-build / 1796c97b437a7bb998c489caba09a026bbb16564 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
Glamo: don't break kernel build if disabled
If we disable CONFIG_MFD_GLAMO, a dependency on glamo_lcm_reset from
arch/arm/mach-s3c2440/mach-gta02.c:gta02_jbt6k74_reset cannot be
resolved.
There are many ways to fix this - this one does it with a bit of a
swagger ;-)
Signed-off-by: Werner Almesberger <werner@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>
|
|
pending-tracking-hist top was subject-usb-gadget-fix-rndis-w / 8a5ccc279cef316a16f921d7486f4a9efa234493 ... parent commitmessage:
From: David Brownell <dbrownell@users.sourceforge.net>
Subject: USB: gadget: fix rndis working at high speed
X-Git-Tag: v2.6.28-rc9~8^2~7
X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=7c12414955e9b44a3e33d54e578bf008caa4475d
USB: gadget: fix rndis working at high speed
Fix a bug specific to highspeed mode in the recently updated RNDIS
support: it wasn't setting up the high speed notification endpoint,
which prevented high speed RNDIS links from working.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Tested-by: Anand Gadiyar <gadiyar@ti.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
pending-tracking-hist top was subject-usb-gadget-rndis-send- / 3c29888770bfa8ce3a5e2ed590c3edb97ca4abaf ... parent commitmessage:
From: Richard Röjfors <richard.rojfors@endian.se>
Subject: USB: gadget rndis: send notifications
X-Git-Tag: v2.6.28-rc6~2^2~2
X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=ff3495052af48f7a2bf7961b131dc9e161dae19c;hp=9c264521a9f836541c122b00f505cfd60cc5bbb5
USB: gadget rndis: send notifications
It turns out that atomic_inc_return() returns the *new* value
not the original one, so the logic in rndis_response_available()
kept the first RNDIS response notification from getting out.
This prevented interoperation with MS-Windows (but not Linux).
Fix this to make RNDIS behave again.
Signed-off-by: Richard Röjfors <richard.rojfors@endian.se>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
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>
|
|
screen-filte-1232327393
pending-tracking-hist top was MERGE-via-stable-tracking-fix-pcap7200-touchscreen-filte-1232327393 / 751df35b8e57667cc0669a7437f80b6c025f24ec ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-fix-pcap7200-touchscreen-filte
stable-tracking-hist top was fix-pcap7200-touchscreen-filte / e053b5719609ded159a22bcd1889bbd2611789ba ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-pcap7200-touchscreen-filter-move.patch
pcap7200 driver also uses our filter chain stuff now, so it needed a little
fixup when the includes moved for upstream
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
global_inside_suspend only exists if CONFIG_PM is enabled.
We're actually the only ones using it outside power management,
so I guess it's okay not to try to find a more elegant solution
for upstream.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix resume dummy in jbt6k74.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix suspend/resume dummy in glamo-fb.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>
|
|
pending-tracking-hist top was clean-pcf50633-delete-deprecat / 4eb8d070641202940f12587b7efb77cac781b19d ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
clean-pcf50633-delete-deprecated-sensors-version.patch
Proposed-by: Sven sleipnir Rebhan <odinshorse@googlemail.com>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
When building the MMC subsystem as modules,
drivers/mfd/glamo/glamo-mci.ko cannot access irq_desc, because it
isn't exported by kernel/irq/handle.c All the functions that
indirectly access irq_desc are inlined, so they cannot be used to
avoid having to resolve irq_desc.
Fortunately, we can solve the problem locally: we don't really need
to access irq_desc anyway. This patch splits glamo_mci_irq into a
small wrapper that implements the IRQ handler interface and the main
code that doesn't need to know about the semantics of the latter.
Then we simply call the main code with the information we already
have.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Tested-by: Rafael Ignacio Zurita <rizurita@yahoo.com>
|
|
As I've mentioned before, telling the WLAN module not to sleep
with "wmiconfig -i eth0 --power maxperf" reportedly improves
network stability in some situations where otherwise disconnects
were frequent. (Sorry if this sounds rather vague. I don't have
much real data on this phenomenon. More details would be welcome.)
Paul Lever from Atheros suggested that one possible source of
trouble when not using --power maxperf could be that the module
very often takes a nap and then needs to delay new commands while
waking up, and some SDIO hosts may fail to handle the delay
properly.
The S3C2442 manual leaves it unclear whether the controller handles
this condition or not. The Linux MMC/SDIO stack explicitly polls
for busy status in MMC mode but not in SDIO mode.
I've attached a patch against andy-tracking that rather crudely
checks if the module is signalling that it's still busy while we're
about to start a new transfer, and delays in this case.
In my tests, I could not make the busy condition occur (unless I
explicitly violated the stack's synchronization), but then I hardly
see any disconnects anyway.
So it would be good if those affected by frequent loss of association
could try this patch. More precisely,
- if association with the base station is often lost, and
- "wmiconfig -i eth0 --power maxperf" improves this, then
- please apply this patch, leave WLAN power at default settings
(i.e., wmiconfig -i eth0 --power rec), and report
- if the patch had any effect on the stability of associations, and
- whether "READ WHILE BUSY !" or "WRITE WHILE BUSY !" gets
logged in dmesg.
It may make sense to temporarily put this patch into andy-tracking.
While it may be perfectly useless, it shouldn't create any new
trouble either. In case it turns out to make a difference, I'll have
to find a better place in the stack for it, so it'll be reverted
either way.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
