| Age | Commit message (Collapse) | Author |
|---|
|
Setup interrupt latching for thresholded operation
From: Simon Kagstrom <simon.kagstrom@gmail.com>
This patch, for stable-tracking, sets up interrupt latching for
thresholded operation, and also acks the interrupt in the handler. This
reduces the interrupt load, and thresholds < 36 are once again allowed
(though not of much use).
The patch also fixes some warnings in the code (including a potential
bug).
Thanks to Werner for pointing this out!
Signed-off-by: Simon Kagstrom <simon.kagstrom@gmail.com>
|
|
When compiling s3cmci as a module and doing an insmod-rmmod-insmod
sequence, s3cmci_probe often oopses because the platform data contains
garbage.
The reason for this is that I'm not providing any platform data (removed
in gta02-mmc-mci.patch), and thus s3cmci tries to put its own defaults:
if (!host->pdata) {
pdev->dev.platform_data = &s3cmci_def_pdata;
host->pdata = &s3cmci_def_pdata;
}
s3cmci_def_pdata is inside the module, so the pointer in
pdev->dev.platform_data becomes invalid after the module is unloaded.
Since nothing else in s3cmci uses pdev->dev.platform_data, "patching"
it seems unnecessary. This patch removes it.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Oops ! It compiled file as non-module, but not as module.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This patch adds the module parameter f_max to s3cmci to limit the
maximum clock frequency of the SD interface.
E.g., when booting with s3cmci.f_max=10000000, the kernel should say
s3c2440-sdi s3c2440-sdi: f_max lowered from 50000000 to 10000000 Hz
and the interface frequency should be limited accordingly.
Setting the limit above the maximum frequency supported by the card
or the interface has no effect, so the option is ignored (and no
"f_max lowered" line is printed).
Setting the limit below the minimum frequency supported by the
interface sets it to that frequency.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This solves the problem that the backlight never turns off
in stable-tracking
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Merge in the accelerometer functionality from stable
From: Simon Kagstrom <simon.kagstrom@gmail.com>
This giant patch merges the functionality from stable. It also changes
the default threshold to 0 (generate interrupts on data). As the
level-triggered interrupts cause too frequent interruptions on low
thresholds, also set a lower limit to 36mg to avoid slowing down the
phone too much.
Also rearrange the probe function to disable interrupts only over device
I/O. This fixes the kernel errors when inserting the module.
Andy was right: In stable-tracking, no magic workaround is needed to
make suspend/resume work. I've tested the accelerometers under heavy
load (making the phone basically unusable) without getting lockups.
Signed-off-by: Simon Kagstrom <simon.kagstrom@gmail.com>
|
|
Export some irq-related functionality to modules
From: Simon Kagstrom <simon.kagstrom@gmail.com>
This patch exports handle_level_irq and __set_irq_handler to modules.
It's needed to compile lis302dl as a module.
Signed-off-by: Simon Kagstrom <simon.kagstrom@gmail.com>
|
|
Work in progress.
|
|
* Improve comment about the chip select issue with the accelerometers.
Signed-off-by: Nelson Castillo <nelsoneci@gmail.com>
|
|
Make accelerometers work again in stable-tracking.
They stopped working with a previous commit.
(shifter >> 7) & 1); ...; shifter <<= 1;
Had been changed to:
(shifter >> (7 - n)) & 1) /* assuming tx_bytes == 1 */
The problem: an unneeded shifter <<= 1 was still there.
We make a small change to the indexing code to make things work again.
Signed-off-by: Nelson Castillo <nelsoneci@gmail.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Glamo GPIO are not set correctly after resume / reset action.
This patch forces them to correct state for GTA02.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Micael Henriksson <micael.h@gmail.com>
|
|
This patch changes the ./build script to generate a uImage.bin file with
the build device appended, eg, uImage-GTA02.bin.
The reason for this change is that it is possible to generate rootfs images
now that can target multiple (and probably increasing numbers of) devices
with the one image. Therefore qi or other bootloader running on the device
is going to have to pick out the right kernel from the rootfs filesystem
for the device it finds it is running on from a set provided down /boot
by the rootfs generator.
/lib/modules for the kernels doesn't get in the way of each other because the
version-specific path is also extended to have the device name as part of it.
2.6.28-GTA02_stable-tracking_c77dda03a7c11666-mokodev
For legacy U-Boot support on GTA01 or GTA02, a symlink to uImage-GTA01.bin or
uImage-GTA02.bin will be needed.
The dfu utility script is updated to take an argument, eg, GTA02
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>
|
|
Change to removing Atheros stack left a dangling reference to Makefile
in drivers/sdio that made errors on make distclean
Reported-by: Christopher Hall <hsw@openmoko.org>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Sean McNeil <sean@mcneil.com>
|
|
This is probably not correct as the i2c registration is not supposed to
work this way, but for the time being, add this hack to make the GTA01
at least boot. Revisit this and drop this patch when possible.
Thanks to Andy Green for the tip.
Signed-off-by: Jonas Bonn <jonas.bonn@gmail.com>
|
|
Some header files have moved so update #includes.
devs.h has been moved and updated. Delete the old version at
include/asm-arm/plat-s3c24xx as it is no longer used. Nothing to
migrate from this file to the new file at the new location.
s3c_device_i2c has become s3c_device_i2c0
Signed-off-by: Jonas Bonn <jonas.bonn@gmail.com>
|
|
Tacls can actually be zero with some NAND flash devices, so we need
to permit this.
Also, the TACLS register actually specifies the actual number of
HCLK clocks, where the TWRPH0 and TWRPH1 registers are auto-incremented
by one HCLK clock in hardware.
Signed-off-by: Harald Welte <laforge@openmoko.org>
|
|
Hi Andy,
I found that stable tracking usb_curlim was zero because of this and the
battery was not getting charged by default.
CONFIG_USB_GADGET_VBUS_DRAW was introduced in .27-rc6 I guess.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Change battery name from bat to battery to conform with Android better
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
i2c0 platform data wasn't initialized, which caused driver registration
to fail, and kept many other peripherals from initializing.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
|
|
This is a replacement for Atheros' HIF layer that uses the Linux SDIO
stack.
Using GPLv2, like Atheros' code this is based on.
Work in progress.
Not-Yet-Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
|
|
After killing the Atheros SDIO stack, we shall no longer deny ourselves
the pleasure of also getting rid of the glue that keeps it on the
platform.
Not-Yet-Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Make the AR6000 WLAN driver compile after moving it outside the
Atheros SDIO stack. Note that the config option's name changes
as well.
The choice of a non-standard location (drivers/ar6000/) is
intentional. The driver is still very far from being in shape for
mainline inclusion, and the odd location should serve as an
immediate warning.
Not-Yet-Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
I've noticed some pretty poor behavior on OLPC machines after bootup, when
gdm/X are starting. The GCD monopolizes the scheduler (which in turns means
it gets to do more nand i/o), which results in processes taking much much
longer than they should to start.
As an example, on an OLPC machine going from OFW to a usable X (via auto-login
gdm) takes 2m 30s. The majority of this time is consumed by the switch into
graphical mode. With this patch, we cut a full 60s off of bootup time. After
bootup, things are much snappier as well.
Note that we have seen a CRC node error with this patch that causes the machine
to fail to boot, but we've also seen that problem without this patch.
Signed-off-by: Andres Salomon <dilinger@debian.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>
|
|
Ben Dooks wrote:
> My only comment would be
> that a slightly better solution would be to do:
Oh, that's much better, thanks ! I hadn't realized at first that
once could read the FIFO one byte at a time.
The revised patch is below.
- Werner
---------------------------------- cut here -----------------------------------
fix-s3c-nand-read-bytes.patch
With the introduction of optimized OOB reads in nand_read_subpage,
the length of the data requested may not be a multiple of four bytes.
This caused a partial read on the 2440, leading to false ECC errors
and, worse, attempts to "correct" them.
Note that there is a similar issue in s3c2440_nand_write_buf, which
doesn't seem to cause trouble yet.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Subject: [PATCH] glamofb: Initialize only visible part of the memory.
It takes lots of time (0.5 seconds) to initialize the whole memory. As
only the visible part matters, we could just initialize that part.
Signed-off-by: Chia-I Wu <olv@openmoko.com>
|
|
christer-mmc-byte-alignment.patch reduced the FIFO I/O granularity
from words to bytes. This also includes the decision when the FIFO
is empty or full.
However, we sometimes only want to transfer full words, in which
case do_pio_read/do_pio_write busy-loop until the FIFO has filled
up or drained enough.
In the case of do_pio_write, this can cause an endless loop if the
amount of data exceeds the FIFO size, because do_pio_write runs
before the transfer is initiated, so the FIFO never drains.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add fake GPIO I2C bus so we can start config with pcf50633 before
real 6410 I2C bus driver is ready
Enable pcf50633 and current APM emulation to get it going (will be
deprecated shortly hopefully).
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Use the same code for bringup during initialization and when switching
the module on/off through sysfs.
This also solves the problem of not resetting the WLAN module, which
was caused by fix-set-wlan-power-mgt-to-default-on.patch only partially
reverting the power-off default introduced with
introduce-gta02-pm-wlan.patch.
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>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Make the load address within RAM, rather than a memory mapped
register. (Fix a copy-and-paste error.)
|
