Re: [PATCH] arm: dts: twl6030: typical connection to omap4 as a separate dtsi file

2013-07-19 Thread Nishanth Menon
*/ + ; + }; +}; + +omap4_pmx_core { + twl6030_pins: pinmux_twl6030_pins { + pinctrl-single,pins = + 0x15e (WAKEUP_EN | PIN_INPUT_PULLUP | MUX_MODE0) /* sys_nirq1.sys_nirq1 */ + ; + }; +}; -- Regards, Nishanth Menon

Re: [PATCH 0/4] dra7: I2C/MCSPI/UART pin control datas

2013-07-19 Thread Nishanth Menon
=137335590702349w=2 -- Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH 1/3] misc: Add crossbar driver

2013-07-18 Thread Nishanth Menon
+ interrupts = GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH; we should be able to do the following: uart1: serial@4806a000 { snip + interrupts = TI_IRQ_CROSSBAR 192 IRQ_TYPE_LEVEL_HIGH; and not worry about the GIC interrupt number used -- Regards, Nishanth Menon

Re: [PATCH 2/3] ARM: dts: DRA: Add crossbar device binding

2013-07-18 Thread Nishanth Menon
; + }; + counter32k: counter@4ae04000 { compatible = ti,omap-counter32k; reg = 0x4ae04000 0x40; -- Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https

Re: [PATCH 1/3] misc: Add crossbar driver

2013-07-18 Thread Nishanth Menon
On Thu, Jul 18, 2013 at 6:39 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: On Thursday 18 July 2013 02:56 PM, Nishanth Menon wrote: On 07/18/2013 11:43 AM, Sricharan R wrote: Some socs have a large number of interrupts/dma requests to service the needs of its many peripherals

[PATCH 8/9] ARM: dts: omap5-uevm: update LDO7 voltage to 2V and settings

2013-07-17 Thread Nishanth Menon
-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts index 3ff5874..ef05676 100644 --- a/arch/arm/boot/dts/omap5-uevm.dts +++ b/arch/arm

[PATCH 5/9] ARM: dts: omap5-uevm: update LDO3 voltage to 1.5V and settings

2013-07-17 Thread Nishanth Menon
Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts |7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts index a55f4d8..c6d560b 100644 --- a/arch/arm/boot

[PATCH 7/9] ARM: dts: omap5-uevm: update LDO6 voltage to 1.2V

2013-07-17 Thread Nishanth Menon
boards. LDO6 supplies the board specified VDDS_1V2_WKUP supply going to ldo_emu_wkup/vdds_hsic. To stay within the SoC specification supply 1.2V instead of 1.5V. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts |4

[PATCH 0/9] ARM: dts: omap5-uevm: fixup wrong regulator configuration

2013-07-17 Thread Nishanth Menon
Data Manual: http://www.ti.com/product/OMAP5432 - TWL6037 / OTP information: Currently available only under NDA Nishanth Menon (9): ARM: dts: omap5-uevm: document regulator signals used on the actual board ARM: dts: omap5-uevm: update SMPS9 settings ARM: dts: omap5-uevm: update and disable

[PATCH 6/9] ARM: dts: omap5-uevm: update LDO4 voltage to 1.5V and settings

2013-07-17 Thread Nishanth Menon
' supply to SoC IP and is not enabled by PMIC by default at boot. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch

[PATCH 1/9] ARM: dts: omap5-uevm: document regulator signals used on the actual board

2013-07-17 Thread Nishanth Menon
- which is meant to be supported by this dts. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts | 18 ++ 1 file changed, 18 insertions(+) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts

[PATCH 2/9] ARM: dts: omap5-uevm: update SMPS9 settings

2013-07-17 Thread Nishanth Menon
boards. SMPS9 supplies TWL6040 over VDDA_2v1_AUD. This regulator needs to be enabled only when audio is active. Since it does not come active by default, it does not require always-on or boot-on. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm

[PATCH 9/9] ARM: dts: omap5-uevm: update SDCARD LDO9 and resource REGEN3

2013-07-17 Thread Nishanth Menon
. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts index ef05676..65d7b60

[PATCH 3/9] ARM: dts: omap5-uevm: update and disable unused regulators LDO[28]

2013-07-17 Thread Nishanth Menon
...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts index 6709f1e..87b3e9e 100644 --- a/arch/arm/boot/dts/omap5

[PATCH 4/9] ARM: dts: omap5-uevm: update LDO1 voltage to 1.5V and settings

2013-07-17 Thread Nishanth Menon
to SoC IP and is not enabled by PMIC by default at boot. Reported-by: Marc Jüttner m-juett...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap5-uevm.dts |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch

[PATCH 1/2] regulator: palmas-pmic: doc: fix typo for sleep-mode

2013-07-16 Thread Nishanth Menon
commit 3c870e3f9d9d98f1ab98614b3b1fd5c79287d361 (regulator: palmas: Change the DT node property names to follow the convention) Missed updating mode-sleep from sleep-mode. Fix the same. Documentation seems proper for this property. Signed-off-by: Nishanth Menon n...@ti.com --- .../devicetree

Re: [PATCH 0/2] regulator: palmas-pmic: doc: update device tree bindings

2013-07-16 Thread Nishanth Menon
On 09:23-20130716, Nishanth Menon wrote: We seem to have a few missing updates to device tree bindings with the latest set of changes getting merged in. Oops.. seems like I have an old mailID for Mark :( Based on v3.11-rc1 tag Nishanth Menon (2): regulator: palmas-pmic: doc: fix typo

[PATCH V2 0/2] regulator: palmas-pmic: doc: update device tree bindings

2013-07-16 Thread Nishanth Menon
=137398467901450w=2 Based on v3.11-rc1 tag Nishanth Menon (2): regulator: palmas-pmic: doc: fix typo for sleep-mode regulator: palmas-pmic: doc: remove ti,tstep .../devicetree/bindings/regulator/palmas-pmic.txt |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) -- 1.7.9.5 Regards

[PATCH V2 2/2] regulator: palmas-pmic: doc: remove ti,tstep

2013-07-16 Thread Nishanth Menon
commit 28d1e8cd671a53d6b4f967abbbc2a55f7bd333f6 (regulator: palma: add ramp delay support through regulator constraints) Removed the regulator's ti,step option from driver without updating the documentation. So, remove from documentation and example as well. Signed-off-by: Nishanth Menon n

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-09 Thread Nishanth Menon
On 07/09/2013 10:29 AM, Mark Brown wrote: On Mon, Jul 08, 2013 at 12:22:36PM -0500, Nishanth Menon wrote: case #1 - TPS62361 has a single SMPS and a single generic i2c bus, one can talk on. In this case, you'd associate the regulator device in one place - i2cX or on custom SoC hardware

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-08 Thread Nishanth Menon
On 07/05/2013 12:47 PM, Mark Brown wrote: On Fri, Jul 05, 2013 at 12:33:10PM -0500, Nishanth Menon wrote: Taking an example of twl-regulator and omap_pmic, are you suggesting omap_pmic to be a user twl-regulator using include/linux/regulator/consumer.h? or are you suggesting that omap_pmic

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-05 Thread Nishanth Menon
On 16:41-20130704, Mark Brown wrote: On Fri, Jun 21, 2013 at 04:25:42PM -0500, Nishanth Menon wrote: +static const struct omap_pmic_info omap_twl4030_vdd1 = { + .slave_addr = 0x12, + .voltage_reg_addr = 0x00, + .cmd_reg_addr = 0x00, + .i2c_timeout_us = 200, + .slew_rate_uV

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-05 Thread Nishanth Menon
On 07/05/2013 09:08 AM, Mark Brown wrote: On Fri, Jul 05, 2013 at 08:55:07AM -0500, Nishanth Menon wrote: Please write in paragraphs, an enormous wall of unbroken text isn't helpful for legibility. Apologies on the same. Will try to do better. On 16:41-20130704, Mark Brown wrote: So

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-05 Thread Nishanth Menon
On 07/05/2013 11:52 AM, Mark Brown wrote: On Fri, Jul 05, 2013 at 09:50:34AM -0500, Nishanth Menon wrote: On 07/05/2013 09:08 AM, Mark Brown wrote: option 1) we just bypass get_voltage/set_voltage to point through to this function. result will be something similar to what we got here[1] I

Re: [PATCH v2 4/9] wl12xx: use frequency instead of enumerations for pdata clocks

2013-07-02 Thread Nishanth Menon
CONFIG_WILINK_PLATFORM_DATA -- 1.7.10.4 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, Nishanth Menon

Re: [PATCH] Documentation: dt: bindings: TI WiLink modules

2013-06-27 Thread Nishanth Menon
On 11:47-20130627, Luciano Coelho wrote: (added mailing lists and everyone back to the thread) On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote: On 06/25/2013 03:35 AM, Luciano Coelho wrote: +Optional properties: + + +- refclock: the internal WLAN

Re: [PATCH] Documentation: dt: bindings: TI WiLink modules

2013-06-27 Thread Nishanth Menon
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com wrote: On Thu, 2013-06-27 at 07:51 -0500, Nishanth Menon wrote: On 11:47-20130627, Luciano Coelho wrote: (added mailing lists and everyone back to the thread) On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote: On 06/25

Re: [PATCH] Documentation: dt: bindings: TI WiLink modules

2013-06-27 Thread Nishanth Menon
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote: On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote: On 06/27/2013 08:19 AM, Luciano Coelho wrote: On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote: On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com

Re: [PATCH] Documentation: dt: bindings: TI WiLink modules

2013-06-27 Thread Nishanth Menon
On 06/27/2013 01:51 PM, Luciano Coelho wrote: On Thu, 2013-06-27 at 08:39 -0500, Nishanth Menon wrote: On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote: On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote: On 06/27/2013 08:19 AM, Luciano Coelho wrote: On Thu, 2013-06

Re: [PATCH] Documentation: dt: bindings: TI WiLink modules

2013-06-27 Thread Nishanth Menon
On 06/27/2013 02:46 PM, Luciano Coelho wrote: On Thu, 2013-06-27 at 14:12 -0500, Nishanth Menon wrote: [...] Indexes to another entity is always a maintenance burden in the longer run and needs judicious control. If it is possible to avoid it by selecting the right parameters, I am a hard

Re: [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support

2013-06-26 Thread Nishanth Menon
On Wed, Jun 26, 2013 at 3:03 AM, Ruslan Bilovol ruslan.bilo...@ti.com wrote: Hi Nishanth, On Tue, Jun 25, 2013 at 3:43 PM, Nishanth Menon n...@ti.com wrote: On 06/25/2013 07:01 AM, Nishanth Menon wrote: On 06/25/2013 06:32 AM, Ruslan Bilovol wrote: The OMAP4 Blaze Tablet is TI OMAP4

Re: [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support

2013-06-25 Thread Nishanth Menon
://svtronics.com/omap/sevm4460,blaze,omap might help too :) [...] + +#include twl6030.dtsi + Might be good to see the TWL interrupt pin information made available as well? [...] Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss

Re: [PATCH v2] ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support

2013-06-25 Thread Nishanth Menon
On 06/25/2013 07:01 AM, Nishanth Menon wrote: On 06/25/2013 06:32 AM, Ruslan Bilovol wrote: The OMAP4 Blaze Tablet is TI OMAP4 processor-based development platform in a tablet formfactor. The platform contains many of the features found in present-day handsets (such as audio, video, wireless

Re: [PATCHv2 02/11] CLK: use of_property_read_u32 instead of read_u8

2013-06-21 Thread Nishanth Menon
, __func__, shift, node-name); -- 1.7.9.5 -- Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

[RFC PATCH V2 5/8] ARM: dts: OMAP4: add voltage processor nodes

2013-06-21 Thread Nishanth Menon
OMAP443x, OMAP446x SoC use same offsets for voltage processor, however their voltage characteristics differ a little. Introduce the voltage processor nodes for the same. Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4.dtsi| 43

[RFC PATCH V2 4/8] ARM: dts: OMAP4: add voltage controller nodes

2013-06-21 Thread Nishanth Menon
OMAP443x, OMAP446x SoC use same offsets for voltage controller, however their voltage characteristics differ a little. Introduce the voltage controller nodes for the same. Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4.dtsi| 26 ++ arch/arm

[RFC PATCH V2 6/8] ARM: dts: TWL6030/OMAP4: Add OMAP voltage path linkage

2013-06-21 Thread Nishanth Menon
on 4460. Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4-panda-common.dtsi |1 + arch/arm/boot/dts/omap4-panda-es.dts | 13 +++ arch/arm/boot/dts/omap4-sdp.dts |1 + arch/arm/boot/dts/omap4-var-som.dts |1 + arch/arm/boot/dts

[RFC PATCH V2 7/8] ARM: dts: omap4-panda-es: add TPS62361 supply for vdd_mpu

2013-06-21 Thread Nishanth Menon
Unlike other OMAP4 platforms including the the vanilla PandaBoard, PandaBoard-ES uses TPS62361 to supply vdd_mpu. Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4-panda-es.dts | 18 ++ arch/arm/boot/dts/tps62361_omap.dtsi | 18 ++ 2 files

[RFC PATCH V2 8/8] ARM: dts: OMAP4-panda-es: use tps regulator as cpu0 supply

2013-06-21 Thread Nishanth Menon
TPS62361 is used for cpufreq regulation. As part of this change use labels that can be used to reference cpu0 to setup it's supply. Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4-panda-es.dts |4 arch/arm/boot/dts/omap4.dtsi |4 ++-- arch/arm/boot/dts

[RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-21 Thread Nishanth Menon
-developer] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Taras Kondratiuk ta...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../bindings/regulator/omap-pmic-regulator.txt | 41 ++ drivers/regulator/Kconfig | 12 + drivers

[RFC PATCH V2 0/8] regulator/OMAP: support VC/VP support in dts

2013-06-21 Thread Nishanth Menon
discussion: v1 of RFC: http://marc.info/?t=13692468965r=1w=2 related discussion: http://marc.info/?t=13716695495r=1w=2 Nishanth Menon (8): regulator: Introduce OMAP regulator to control PMIC over VC/VP PM / AVS: Introduce support for OMAP Voltage Controller(VC) with device tree

[RFC PATCH V2 2/8] PM / AVS: Introduce support for OMAP Voltage Controller(VC) with device tree nodes

2013-06-21 Thread Nishanth Menon
to the voltage processor. [grygorii.stras...@ti.com, ta...@ti.com: co-developer] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Taras Kondratiuk ta...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../devicetree/bindings/power/omap-vc.txt | 99 ++ drivers

[RFC PATCH V2 3/8] PM / AVS: Introduce support for OMAP Voltage Processor(VP) with device tree nodes

2013-06-21 Thread Nishanth Menon
and OMAP Voltage Controller. [grygorii.stras...@ti.com, ta...@ti.com: co-developer] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Taras Kondratiuk ta...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../devicetree/bindings/power/omap-vp.txt | 39 + drivers

Re: [PATCHv2 10/11] ARM: dts: omap4 clock data

2013-06-19 Thread Nishanth Menon
to omap4460 + */ +/* + * clocks specific to omap4430 + */ +/* + * clocks common to omap44xx + */ could be dropped? btw, are we differentiating 4430 and 4460?A Example: bandgap_fclk in 4430 Vs div_ts_ck, bandgap_ts_fclk in 4460? -- Regards, Nishanth Menon

Re: [PATCHv2 10/11] ARM: dts: omap4 clock data

2013-06-19 Thread Nishanth Menon
On 16:49-20130619, Tero Kristo wrote: On 06/19/2013 04:30 PM, Nishanth Menon wrote: On 16:19-20130619, Tero Kristo wrote: [...] + +/* + * clocks specific to omap4460 + */ +/* + * clocks specific to omap4430 + */ +/* + * clocks common to omap44xx + */ could be dropped? Same

Re: [RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-13 Thread Nishanth Menon
On 19:01-20130610, Mark Brown wrote: On Mon, Jun 10, 2013 at 12:51:42PM -0500, Nishanth Menon wrote: a) Tegra seems to use Lookup Table for sending predefinied voltage values to PMIC. OMAP has no concept of lookup table. They seem to be doing basically the same thing here, you've got

Re: [RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-13 Thread Nishanth Menon
On 15:47-20130613, Mark Brown wrote: On Thu, Jun 13, 2013 at 08:39:50AM -0500, Nishanth Menon wrote: I am having a bit of a difficulty trying to understand your concern here. Your device tree for this stuff appears to mostly consist of repeating the description of the PMIC that we

Re: [RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-13 Thread Nishanth Menon
On Thu, Jun 13, 2013 at 10:07 AM, Mark Brown broo...@kernel.org wrote: On Thu, Jun 13, 2013 at 09:58:03AM -0500, Nishanth Menon wrote: I am proposing moving the following into OF match data. ti,i2c-slave-address ti,i2c-voltage-register ti,i2c-command-register ti,slew-rate-microvolt ti,step

Re: [RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-10 Thread Nishanth Menon
+Paul. On Mon, Jun 10, 2013 at 5:31 AM, Mark Brown broo...@kernel.org wrote: On Wed, May 22, 2013 at 01:18:34PM -0500, Nishanth Menon wrote: So, the biggest problem here has been patch 4 (having to have a hack to deploy this stuff is a bit worrying) plus the general not having a real driver

Re: [RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-06-10 Thread Nishanth Menon
On Mon, Jun 10, 2013 at 11:49 AM, Mark Brown broo...@kernel.org wrote: On Mon, Jun 10, 2013 at 11:16:59AM -0500, Nishanth Menon wrote: On Mon, Jun 10, 2013 at 5:31 AM, Mark Brown broo...@kernel.org wrote: On Wed, May 22, 2013 at 01:18:34PM -0500, Nishanth Menon wrote: So, the biggest

[RFC PATCH 0/4] regulator/OMAP: support VC/VP support in dts

2013-05-22 Thread Nishanth Menon
for 4430 sdp: http://pastebin.com/SkAGB273 4. Once this approach is agreed upon, I can do the dts changes for all SoCs OMAP3-5 and will post a formal series. Related defects: https://bugzilla.kernel.org/show_bug.cgi?id=58541 https://bugzilla.kernel.org/show_bug.cgi?id=58611 Nishanth Menon

[RFC PATCH 4/4] HACK: OMAP4460/TPS/TWL/PandaBoardES - Enable VP regulator for cpufreq

2013-05-22 Thread Nishanth Menon
-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4-panda-es.dts | 55 +++-- arch/arm/boot/dts/omap4.dtsi | 84 +++ arch/arm/boot/dts/omap4460.dtsi |1 + arch/arm/boot/dts/tps62361.dtsi | 90

[RFC PATCH 3/4] PM / AVS: Introduce support for OMAP Voltage Processor(VP) with device tree nodes

2013-05-22 Thread Nishanth Menon
and OMAP Voltage Controller. [grygorii.stras...@ti.com: co-developer] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../devicetree/bindings/power/omap-vp.txt | 39 + drivers/power/avs/Makefile |2

[RFC PATCH 1/4] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-05-22 Thread Nishanth Menon
] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../bindings/regulator/omap-pmic-regulator.txt | 121 + drivers/regulator/Kconfig | 12 + drivers/regulator/Makefile |1 + drivers

[RFC PATCH 2/4] PM / AVS: Introduce support for OMAP Voltage Controller(VC) with device tree nodes

2013-05-22 Thread Nishanth Menon
to the voltage processor. [grygorii.stras...@ti.com: co-developer] Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- .../devicetree/bindings/power/omap-vc.txt | 99 ++ drivers/power/avs/Kconfig | 15 + drivers

Re: [PATCH v5] ARM:dts:omap4-panda: Update the LED support for the panda DTS

2013-05-17 Thread Nishanth Menon
this + gpios = gpio4 14 0; needed + linux,default-trigger = heartbeat; can be dropped + }; + mmc { + label = pandaboard::status2; could be dropped + gpios = gpio1 8 0; needed + linux,default-trigger = mmc0; could be dropped. -- Regards, Nishanth

Re: [PATCH v4] ARM:dts:omap4-panda: Update the LED support for the panda DTS

2013-05-16 Thread Nishanth Menon
On Thu, May 16, 2013 at 10:35 AM, Dan Murphy dmur...@ti.com wrote: I am not sure you really want to do this. If I make the pinctrl part of the led structure then the only way the gpio_wk7 on a1-a3 to be configured is when the CONFIG_LEDS_GPIO flag is set. Do you really want that dependency?

Re: [PATCH v4] ARM:dts:omap4-panda: Update the LED support for the panda DTS

2013-05-15 Thread Nishanth Menon
-- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, Nishanth Menon ___ devicetree-discuss mailing list

Re: [PATCH v3] ARM:dts:omap4-panda:Update the LED support for the panda DTS

2013-05-14 Thread Nishanth Menon
; + gpios = gpio1 8 0; + linux,default-trigger = gpio; mmc0? + }; +}; + Other that that, Tested-by: Nishanth Menon n...@ti.com -- Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https

Re: [PATCH v3 1/5] regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver

2013-05-03 Thread Nishanth Menon
Hi Mark, On 10:02-20130503, Mark Brown wrote: On Thu, May 02, 2013 at 12:20:10PM -0500, Nishanth Menon wrote: From: Andrii.Tseglytskyi andrii.tseglyts...@ti.com Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage

[PATCH v3 4/5] ARM: dts: OMAP4460: Add device nodes for ABB

2013-05-02 Thread Nishanth Menon
From: Andrii.Tseglytskyi andrii.tseglyts...@ti.com Add ABB device nodes for OMAP4460 device Data is based on OMAP4460 Technical Reference Manual revision Z (April 2013) [n...@ti.com: co-developer] Signed-off-by: Nishanth Menon n...@ti.com Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts

[PATCH v3 3/5] ARM: dts: OMAP443x: Add device nodes for ABB

2013-05-02 Thread Nishanth Menon
2013). [n...@ti.com: co-developer] Signed-off-by: Nishanth Menon n...@ti.com Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts...@ti.com --- arch/arm/boot/dts/omap4.dtsi| 32 arch/arm/boot/dts/omap443x.dtsi | 26 ++ 2 files changed

[PATCH v3 2/5] ARM: dts: OMAP36xx: Add device node for ABB

2013-05-02 Thread Nishanth Menon
From: Andrii.Tseglytskyi andrii.tseglyts...@ti.com Add ABB device node for OMAP36xx family of devices. Data is based on OMAP36XX Technical Reference Manual revision AB (Dec 2012). [n...@ti.com: co-developer] Signed-off-by: Nishanth Menon n...@ti.com Signed-off-by: Andrii.Tseglytskyi

[PATCH v3 0/5] regulator/OMAP: Support TI Adaptive Body Bias(ABB) on-chip LDO driver

2013-05-02 Thread Nishanth Menon
Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage. Texas Instruments' SoC processors have an on chip LDO subsystem which is part of the SmartReflex 2 technology and provides support for this power management technique

[PATCH v3 5/5] ARM: dts: OMAP5: Add device nodes for ABB

2013-05-02 Thread Nishanth Menon
] Signed-off-by: Nishanth Menon n...@ti.com Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts...@ti.com --- arch/arm/boot/dts/omap5.dtsi | 67 ++ 1 file changed, 67 insertions(+) diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi index

[PATCH v3 1/5] regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver

2013-05-02 Thread Nishanth Menon
=134931341818379w=2 [3] http://marc.info/?l=linux-arm-kernelm=134931402406853w=2 [n...@ti.com: co-developer] Signed-off-by: Nishanth Menon n...@ti.com Signed-off-by: Andrii.Tseglytskyi andrii.tseglyts...@ti.com --- V2: http://marc.info/?l=linux-omapm=136611169104414w=2 V1: http://marc.info/?l=linux

Re: [PATCH 1/2] PM / OPP: add support to specify phandle of another node for OPP

2013-05-01 Thread Nishanth Menon
-- Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH 2/2] PM / OPP: check for existing OPP list when initialising from device tree

2013-05-01 Thread Nishanth Menon
-ENODEV; -- 1.7.10.4 -- To unsubscribe from this list: send the line unsubscribe linux-pm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, Nishanth Menon

Re: [PATCH 1/2] PM / OPP: add support to specify phandle of another node for OPP

2013-05-01 Thread Nishanth Menon
On 17:28-20130501, Sudeep KarkadaNagesha wrote: On 01/05/13 15:41, Nishanth Menon wrote: On 12:11-20130501, sudeep.karkadanage...@arm.com wrote: From: Sudeep KarkadaNagesha sudeep.karkadanage...@arm.com If more than one similar devices share the same OPPs, currently we need to replicate

[PATCH 1/2] ARM: dts: OMAP36xx: Fix CPU OPP voltages

2013-04-26 Thread Nishanth Menon
commit 3027e26 (ARM: dts: OMAP36xx: Add CPU OPP table) introduced wrong OPP voltages per OPP by mistake. Sync the OPP tables with existing OMAP36xx OPP data in arch/arm/mach-omap2/opp3xxx_data.c Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap36xx.dtsi |6 +++--- 1 file

[PATCH 0/2] ARM: dts: OMAP36xx/OMAP4460 Fix CPU OPP voltages

2013-04-26 Thread Nishanth Menon
entries. I have cross verified that OMAP3430,3630,4430 and 4460 entries now match that of corresponding opp*_data.c My sincere apologies on the oversight. Nishanth Menon (2): ARM: dts: OMAP36xx: Fix CPU OPP voltages ARM: dts: OMAP4460: Fix CPU OPP voltages arch/arm/boot/dts/omap36xx.dtsi

[PATCH 2/2] ARM: dts: OMAP4460: Fix CPU OPP voltages

2013-04-26 Thread Nishanth Menon
commit d16fb25 (ARM: dts: OMAP4460: Add CPU OPP table) introduced wrong OPP voltages per OPP by mistake. Sync the OPP tables with existing OMAP4460 OPP data in arch/arm/mach-omap2/opp4xxx_data.c Signed-off-by: Nishanth Menon n...@ti.com --- arch/arm/boot/dts/omap4460.dtsi |6 +++--- 1 file

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-15 Thread Nishanth Menon
On Mon, Apr 15, 2013 at 11:22 AM, Stephen Warren swar...@wwwdotorg.org wrote: On 04/12/2013 04:54 PM, Nishanth Menon wrote: OMAP clock data is located in arch/arm/mach-omap2/cclockXYZ_data.c. However, this presents an obstacle for using these clock nodes in Device Tree definitions

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-14 Thread Nishanth Menon
On 10:22-20130413, Tony Lindgren wrote: * Nishanth Menon n...@ti.com [130412 16:43]: Thanks for checking up. Fixed all of them below, will post part of series again, only if I need to address further comments in other patches.. Thanks it seems that the other ones are ready to go, just

[PATCH V4 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot

2013-04-12 Thread Nishanth Menon
/1jjSRKQh Pandaboard-ES -(OMAP4460 ES1.1) - http://pastebin.com/B5acTbch Nishanth Menon (6): clk: OMAP: introduce device tree binding to kernel clock data [Clk probably belongs to mike's tree?] ARM: dts: OMAP3: add clock nodes for CPU ARM: dts: OMAP4: add clock nodes for CPU ARM: dts

[PATCH V4 2/6] ARM: dts: OMAP3: add clock nodes for CPU

2013-04-12 Thread Nishanth Menon
OMAP34xx and OMAP36xx platforms use dpll1 clock. Add same to common definition. Cc: Benoit Cousson b-cous...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- RFC of this patch was discussed in http://marc.info/?t=13637032569r=1w=2 along with the detailed context as to why

[PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-12 Thread Nishanth Menon
, Grygorii Strashko and others. Cc: Kevin Hilman khil...@deeprootsystems.com Cc: Mike Turquette mturque...@linaro.org Cc: Paul Walmsley p...@pwsan.com [t...@atomide.com: co-developed] Signed-off-by: Tony Lindgren t...@atomide.com Signed-off-by: Nishanth Menon n...@ti.com --- RFC of this patch

[PATCH V4 3/6] ARM: dts: OMAP4: add clock nodes for CPU

2013-04-12 Thread Nishanth Menon
OMAP443x, OMAP446x and OMAP447x platforms use dpll_mpu clock. Add same to common definition. Cc: Benoit Cousson b-cous...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- RFC of this patch approach for OMAP3 was discussed in http://marc.info/?t=13637032569r=1w=2 along with the detailed

[PATCH V4 4/6] ARM: dts: AM33XX: add clock nodes for CPU

2013-04-12 Thread Nishanth Menon
...@atomide.com Signed-off-by: Nishanth Menon n...@ti.com --- RFC of this patch was discussed in http://marc.info/?t=13637032569r=1w=2 along with the detailed context as to why this is an intermediate step. previous revisions of cpufreq-cpu0 support do not use this approach. [Probably belongs

[PATCH V4 6/6] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot

2013-04-12 Thread Nishanth Menon
: Paul Walmsley p...@pwsan.com Cc: Tony Lindgren t...@atomide.com Signed-off-by: Nishanth Menon n...@ti.com --- Introduced as a result of alignment in http://marc.info/?t=13645077344r=1w=2 previous versions do not use this approach. This would probably be good to get merged *after* Rafael's tree

[PATCH V4 5/6] ARM: OMAP2+: AM33XX: add lateinit hook for calling pm late init

2013-04-12 Thread Nishanth Menon
Signed-off-by: Nishanth Menon n...@ti.com --- Introduced as a result of alignment in http://marc.info/?t=13645077344r=1w=2 previous versions do not use this approach. [Probably belongs to Kevin/Tony's tree?] arch/arm/mach-omap2/board-generic.c |1 + arch/arm/mach-omap2/common.h

Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data

2013-04-12 Thread Nishanth Menon
On 16:31-20130412, Tony Lindgren wrote: * Nishanth Menon n...@ti.com [130412 15:59]: --- /dev/null +++ b/drivers/clk/omap/clk.c +/** + * omap_clk_src_get() - Get OMAP clock from node name when needed + * @clkspec: clkspec argument + * @data: unused + * + * REVISIT: We

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-11 Thread Nishanth Menon
On Thu, Apr 11, 2013 at 1:46 PM, Mike Turquette mturque...@linaro.org wrote: Quoting Nishanth Menon (2013-04-10 10:39:21) diff --git a/drivers/clk/omap/clk.c b/drivers/clk/omap/clk.c new file mode 100644 index 000..63a4cce --- /dev/null +++ b/drivers/clk/omap/clk.c @@ -0,0 +1,94

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-11 Thread Nishanth Menon
On Thu, Apr 11, 2013 at 2:48 AM, Roger Quadros rog...@ti.com wrote: On 04/10/2013 08:39 PM, Nishanth Menon wrote: On 13:55-20130410, Roger Quadros wrote: On 04/10/2013 11:06 AM, Mike Turquette wrote: Quoting Nishanth Menon (2013-04-09 13:49:00) Folks, this does seem to be the best compromise

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-10 Thread Nishanth Menon
On 13:55-20130410, Roger Quadros wrote: On 04/10/2013 11:06 AM, Mike Turquette wrote: Quoting Nishanth Menon (2013-04-09 13:49:00) On 10:43-20130409, Tony Lindgren wrote: * Tony Lindgren t...@atomide.com [130409 09:54]: * Roger Quadros rog...@ti.com [130409 03:00]: On 04/05/2013 06:58

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-10 Thread Nishanth Menon
Hi Tony, On Wed, Apr 10, 2013 at 1:49 PM, Tony Lindgren t...@atomide.com wrote: * Nishanth Menon n...@ti.com [130410 10:44]: Details in the patch below (Tony, I have added you as collaborator for helping in getting this working-clk_add_alias was'nt needed in the internal patch discussion we

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-09 Thread Nishanth Menon
- see log: http://pastebin.com/F9A2zSTr Would an cleaned up version be good enough as a step #1 of transition? From 7d373bdb9e9549c1b6ba1775a8dfd96ebe78abfb Mon Sep 17 00:00:00 2001 From: Nishanth Menon n...@ti.com Date: Tue, 26 Mar 2013 10:23:27 + Subject: [PATCH] OMAP: add devicetree support

Re: [RFC][PATCH 1/2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-09 Thread Nishanth Menon
On 15:49-20130409, Nishanth Menon wrote: On 10:43-20130409, Tony Lindgren wrote: * Tony Lindgren t...@atomide.com [130409 09:54]: * Roger Quadros rog...@ti.com [130409 03:00]: On 04/05/2013 06:58 PM, Tony Lindgren wrote: Can't you just use the clock name there to get

Re: [PATCH v2] ARM: OMAP4: clock: Add device tree support for AUXCLKs

2013-04-05 Thread Nishanth Menon
, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH V2 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot

2013-03-28 Thread Nishanth Menon
today. Regards, Nishanth Menon ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH V2 8/8] cpufreq: OMAP: donot allow to be used with device tree

2013-03-27 Thread Nishanth Menon
On 11:39-20130327, Kevin Hilman wrote: Nishanth Menon n...@ti.com writes: #include linux/module.h @@ -174,6 +175,19 @@ static inline void freq_table_free(void) static int __cpuinit omap_cpu_init(struct cpufreq_policy *policy) { int result = 0; + struct device_node *np

[PATCH V2 6/8] ARM: dts: OMAP4460: Add CPU OPP table

2013-03-19 Thread Nishanth Menon
...@vger.kernel.org Cc: devicetree-discuss@lists.ozlabs.org Cc: linux-arm-ker...@lists.infradead.org Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - depend on 4460.dtsi available in benoit/for_3.10/dts branch - donot delete

[PATCH V2 8/8] cpufreq: OMAP: donot allow to be used with device tree

2013-03-19 Thread Nishanth Menon
: Shawn Guo shawn@linaro.org Cc: Keerthy j-keer...@ti.com Cc: linux-o...@vger.kernel.org Cc: devicetree-discuss@lists.ozlabs.org Cc: linux-arm-ker...@lists.infradead.org Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2

[PATCH V2 2/8] ARM: dts: OMAP36xx: Add CPU OPP table

2013-03-19 Thread Nishanth Menon
...@vger.kernel.org Cc: devicetree-discuss@lists.ozlabs.org Cc: linux-arm-ker...@lists.infradead.org Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - donot delete the OPP table entries in omap3xxx_data.c - little more

[PATCH V2 4/8] ARM: dts: OMAP443x: Add CPU OPP table

2013-03-19 Thread Nishanth Menon
...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - introduce omap443x.dtsi - donot delete the OPP table entries in omap4xxx_data.c - little more verbose commit log V1: https://patchwork.kernel.org/patch/2273581/ arch

[PATCH V2 1/8] ARM: dts: OMAP34xx/35xx: Add CPU OPP table

2013-03-19 Thread Nishanth Menon
Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - introduce omap34xx.dtsi - donot delete the OPP table entries in omap3xxx_data.c - little more verbose commit log V1: https://patchwork.kernel.org/patch

[PATCH V2 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot

2013-03-19 Thread Nishanth Menon
/3EymNTMp Nishanth Menon (8): ARM: dts: OMAP34xx/35xx: Add CPU OPP table ARM: dts: OMAP36xx: Add CPU OPP table ARM: dts: OMAP3: use twl4030 vdd1 regulator for CPU ARM: dts: OMAP443x: Add CPU OPP table ARM: dts: omap4-panda: move generic sections to panda-common ARM: dts: OMAP4460: Add CPU OPP

[PATCH V2 3/8] ARM: dts: OMAP3: use twl4030 vdd1 regulator for CPU

2013-03-19 Thread Nishanth Menon
: linux-arm-ker...@lists.infradead.org Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - little more verbose commit log (no functional changes) V1: https://patchwork.kernel.org/patch/2273701/ arch/arm/boot/dts/omap3-beagle

[PATCH V2 5/8] ARM: dts: omap4-panda: move generic sections to panda-common

2013-03-19 Thread Nishanth Menon
: Keerthy j-keer...@ti.com Cc: linux-o...@vger.kernel.org Cc: devicetree-discuss@lists.ozlabs.org Cc: linux-arm-ker...@lists.infradead.org Cc: cpuf...@vger.kernel.org Cc: linux...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - use omap443x.dtsi and 4460.dtsi

[PATCH V2 7/8] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot

2013-03-19 Thread Nishanth Menon
...@vger.kernel.org Signed-off-by: Nishanth Menon n...@ti.com --- Changes in V2: - no functional changes V1: https://patchwork.kernel.org/patch/2273621/ arch/arm/mach-omap2/board-generic.c |5 + arch/arm/mach-omap2/cclock33xx_data.c |2 +- arch/arm/mach-omap2/cclock3xxx_data.c

  1   2   >