aboutsummaryrefslogtreecommitdiff
path: root/drivers
AgeCommit message (Collapse)Author
2010-01-22Merge branch 'pcf50633-2.6.32' into om-gta02-2.6.32om-gta02-2.6.32Lars-Peter Clausen
2010-01-22pcf50633: Move pcf50633-gpio driver to the gpio drivers folderLars-Peter Clausen
2010-01-22pcf50633-gpio: Add gpiolib support.Lars-Peter Clausen
2010-01-19Merge branch 'om-s3c-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
2010-01-19s3c-mci: Disable write-protect and detect gpios in default platfrom dataLars-Peter Clausen
Due to the change that gpio0 is now seen as a valid gpio by the driver it tries to request gpio0 as card detect and write-protect pin if no platform_data was given. This patch initalises no_wprotect and no_detect of the default platform data to 1 and restores pre 2.6.32 behaviour.
2010-01-17Merge branch 'glamo-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
2010-01-17glamo: ups... forgot to commit header file for previous commitLars-Peter Clausen
2010-01-17Merge branch 'glamo-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
2010-01-17glamo: restore irq mask after resume.Lars-Peter Clausen
2009-12-27Merge branch 'ar6000-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
2009-12-27Add ar6000 wireless driver.Lars-Peter Clausen
2009-12-27Merge branch 's3c-touchscreen-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
2009-12-21s3c-ts: Fix adc callback function parametersLars-Peter Clausen
2009-12-21Merge branch 'platform_battery-2.6.32' into om-gta02-2.6.32Lars-Peter Clausen
Conflicts: drivers/power/Kconfig drivers/power/Makefile
2009-12-21Merge branches 'bq27000-2.6.32', 'glamo-2.6.32', 'jbt6k74-2.6.32', ↵Lars-Peter Clausen
'pcf50633-2.6.32', 'wm8753-2.6.32', 's3c-touchscreen-2.6.32' and 'om-s3c-2.6.32' into om-gta02-2.6.32
2009-12-21Kconfig: TOUCHSCREEN_S3C2410 depends on S3C24XX_ADC add select S3C24XX_ADCMartin Jansa
2009-12-21touchscreen patches for om-gta02-2.6.31Nelson Castillo
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>
2009-12-21ts-filter: Move include files to include/linux/input/touchscreenLars-Peter Clausen
2009-12-15Add jbt6k74 display driver.Lars-Peter Clausen
2009-12-15Add s3c2410tsNelson Castillo
Add the ts and the relevant files. Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
2009-12-15Add touchscreen filtersNelson Castillo
Add filter source code and add it to the defconfig. Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
2009-12-07power: implement platform battery driverPaul Fertser
This driver can be used for dumb batteries when all knowledge about their state belongs to the platform that does necessary ADC readings, conversions, guessimations etc. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06s3c2410_udc-2440_dual_packet-workaround.patchmokopatches
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.
2009-12-06mtd: s3c2410_nand: Add config option to disable hw ecc at runtimeHolger Freyther
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>
2009-12-06Add s3c24xx_serial_console_set_silenceLars-Peter Clausen
2009-12-06backlight/mfd: Add pcf50633 backlight driverLars-Peter Clausen
This patch adds a backlight driver controling the pcf50633 led converter. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-12-06MFD: pcf50633: Fix bitfield logic in interrupt handlerLars-Peter Clausen
As those constans are alread bitfields it's wrong Those constants are already bitfields.
2009-12-06mfd: pcf50633: Fix pcf50633-regulator drvdata usageLars-Peter Clausen
Currently the pcf50633-regulator driver data is set to the pcf50633 core structure, but the pcf50633-regulator remove handler assumes that it is set to the regulator device. This patch fixes the issue by accessing the pcf506533 core structure through its parent device and setting the driver data to the regulator device. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-12-06mfd: pcf50633: Use platform_device_add_data to set regulator platform dataLars-Peter Clausen
Platform devices allocated with platform_device_alloc should use platform_device_add_data to set the platform data, because kfree will be called on the platform_data when the device is released. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-12-06mfd: pcf50633: Cleanup pcf50633_probe error handlingLars-Peter Clausen
Currently the child devices were not freed if the irq could not be requested. This patch restructures the function, that in case of an error all previously allocated resources are freed. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-12-06mfd: pcf50633: Fix memleak in pcf50633_client_dev_registerLars-Peter Clausen
Since platform_device_add_data copies the passed data, the allocated subdev_pdata is never freed. A simple fix would be to either free subdev_pdata or put it onto the stack. But since the pcf50633 child devices can rely on beeing children of the pcf50633 core device it's much more elegant to get access to pcf50633 core structure through that link. This allows to get completly rid of pcf5033_subdev_pdata. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-12-06mfd: pcf50633: move messages to appropriate log levelsArnaud Patard
Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06mfd: pcf50633: make suspend/resume belong to i2c_driverLars-Peter Clausen
When not using the i2c suspend/resume callbacks the i2c client resumed before the i2c master. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06mfd: pcf50633 disable unnecessary shutdown on lowsysPaul Fertser
On gta02 hardware revision A5 it can actually bring the system down during normal operating conditions so we disable it. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06power: pcf50633: query charger status directlyPaul Fertser
Current scheme is fragile and is likely to go off sync, especially on batfull->adapter charging automatic MBC transition. Query the status bit every time we need it instead. We need to export another function to query for USB presence because we can't read anything from PCF50633 (via I2C) inside irq context and that is needed by usb gadgets. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06power: pcf50633: properly reenable charging when the supply conditions changePaul Fertser
If chgmod == BATFULL, setting chgena has no effect. Datasheet says we need to set resume instead but when autoresume is used resume doesn't work. Clear and set chgena instead. This enables a user to force charging by re-plugging USB even when the charger entered Battery Full mode, might be handy before a long trip. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06power: pcf50633: get rid of charging restart software auto-triggeringPaul Fertser
After reaching Battery Full condition MBC state machine switches back into charging mode when the battery voltage falls below 96% of a battery float voltage. The voltage drop in Li-Ion batteries is marginal (1-2%) till about 80% of its capacity - which means, after a BATFULL, charging won't be restarted until 75-80%. That is a desired behaviour recommended by battery manufacturers, don't mess with it. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06power: pcf50633: introduces battery charging current controlBalaji Rao
Signed-off-by: Balaji Rao <balajirrao@openmoko.org> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06power: pcf50633: add ac power supply class to the chargerSean McNeil
This adds an appropriate ac power_supply class and shows usb only when at the appropriate current limit. Signed-off-by: Sean McNeil <sean@mcneil.com> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06rtc: pcf50633: manage RTC alarm "pending" flagWerner Almesberger
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: Paul Fertser <fercerpav@gmail.com>
2009-12-06mfd: pcf50633: use set_irq_handler before requesting irqPaul Fertser
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-12-06glamo-mci: select CRC7 in KconfigMarc Andre Tanner
Signed-off-by: Marc Andre Tanner <mat@brain-dump.org>
2009-12-06Fix jiffies comparisonNelson Castillo
Jiffies can wrap. We have to use macros to compare them. Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
2009-12-06glamo: Remove stupid debug message.Lars-Peter Clausen
2009-12-06glamo-mci: Fix regulator error checkLars-Peter Clausen
regulator_get returns a ERR_PTR in case of an error and not a NULL pointer.
2009-12-06glamo-core: Use set_irq_flags on ARM only. set_irq_{no,}prove everywhere elseLars-Peter Clausen
Although there will probably never any other platform using the glamo...
2009-12-06glamo: Use set_irq_data instead of set_irq_chip_data for the demux handlerLars-Peter Clausen
Also fixup order in which the irq handler and it's data are initalized.
2009-12-06glamo: Fix checkpatch issuses.Lars-Peter Clausen
2009-12-06glamo-core: Properly initalize irq_baseLars-Peter Clausen
2009-12-06glamo-mci: Reset if engine is stalled.Lars-Peter Clausen