| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Conflicts:
drivers/power/pcf50606-charger.c
|
|
The owner of the file should be able to modify it's content.
Also output the string representation of a charge mode if it exists.
|
|
This must have been lost during some merge conflict.
|
|
Conflicts:
drivers/mfd/Kconfig
|
|
om-gta02-2.6.31
|
|
This patch adds a backlight driver controling the pcf50633 led converter.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
|
|
This is a patch that seems to make the USB hangs on the S3C2440 go away. At
least a good amount of ping torture didn't make them come back so far.
The issue is that, if there are several back-to-back packets,
sometimes no interrupt is generated for one of them. This
seems to be caused by the mysterious dual packet mode, which
the USB hardware enters automatically if the endpoint size is
half that of the FIFO. (On the 2440, this is the normal
situation for bulk data endpoints.)
There is also a timing factor in this. I think what happens is
that the USB hardware automatically sends an acknowledgement
if there is only one packet in the FIFO (the FIFO has space
for two). If another packet arrives before the host has
retrieved and acknowledged the previous one, no interrupt is
generated for that second one.
However, there may be an indication. There is one undocumented
bit (none of the 244x manuals document it), OUT_CRS1_REG[1],
that seems to be set suspiciously often when this condition
occurs. There is also CLR_DATA_TOGGLE, OUT_CRS1_REG[7], which
may have a function related to this. (The Samsung manual is
rather terse on that, as usual.)
This needs to be examined further. For now, the patch seems to do the
trick.
Note that this is not a clean solution by any means, because we
might potentially get stuck in that interrupt for quite a while.
|
|
|
|
|
|
On Sat, Oct 24, 2009 at 3:04 AM, Nelson Castillo
<arhuaco@freaks-unidos.net> wrote:
> Hi there. I finally made this work. I tested with: cat /dev/input/touchscreen0 | hexdump
>
> I wonder why it didn't work with X... This rootfs works with other drivers I've tested (even with the upstream kernel).
Problem found.
Patch attached.
From: Nelson Castillo <arhuaco@freaks-unidos.net>
Date: Sat, 24 Oct 2009 14:12:58 -0500
Subject: [PATCH] Add auto-pst
Without these lines the TS doesn't work.
I didn't check who the author of the lines is.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
As those constans are alread bitfields it's wrong
Those constants are already bitfields.
|
|
|
|
|
|
Add the ts and the relevant files.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Add filter source code and add it to the defconfig.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
|
|
|
|
|
|
|
|
If the regulator id is out of range something else has been terrible gone
wrong and it does not make sense to catch it here in a soft way.
|
|
|
|
|
|
|
|
|
|
If the regulator id is out of range something else has been terrible gone
wrong and it does not make sense to catch it here in a soft way.
|
|
|
|
|
|
|
|
Since it is not use and probably never will be it's safe to remove it.
|
|
Conflicts:
drivers/mfd/Kconfig
drivers/power/Kconfig
drivers/power/Makefile
|
|
'gta01-machine-2.6.31' and 'pcf50606-2.6.31' into om-gta01-2.6.31
|
|
|
|
|
|
|
|
|
|
This patch adds a flag to the s3c2410_nand platform data, which configures
whether hardware ecc is used for that chip.
Currently hardware ecc is used if it was compiled into the kernel. But if you
want to build a kernel which runs on multiple devices you might have a
configuration where you have devices which require hw ecc as well as devices
which want software ecc.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
Ported from 01f61025cee418405880d653f33ce179873a3610
|
|
Ported from 0231c22f5955bbe72c88815f119198c734149e00
|
|
Ported from f9745d7f9cca30230a827f2170cf038a368f9992
|
|
Ported from 207ec43e8c5a54dfc82a0e65af5b8f2765e3cbb8
|
|
Ported from 804ed578713f259c23e6e98e4740588f4aa00519
|
|
|
|
regulator_get returns a ERR_PTR in case of an error and not a NULL pointer.
|
|
|
|
Although there will probably never any other platform using the glamo...
|
|
Also fixup order in which the irq handler and it's data are initalized.
|
|
|
|
|
