-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Friday, September 17, 2010 11:21 PM
To: Shilimkar, Santosh
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: Re: [PATCH 00/14] omap sram, omap4 control module and es2.0
support
Hello
On Sat, Sep 18, 2010 at 5:11 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Govindraj.R govindraj.r...@ti.com writes:
This patch series adds a serial driver to handle uarts on omap platforms.
Currenlty omap-uarts are handled with 8250 driver, since updating
this driver with omap specific
On Sat, Sep 18, 2010 at 5:13 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Govindraj.R govindraj.r...@ti.com writes:
From: Kevin Hilman khil...@ti.com
Major rework of OMAP UART init for omap_device conversion as well as
use with either 8250 driver or new omap-serial driver.
In
On Fri, Sep 17, 2010 at 05:37:06PM -0700, Kevin Hilman wrote:
[trimmed Cc list a bit, as vger bounced my last reply due to header too long]
Mark Brown broo...@opensource.wolfsonmicro.com writes:
The enable/disable thing wasn't so noticable in the API itself, it was
in the data structures
On Fri, Sep 17, 2010 at 07:45:43PM +0300, Phil Carmody wrote:
On 17/09/10 17:36 +0200, ext Mark Brown wrote:
It might be clearer to use some term other than enabled in the code -
when reading I wasn't immediately sure if enabled meant that it was
available to be selected or if it was the
Hi Thara,
On 9/17/2010 4:55 PM, Gopinath, Thara wrote:
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Thursday, September 16, 2010 8:58 PM
Gopinath, Tharath...@ti.com writes:
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, September 03, 2010 5:12 AM
This patch introduces platform_data structure for
GPIO so that GPIO module can be implemented in
platform device model.
This patch also adds support for handling OMAP15xx
specific gpio_init by providing platform device data
and doing device registration.
Signed-off-by: Charulatha V ch...@ti.com
This patch series makes OMAP2PLUS specific GPIO implemented in hwmod
FW way. This is done by implementing GPIO module in platform device model.
This patch series is generated on origin/pm-wip/pm-core which
has Kevin's pm-next series, the runtime PM core patch series,
and a collection of hwmod
gpio_context array, which is used to save gpio bank's context,
is used only for OMAP3 architecture.
This patch moves gpio_context as part of gpio_bank structure
so that it can be specific to each gpio bank and can be
used for any OMAP architecture
Signed-off-by: Charulatha V ch...@ti.com
---
This patch implements GPIO as a platform device.
GPIO APIs are used in machine_init functions. Hence it is
required to complete GPIO probe before board_init. Therefore
GPIO device register and driver register are implemented as
postcore_initcalls.
Inorder to convert GPIO as platform device,
This patch adds support for handling OMAP7xx specific gpio_init
by providing platform device data and doing device registration.
Signed-off-by: Charulatha V ch...@ti.com
---
arch/arm/mach-omap1/gpio7xx.c | 274 +
1 files changed, 274 insertions(+), 0
Use omap_device_build() API instead of platform_device_register for
GPIO device registration. For OMAP2PLUS chips, the device specific
data defined in centralized hwmod database will be used.
gpio_init needs to be done before machine_init functions access
gpio APIs. Hence gpio_init is made as a
Add GPIO hwmod data for OMAP3 chip
Signed-off-by: Charulatha V ch...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 364
1 files changed, 364 insertions(+), 0 deletions(-)
diff --git
From: Benoit Cousson b-cous...@ti.com
Add GPIO hwmod data for OMAP4 chip
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Charulatha V ch...@ti.com
---
This patch is extracted from the below patch sent by Benoit
OMAP4: hwmod: Add partial hwmod support for OMAP4430 ES1.0
This patch also adds support for handling OMAP16xx
specific gpio_init by providing platform device data
and doing device registration.
Signed-off-by: Charulatha V ch...@ti.com
---
arch/arm/mach-omap1/gpio16xx.c | 208
1 files changed, 208 insertions(+),
Add GPIO hwmod data for OMAP2430 chip
Signed-off-by: Charulatha V ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 273
1 files changed, 273 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_2430_data.c
Add GPIO hwmod data for OMAP2420 chip
Signed-off-by: Charulatha V ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 227
1 files changed, 227 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_2420_data.c
This is in prepartion for implementing GPIO as a platform device.
gpio bank's base addresses are moved from gpio.c to plat/gpio.h.
This patch also modifies omap_gpio_init() to make use of
omap_gpio_chip_init() and omap_gpio_mod_init(). omap_gpio_mod_init() does
the module init by clearing the
Call runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks, sysconfig settings instead of using
clock FW APIs.
Note: OMAP16xx OMAP2 has interface and functional clocks whereas
OMAP34 has interface and debounce clocks.
GPIO driver is modified to use
This patch removes the usage of omap_gpio_init() from all
omap board files since omap_gpio_init() does nothing, after gpio
is implemented as a platform device.
Signed-off-by: Charulatha V ch...@ti.com
---
arch/arm/mach-omap1/board-ams-delta.c |1 -
arch/arm/mach-omap1/board-fsample.c
The patch series is basically for OMAP4 and is based on mainline 2.6.36-rc4.
The series is tested on OMAP3430SDP and OMAP4430SDP and has dependency on
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg34718.html
V1:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg34040.html
Adding card detect callback function and card detect configuration
function for MMC1 Controller.
Card detect configuration function does initial configuration of the
MMC Control PullUp-PullDown registers of Phoenix.
For MMC1 Controller, Card detect interrupt source is
twl6030 and the card
From: Benoit Cousson b-cous...@ti.com
Avoid possible crash if CONFIG_MMC_OMAP_HS is not set
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Kishore Kadiyala kishore.kadiy...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c |8 +++-
1 files changed, 7 insertions(+), 1
The offset handling implementation of omap4 mmc registers which
was already present can't be reused once hwmod modifications are done
for mmc driver.
Since hwmod data file for OMAP4 is an auto generated the base
address for MMC will remain same as OMAP3 and thus the offset deviation
of registers
On OMAP4, MMC2 controller has eMMC which draws power from VAUX regulator
on TWL. Though the eMMC supports dual voltage[1.8v/3v] as per ocr register,
its VCC is fixed at 3V for operation. With this once the mmc core selects
the minimum voltage supported based on the ocr value read from OCR
Tony,
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, September 17, 2010 11:25 PM
To: Ghorai, Sukumar
Cc: linux-omap@vger.kernel.org; linux-...@lists.infradead.org; linux-arm-
ker...@lists.infradead.org; Vimal Singh
Subject: Re: [PATCH RESEND v4 1/4]
[Trimming the CC list.]
On Saturday, September 18, 2010, Nishanth Menon wrote:
Rafael J. Wysocki had written, on 09/17/2010 06:07 PM, the following:
...
Apart from this, it might be a good idea to help callers a bit and actually
introduce some sort of locking into the framework.
in OMAP
[Trimming the CC list]
On Saturday, September 18, 2010, Nishanth Menon wrote:
Rafael J. Wysocki had written, on 09/17/2010 05:45 PM, the following:
Thanks for your review. few views below..
On Friday, September 17, 2010, Nishanth Menon wrote:
Nishanth Menon had written, on 09/17/2010
28 matches
Mail list logo
