From: Kevin Hilman khil...@ti.com
The omap_device layer currently has two ways of getting an omap_device
pointer from a platform_device pointer.
Replace current usage of _find_by_pdev() with to_omap_device() since
to_omap_device() is more familiar to the existing to_platform_device()
used when
From: Kevin Hilman khil...@ti.com
For consistency in kernel printk output for devices, use dev_dbg(),
dev_warn(), dev_err() instead of pr_debug(), pr_warning() and
pr_err(), some of which currently use direct access of name from
platform_device and others of which use dev_name(). Using the
From: Kevin Hilman khil...@ti.com
Board code should not touch omap_device internals. To get the MPU/IVA devices,
use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device().
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 27
From: Kevin Hilman khil...@ti.com
For converting from struct device to platform_device, and from
platform_device to struct device, there are existing macros. Use
them instead of manual use of container_of().
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/mcbsp.c |6
From: Kevin Hilman khil...@ti.com
The *_device_register() functions and the count/fill resources functions
are internal to omap_device and do not need to be in the header.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/omap_device.h |6 --
From: Kevin Hilman khil...@ti.com
All of the device init and device driver interaction with omap_device
is done using platform_device pointers. To make this more explicit,
have omap_device return a platform_device pointer instead of an
omap_device pointer.
All current users of the omap_device
From: Kevin Hilman khil...@ti.com
Add omap_device pointer to the ARM-specific arch data in the
platform_device. This will be used to attach OMAP-specific
device-data to the platform device with device lifetime.
Suggested-by: Russell King rmk+ker...@arm.linux.org.uk
Cc: Grant Likely
From: Tony Lindgren t...@atomide.com
As noted by Grant Likely grant.lik...@secretlab.ca, omap2+ Makefile
unnecessarily
repeats entries for common device init code instead of using Kconfig symbol.
Remove references to hsmmc.o and board-flash.o. Also omap_phy_internal.o
references can be removed
, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/devices.c |2 +-
arch/arm/mach-omap2/mcbsp.c |2 +-
arch/arm/plat-omap/include/plat/omap_device.h | 11 +-
arch/arm/plat-omap/omap_device.c | 53 ++---
4 files
Add pd_size in the AUXDATA structure so that device drivers which require
platform_data size can pass along with AUXDATA.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/of/platform.c |2 ++
include/linux/of_platform.h |5 +
2 files changed, 7 insertions(+), 0
Add omap3 soc file for handling omap3 soc i2c controllers existing
on l4-core bus.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi | 62 ++
1 files changed, 62 insertions(+), 0 deletions(-)
create mode 100644 arch
Update omap3 beagle dts file with required clock frequencies for the i2c
client devices existing on beagle board.
Beagle custom board dts file is cleaned up so that it can coexist with omap3
soc dts file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle
which provides basic platform for converting device drivers for
using dt.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/Kconfig | 11
arch/arm/mach-omap2/Makefile|1 +
arch/arm/mach-omap2/board-omap3-dt.c| 93
Adapt dt for omap i2c1 controller and remove legacy i2c
initilization in omap3 generic board file.
Tested on omap3 beagle board for dt and non-dt builds.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi |6 ++--
arch/arm/mach-omap2/board-omap3
Hi Benoit,
On Tue, Aug 09, 2011 at 11:23:20AM +0200, Cousson, Benoit wrote:
Hi Grant,
Trying to bind hwmod informations with DT, I'm facing a little limitation.
A bunch of drivers are using the platform_get_resource_byname, so
the name for the resource is needed.
The name is used so far
in
generic board file and hwmod device pointer will be scanned and attached
in notifier call.
Used 3.0 stable kernel version for this patch series since latest mainline
was broken for beagle boot last week.
git://git.secretlab.ca/git/linux-2.6.git
Branch: devicetree/test-3.0
G, Manjunath Kondaiah (6
From: Kevin Hilman khil...@ti.com
The omap_device layer currently has two ways of getting an omap_device
pointer from a platform_device pointer.
Replace current usage of _find_by_pdev() with to_omap_device() since
to_omap_device() is more familiar to the existing to_platform_device()
used when
From: Kevin Hilman khil...@ti.com
For consistency in kernel printk output for devices, use dev_dbg(),
dev_warn(), dev_err() instead of pr_debug(), pr_warning() and
pr_err(), some of which currently use direct access of name from
platform_device and others of which use dev_name(). Using the
From: Kevin Hilman khil...@ti.com
Board code should not touch omap_device internals. To get the MPU/IVA devices,
use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device().
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 27
From: Kevin Hilman khil...@ti.com
For converting from struct device to platform_device, and from
platform_device to struct device, there are existing macros. Use
them instead of manual use of container_of().
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/mcbsp.c |6
From: Kevin Hilman khil...@ti.com
The *_device_register() functions and the count/fill resources functions
are internal to omap_device and do not need to be in the header.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/omap_device.h |6 --
From: Kevin Hilman khil...@ti.com
All of the device init and device driver interaction with omap_device
is done using platform_device pointers. To make this more explicit,
have omap_device return a platform_device pointer instead of an
omap_device pointer.
All current users of the omap_device
From: Kevin Hilman khil...@ti.com
Add omap_device pointer to the ARM-specific arch data in the
platform_device. This will be used to attach OMAP-specific
device-data to the platform device with device lifetime.
Suggested-by: Russell King rmk+ker...@arm.linux.org.uk
Cc: Grant Likely
From: Tony Lindgren t...@atomide.com
As noted by Grant Likely grant.lik...@secretlab.ca, omap2+ Makefile
unnecessarily
repeats entries for common device init code instead of using Kconfig symbol.
Remove references to hsmmc.o and board-flash.o. Also omap_phy_internal.o
references can be removed
, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/devices.c |2 +-
arch/arm/mach-omap2/mcbsp.c |2 +-
arch/arm/plat-omap/include/plat/omap_device.h | 11 +-
arch/arm/plat-omap/omap_device.c | 53 ++---
4 files
Add omap3 soc file for handling omap3 soc i2c controllers existing
on l4-core bus.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi | 62 ++
1 files changed, 62 insertions(+), 0 deletions(-)
create mode 100644 arch
Update omap3 beagle dts file with required clock frequencies for the i2c
client devices existing on beagle board.
Beagle custom board dts file is cleaned up so that it can coexist with omap3
soc dts file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle
which provides basic platform for converting device drivers for
using dt.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/Kconfig | 11
arch/arm/mach-omap2/Makefile|1 +
arch/arm/mach-omap2/board-omap3-dt.c| 93
Adapt dt for omap i2c1 controller and remove legacy i2c
initilization in omap3 generic board file.
Tested on omap3 beagle board for dt and non-dt builds.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi |6 ++--
arch/arm/mach-omap2/board-omap3
Hi Benoit,
On Tue, Aug 09, 2011 at 11:23:20AM +0200, Cousson, Benoit wrote:
Hi Grant,
Trying to bind hwmod informations with DT, I'm facing a little limitation.
A bunch of drivers are using the platform_get_resource_byname, so
the name for the resource is needed.
The name is used so far
On Wed, Aug 10, 2011 at 10:56 AM, Rajendra Nayak rna...@ti.com wrote:
On 8/9/2011 7:40 PM, G, Manjunath Kondaiah wrote:
This is in continuation of patch series posted at:
http://lwn.net/Articles/451917/
Patches from Kevin Hilman and others are consolidated along with this
series since
Hi Benoit,
On Wed, Aug 3, 2011 at 8:34 PM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Grant,
Going further with the usage of OF_DEV_AUXDATA_ID, I realized that this is is
not doing what I was expecting. My expectation might be silly, but in order
to make platform_match to work without DT
Hi Benoit,
On Wed, Aug 3, 2011 at 8:34 PM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Grant,
Going further with the usage of OF_DEV_AUXDATA_ID, I realized that this is is
not doing what I was expecting. My expectation might be silly, but in order
to make platform_match to work without DT
Kevin,
On Thu, Jul 21, 2011 at 04:52:10PM -0700, Kevin Hilman wrote:
Here's a first whack, proof-of-concept on how we could start to
decouple the platform_device from an omap_device.
The main RFC is in the last patch, and everything leading up to it are
misc. omap_device cleanups that make
Kevin,
On Thu, Jul 21, 2011 at 04:52:10PM -0700, Kevin Hilman wrote:
Here's a first whack, proof-of-concept on how we could start to
decouple the platform_device from an omap_device.
The main RFC is in the last patch, and everything leading up to it are
misc. omap_device cleanups that make
On Wed, Jul 27, 2011 at 02:45:33PM -0700, Hilman, Kevin wrote:
Hi Manjunath,
On Wed, Jul 27, 2011 at 7:04 AM, G, Manjunath Kondaiah manj...@ti.com wrote:
Kevin,
On Thu, Jul 21, 2011 at 04:52:10PM -0700, Kevin Hilman wrote:
Here's a first whack, proof-of-concept on how we could start
Hi Grant,
On Wed, Jul 20, 2011 at 3:07 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Tue, Jul 19, 2011 at 11:28:53AM +0530, G, Manjunath Kondaiah wrote:
Grant/Kevin,
On Sun, Jul 17, 2011 at 10:43 AM, Grant Likely
grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I
On Tue, Jul 19, 2011 at 2:00 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Mon, Jul 18, 2011 at 5:53 AM, G, Manjunath Kondaiah
manj...@linaro.org wrote:
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add
On Tue, Jul 19, 2011 at 2:00 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Mon, Jul 18, 2011 at 5:53 AM, G, Manjunath Kondaiah
manj...@linaro.org wrote:
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add
On Tue, Jul 19, 2011 at 2:00 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Mon, Jul 18, 2011 at 5:53 AM, G, Manjunath Kondaiah
manj...@linaro.org wrote:
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add
Hi Grant,
On 17 July 2011 10:43, Grant Likely grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I left in a lot of context for the new folks that
I've cc'd (Tony and Kevin).
On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Jul 14, 2011 at 4
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add device node for i2c instance 1 and list all its connected slave
devices.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add device node for i2c instance 1 and list all its connected slave
devices.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
Hi Grant,
On 17 July 2011 10:43, Grant Likely grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I left in a lot of context for the new folks that
I've cc'd (Tony and Kevin).
On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Jul 14, 2011 at 4
Grant/Kevin,
On Sun, Jul 17, 2011 at 10:43 AM, Grant Likely
grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I left in a lot of context for the new folks that
I've cc'd (Tony and Kevin).
On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Jul
Abraham,
Few comments on i2c child devices handling:
On 18 July 2011 06:20, Thomas Abraham thomas.abra...@linaro.org wrote:
Add device node for i2c instance 1 and list all its connected slave
devices.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
---
ps: posting again since my mailer has triggered the mail in html format hence
it does not reach some mailing lists.
Hi Grant,
On Thu, Jul 14, 2011 at 4:45 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah manj...@ti.com
wrote
cleanly on top of:
git://git.secretlab.ca/git/linux-2.6
Branch: origin/devicetree/test
commit 88c559f5479ec28a1acd38c081d89f90a059a6ef
Author: Grant Likely grant.lik...@secretlab.ca
drivercore: Add driver probe deferral mechanism
G, Manjunath Kondaiah (4):
DT: OMAP3: Add SoC file for handling
registration through dt is disabled till hwmod dependencies
are resolved.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi | 65 ++
1 files changed, 65 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts
Update omap3 beagle dts file with required clock frequencies for the i2c
client devices existing on beagle board.
Beagle custom board dts file is cleaned up so that it can coexist with omap3
soc dts file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle
in the series will adopt i2c driver to use dt registered i2c
devices.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/Kconfig | 12 +
arch/arm/mach-omap2/Makefile|2 +
arch/arm/mach-omap2/board-omap3-dt.c| 623
The i2c-omap driver is converted for supporting both
dt and non dt builds and driver is modified to use dt
data partially.
Tested on OMAP3 beagle board.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 48 -
1
On Thu, Jul 14, 2011 at 07:57:16AM +0900, Grant Likely wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah manj...@ti.com wrote:
Add omap3 SoC file for handling omap3 SoC i2c controllers existing
on l4-core bus.
Out of three i2c controllers, first i2c controller is interfaced
On Thu, Jul 14, 2011 at 07:58:35AM +0900, Grant Likely wrote:
On Thu, Jul 14, 2011 at 7:57 AM, Grant Likely grant.lik...@secretlab.ca
wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah manj...@ti.com
wrote:
Add omap3 SoC file for handling omap3 SoC i2c controllers existing
cleanly on top of:
git://git.secretlab.ca/git/linux-2.6
Branch: origin/devicetree/test
commit 88c559f5479ec28a1acd38c081d89f90a059a6ef
Author: Grant Likely grant.lik...@secretlab.ca
drivercore: Add driver probe deferral mechanism
G, Manjunath Kondaiah (4):
DT: OMAP3: Add SoC file for handling
registration through dt is disabled till hwmod dependencies
are resolved.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi | 65 ++
1 files changed, 65 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts
Update omap3 beagle dts file with required clock frequencies for the i2c
client devices existing on beagle board.
Beagle custom board dts file is cleaned up so that it can coexist with omap3
soc dts file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle
in the series will adopt i2c driver to use dt registered i2c
devices.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/Kconfig | 12 +
arch/arm/mach-omap2/Makefile|2 +
arch/arm/mach-omap2/board-omap3-dt.c| 623
The i2c-omap driver is converted for supporting both
dt and non dt builds and driver is modified to use dt
data partially.
Tested on OMAP3 beagle board.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 48 -
1
On Thu, Jul 14, 2011 at 07:57:16AM +0900, Grant Likely wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah manj...@ti.com wrote:
Add omap3 SoC file for handling omap3 SoC i2c controllers existing
on l4-core bus.
Out of three i2c controllers, first i2c controller is interfaced
On Thu, Jul 14, 2011 at 07:58:35AM +0900, Grant Likely wrote:
On Thu, Jul 14, 2011 at 7:57 AM, Grant Likely grant.lik...@secretlab.ca
wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah manj...@ti.com
wrote:
Add omap3 SoC file for handling omap3 SoC i2c controllers existing
On Wed, Jul 06, 2011 at 12:57:12PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:24PM +0500, G, Manjunath Kondaiah wrote:
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock
On Wed, Jul 06, 2011 at 01:00:22PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:25PM +0500, G, Manjunath Kondaiah wrote:
The beagle board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch
On Wed, Jul 06, 2011 at 01:08:03PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:27PM +0500, G, Manjunath Kondaiah wrote:
The OMAP I2C driver is modified to use platform_device data from
device tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
On Wed, Jul 06, 2011 at 12:57:12PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:24PM +0500, G, Manjunath Kondaiah wrote:
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock
On Wed, Jul 06, 2011 at 01:00:22PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:25PM +0500, G, Manjunath Kondaiah wrote:
The beagle board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch
On Wed, Jul 06, 2011 at 01:08:03PM -0600, Grant Likely wrote:
On Thu, Jun 30, 2011 at 03:07:27PM +0500, G, Manjunath Kondaiah wrote:
The OMAP I2C driver is modified to use platform_device data from
device tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
manually in i2c driver and i2c driver will not work after
the probe due to non availability of clock for I2C controllers(Testing is
exempted for I2C1 since it interfaces with power chip).
G, Manjunath Kondaiah (5):
OMAP3:I2C: Add device tree nodes for beagle board
OMAP4:I2C: Add device tree nodes
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock changes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle-nunchuck.dts |5 ---
arch/arm/boot/dts
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock changes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 57
The OMAP4 panda board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach
The OMAP I2C driver is modified to use platform_device data from
device tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 30 +-
1 files changed, 29 insertions(+), 1 deletions(-)
diff --git a/drivers/i2c
The beagle board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 24
1 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach
manually in i2c driver and i2c driver will not work after
the probe due to non availability of clock for I2C controllers(Testing is
exempted for I2C1 since it interfaces with power chip).
G, Manjunath Kondaiah (5):
OMAP3:I2C: Add device tree nodes for beagle board
OMAP4:I2C: Add device tree nodes
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock changes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3-beagle-nunchuck.dts |5 ---
arch/arm/boot/dts
Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock changes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 57
The beagle board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 24
1 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach
The OMAP4 panda board file is updated to use i2c nodes from device
tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach
The OMAP I2C driver is modified to use platform_device data from
device tree data structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 30 +-
1 files changed, 29 insertions(+), 1 deletions(-)
diff --git a/drivers/i2c
Panda Testing update:
Booting on panda seems to be fine but sd/mmc dumps lot of I/O errors on
console.
Tested with device tree enabled and disabled. With device tree enable, the
MMC I/O
errors are more. Tried with multiple SD cards with different brands.
Not sure if there is any bug already
Hi Andy,
On Thu, May 26, 2011 at 2:04 PM, Andy Green a...@warmcat.com wrote:
On 05/26/2011 08:15 AM, Somebody in the thread at some point said:
Hi -
Panda Testing update:
Booting on panda seems to be fine but sd/mmc dumps lot of I/O errors on
console.
Tested with device tree enabled
On Thu, May 26, 2011 at 3:08 PM, Jassi Brar jassisinghb...@gmail.comwrote:
On Thu, May 26, 2011 at 2:50 PM, G, Manjunath Kondaiah manj...@ti.com
wrote:
Is your card really 1GB SD Card? Were any of the other cards SDHC?
yeah...it's Kingston 1GB card. I have only two cards with me now
Kevin/Paul,
On Mon, Mar 28, 2011 at 07:56:58PM +0530, G, Manjunath Kondaiah wrote:
Patch series to support mstandby mode handling and enabling runtime PM
support for DMA driver.
If you don't have further comments, can you pls ack these patches for
merging?
-Manjunath
[...]
--
To unsubscribe
details on testing is available at:
http://article.gmane.org/gmane.linux.ports.arm.omap/54753
G, Manjunath Kondaiah (4):
OMAP2+: PM: omap device: API's for handling mstandby mode
OMAP2+: DMA: prevent races while setting M idle mode to nostandby
OMAP: PM: DMA: Enable runtime pm
OMAP: DMA: Fix
/366831/
Patch reworked to use API implemented at hwmod layer.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
arch/arm/mach-omap1/dma.c |1 +
arch/arm/mach-omap2/dma.c | 16 +
arch/arm/plat-omap
after completing the data transfer operation.
Applicable only for OMAP3430 ES1.0
Also fixes typo HWMOD_SWSUP_MSTDBY to HWMOD_SWSUP_MSTANDBY in
omap_hwmod.h
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/omap_hwmod.c | 42 +
arch/arm/plat
it will be handled through hwmod layer.
Tested on OMAP3430 Zoom2 with
- off mode enabled
- one time DMA channel configuration
- repeated DMA transfers
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/plat-omap/dma.c |9 -
1 files changed, 0 insertions(+), 9
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/plat-omap/dma.c | 147 --
1 files changed, 141 insertions(+), 6 deletions(-)
diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
index 5af9bb2..3c39794 100644
--- a/arch/arm/plat
On Wed, Mar 23, 2011 at 10:46:35PM -0600, Paul Walmsley wrote:
Hi
comments below
On Thu, 24 Mar 2011, G, Manjunath Kondaiah wrote:
Certain errata in OMAP2+ processors will require forcing
master standby to no standby mode before completing on going
operation. Without
Kevin,
On Sat, Mar 19, 2011 at 08:46:05AM +0530, G, Manjunath Kondaiah wrote:
On Fri, Mar 18, 2011 at 11:27:00AM -0700, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
On Thu, Mar 17, 2011 at 02:29:18PM -0700, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com
it will be handled through hwmod layer.
Tested on OMAP3430 Zoom2 with
- off mode enabled
- one time DMA channel configuration
- repeated DMA transfers
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/plat-omap/dma.c |9 -
1 files changed, 0 insertions(+), 9
-for-linus
commit 05f689400ea5fa3d71af82f910c8b140f87ad1f3
Merge branches 'devel-mux' and 'devel-misc' into omap-for-linus
G, Manjunath Kondaiah (4):
OMAP2+: PM: omap device: API's for handling mstandby mode
OMAP2+: DMA: prevent races while setting M idle mode to nostandby
OMAP: PM: DMA
/366831/
Patch reworked to use API implemented at hwmod layer.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
arch/arm/mach-omap1/dma.c |1 +
arch/arm/mach-omap2/dma.c | 16 +
arch/arm/plat-omap
after completing the data transfer operation.
Applicable only for OMAP3430 ES1.0
Also fixes typo HWMOD_SWSUP_MSTDBY to HWMOD_SWSUP_MSTANDBY in
omap_hwmod.h
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/omap_hwmod.c | 42
arch/arm/plat
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/plat-omap/dma.c | 147 --
1 files changed, 141 insertions(+), 6 deletions(-)
diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
index 5af9bb2..3c39794 100644
--- a/arch/arm/plat
On Fri, Mar 18, 2011 at 11:27:00AM -0700, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
On Thu, Mar 17, 2011 at 02:29:18PM -0700, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
Patch series to support mstandby mode handling and enabling runtime PM
On Thu, Mar 17, 2011 at 02:08:34PM -0700, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
The current DMA context restore clears all the DMA channel registers
even if the channels are in use. This will result in transfer failures
if repeated DMA transfers are initiated
On Wed, Mar 16, 2011 at 07:37:10PM +0530, G, Manjunath Kondaiah wrote:
On Mon, Mar 14, 2011 at 12:25:38PM -0700, Tony Lindgren wrote:
Hi all,
I've applied few random fix like patches today into omap-for-linus
but that's it for this merge window.
So let's do some testing
Hi Kevin,
On Fri, Mar 11, 2011 at 07:50:11PM +0530, G, Manjunath Kondaiah wrote:
Patch series to support mstandby mode handling and enabling runtime PM
support for DMA driver.
Changes from v1:
- fixed runtime_status issue if channel linking feature is used.
- fixed context restore issue
On Fri, Mar 11, 2011 at 11:05:25AM +0530, DebBarma, Tarun Kanti wrote:
[...]
* Tarun Kanti DebBarma tarun.ka...@ti.com [110308 15:41]:
switch-over to platform device driver through following changes:
(a) initiate dmtimer early initialization from omap2_gp_timer_init()
in
101 - 200 of 536 matches
Mail list logo
