Age | Commit message (Collapse) | Author |
|
Adds support for MMC 3, 4, 5 support on OMAP4
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
Enables power saving option
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
As a part of hwmod framework, hsmmc host driver is updated with
hwmod clock enable and idle calls.
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
Making OMAP4 and OMAP3 specific hwmod data naming convensiongeneric , thereby
following same hwmod_name for MMC controllers.
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
The OMAP4 and OMAP3 MMC controllers has an offset difference of
0x100 which is updated in hwmod data.
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
The attribute flags are updated in hwmod data for specific MMC
controller.The same can be used to check the capabilites of the
controller
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
Convert the HSMMC driver to use the runtime PM layer. A notable
aspect of this is that the use of the dev_attr data from the
omap_hwmod allows the redaction of all of the integration-specific
hacks inside this driver. Regulator control has not yet been
converted; the driver still uses the platform_data set_power hook.
In converting to runtime PM layer, the clock frameworks is no longer
used for fclk and iclk. Instead, the runtime PM get and put functions
are used. These result in calls into the OMAP runtime PM core which
internally uses the omap_device API to disable/re-enable the device.
(Note that the 2430 debounce clock is not currently handled here,
only the fclk and iclk are managed.)
Based on an initial conversion of this driver to use omap_device by
by Paul Walmsely: http://marc.info/?l=linux-omap&m=124419789124570&w=2
and then converted to use runtime PM API instead of omap_device API.
The omap_hsmmc driver has some hacks in this version to compensate for
the fact that the main runtime PM core prevents runtime transitions
during suspend. This prevens us from using common hooks for runtime
PM and static PM. Current workaround is to hack in some extra put/get
calls in the suspend/resume path while this issue is being discussed
on linux-pm.
Cc: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
Split OMAP-common MMC device registration into OMAP1 and OMAP2
components. This is in preparation for the omap_device conversion of
the HSMMC portions.
Original version by Paul: http://marc.info/?l=linux-omap&m=124419789024565&w=2
Updated for current linux-omap by Kevin.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
Convert PM operations to use dev_pm_ops. This will facilitate
the runtime PM coversion which will add to dev_pm_ops hooks.
Note that dev_pm_ops version of the suspend hook no longer takes a
'state' argument. However, the MMC core function mmc_suspend_host()
still takes a 'state' argument, but it is unused, so a dummy
state variable was created to pass to the MMC core.
In the future, the MMC core should be converted to drop this
state argument and the rest of the MMC drivers could be easily
converted to dev_pm_ops as well.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
The integration data is so similar between 2430 and 34xx in this
case that these entries could almost be shared; that is probably worth
investigating.
Updated against recent hwmod changes by Kevin Hilman
Updated 2430 hwmod against recent hwmod changes by Rajendra Nayak
Compile fixes for 2430 by charulatha V <charu@ti.com>
Cc: Charulatha V <charu@ti.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
|
|
This reverts commit 907ff9a993eb51c8e9613015fa9fd8f8a841b7ae.
Regression with suspend
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
remove unnessesary noice in omap_device and omap_hwmod
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
|
|
Use runtime api's in omap i2c driver, if CONFIG_PM_RUNTIME
is not defined the driver still using omap_device/hwmod api's.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
|
|
As part of the runtime PM support, bus-level code can automatically
handle the enable/idle for each omap_device. There are, however, some
special cases where we don't want the bus-level layer to handle this,
and instead handle it manually.
Specific use cases are for omap_devices that are controlled
inside the idle path (like UART.)
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
|
|
Hook into the platform bus methods for suspend and resume and
use the omap_device API to automatically idle and enable the
device on suspend and resume.
This allows device drivers to get rid of direct management of their
clocks in their suspend/resume paths, and let omap_device do it for
them.
We currently use the _noirq (late suspend, early resume) versions of
the suspend/resume methods to ensure that the device is not disabled
too early for any drivers also using the _noirq methods.
NOTE: only works for devices with omap_hwmod support.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
|
|
Implement the new runtime PM framework as a thin layer on top of the
omap_device API. Since we don't have an OMAP-specific bus, override
the runtime PM hooks for the platform_bus for the OMAP specific
implementation.
While the runtime PM API has three main states (idle, suspend, resume)
This version treats idle and suspend the same way by implementing both
on top of omap_device_disable(), which follows closely with how driver
are currently using clock enable/disable calls. Longer-termm
pm_runtime_idle() could take other constraints into consideration to
make the decision, but the current
Device driver ->runtime_suspend() hooks are called just before the
device is disabled (via omap_device_idle()), and device driver
->runtime_resume() hooks are called just after device has been
enabled (via omap_device_enable().)
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
|
|
When runtime PM for platform_bus was added, it allowed for platforms
to customize the runtime PM methods since they are defined as weak
symbols.
This patch allows platforms to also extend the system PM methods with
custom hooks so runtime PM and system PM extensions can be managed
together by custom platform-specific code.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Magnus Damm <damm@opensource.se>
Cc: Rafael Wysocki <rjw@sisk.pl>
Cc: Dmitry Torokhov <dtor@mail.ru>
Cc: Eric Miao <eric.y.miao@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
Signed-off-by: Hemanth V <hemanthv@ti.com>
|
|
OMAP4 platform has different register bits for Warm and Cold Resets.
Write one into appropriate bits.
Signed-off-by: Rajeev Kulkarni <rajeevk@ti.com>
Signed-off-by: Benoit Cousson <b-cousson@ti.com>
Cc: Leed Aguilar <leed.aguilar@ti.com>
|
|
Update omap_4430sdp_defconfig to enable TWL6030 BCI, BQ24156, GPADC
and power supply class
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
Create bq2415x_charger.c for BQ24156 AC charger
BQ24156 interacts with TWL6030 for AC charger detection and
charge control
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
add support for RealTime GPADC conversion and return result via
callback function provided
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
This patch add support
for backup battery charging
to measure vbus voltage and id level via sysfs
to control fuel gauge mode via sysfs
to measure average current
charge_src - sysfs to select AC (=3) or USB (=2) charging
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
This patch adds support for the battery charging component of the
Phoenix IC. It enables charging via USB.
Following patches are folded into this patch
MFD: TWL6030: Add twl6030_bci as child to twl
ARM: OMAP4: Add platform data for TWL6030 BCI
POWER: TWL6030: Enable BCI in Kconfig and Makefile
MFD: TWL6030: Add AC charger support to TWL6030
Reconfig AC and USB for high current of 1500mA
replace printk by pr_debug in twl6030 bci
fix crash due to rmmod of twl6030_bci_battery
Signed-off-by: Nishant Kamat <nskamat@ti.com>
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
This patch adds support for the General Purpose A/D Convertor in TWL6030.
This driver is based on the twl4030-madc driver written by Mikko Ylinen
and Filipe Balbi, and currently has a 'misc' device interface. It needs
to be moved to drivers/hwmon as per comments from the community on the
twl4030-madc driver.
Following patches are folded into this patch
MFD: TWL6030: Add gpadc as child to twl
ARM: OMAP4: Add platform data for TWL6030 GPADC
MFD: TWL6030: Enable gpadc in Kconfig and Makefile
Signed-off-by: Nishant Kamat <nskamat@ti.com>
Signed-off-by: Balaji T K <balajitk@ti.com>
|
|
The MMC1 and MMC2 cards have seperate LDO supplies. Current code assumes
that they are powered by same LDO.
This patch fixes the same and has VAUX1 as supply to MMC2 card.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Sukumar Ghorai <s-ghorai@ti.com>
Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
Tested-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
|
|
This reverts commit 11ee9e1f7ac77757b1b7b12fee70c23a89163686.
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
|
|
Dma channels are allocated in musb_gadget_enable function.
Mentor has only 8 dma channels against 31 endpoints.If there are
multiple gadgets(g_multi) using multiple endpoints enable the endpoints
but not doing the data trasnfers,then other endpoints endup using PIO mode.
The effective utilization of DMA channels will be done by allocating
the dma channels during data transfer request and releasing when the
request completes.
Signed-off-by: Hema HK <hemahk@ti.com>
Cc: Felipe Balbi <felipe.balbi@nokia.com>
|
|
Buffer is mapped to dma when dma channel is allocated. buffer needs
to be unmapped when fallback to PIO mode if dma channel_program
fails.
Signed-off-by: Hema HK <hemahk@ti.com>
|
|
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
By default "unix socket" support is not enabled in 4430 defconfig.
Without this option, most of daemons are falling (udevd,dbus-demaon,etc)
during the boot.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
Sync up code with latest comments from Linux Input mailing list
http://www.spinics.net/lists/linux-omap/msg30745.html
Signed-off-by: Abraham Arce <x0066660@ti.com>
|
|
|
|
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
|
|
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
|
|
Adds the driver support for the TMP105 temperature sensor device. The
interface is I2C.The driver supports the read of the temperature values.
Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
|
|
This reverts commit 67e4684e4b9236b667487678be3e3a92e785e206.
Regression in BT stack
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
The current DMA code is expected the DMA request line to start at 1,
whereas the information in the HW data based start at 0.
Add the offset to the DMA request lines for the moment.
In the future, the DMA code might be revisited in order to take
into acccount that offset directly in the code.
Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Benoit Cousson <b-cousson@ti.com>
|
|
Remove temporary hack added to avoid uart clocks
from being disabled.
Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
|
|
This patch ensures uart port which is active should
enable the clocks if disabled during init. Currenlty the
complete framework is binded with CONIFG_PM. But if clocks
are disabled by any other mneans from hwmod_idle or
omap_device_idle then we need to enable them back using
shared interrupt handler for which the mechanism is currenlty
available in serial layer.
Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
|
|
This patch corrects some of the OMAP3 gptimer hwmod data so that they are
in sync with those in OMAP4 data base and enables OMAP3 boot up.
Signed-off-by: Thara Gopinath <thara@ti.com>
|
|
Signed-off-by: Hemanth V <hemanthv@ti.com>
|
|
Updated 4430 SDP board file for BH1780 Ambient light sensor driver
Signed-off-by: Hemanth V <hemanthv@ti.com>
|
|
This patch adds support for ROHM BH1780GLI Ambient light sensor.
BH1780 supports I2C interface. Driver supports read/update of power state and
read of lux value (through SYSFS). Writing value 3 to power_state enables the
sensor and current lux value could be read.
Signed-off-by: Hemanth V <hemanthv@ti.com>
Reviewed-by: Daniel Mack <daniel@caiaq.de>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
|
|
This was missed in commit "74efcf6c". Also sync up the
defconfig with .config
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
|
|
This patch enables omap-serial by default and sets
dma mode for UART2 used by bluetooth.
Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
|
|
On SMP systems, there is a small chance of a PTE becoming visible to a
different CPU before the cache maintenance operations in
update_mmu_cache(). This patch clears the L_PTE_EXEC bit in set_pte_at()
but sets it later in update_mmu_cache() if vm_flags & VM_EXEC.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
|
Signed-off-by: Hemanth V <hemanthv@ti.com>
|