aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2009-10-10glamo: 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-10-10glamo: Fix checkpatch issuses.Lars-Peter Clausen
2009-10-10glamo-core: Properly initalize irq_baseLars-Peter Clausen
2009-10-10glamo-mci: Reset if engine is stalled.Lars-Peter Clausen
2009-10-10Merge branch 'glamo-2.6.31' into om-gta02-2.6.31Lars-Peter Clausen
2009-10-10glamo-mci: Wait for the mmc engine to become idle before signaling that aLars-Peter Clausen
request has been finished.
2009-10-10glamo-mci: do_pio_{read,write}: Use sg_mapping_iter to iterate through the ↵Lars-Peter Clausen
sg list.
2009-10-09Add a preliminary defconfigLars-Peter Clausen
2009-10-09Merge branch 'gta02-machine-devices-2.6.31' into om-gta02-2.6.31Lars-Peter Clausen
2009-10-09Merge branches 'om-s3c-2.6.31', 'gta02-machine-2.6.31', 'ar6000-2.6.31', ↵Lars-Peter Clausen
'glamo-2.6.31', 'jbt6k74-2.6.31', 'gta02-vibrator-2.6.31', 'bq27000-2.6.31', 'wm8753-2.6.31' and 'pcf50633-2.6.31' into om-gta02-2.6.31
2009-10-09mfd: 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-10-09mfd: 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-10-09mfd: 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-10-09gta02: request usb pullup pin before using it.Lars-Peter Clausen
2009-10-08gta02: Set pcf50633 chg_ref_current_maLars-Peter Clausen
2009-10-08gta02: Add power supply consumers.Lars-Peter Clausen
2009-10-08gta02: Add vibrator device.Lars-Peter Clausen
2009-10-08gta02: Add battery driverLars-Peter Clausen
2009-10-08gta02: Add fiq handlerLars-Peter Clausen
2009-10-08Add jbt6k74 deviceLars-Peter Clausen
2009-10-07mfd: 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-10-07mfd: 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-10-07mfd: 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-10-07mfd: 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-10-07power: 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-10-07power: 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-10-07power: 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-10-07power: pcf50633: introduces battery charging current controlBalaji Rao
Signed-off-by: Balaji Rao <balajirrao@openmoko.org> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-10-07power: 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-10-07rtc: 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-10-07rtc: pcf50633: consider alrm->enable in pcf50633_rtc_set_alarmWerner Almesberger
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: Paul Fertser <fercerpav@gmail.com>
2009-10-07rtc: pcf50633: Fix month off-by-one errorRask Ingemann Lambertsen
The PCF50633 stores a month value of 1-12, but the kernel wants 0-11. Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-10-07mfd: pcf50633: use set_irq_handler before requesting irqPaul Fertser
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-10-07Regulator: Implement list_voltage for pcf50633 regulator driver.Lars-Peter Clausen
This patch implements list_voltage for the pcf50644 regulator driver. As the voltages are linearly scaled the code to convert register values to voltages can be reused and most of the code can be shared with get_voltage. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
2009-10-07pcf50633: use a dedicated workqueue for irq processingPaul Fertser
Using the default kernel "events" workqueue causes problems with synchronous adc readings if initiated from some task on the same workqueue. I had a deadlock trying to use pcf50633_adc_sync_read from a power_supply class driver because the reading was initiated from the workqueue and it waited for the irq processing to complete (to get the result) and that was put on the same workqueue. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
2009-10-05ASoC: neo1973_gta02_wm8753: Get rid of lm4853_{set,get}_state and some minorLars-Peter Clausen
cleanups
2009-10-05gta02: Include mach/regs-gpioj.hLars-Peter Clausen
2009-10-05gta02: Add glamo deviceLars-Peter Clausen
2009-10-05ARM: S3C24XX: Introduce S3C2442B CPULars-Peter Clausen
Add the S3C2442B CPU ID to aid support the Openmoko GTA02 / Freerunner. Signed-off-by: Harald Welte <laforge@gnumonks.org> Signed-off-by: Andy Green <andy@warmcat.com> Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net> [ben-linux@fluff.org: edit description for clarity and S3C2442B as uppercase] Signed-off-by: Ben Dooks <ben-linux@fluff.org>
2009-10-05Add glamo driver.Lars-Peter Clausen
2009-10-05Add atheros sdio ids.Lars-Peter Clausen
2009-10-05Select usb host device.Lars-Peter Clausen
2009-10-05Add s3c24xx_serial_console_set_silenceLars-Peter Clausen
2009-10-05Add power management devices.Lars-Peter Clausen
2009-10-05Add s3c pwm device driver.Lars-Peter Clausen
2009-10-05Add c fiq handler.Lars-Peter Clausen
2009-10-04ARM: gta02: Add gpio bank B quirk for hardware revision 5 and earlierLars-Peter Clausen
On hardware revision 5 and earlier the leds found on the gta02 are missing a resistor and reading their gpio pin status will always return 0. So we have to shadow the led states in software. This is done by "hijacking" the gpio accessor functions for bank B. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-10-04ARM: gta02: Add LED supportLars-Peter Clausen
The gta02 has three leds which are connected though gpio pins and thus can get supported by using the generic leds-gpio driver. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-10-04ARM: gta02: Add button supportLars-Peter Clausen
The gta02 has two buttons which are connected to gpio pins and thus can get supported by using the generic gpio-keys driver. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2009-10-04Add jbt6k74 display driver.Lars-Peter Clausen
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-01 08:33:39 +0000