linux-arm-kernel&m=137335590702349&w=2
--
Regards,
Nishanth Menon
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
drm_msecure */
+ >;
+ };
+};
+
+&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
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
On Thu, Jul 18, 2013 at 6:39 PM, Santosh Shilimkar
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 periphe
reg-width = <16>;
+ crossbar-lines = "dma-req", "mcasp3-rx", <0x7e 0x84
0xfc>,
+"dma-req", "mcasp3-tx", <0x7d 0x85
0xfa>;
+ };
+
counter32k: coun
tion happens dynamically
c) allow products use IPs as needed.
Sorry, Conceptually option 3 is the right approach in my view.
instead of doing
uart1: serial@4806a000 {
+ interrupts = ;
we should be able to do the following:
uart1: serial@4806a000 {
+
it is
a 'on need' supply to SoC IP and is not enabled by PMIC by
default at boot.
Reported-by: Marc Jüttner
Signed-off-by: Nishanth Menon
---
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
-by: Nishanth Menon
---
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-uevm.dts
+++ b/arch/arm/boot
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
Signed-off-by: Nishanth Menon
---
arch/arm/boo
need basis.
Reported-by: Marc Jüttner
Signed-off-by: Nishanth Menon
---
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 100644
--- a/arc
- which is meant to be supported by this dts.
Reported-by: Marc Jüttner
Signed-off-by: Nishanth Menon
---
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/omap5-uevm.dts
index 08b7267
as it is a 'on need'
supply to SoC IP and is not enabled by PMIC by default at boot.
Reported-by: Marc Jüttner
Signed-off-by: Nishanth Menon
---
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/ar
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
Signed-off-by: Nishanth Menon
---
arch/arm/boot/dts/omap5-uevm.dts |4 ++--
1 file changed, 2
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
Jüttner
Signed-off-by: Nishanth Menon
---
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/dts/omap5-uevm.dts
+++ b/arch
ce we have no plans
of programming efuse bits - it can only be done once - in factory.
Further it is not enabled by default by PMIC so, 'boot-on' must be
removed, and the 'always-on' needs to be removed to achieve pulsing
if efuse needs to be programmed.
Reported-by: Marc Jü
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
mp;m=137398467901450&w=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
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 example seems proper for this property.
Signed-off-by: Nishanth Menon
---
.../devicetree
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):
> regula
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
---
.../devicetree/bindings
commit 28d1e8cd671a53d6b4f967abbbc2a55f7bd333f6
(regulator: palma: add ramp delay support through regulator constraints)
Removed the regulator's ti,step option from driver without updating the
documentation. remove the support from documentation and example as well.
Signed-off-by: Nishanth
We seem to have a few missing updates to device tree bindings with the
latest set of changes getting merged in.
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
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 har
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
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
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:
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,
> - WL12XX_TCXOCLOCK_16_368 = 4, /* 16.368 MHz */
> - WL12XX_TCXOCLOCK_32_736 = 5, /* 32.736 MHz */
> - WL12XX_TCXOCLOCK_16_8 = 6, /* 16.8 MHz */
> - WL12XX_TCXOCLOCK_33_6 = 7, /* 33.6 MHz */
> -};
> -
> struct wl1251_platform_data {
> void (*set_pow
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
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 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
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho 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, Luc
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 wrote:
For the actual DTS files, I could add a wilink.dtsi with enumerations
for these values so they could be used in the node definitions
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho 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
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:
> > > +--
On Wed, Jun 26, 2013 at 3:03 AM, Ruslan Bilovol wrote:
> Hi Nishanth,
>
> On Tue, Jun 25, 2013 at 3:43 PM, Nishanth Menon wrote:
>> On 06/25/2013 07:01 AM, Nishanth Menon wrote:
>>>
>>> On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
>>>>
>>&g
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
://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
devicetr
AP Voltage Processor and OMAP Voltage Controller.
[grygorii.stras...@ti.com, ta...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Taras Kondratiuk
Signed-off-by: Nishanth Menon
---
.../devicetree/bindings/power/omap-vp.txt | 39 +
driver
ng to the voltage processor.
[grygorii.stras...@ti.com, ta...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Taras Kondratiuk
Signed-off-by: Nishanth Menon
---
.../devicetree/bindings/power/omap-vc.txt | 99 ++
drivers/power/avs/Kc
rnel.org/show_bug.cgi?id=58611
Related discussion:
v1 of RFC: http://marc.info/?t=13692468965&r=1&w=2
related discussion: http://marc.info/?t=13716695495&r=1&w=2
Nishanth Menon (8):
regulator: Introduce OMAP regulator to control PMIC over VC/VP
PM / AVS: Introduc
ture equivalent modules.
[grygorii.stras...@ti.com, ta...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Taras Kondratiuk
Signed-off-by: Nishanth Menon
---
.../bindings/regulator/omap-pmic-regulator.txt | 41 ++
drivers/regulator/Kconfig
Unlike other OMAP4 platforms including the the "vanilla" PandaBoard,
PandaBoard-ES uses TPS62361 to supply vdd_mpu.
Signed-off-by: Nishanth Menon
---
arch/arm/boot/dts/omap4-panda-es.dts | 18 ++
arch/arm/boot/dts/tps62361_omap.dtsi | 18 ++
2 fil
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
---
arch/arm/boot/dts/omap4-panda-es.dts |4
arch/arm/boot/dts/omap4.dtsi |4 ++--
arch/arm/boo
4460.
Signed-off-by: Nishanth Menon
---
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/twl6030_omap4.dtsi
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
---
arch/arm/boot/dts/omap4.dtsi| 26 ++
arch/arm/boot/dts
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
---
arch/arm/boot/dts/omap4.dtsi| 43 +++
arch/arm
gt; index c9f9f32..e63dd1b 100644
> > --- a/drivers/clk/clk-mux.c
> > +++ b/drivers/clk/clk-mux.c
> > @@ -170,7 +170,7 @@ void of_mux_clk_setup(struct device_node *node)
> > int i;
> > u8 clk_mux_flags = 0;
> > u32 mask = 0;
> &g
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 sp
* 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
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
On Thu, Jun 13, 2013 at 10:07 AM, Mark Brown 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
>&g
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 d
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
On Mon, Jun 10, 2013 at 11:49 AM, Mark Brown 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 wrote:
>> > On Wed, May 22, 2013 at 01:18:34PM -0500, Nishanth Menon wrote:
>
>> > So, the biggest
+Paul.
On Mon, Jun 10, 2013 at 5:31 AM, Mark Brown 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
> driv
ng to the voltage processor.
[grygorii.stras...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Nishanth Menon
---
.../devicetree/bindings/power/omap-vc.txt | 99 ++
drivers/power/avs/Kconfig | 15 +
drivers/power/avs/Mak
ture equivalent modules.
[grygorii.stras...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Nishanth Menon
---
.../bindings/regulator/omap-pmic-regulator.txt | 121 +
drivers/regulator/Kconfig | 12 +
drivers/regulator/Makefile
AP Voltage Processor and OMAP Voltage Controller.
[grygorii.stras...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko
Signed-off-by: Nishanth Menon
---
.../devicetree/bindings/power/omap-vp.txt | 39 +
drivers/power/avs/Makefile |2 +-
drivers
C -> TWL6030/vcore1
NOT-Signed-off-by: Nishanth Menon
---
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/dt
rs/power/avs/omap_vc.c
create mode 100644 drivers/power/avs/omap_vc.h
create mode 100644 drivers/power/avs/omap_vp.c
create mode 100644 drivers/regulator/omap-pmic-regulator.c
create mode 100644 include/linux/regulator/omap-pmic-regulator.h
Regar
ins: gpio_led_pmx {
> + pinctrl-single,pins = <
> + 0xb6 0x3/* gpio_110 OUTPUT | MODE 3 */
> + >;
> + };
> +};
> +
> +&led_wkgpio_pins {
> + pinctrl-single,pins = <
> +
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 Menon
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
On Thu, May 16, 2013 at 3:22 PM, Dan Murphy wrote:
> On 05/16/2013 01:18 PM, Nishanth Menon wrote:
>> On Thu, May 16, 2013 at 10:35 AM, Dan Murphy 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
On Thu, May 16, 2013 at 10:35 AM, Dan Murphy 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? You did
ap4_pmx_wkup {
> + pinctrl-names = "default";
> + pinctrl-0 = <
> + &led_wkgpio_pins
> + >;
> +
> + led_wkgpio_pins: pinmux_leds_wkpins {
> + pinctrl-single,pins = <
> + 0x1c 0x3/* gpio_wk8 OUTPUT | MODE 3 */
> + >;
> + };
> +};
> --
> 1.7.5.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
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
;&gpio4 14 0>;
> + linux,default-trigger = "heartbeat";
> + };
> + mmc {
> + label = "pandaboard::status2";
> + gpios = <&gpio1 8 0>;
> + linux,default-trigger = "gpio";
mmc0?
>
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"
> >
> > Adaptive Body Biasing (ABB) modulates transistor bias voltages
> > dynamically in order to optimize swit
m=134931341818379&w=2
[3] http://marc.info/?l=linux-arm-kernel&m=134931402406853&w=2
[n...@ti.com: co-developer]
Signed-off-by: Nishanth Menon
Signed-off-by: Andrii.Tseglytskyi
---
V2: http://marc.info/?l=linux-omap&m=136611169104414&w=2
V1: http://marc.info/?l=linux-omap&m=13
From: "Andrii.Tseglytskyi"
Add ABB device nodes for OMAP5 family of devices. Data is based on
OMAP543x Technical Reference Manual revision U (April 2013).
NOTE: clock node has been disabled in this patch due to the lack of
OMAP5 clock data.
[n...@ti.com: co-developer]
Signed-off-by
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 wit
From: "Andrii.Tseglytskyi"
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
Signed-off-by: Andrii.Tseglytskyi
---
arch/arm/boot/dts/omap3.dtsi
...@ti.com: co-developer]
Signed-off-by: Nishanth Menon
Signed-off-by: Andrii.Tseglytskyi
---
arch/arm/boot/dts/omap4.dtsi| 32
arch/arm/boot/dts/omap443x.dtsi | 26 ++
2 files changed, 58 insertions(+)
diff --git a/arch/arm/boot
From: "Andrii.Tseglytskyi"
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
Signed-off-by: Andrii.Tseglytskyi
---
arch/arm/boot/dts/omap4460.d
On 17:33-20130501, Sudeep KarkadaNagesha wrote:
> On 01/05/13 16:04, Nishanth Menon wrote:
> > On 12:11-20130501, sudeep.karkadanage...@arm.com wrote:
> >> From: Sudeep KarkadaNagesha
[...]
> >> diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
> &g
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
> >>
> >> If more than one similar devices share the same OPPs, current
two?
> prop = of_find_property(of_node, "operating-points", NULL);
> if (!prop)
> return -ENODEV;
> --
> 1.7.10.4
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majord...
> @@ -741,5 +745,15 @@ int of_init_opp_table(struct device *dev)
>
> return 0;
> }
missing EOL?
> +/**
> + * of_init_opp_table() - Initialize opp table from device tree
> + * @dev: device pointer used to lookup device OPPs.
> + *
> + * Register the initial O
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
---
arch/arm/boot/dts/omap4460.dtsi |6 +++---
1 file changed, 3
o 3.10 dts 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/oma
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
---
arch/arm/boot/dts/omap36xx.dtsi |6 +++---
1 file changed, 3
On Mon, Apr 15, 2013 at 11:22 AM, Stephen Warren 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. Th
On 10:22-20130413, Tony Lindgren wrote:
> * Nishanth Menon [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 one
On 16:31-20130412, Tony Lindgren wrote:
> * Nishanth Menon [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
> > + * @da
Call OMAP2+ generic lateinit hook from AM specific late init hook.
This allows the generic late initializations such as cpufreq hooks
to be active.
Cc: Benoit Cousson
Cc: Kevin Hilman
Cc: Paul Walmsley
Cc: Tony Lindgren
Signed-off-by: Nishanth Menon
---
Introduced as a result of alignment in
-by: Nishanth Menon
---
Introduced as a result of alignment in
http://marc.info/?t=13645077344&r=1&w=2
previous versions do not use this approach.
This would probably be good to get merged *after* Rafael's tree is merged in.
[Probably belongs to Kevin/Tony's tree?]
arch/a
AM33XX based platforms use dpll_mpu clock. Add same to common dtsi
and remove the dummy clock node entry as AM33XX platform supports
only device tree based boot.
Cc: Benoit Cousson
Cc: Kevin Hilman
Cc: Paul Walmsley
Cc: Tony Lindgren
Signed-off-by: Nishanth Menon
---
RFC of this patch was
OMAP443x, OMAP446x and OMAP447x platforms use dpll_mpu clock.
Add same to common definition.
Cc: Benoit Cousson
Signed-off-by: Nishanth Menon
---
RFC of this patch approach for OMAP3 was discussed in
http://marc.info/?t=13637032569&r=1&w=2
along with the detailed context as to why
contributions from Roger Quadros, Grygorii Strashko
and others.
Cc: Kevin Hilman
Cc: Mike Turquette
Cc: Paul Walmsley
[t...@atomide.com: co-developed]
Signed-off-by: Tony Lindgren
Signed-off-by: Nishanth Menon
---
RFC of this patch was discussed in http://marc.info/?t=13637032569&r=
OMAP34xx and OMAP36xx platforms use dpll1 clock. Add same to common
definition.
Cc: Benoit Cousson
Signed-off-by: Nishanth Menon
---
RFC of this patch was discussed in http://marc.info/?t=13637032569&r=1&w=2
along with the detailed context as to why this is an intermediate step.
/pastebin.com/FdrG4Rna
Pandaboard -(OMAP4430 ES2.1) - http://pastebin.com/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
On Thu, Apr 11, 2013 at 2:48 AM, Roger Quadros 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
On Thu, Apr 11, 2013 at 1:46 PM, Mike Turquette 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/driver
Hi Tony,
On Wed, Apr 10, 2013 at 1:49 PM, Tony Lindgren wrote:
> * Nishanth Menon [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 discussi
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 [130409 09:54]:
> >>>> * Roger Quadros [130409
On 15:49-20130409, Nishanth Menon wrote:
> On 10:43-20130409, Tony Lindgren wrote:
> > * Tony Lindgren [130409 09:54]:
> > > * Roger Quadros [130409 03:00]:
> > > > On 04/05/2013 06:58 PM, Tony Lindgren wrote:
> > > > >
> > >
o clock = <&clk mpu_dpll>;
instead, I am forced to do clock = <&clk 249>;
Here is an attempt on beagleXM - adds every clock node to the list.
Tons of un-necessary prints added to give an idea - see log:
http://pastebin.com/F9A2zSTr
Would an cleaned up version be good enough as a
eate mode 100644 Documentation/devicetree/bindings/clock/omap4-clock.txt
If we are doing this, we might as well do for all platforms(OMAP3-5,
AM..) in an series, no?
--
Regards,
Nishanth Menon
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
of remaining patches later today.
Regards,
Nishanth Menon
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
On 11:39-20130327, Kevin Hilman wrote:
> Nishanth Menon writes:
> > #include
> > @@ -174,6 +175,19 @@ static inline void freq_table_free(void)
> > static int __cpuinit omap_cpu_init(struct cpufreq_policy *policy)
> > {
> > int result =
c: Santosh Shilimkar
Cc: Shawn Guo
Cc: Keerthy
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
---
Changes in V2:
- no function
ux-arm-ker...@lists.infradead.org
Cc: cpuf...@vger.kernel.org
Cc: linux...@vger.kernel.org
Signed-off-by: Nishanth Menon
---
Changes in V2:
- use omap443x.dtsi and 4460.dtsi
- little more verbose commit log
V1: https://patchwork.kernel.org/patch/2273671/
arch/arm/boot/dts/omap4-pa
1 - 100 of 129 matches
Mail list logo
