On Fri, Oct 07, 2011 at 04:09:38PM -0600, Grant Likely wrote:
On Fri, Oct 7, 2011 at 4:06 AM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
On Fri, 07 Oct 2011 10:33:09 +0500
G, Manjunath Kondaiah manj...@ti.com wrote:
The gpio library should return -EPROBE_DEFER in gpio_request
if gpio
, Grant Likely said:
On Fri, Oct 7, 2011 at 12:43 AM, Greg KH g...@kroah.com wrote:
On Fri, Oct 07, 2011 at 10:33:06AM +0500, G, Manjunath Kondaiah
wrote:
+#define EPROBE_DEFER 517 /* restart probe again after some
time */
Can we really do
On Mon, Oct 10, 2011 at 10:37:22AM -0700, Andrei Warkentin wrote:
Hi,
- Original Message -
From: Greg KH g...@kroah.com
To: Josh Triplett j...@joshtriplett.org
Cc: G, Manjunath Kondaiah manj...@ti.com,
linux-arm-ker...@lists.infradead.org, Grant Likely
grant.lik
Hi Greg,
On Thu, Oct 06, 2011 at 11:50:42PM -0700, Greg KH wrote:
On Fri, Oct 07, 2011 at 10:33:05AM +0500, G, Manjunath Kondaiah wrote:
Why did you send this series of patches out twice? Were they different?
confused,
Looks like this patch series has reached only individual recepients
On Tue, Oct 04, 2011 at 05:35:04PM -0600, Grant Likely wrote:
On Wed, Oct 05, 2011 at 12:05:16AM +0530, G, Manjunath Kondaiah wrote:
On Tue, Oct 04, 2011 at 09:58:10AM -0600, Grant Likely wrote:
On Tue, Oct 4, 2011 at 8:51 AM, G, Manjunath Kondaiah manj...@ti.com
wrote:
On Thu, Sep
The gpio library should return -EPROBE_DEFER in gpio_request
if gpio driver is not ready. If drivers pass this error code through to
their caller (which they really should) then this will ensure that the
probe is retried later when further devices become available.
Signed-off-by: G, Manjunath
Existing omap hsmmc driver uses platform_driver_probe in init
function. Change it to use platform_driver_register in order to
use deferral probe mechanism.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Reported-by: Grant Likely grant.lik...@secretlab.ca
---
Cc: linux-omap@vger.kernel.org
HSMMC and GPIO drivers are adopted to use
deferral probe mechanism and successfully tested on omap3 beagle
board.
Applies cleanly on top of v3.1-rc8
G, Manjunath Kondaiah (3):
drivercore: add new error value for deferred probe
gpiolib: handle deferral probe error
omap: hsmmc: use
Add new error value so that drivers can request deferred probe
from drivercore.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Reported-by: Grant Likely grant.lik...@secretlab.ca
---
Cc: linux-omap@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: Grant
to be retried after a few more other drivers get probed.
Original patch posted by Grant Likely grant.lik...@secretlab.ca at:
http://lwn.net/Articles/460522/
Enhancements to original patch by G, Manjunath Kondaiah manj...@ti.com
- checkpatch warning fixes
- added Kconfig symbol CONFIG_PROBE_DEFER
.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
[manj...@ti.com: changed error value from EAGAIN to EPROBE_DEFER]
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Acked-by: Liam Girdwood l...@ti.com
---
Cc: linux-omap@vger.kernel.org
HSMMC and GPIO drivers are adopted to use
deferral probe mechanism and successfully tested on omap3 beagle
board.
Applies cleanly on top of v3.1-rc8
G, Manjunath Kondaiah (3):
drivercore: add new error value for deferred probe
gpiolib: handle deferral probe error
omap: hsmmc: use
Add new error value so that drivers can request deferred probe
from drivercore.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Reported-by: Grant Likely grant.lik...@secretlab.ca
---
Cc: linux-omap@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: Grant
to be retried after a few more other drivers get probed.
Original patch posted by Grant Likely grant.lik...@secretlab.ca at:
http://lwn.net/Articles/460522/
Enhancements to original patch by G, Manjunath Kondaiah manj...@ti.com
- checkpatch warning fixes
- added Kconfig symbol CONFIG_PROBE_DEFER
.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
[manj...@ti.com: changed error value from EAGAIN to EPROBE_DEFER]
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Acked-by: Liam Girdwood l...@ti.com
---
Cc: linux-omap@vger.kernel.org
The gpio library should return -EPROBE_DEFER in gpio_request
if gpio driver is not ready. If drivers pass this error code through to
their caller (which they really should) then this will ensure that the
probe is retried later when further devices become available.
Signed-off-by: G, Manjunath
Existing omap hsmmc driver uses platform_driver_probe in init
function. Change it to use platform_driver_register in order to
use deferral probe mechanism.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Reported-by: Grant Likely grant.lik...@secretlab.ca
---
Cc: linux-omap@vger.kernel.org
Hi Grant,
On Thu, Sep 22, 2011 at 12:51:23PM -0600, Grant Likely wrote:
Allow drivers to report at probe time that they cannot get all the resources
required by the device, and should be retried at a later time.
This should completely solve the problem of getting devices
initialized in the
On Tue, Oct 04, 2011 at 09:58:10AM -0600, Grant Likely wrote:
On Tue, Oct 4, 2011 at 8:51 AM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Sep 22, 2011 at 12:51:23PM -0600, Grant Likely wrote:
Hi Manjunath,
Here's the current state of the patch. The major think that needs
, that board will
be converted to an even more generic board-dt.c that will support
every OMAP2+ platforms.
Based on original patch from Manju:
http://www.spinics.net/lists/linux-omap/msg55832.html
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: G, Manjunath
Hi Benoit,
On Thu, Sep 01, 2011 at 07:34:11PM +0200, Cousson, Benoit wrote:
Hi Manju,
On 8/23/2011 5:46 PM, G, Manjunath Kondaiah wrote:
Hi Grant,
[...]
This function calls of_i2c_register_devices which attaches all the required
parameters reg, irq, archdata etc into i2c adapter
On Tue, Aug 23, 2011 at 01:53:54PM +0530, Rajendra Nayak wrote:
On 8/23/2011 10:33 AM, G, Manjunath Kondaiah wrote:
Add omap4 soc dts file for handling omap4 soc i2c
controllers existing on l4-core bus.
Signed-off-by: G, Manjunath Kondaiahmanj...@ti.com
---
arch/arm/boot/dts/omap4
On Tue, Aug 23, 2011 at 03:48:15PM +0200, Cousson, Benoit wrote:
From: G, Manjunath Kondaiahmanj...@ti.com
To: devicetree-disc...@lists.ozlabs.org
CC: linux-omap@vger.kernel.org, linux-arm-ker...@lists.infradead.org
Add omap4 soc dts file for handling omap4 soc i2c
controllers existing on
this.
-M
Jamie
On Tue, Aug 23, 2011 at 10:03:35AM +0500, G, Manjunath Kondaiah wrote:
The omap devices will use HWMOD for fetching device information
hence it needs to be handled seperately during platform bus
creation during dt build.
Signed-off-by: G, Manjunath Kondaiah manj
On Tue, Aug 23, 2011 at 03:05:01PM +0200, Cousson, Benoit wrote:
From: G, Manjunath Kondaiahmanj...@ti.com
The generic board file is created and derived from omap4 panda board file.
The changes here focus on minimal configuration to boot panda board with
dt enabled which provides basic
On Tue, Aug 23, 2011 at 10:03:28AM +0500, G, Manjunath Kondaiah wrote:
Patch series reworked from:
http://permalink.gmane.org/gmane.linux.ports.arm.omap/61674
Also added support for i2c1 controller on omap4 based panda
board.
Baseline:
=
git://git.secretlab.ca/git/linux-2.6.git
Hi Grant,
On Tue, Aug 23, 2011 at 10:03:36AM +0500, G, Manjunath Kondaiah wrote:
The device tree support has been added to i2c1 controller and
corresponding i2c initilization in generic board file is cleaned
up so that platfom device is registered through dt and omap device
and not through
Hi Benoit,
On Wed, Aug 24, 2011 at 12:33 AM, Cousson, Benoit b-cous...@ti.com wrote:
From: G, Manjunath Kondaiahmanj...@ti.com
To: devicetree-disc...@lists.ozlabs.org
CC: linux-omap@vger.kernel.org, linux-arm-ker...@lists.infradead.org
Update omap4 panda dts file with required clock
: OMAP3530 Beagle Board and OMAP4430 Panda board
Limitation:
===
The current implementation of omap-device build through
device tree supports only single instance of hwmod and
multiple instances are not supported.
G, Manjunath Kondaiah (13):
OMAP: omap_device: Add device tree node pointer
dt
.
Signed-off-by: G, 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 | 46
Add pd_size in the AUXDATA structure so that omap HWMOD 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.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| 84
Add omap-device to the i2c controllers compatible property.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap3.dtsi |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index
The omap devices will use HWMOD for fetching device information
hence it needs to be handled seperately during platform bus
creation during dt build.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
drivers/of/platform.c | 41 -
1 files changed
functionality
is retained.
Tested with dt and non dt builds and boot tested on beagle board.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap3-dt.c | 14 +++---
drivers/i2c/busses/i2c-omap.c| 23 ---
2 files changed, 27
Add omap4 soc dts file for handling omap4 soc i2c
controllers existing on l4-core bus.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts |7 +---
arch/arm/boot/dts/omap4.dtsi | 68 +
2 files changed, 69
Update omap4 panda dts file with required clock frequencies
for the i2c client devices existing on panda board.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/arch
The generic board file is created and derived from omap4 panda board file.
The changes here focus on minimal configuration to boot panda board with
dt enabled which provides basic platform for converting device drivers for
using dt.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch
Enable dt support for omap4 i2c1 controller and cleanup
legacy i2c device registration in omap4 generic board file.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
arch/arm/mach-omap2/board-omap4-dt.c | 21 +++--
1 files changed, 15 insertions(+), 6 deletions(-)
diff
Add documentation for using omap i2c controller with device
tree support enabled.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
---
Documentation/devicetree/bindings/i2c/omap-i2c.txt | 57
1 files changed, 57 insertions(+), 0 deletions(-)
create mode 100644
On Wed, Aug 10, 2011 at 07:45:42PM +0200, Cousson, Benoit wrote:
+ Tony
On 8/10/2011 6:57 PM, G, Manjunath Kondaiah wrote:
On Wed, Aug 10, 2011 at 02:36:50PM +0200, Cousson, Benoit wrote:
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
Add omap3 soc file for handling omap3 soc i2c
On Wed, Aug 10, 2011 at 09:58:46PM +0530, G, Manjunath Kondaiah wrote:
On Wed, Aug 10, 2011 at 01:51:47PM +0200, Cousson, Benoit wrote:
Hi Manju,
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
The omap dt requires new omap hwmod api to be added for in order
to support omap dt
On Wed, Aug 10, 2011 at 02:57:21PM +0200, Cousson, Benoit wrote:
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
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
On Wed, Aug 10, 2011 at 11:09 AM, Rajendra Nayak rna...@ti.com wrote:
On 8/10/2011 11:00 AM, G, Manjunath Kondaiah wrote:
On Wed, Aug 10, 2011 at 10:56 AM, Rajendra Nayakrna...@ti.com wrote:
On 8/9/2011 7:40 PM, G, Manjunath Kondaiah wrote:
This is in continuation of patch series posted
On Wed, Aug 10, 2011 at 07:16:30AM -0600, Grant Likely wrote:
On Wed, Aug 10, 2011 at 5:57 AM, Cousson, Benoit b-cous...@ti.com wrote:
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
Add pd_size in the AUXDATA structure so that device drivers which require
platform_data size can pass
On Wed, Aug 10, 2011 at 12:15:50PM +0200, Cousson, Benoit wrote:
Manju,
On 8/10/2011 9:07 AM, Jarkko Nikula wrote:
Hi
On Tue, 09 Aug 2011 19:10:22 +0500
G, Manjunath Kondaiahmanj...@ti.com wrote:
From: Kevin Hilmankhil...@ti.com
For converting from struct device to platform_device,
On Wed, Aug 10, 2011 at 01:51:47PM +0200, Cousson, Benoit wrote:
Hi Manju,
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
The omap dt requires new omap hwmod api to be added for in order
to support omap dt.
Both the subject and the changelog are misleading. You are not doing
any
On Wed, Aug 10, 2011 at 02:42:56PM +0200, Cousson, Benoit wrote:
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
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
On Wed, Aug 10, 2011 at 02:36:50PM +0200, Cousson, Benoit wrote:
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
Add omap3 soc file for handling omap3 soc i2c controllers existing
on l4-core bus.
Signed-off-by: G, Manjunath Kondaiahmanj...@ti.com
---
arch/arm/boot/dts/omap3-soc.dtsi
On Wed, Aug 10, 2011 at 10:41 PM, Cousson, Benoit b-cous...@ti.com wrote:
On 8/10/2011 6:28 PM, G, Manjunath Kondaiah wrote:
On Wed, Aug 10, 2011 at 01:51:47PM +0200, Cousson, Benoit wrote:
Hi Manju,
On 8/9/2011 4:10 PM, G, Manjunath Kondaiah wrote:
The omap dt requires new omap hwmod api
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
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
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
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
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 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
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
1 - 100 of 436 matches
Mail list logo
