As the architectures tend to add more cores [1][2], that means more
memory consumption. In a very near future, we will have 100 cores in a
cpu. Assuming we have 4 C-states, that is 100 * 4 * 8 = 3200 bytes of
memory used for a single function. IMHO, the kernel shouldn't assume the
user must add mo
Hi Daniel,
On Friday 06 July 2012 04:28 PM, Daniel Lezcano wrote:
The main purpose of all these cleanup patches are to move out all
non-data information from the cpuidle_state structure in order to add a
new api which could be 'cpuidle_register_cpu_latency(int cpu, struct
cpuidle_latencies laten
subsystem is disabled instead of adding big section in C files.
Looks good to me.
Reviewed-by: Rajendra Nayak
This patch fix this also.
Signed-off-by: Daniel Lezcano
Reviewed-by: Jean Pihet
---
arch/arm/mach-omap2/Kconfig |2 ++
arch/arm/mach-omap2/Makefile | 11
Hi Mike,
On Friday 16 March 2012 11:41 AM, Mike Turquette wrote:
The common clock framework defines a common struct clk useful across
most platforms as well as an implementation of the clk api that drivers
can use safely for managing clocks.
The net result is consolidation of many different str
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
Acked-by: Rob Herring
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 33 +
drivers/mmc/host
Add omap mmc related device tree data for OMAP3.
Currenly limited to only omap3-beagle board.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3-beagle.dts | 14 ++
arch/arm/boot/dts/omap3.dtsi | 16
2 files changed, 30 insertions(+), 0 deletions
t functional and needs twl4030 gpio
to be DT converted.
-2- pbias cell programming is missing and needs an OMAP
control module driver.
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
Add omap mmc related device tree data for OMAP4.
Currenly limited to only omap4-panda and omap4-sdp
boards.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-panda.dts | 22 ++
arch/arm/boot/dts/omap4-sdp.dts | 24
arch/arm/boot/dts
achieve better
power savings.
Signed-off-by: Rajendra Nayak
---
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 38ae8c0..f29e1a2 100644
--- a/drivers/mmc/host
Hi Paul,
On Friday 09 March 2012 12:21 PM, Paul Walmsley wrote:
On Thu, 8 Mar 2012, Grant Likely wrote:
Yes, absolutely use separate compatible values. It is always important
to be specific as to the silicon implementing the IP.
In that case, it is probably best to use the full chip name in
On Friday 09 March 2012 11:16 AM, Grant Likely wrote:
On Fri, 24 Feb 2012 10:49:00 -0800, Tony Lindgren wrote:
* Rajendra Nayak [120223 19:29]:
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
Hi Grant,
On Friday 09 March 2012 11:12 AM, Grant Likely wrote:
On Thu, 23 Feb 2012 17:31:27 +0530, Rajendra Nayak 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: Rajendra Nayak
Hi Chris,
On Wednesday 07 March 2012 08:29 PM, Chris Ball wrote:
Hi Rajendra,
On Wed, Mar 07 2012, Rajendra Nayak wrote:
Chris, Ping. I am basing my DT support patches on top of these cleanups.
Would be great if you can have a look and pull them in.
Chris, just realized the last two
Hi Rob/Grant,
On Thursday 23 February 2012 05:31 PM, Rajendra Nayak 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.
Any comments on these bindings for omap hsmmc? All the dependent
patches
On Wednesday 07 March 2012 08:29 PM, Chris Ball wrote:
Hi Rajendra,
On Wed, Mar 07 2012, Rajendra Nayak wrote:
Chris, Ping. I am basing my DT support patches on top of these cleanups.
Would be great if you can have a look and pull them in.
Chris, just realized the last two requests from me
On Monday 05 March 2012 01:24 PM, Rajendra Nayak wrote:
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'
T
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 hardcodin
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. The
additional LDOs.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Rajendra Nayak
Cc: Samuel Ortiz
Cc: Misael Lopez Cruz
Cc: Santosh Shilimkar
---
.../bindings/regulator/twl-regulator.txt |2 ++
drivers/regulator/twl-regulator.c |4
2 files changed, 6 insertions
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
---
.../bindings/regulator/twl
and requires external controller.
Signed-off-by: Tero Kristo
Signed-off-by: Rajendra Nayak
Cc: Mark Brown
Cc: Liam Girdwood
Cc: Samuel Ortiz
Cc: Kevin Hilman
---
drivers/mfd/twl-core.c| 15 ++
drivers/regulator/twl-regulator.c | 39
From: Peter Ujfalusi
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
Signed-off-by: Rajendra Nayak
Cc: Samuel Ortiz
Cc: Misael Lopez Cruz
Cc: Santosh Shilimkar
---
drivers/mfd/twl-core.c | 10
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
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
On Monday 27 February 2012 05:45 PM, Peter Ujfalusi wrote:
Hi Rajendra,
On 02/27/2012 12:35 PM, Rajendra Nayak wrote:
Re-sending on top of Tero's changes which are already
in -next and the one which adds support for twl6030
vdd1/2/3 SMPS [1].
Would you be able to add support for V1V8,
Pass all the voltage regulator information for
twl6030/twl4030 PMIC from device tree.
Signed-off-by: Rajendra Nayak
Signed-off-by: Benoit Cousson
---
arch/arm/boot/dts/omap3-beagle.dts |6 +++
arch/arm/boot/dts/twl4030.dtsi | 18 +++
arch/arm/boot/dts/twl6030.dtsi | 60
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
---
.../bindings/regulator/twl
les[2].
I have tested the patches on omap4panda and omap3beagle boards.
[1] http://marc.info/?l=linux-omap&m=133009693905864&w=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
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 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 Nayak wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23, 2012 at 5:31 PM, Rajendra Nayak 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: Rajendra
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;
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
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 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 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 includ
Add omap mmc related device tree data for OMAP3.
Currenly limited to only omap3-beagle board.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3.dtsi | 26 ++
2 files changed, 32 insertions(+), 0 deletions
achieve better
power savings.
Signed-off-by: Rajendra Nayak
---
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/mmc/host
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
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 31 +
drivers/mmc/host/omap_hsmmc.c
ver.
[1] http://marc.info/?l=linux-omap&m=132999699905180&w=2
[2] http://marc.info/?l=linux-omap&m=132999646604985&w=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
Add omap mmc related device tree data for OMAP4.
Currenly limited to only omap4-panda and omap4-sdp
boards.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-panda.dts | 10 ++
arch/arm/boot/dts/omap4-sdp.dts | 16
arch/arm/boot/dts/omap4.dtsi | 31
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
---
.../bindings/regulator/twl
Pass all the voltage regulator information for
twl6030/twl4030 PMIC from device tree.
Signed-off-by: Rajendra Nayak
Signed-off-by: Benoit Cousson
---
arch/arm/boot/dts/omap3-beagle.dts |6 +++
arch/arm/boot/dts/twl4030.dtsi | 18 +++
arch/arm/boot/dts/twl6030.dtsi | 60
atches on omap4panda 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/regulat
m_get_resource_byname for tx/rx 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 func
From: Balaji T K
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
Signed-off-by: Rajendra Nayak
Tested-by: Venkatraman S
---
drivers/mmc/host/omap_hsmmc.c |
From: Balaji T K
set_sleep seems to be unused in omap_hsmmc driver. so get rid of it.
Signed-off-by: Balaji T K
Signed-off-by: Rajendra Nayak
Tested-by: Venkatraman S
---
arch/arm/plat-omap/include/plat/mmc.h |2 -
drivers/mmc/host/omap_hsmmc.c | 60
additional checks and hence should just work for MMC1
as well.
Signed-off-by: Rajendra Nayak
Tested-by: Venkatraman S
Tested-by: Balaji T K
---
drivers/mmc/host/omap_hsmmc.c | 30 +++---
1 files changed, 3 insertions(+), 27 deletions(-)
diff --git a/drivers/mmc/host
ng and use omap_hsmmc_set_power() for all MMC modules.
Signed-off-by: Rajendra Nayak
Tested-by: Venkatraman S
Tested-by: Balaji T K
---
drivers/mmc/host/omap_hsmmc.c | 21 +
1 files changed, 1 insertions(+), 20 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drive
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
From: Balaji T K
Use OMAP_HSMMC_SUPPORTS_DUAL_VOLT flag instead of host->id
for identifying SD bus voltage capabilities.
Signed-off-by: Balaji T K
Signed-off-by: Rajendra Nayak
Tested-by: Venkatraman S
---
drivers/mmc/host/omap_hsmmc.c |2 +-
1 files changed, 1 insertions(+)
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 Nayak wrote:
@@ -324,8 +302,8 @@ static int omap_hsmmc_reg_get(struct omap_hsmmc_host
*host
On Friday 10 February 2012 06:57 PM, T Krishnamoorthy, Balaji wrote:
On Tue, Feb 7, 2012 at 3:32 PM, S, Venkatraman wrote:
> On Sat, Feb 4, 2012 at 8:21 PM, Rajendra Nayak wrote:
>> This series mainly cleans up all instances of hardcoding's in
>> the driver based
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 S
Great, thanks Venkat.
___
linaro-dev mailing list
l
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
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 Lindgren
--- /dev/null
+++ b/arch/arm/boot/dts/omap2.dtsi
@@ -0,0 +1,67 @@
+/*
+ * Device Tree Source for OMAP2 SoC
+ *
+ * Copyright (C)
On Thursday 15 December 2011 12:55 AM, Tony Lindgren wrote:
* Rajendra Nayak [111214 03:24]:
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
Signed-off-by
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
---
drivers/tty/serial/omap-serial.c | 30 +++---
1 fi
.
Acked-by: Rob Herring
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/serial/omap_serial.txt | 10
drivers/tty/serial/omap-serial.c | 45 ++-
2 files changed, 52 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree
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 defa
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
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3.dtsi| 31
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
---
drivers/tty/serial/omap-serial.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/tty/serial/omap-serial.c b
://gitorious.org/omap-pm/linux.git for-dt/regulator-twl
regards,
Rajendra
[1] git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
[2] git://gitorious.org/omap-pm/linux.git for_3.3/3_omap_dt_i2c_twl
Rajendra Nayak (3):
regulator: twl: adapt twl-regulator driver to dt
ARM
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
---
.../bindings/regulator/twl
Pass the adjustable voltage regulator information for
omap4panda board from device tree.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-panda.dts | 24
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
b/arch
Pass the adjustable voltage regulator information for
omap4sdp board from device tree.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4-sdp.dts | 36
1 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b
On Monday 05 December 2011 04:27 PM, Mark Brown wrote:
On Mon, Dec 05, 2011 at 04:14:40PM +0530, Thomas Abraham wrote:
On 5 December 2011 16:04, Mark Brown
With the regulator device tree bindings if the regulator is configured
to run a single voltage the bindings will set apply_uV uncondition
Documentation/power/regulator/regulator.txt would also require an
update the reflect the change in api.
Thanks Thomas, I just sent a patch to fix this up.
regards,
Rajendra
Thanks,
Thomas.
[...]
___
linaro-dev mailing list
linaro-dev@lists.lin
On Monday 28 November 2011 07:09 PM, Rob Herring wrote:
On 11/22/2011 07:44 AM, Rajendra Nayak wrote:
Adapt the driver to device tree and pass minimal platform
data from device tree needed for console boot.
No power management features will be suppported for now
since it requires more tweaks
On Sunday 27 November 2011 09:06 AM, Greg KH wrote:
On Tue, Nov 22, 2011 at 07:14:12PM +0530, Rajendra Nayak wrote:
v2 is based on the latest omap-serial runtime patches, which
can be found here[1]
The series passes minimal data that allows serial console
boot, with UART's initialised
ulate port.line
regards,
Rajendra
[1] git://gitorious.org/runtime_3-0/runtime_3-0.git 3.2-rc2_uart_runtime
Rajendra Nayak (4):
omap-serial: Get rid of all pdev->id usage
omap-serial: Use default clock speed (48Mhz) if not specified
omap-serial: Add minimal device tree support
ARM: om
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
---
drivers/tty/serial/omap-serial.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/tty/serial/omap-serial.c b
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
---
drivers/tty/serial/omap-serial.c | 30 +++---
1 fi
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.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3.dtsi| 31 +++
arch/arm/boot/dts
.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/serial/omap_serial.txt | 10
drivers/tty/serial/omap-serial.c | 45 ++-
2 files changed, 52 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial
debug prints to appear on
the console.
Acked-by: Kevin Hilman
Acked-by: Benoit Cousson
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 23 ++-
arch/arm/plat-omap/include/plat/omap_hwmod.h |6 ++
2 files changed, 28 insertions(+), 1 delet
On Monday 21 November 2011 03:33 PM, Govindraj wrote:
Hi Rajendra,
On Mon, Nov 21, 2011 at 11:45 AM, 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
ch a device is an UART used as debug console.
The UART module needs to be kept enabled through the boot, until the
UART driver takes control of it, for debug prints to appear on
the console.
Acked-by: Kevin Hilman
Acked-by: Benoit Cousson
Signed-off-by: Rajendra Nayak
---
changes in v2:
Fixed mi
ore.
Signed-off-by: Rajendra Nayak
Acked-by: Mark Brown
Cc: Michael Hennerich
Cc: Ian Lartey
Cc: Dimitris Papastamos
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Wolfram Sang
Cc: Zeng Zhaoming
Cc: Dan Carpenter
---
drivers/regulator/88pm8607.c |2 +-
drivers/regulator/aat2870-regulato
the Acks recieved on the
last 2 patches (3/4 and 4/4) as they remain unchanged.
regards,
Rajendra
Rajendra Nayak (4):
regulator: helper routine to extract regulator_init_data
regulator: adapt fixed regulator driver to dt
regulator: pass additional of_node to regulator_register()
regulator
The fixed regulator driver uses of_get_fixed_voltage_config()
to extract fixed_voltage_config structure contents from device tree.
Also add documenation for additional bindings for fixed
regulators that can be passed through dt.
Signed-off-by: Rajendra Nayak
---
.../bindings/regulator/fixed
ch are linux and board specific,
are left out since its not clear if they can
be in someway embedded into the kernel or passed in from DT.
They will be revisited later.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/regulator/regulator.txt| 54 +
drivers/re
specify a supply_name, which can then be used to lookup dt
to find the parent phandle.
Signed-off-by: Rajendra Nayak
Acked-by: Grant Likely
Acked-by: Mark Brown
---
drivers/regulator/core.c | 79 --
include/linux/regulator/driver.h |2 +
2 fil
Hi Kevin,
On Friday 18 November 2011 01:05 AM, Kevin Hilman wrote:
Rajendra Nayak writes:
A 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 it
at a later
On Thursday 17 November 2011 04:09 PM, Cousson, Benoit wrote:
+ Paul
On 11/17/2011 11:11 AM, Rajendra Nayak wrote:
A 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
On Thursday 17 November 2011 01:50 PM, Linus Walleij wrote:
On Mon, Nov 14, 2011 at 1:40 PM, Rajendra Nayak wrote:
(...)
+ * The OMAP control module has a device-control sub-module
+ * which handles all pin/padmuxing for OMAP. The sub-module
+ * is further split into a 'core' insta
[]...
Why do we have to idle -> enable? The module is already enabled, isn't
it?
The comment is not super clear for me :-)
Is the goal is to reset the IP?
Yes, now that I read it, it does sound confusing. I should have at-least
read it once before I picked it from serial.c
But anyway, here's
ch a device is an UART used as debug console.
The UART module needs to be kept enabled through the boot, until the
UART driver takes control of it, for debug prints to appear on
the console.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 16 ++--
a
ch a device is an UART used as debug console.
The UART module needs to be kept enabled through the boot, until the
UART driver takes control of it, for debug prints to appear on
the console.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 16 ++--
a
On Thursday 17 November 2011 06:34 AM, Rob Herring wrote:
On 11/16/2011 05:02 AM, Rajendra Nayak wrote:
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.
Signed-off-by: Rajendra
On Wednesday 16 November 2011 08:29 PM, Rob Herring wrote:
On 11/16/2011 05:02 AM, Rajendra Nayak wrote:
Adapt the driver to device tree and pass minimal platform
data from device tree needed for console boot.
No power management features will be suppported for now
since it requires more tweaks
Hi Rob,
On Wednesday 16 November 2011 08:20 PM, Rob Herring wrote:
[]...
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt
b/Documentation/devicetree/bindings/arm/omap/omap.txt
index dbdab40..46ffd41 100644
--- a/Documentation/devicetree/bindings/arm/omap/omap.txt
+++ b/Document
[...]
+static int omap_console_hwmod_enable(struct omap_device *od)
+{
+ console_lock();
+ /*
+* For early console we prevented hwmod reset and idle
A period is missing. Or maybe it should a comma with not capital letter.
+* So before we enable the uart clocks idle
.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/serial/omap_serial.txt |9 +
drivers/tty/serial/omap-serial.c | 37 +++-
2 files changed, 45 insertions(+), 1 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial
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.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap3-beagle.dts | 17 +
arch/arm/boot/dts/omap3.dtsi
t for UART and remote
wakeup needs more work.
Boot tested on OMAP4 panda and OMAP4 sdp boards.
[1] git://gitorious.org/runtime_3-0/runtime_3-0.git 3.2-rc1_uart_runtime
[2] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg58486.html
Rajendra Nayak (3):
ARM: omap_device: handle first
-off-by: Rajendra Nayak
---
.../devicetree/bindings/arm/omap/omap.txt |1 +
arch/arm/plat-omap/omap_device.c | 33 +++-
2 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt
b/Documentation
Fix u300_pmx_endisable() to iterate over the list of 'bits' and
'mask' populated as part of u300_pmx_functions.mask[]
Signed-off-by: Rajendra Nayak
---
Linus W,
I am not sure if this is a right fix. I just stumbled
upon this while looking at the u300 pinmux driver
while I
Fix some minor typos in the pinctrl documentation.
Signed-off-by: Rajendra Nayak
---
Documentation/pinctrl.txt | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index b04cb7d..c849a09 100644
--- a
On Monday 14 November 2011 10:53 PM, Tony Lindgren wrote:
* Rajendra Nayak [14 04:05]:
> --- /dev/null
> +++ b/drivers/pinctrl/pinmux-omap.c
> @@ -0,0 +1,735 @@
> +
> +/* omap4 core pads */
> +static const struct pinctrl_pin_desc omap4_core_pads[] = {
>
1 - 100 of 105 matches
Mail list logo
