On Tuesday 06 March 2012 09:43 AM, Paul Walmsley wrote:
Hi Rajendra
(thanks for adding in Nilesh, added him again here)
On Tue, 6 Mar 2012, Rajendra Nayak wrote:
Yes, thats my understanding too, again based on taking to people like
Nilesh, because the documentation just doesn't mention
On Tuesday 06 March 2012 09:51 AM, Paul Walmsley wrote:
added Rajendra, Nilesh, Vishwa, Mohan
Hi
On Fri, 2 Mar 2012, Tero Kristo wrote:
Enable IO Wake up for OMAP3/4 as part of PRM Init. Currently this has been
managed in cpuidle path which is not the right place. Subsequent patch
will
On Tuesday 06 March 2012 10:20 AM, Rajendra Nayak wrote:
On Tuesday 06 March 2012 09:51 AM, Paul Walmsley wrote:
added Rajendra, Nilesh, Vishwa, Mohan
Hi
On Fri, 2 Mar 2012, Tero Kristo wrote:
Enable IO Wake up for OMAP3/4 as part of PRM Init. Currently this has
been
managed in cpuidle path
On Tuesday 06 March 2012 11:14 AM, Nishanth Menon wrote:
On 17:17-20120302, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Since IO Daisychain modifies only PRM registers, it makes sense to move
it to PRM File. Also changed the timeout value for IO chain enable to
100us and added a
On Friday 24 February 2012 03:40 PM, Rajendra Nayak wrote:
Chris,
On Thursday 23 February 2012 04:56 PM, Rajendra Nayak wrote:
Re-sending as these patches did not make it to the lists due to
issues with my 'git send-email'
This series mainly cleans up all instances of hardcoding's
Hi Tony,
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Hi all,
This series adds gpio_find_by_name() that allows finding
GPIOs on specific gpio_chips. As the GPIO numbers can be
dynamic, it's hard to find the GPIO numbers from drivers
using them directly.
So far we've dealt with this
On Friday 02 March 2012 02:49 PM, Tero Kristo wrote:
On Thu, 2012-03-01 at 14:37 -0800, Kevin Hilman wrote:
Rajendra Nayakrna...@ti.com writes:
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Enable IO Wake up for OMAP3 as part of PM Init.
On Thursday 01 March 2012 01:58 PM, Tero Kristo wrote:
On Thu, 2012-03-01 at 12:19 +0530, Rajendra Nayak wrote:
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Since IO Daisychain modifies only PRM registers, it makes sense to move
it to PRM
to other type2
IPs'.
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Balaji TK balaj...@ti.com
Tested-by: Sourav Poddar sourav.pod...@ti.com
---
Paul,
I based the patch on top of your reset/data cleanup series
for hwmod. So its
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Use gpio_find_by_chip_name() to find the GPIO pins as they can
be dynamically allocated on various gpio_chips.
Note that we don't want to touch the platform data as it can
now specify the GPIO offset on a named gpio_chip.
This removes the
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
We can now remove the setting of GPIO pins with callbacks
as the drivers can access a GPIO offset on a named gpio_chip
directly with gpio_find_by_chip_name().
Cc: Rajendra Nayakrna...@ti.com
Signed-off-by: Tony Lindgrent...@atomide.com
---
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
There's no need to use callbacks for this, we can
do it directly between MMC driver and twl6030.
Cc: Samuel Ortizsa...@linux.intel.com
Cc: Chris Ballc...@laptop.org
Cc: Rajendra Nayakrna...@ti.com
Signed-off-by: Tony
On Friday 02 March 2012 12:25 AM, Tony Lindgren wrote:
Use gpio_find_by_chip_name() to find the GPIO pins as they can
be dynamically allocated on various gpio_chips.
Note that we don't want to touch the platform data as it can
now specify the GPIO offset on a named gpio_chip.
This removes the
implementation code, standardizing the format as
it does so.
looks good to me. Thanks,
Acked-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Paul Walmsleyp...@pwsan.com
Cc: Rajendra Nayakrna...@ti.com
---
arch/arm/mach-omap2/powerdomain.c | 30 ++--
arch/arm
On Thursday 01 March 2012 04:48 AM, Mark Brown wrote:
On Tue, Feb 28, 2012 at 03:09:09PM +0530, Rajendra Nayak wrote:
Hi Mark,
Here is a consolidated series which adds DT support for twl regulator
driver and adds support for VDD1/2/3 regulator and support for
fixed LDO V1V8 and V2V1
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Since IO Daisychain modifies only PRM registers, it makes sense to move
it to PRM File.
Signed-off-by: Vishwanath BSvishwanath...@ti.com
Tested-by: Govindraj.Rgovindraj.r...@ti.com
Signed-off-by:
On Wednesday 29 February 2012 07:56 PM, Tero Kristo wrote:
From: Vishwanath BSvishwanath...@ti.com
Enable IO Wake up for OMAP3 as part of PM Init. Currently this has been
managed in cpuidle path which is not the right place. Subsequent patch
will remove IO Daisy chain handling in cpuidle path
On Wednesday 29 February 2012 08:55 PM, Tero Kristo wrote:
Currently PRCM chain handler for OMAP4 requires SPARSE_IRQ to be enabled
from kernel config, however enabling this option breaks the OMAP kernel
completely and it can't be used. Thus, OMAP_PRCM_IRQ_BASE was added
to the end of the irq
failed with error -22
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/twl-common.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/twl-common.c b/arch/arm/mach-omap2/twl-common.c
index 10b20c6..4b57757 100644
--- a/arch/arm/mach-omap2
change
in the non-DT case.
regards,
Rajendra
Peter Ujfalusi (2):
regulator: twl-regulator: Add fixed LDO for V1V8, V2V1 supply
MFD: twl-core: regulator configuration for twl6030 V1V8, V2V1 SMPS
Rajendra Nayak (1):
regulator: twl: adapt twl-regulator driver to dt
Tero Kristo (1):
regulator
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Also add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
.../bindings
From: Peter Ujfalusi peter.ujfal...@ti.com
To be able to attach consumers to these supplies from board
files we need to have regulator_init_data for them.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Samuel Ortiz sa...@linux.intel.com
Cc
property for these additional LDOs.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Misael Lopez Cruz misael.lo...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
---
.../bindings/regulator/twl
tested the patches on omap4panda and omap3beagle boards.
[1] http://marc.info/?l=linux-omapm=133009693905864w=2
[2] git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.4/dt_i2c_twl
Rajendra Nayak (2):
regulator: twl: adapt twl-regulator driver to dt
arm/dts: twl
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Also add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
.../bindings
Hi Kevin,
On Tuesday 28 February 2012 05:58 AM, Kevin Hilman wrote:
Tero Kristot-kri...@ti.com writes:
From: Rajendra Nayakrna...@ti.com
With no driver handling DSP/TESLA, if brought out of reset, it stays
active and does not assert standby.
Signed-off-by: Rajendra Nayakrna...@ti.com
On Monday 27 February 2012 08:23 PM, Mark Brown wrote:
If adding device tree support breaks existing platforms something is
going wrong, while you're pulling things together device tree might not
work until all the support makes it in but the old non-DT code should
continue to function.
Adding
,
Rajendra
Rajendra Nayak (6):
ARM: OMAP: omap_device: Add omap_device_unregister()
mmc: omap_hsmmc: Make the driver support hotpluggable devices
mmc: omap_hsmmc: If probe fails, give our error messages
ARM: OMAP3: Make only mmc devices using gpio_cd as deferred
ARM: OMAP3: Modify
Add support to unregister an omap_device using
omap_device_unregister api.
While here, also fix the kerneldoc comments for
omap_device_register.
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/omap_device.h |1 +
arch/arm/plat
-by: Rajendra Nayak rna...@ti.com
Cc: Chris Ball c...@laptop.org
Cc: linux-...@vger.kernel.org
---
drivers/mmc/host/omap_hsmmc.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index fd0c661..21b8afa 100644
mmc devices which actually do not depend on twl4030-gpio for
gpio_cd should not be maked as deferred.
Also on overo, since none of the mmc devices need to be deferred,
get rid of omap_hsmmc_late_init() altogether.
Reported-by: Igor Grinberg grinb...@compulab.co.il
Signed-off-by: Rajendra Nayak
existing omap3 boards in subsequent patches.
Reported-by: Russell King rmk+ker...@arm.linux.org.uk
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c |2 +-
arch/arm/mach-omap2/board-cm-t35.c |2 +-
arch/arm/mach-omap2/board-devkit8000.c
Giving out debug messages even in case of probe failure seems
not very useful. Make them error messages instead.
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Chris Ball c...@laptop.org
Cc: linux-...@vger.kernel.org
---
drivers/mmc/host/omap_hsmmc.c |6 +++---
1 files changed, 3 insertions
King rmk+ker...@arm.linux.org.uk
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 13 +
arch/arm/mach-omap2/board-cm-t35.c | 12
arch/arm/mach-omap2/board-devkit8000.c | 13 +
arch/arm/mach
Chris,
On Thursday 23 February 2012 04:56 PM, Rajendra Nayak wrote:
Re-sending as these patches did not make it to the lists due to
issues with my 'git send-email'
This series mainly cleans up all instances of hardcoding's in
the driver based on pdev-id. This is cleanup leading to the
DT
On Friday 24 February 2012 03:46 PM, T Krishnamoorthy, Balaji wrote:
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29f4589..9204f60 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -25,6 +25,11 @@
serial1 =uart2;
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23, 2012 at 5:31 PM, Rajendra Nayakrna...@ti.com wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree.
Signed-off-by:
On Friday 24 February 2012 06:21 PM, Cousson, Benoit wrote:
On 2/24/2012 12:35 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23, 2012 at 5:31 PM, Rajendra Nayakrna...@ti.com wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
On Friday 24 February 2012 06:32 PM, Cousson, Benoit wrote:
On 2/24/2012 1:58 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 06:21 PM, Cousson, Benoit wrote:
On 2/24/2012 12:35 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23
On Saturday 25 February 2012 03:51 AM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120224 01:27]:
mmc devices which actually do not depend on twl4030-gpio for
gpio_cd should not be maked as deferred.
Also on overo, since none of the mmc devices need to be deferred,
get rid of
On Saturday 25 February 2012 06:03 AM, Tony Lindgren wrote:
Hi,
* Rajendra Nayakrna...@ti.com [120224 01:27]:
omap_hsmmc_late_init() adds deferred (if any) mmc devices which are
dependent on twl4030-gpio device to be available.
If twl4030-gpio is built as a module and inserted and deleted
On Thursday 23 February 2012 07:58 PM, Igor Grinberg wrote:
Hi Tony, Rajendra,
On 02/23/12 13:40, Rajendra Nayak wrote:
From: Tony Lindgrent...@atomide.com
Otherwise omap_device_build() and omap_mux related functions
can't be marked as __init when twl is build as a module.
If a board
Igor,
On Thursday 23 February 2012 08:25 PM, Igor Grinberg wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Rajendra,
On 02/23/12 13:40, Rajendra Nayak wrote:
All OMAP3 boards which register a .setup function with twl4030
gpio driver do not seem to have a .teardown hook implemented
On Thursday 23 February 2012 09:01 PM, Mark Brown wrote:
On Thu, Feb 23, 2012 at 05:05:53PM +0530, Rajendra Nayak wrote:
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds
On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -113,5 +113,31 @@
#size-cells =0;
ti,hwmods = i2c3;
};
+
+ mmc1: mmc@1 {
+
On Friday 24 February 2012 12:17 AM, Tony Lindgren wrote:
* Igor Grinberggrinb...@compulab.co.il [120223 05:56]:
--- a/arch/arm/mach-omap2/board-cm-t35.c
+++ b/arch/arm/mach-omap2/board-cm-t35.c
@@ -411,9 +411,9 @@ static struct omap2_hsmmc_info mmc[] = {
{
.mmc
On Friday 24 February 2012 12:22 AM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120223 03:09]:
Re-sending as these patches did not make it to the lists due to
issues with my 'git send-email'
Hi Tony,
This is a re-spin of your series to fix up the section
mismatch warnings noted by
Djamil,
On Thursday 23 February 2012 09:28 PM, Elaidi, Djamil wrote:
Hi Kristo,
I think you must also add a omap_test_timeout() check after the Trigger WUCLKIN
disable, to verify WUCLK_STATUS has come back to 0.
This is needed because the IO daisy chain will not be ready until the WUCLKIN
On Thursday 23 February 2012 07:18 PM, Shilimkar, Santosh wrote:
On Thu, Feb 23, 2012 at 6:51 PM, Tero Kristot-kri...@ti.com wrote:
[..]
+/**
+ * Maximum time(us) it takes to output the signal WUCLKOUT of the last pad of
+ * the I/O ring after asserting WUCLKIN high
+ */
+#define
MMC1 is not the only instance that can be used/wired for SD.
So remove this assumption from the driver.
Now that all the mmc id based usage is removed, get rid
of all the DEVID defines and also the 'id' field from the
omap_hsmmc_host structure.
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested
From: Balaji T K balaj...@ti.com
set_sleep seems to be unused in omap_hsmmc driver. so get rid of it.
Signed-off-by: Balaji T K balaj...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested-by: Venkatraman S svenk...@ti.com
---
arch/arm/plat-omap/include/plat/mmc.h |2 -
drivers/mmc
on additional checks and hence should just work for MMC1
as well.
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested-by: Venkatraman S svenk...@ti.com
Tested-by: Balaji T K balaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 30 +++---
1 files changed, 3 insertions(+), 27 deletions
DMA
channels
mmc: omap_hsmmc: remove unused .set_sleep function
mmc: omap_hsmmc: Use OMAP_HSMMC_SUPPORTS_DUAL_VOLT flag to remove
host-id based hardcoding
Rajendra Nayak (3):
mmc: omap_hsmmc: Get rid of omap_hsmmc_1_set_power function
mmc: omap_hsmmc: Get rid of omap_hsmmc_4_set_power
From: Balaji T K balaj...@ti.com
Git rid of hardcoded tx/rx DMA channels based on pdev-id
and use platform_get_resource_byname() to retrieve them
instead.
Signed-off-by: Balaji T K balaj...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested-by: Venkatraman S svenk...@ti.com
---
drivers
omap_hsmmc_set_power() for all MMC modules.
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested-by: Venkatraman S svenk...@ti.com
Tested-by: Balaji T K balaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 21 +
1 files changed, 1 insertions(+), 20 deletions(-)
diff --git
From: Balaji T K balaj...@ti.com
Use OMAP_HSMMC_SUPPORTS_DUAL_VOLT flag instead of host-id
for identifying SD bus voltage capabilities.
Signed-off-by: Balaji T K balaj...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Tested-by: Venkatraman S svenk...@ti.com
---
drivers/mmc/host
Convert all instances of pr_* prints within the driver
to instead use dev_* prints.
Reported-by: Russell King rmk+ker...@arm.linux.org.uk
Signed-off-by: Rajendra Nayak rna...@ti.com
---
Re-sending as this patch did not make it to the lists due to
issues with my 'git send-email'
drivers/mmc/host
Pass all the voltage regulator information for
twl6030/twl4030 PMIC from device tree.
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Benoit Cousson b-cous...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts |6 +++
arch/arm/boot/dts/twl4030.dtsi | 18 +++
arch/arm/boot
and omap3beagle boards.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.4/dt_i2c_twl
Rajendra Nayak (2):
regulator: twl: adapt twl-regulator driver to dt
arm/dts: twl: Pass regulator data from dt
.../bindings/regulator/twl-regulator.txt
Modify the twl regulator driver to extract the regulator_init_data from
device tree when passed, instead of getting it through platform_data
structures (on non-DT builds)
Also add documentation for TWL regulator specific bindings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
.../bindings
a .teardown hook for twl4030 gpio
driver populated from all OMAP3 board files, which release all the
requested gpios and also unregister the mmc omap/platform device.
regards,
Rajendra
Ohad Ben-Cohen (1):
ARM: OMAP: omap_device: Expose omap_device_{alloc, delete, register}
Rajendra Nayak (4):
ARM
...@wizery.com
Signed-off-by: Kevin Hilman khil...@ti.com
Signed-off-by: Tony Lindgren t...@atomide.com
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/plat-omap/include/plat/omap_device.h |7 +++
arch/arm/plat-omap/omap_device.c | 13 +++--
2 files changed
-by: Rajendra Nayak rna...@ti.com
Cc: Chris Ball c...@laptop.org
Cc: linux-...@vger.kernel.org
---
drivers/mmc/host/omap_hsmmc.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index fd0c661..21b8afa 100644
Add support to unregister an omap_device using
omap_device_unregister api.
While here, also fix the kerneldoc comments for
omap_device_register.
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/omap_device.h |1 +
arch/arm/plat
King rmk+ker...@arm.linux.org.uk
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 10 ++
arch/arm/mach-omap2/board-cm-t35.c |8
arch/arm/mach-omap2/board-devkit8000.c | 10 ++
arch/arm/mach-omap2/board
Giving our debug messages even in case of probe failure seems
not very useful. Make them error messages instead.
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Chris Ball c...@laptop.org
Cc: linux-...@vger.kernel.org
---
drivers/mmc/host/omap_hsmmc.c |6 +++---
1 files changed, 3 insertions
-by: Russell King rmk+ker...@arm.linux.org.uk
Signed-off-by: Tony Lindgren t...@atomide.com
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-2430sdp.c |2 +-
arch/arm/mach-omap2/board-3430sdp.c | 12 ++--
arch/arm/mach-omap2/board-4430sdp.c
...@atomide.com
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-flash.c |2 +-
arch/arm/mach-omap2/board-omap3beagle.c|6 --
arch/arm/mach-omap2/board-omap3evm.c |3 ++-
arch/arm/mach-omap2/board-omap3stalker.c |3 ++-
arch/arm/mach-omap2
] http://marc.info/?l=linux-omapm=132999699905180w=2
[2] http://marc.info/?l=linux-omapm=132999646604985w=2
Rajendra Nayak (4):
mmc: omap_hsmmc: Convert hsmmc driver to use device tree
mmc: omap_hsmmc: Avoid a regulator voltage change with dt
arm/dts: OMAP4: Add mmc controller nodes and board
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 31 +
drivers/mmc/host/omap_hsmmc.c
to achieve better
power savings.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 15 ++-
1 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index 0c93d58..dffde8d 100644
--- a/drivers
Add omap mmc related device tree data for OMAP4.
Currenly limited to only omap4-panda and omap4-sdp
boards.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 10 ++
arch/arm/boot/dts/omap4-sdp.dts | 16
arch/arm/boot/dts/omap4.dtsi
On Thursday 23 February 2012 05:31 PM, Rajendra Nayak wrote:
This series adds device tree support for OMAP hsmmc
driver. The series is dependent on a couple other series,
to add TWL regulator DT support[1] and another to clean
the pdev-id usage within the hsmmc driver[2]
all patches including
On Tuesday 21 February 2012 05:50 PM, Russell King - ARM Linux wrote:
On Tue, Feb 21, 2012 at 05:43:54PM +0530, S, Venkatraman wrote:
On Tue, Feb 21, 2012 at 3:33 PM, Rajendra Nayakrna...@ti.com wrote:
@@ -324,8 +302,8 @@ static int omap_hsmmc_reg_get(struct omap_hsmmc_host
*host)
On Saturday 18 February 2012 01:51 AM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120217 05:53]:
Tony,
On Wednesday 15 February 2012 11:58 PM, Tony Lindgren wrote:
Hi all,
This series fixes up the issues noted by Russell on omap2_hsmmc_init()
where if TWL PMIC is compiled as a
[]...
3. Load the gpio-twl4030 module
I was expecting this to now detect the card, but I instead got
this error which seems to tell gpio-twl4030 has problems
when built/used as a module, outside of the mmc issues.
Looks like I was mislead with the errors and though the twl4030
gpio probe was
On Friday 17 February 2012 03:03 PM, Rajendra Nayak wrote:
[]...
3. Load the gpio-twl4030 module
I was expecting this to now detect the card, but I instead got
this error which seems to tell gpio-twl4030 has problems
when built/used as a module, outside of the mmc issues.
Looks like I
On Friday 17 February 2012 03:03 PM, Rajendra Nayak wrote:
Sorry, I did'nt repond back because I wanted to get this resolved
completely before I did.
(3) did not probe the inserted mmc device because the driver was
doing a platform_driver_probe() and not a platform_driver_register().
Once I
On Friday 17 February 2012 03:36 PM, Russell King - ARM Linux wrote:
On Fri, Feb 17, 2012 at 03:29:55PM +0530, Rajendra Nayak wrote:
hmm, rmmod does not even seem to trigger the drivers .remove if there
are outstanding requests on the module, so a pdata-teardown called
from within the .remove
On Friday 17 February 2012 03:48 PM, Rajendra Nayak wrote:
Yes, I did get a WARN saying the device is already registered. An
unregister in my teardown should fix that too.
And now I see there is no way to unregister an omap_device :-)
which needs to be added.
--
To unsubscribe from
Tony,
On Wednesday 15 February 2012 11:58 PM, Tony Lindgren wrote:
Hi all,
This series fixes up the issues noted by Russell on omap2_hsmmc_init()
where if TWL PMIC is compiled as a module we can't keep a bunch of
functions marked as __init like they should be. This series fixes
the issues by
Hi Tony,
On Wednesday 15 February 2012 11:58 PM, Tony Lindgren wrote:
Otherwise omap_device_build() and omap_mux related functions
can't be marked as __init when twl is build as a module.
If a board is using GPIO pins or regulators configured by an
external chip, such as TWL PMIC on I2C bus,
On Thursday 16 February 2012 03:33 PM, Rajendra Nayak wrote:
better still, I think we should just populate them statically in
omap2_hsmmc_info struct above, so omap_hsmmc_init() takes care
of it already.
I just tried this and it seems to work...
---
arch/arm/mach-omap2/board-omap3beagle.c
On Thursday 16 February 2012 05:42 PM, Russell King - ARM Linux wrote:
On Thu, Feb 16, 2012 at 05:30:59PM +0530, Nayak, Rajendra wrote:
One more patch is needed to sort out the remaining issue with
omap4 that has yet another luck based initialization for the
same issue..
I did this patch on
On Thursday 16 February 2012 06:04 PM, Rajendra Nayak wrote:
Can you test something with these patches?
1. Build the gpio-twl4030.c as a module, but with HSMMC support built in
2. Boot on the 4430SDP
twl4030 gpio is used for card detect on OMAP3, so I tried this
on my Beagle instead
On Thursday 16 February 2012 10:05 PM, Tony Lindgren wrote:
On Thursday 16 February 2012 03:33 PM, Rajendra Nayak wrote:
better still, I think we should just populate them statically in
omap2_hsmmc_info struct above, so omap_hsmmc_init() takes care
of it already.
I just tried
On Saturday 11 February 2012 12:48 AM, Tony Lindgren wrote:
* Santosh Shilimkarsantosh.shilim...@ti.com [120202 05:33]:
From: Rajendra Nayakrna...@ti.com
hwmod setup already does a reset and sets the OCP sysconfig
registers appropriately. Avoid doing a reset again and overriding
the
On Friday 10 February 2012 06:57 PM, T Krishnamoorthy, Balaji wrote:
On Tue, Feb 7, 2012 at 3:32 PM, S, Venkatramansvenk...@ti.com wrote:
On Sat, Feb 4, 2012 at 8:21 PM, Rajendra Nayakrna...@ti.com wrote:
This series mainly cleans up all instances of hardcoding's in
the driver based on
On Tuesday 07 February 2012 02:02 AM, S, Venkatraman wrote:
I gave it a spin on Beagleboard-XM (OMAP3630) with root filesystem
on the SD card, and checked again on 4430SDP.
Tested-by: Venkatraman Ssvenk...@ti.com
Great, thanks Venkat.
--
To unsubscribe from this list: send the line
(hopefully) and precise.
- Fix an error path bug that would not place the clockdomain back into
hardware-supervised idle or sleep mode if the power state could not
be programmed.
All the changes look good. Thanks.
Acked-by: Rajendra Nayak rna...@ti.com
regards,
Rajendra
no
need to do it twice.
It looks like these two for OMAP4 are surpurfluous since the immediately
follow a call to pwrdm_pre_transition() as well.
Santosh/Rajendra, please confirm/ack.
I agree, looks like they should be removed.
Acked-by: Rajendra Nayak rna...@ti.com
Kevin
diff --git a/arch
Hi Paul,
On Friday 16 December 2011 04:07 PM, Paul Walmsley wrote:
On Mon, 21 Nov 2011, Rajendra Nayak wrote:
An hwmod with a 'HWMOD_INIT_NO_IDLE' flag set, is left in
enabled state by the hwmod framework post the initial setup.
Once a real user of the device (a driver) tries to enable
Hi Paul,
On Friday 16 December 2011 04:46 PM, Paul Walmsley wrote:
Hi Rajendra,
I've combined your patches down to one patch and changed the logic a
little bit. It looks to me that the update and clear context registers
can be done in one step, since an IP block shouldn't lose context when
On Friday 16 December 2011 04:53 PM, Paul Walmsley wrote:
Hi
On Fri, 16 Dec 2011, Paul Walmsley wrote:
+ * XXX Will not work correctly if the RM_*_CONTEXT register
+ * offset is 0 -- probably a flag should be used to avoid this
+ * situation, rather than testing @oh-prcm.omap4.context_offs.
On Friday 16 December 2011 06:08 PM, Paul Walmsley wrote:
On Fri, 16 Dec 2011, Rajendra Nayak wrote:
On Friday 16 December 2011 04:46 PM, Paul Walmsley wrote:
Hi Rajendra,
I've combined your patches down to one patch and changed the logic a
little bit. It looks to me that the update
On Friday 16 December 2011 03:09 AM, Tony Lindgren wrote:
Add minimal device tree support for omap2420 and omap2430
Looks good to me.
Signed-off-by: Tony Lindgrent...@atomide.com
--- /dev/null
+++ b/arch/arm/boot/dts/omap2.dtsi
@@ -0,0 +1,67 @@
+/*
+ * Device Tree Source for OMAP2 SoC
+ *
Use a default clock speed of 48Mhz, instead of ending up with 0,
if platforms fail to specify a valid clock speed.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/tty/serial/omap-serial.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/tty/serial
for each OMAP family
-4- Used of_alias_get_id to populate port.line
[1] git://gitorious.org/runtime_3-0/runtime_3-0.git for_3_3/lo_rc4_uartruntime
[2] http://www.spinics.net/lists/arm-kernel/msg150751.html
Rajendra Nayak (4):
omap-serial: Get rid of all pdev-id usage
omap-serial: Use default
Pass minimal data needed for console boot, from dt, for
OMAP4 panda/sdp and OMAP3 beagle boards, and get rid of the
static initialization from generic board file.
Acked-by: Rob Herring rob.herr...@calxeda.com
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/boot/dts/omap3.dtsi
With Device tree, pdev-id would no longer be Valid.
Hence get rid of all instances of its usage in the
driver. Device tree support for the driver is added
in subsequent patches.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
drivers/tty/serial/omap-serial.c | 30
601 - 700 of 1307 matches
Mail list logo
