Re: [PATCH 2/2] arm/dts: OMAP2+: Add mailbox nodes

2012-05-24 Thread Cousson, Benoit
On 5/1/2012 7:47 PM, Omar Ramirez Luna wrote: Add nodes for mailbox DT, to interface with hwmods. Signed-off-by: Omar Ramirez Luna Acked-by: Benoit Cousson --- arch/arm/boot/dts/omap2.dtsi |5 + arch/arm/boot/dts/omap3.dtsi |5 + arch/arm/boot/dts/omap4.dtsi |5 +

Re: [PATCH 0/2] OMAP: mailbox initial device tree support

2012-05-24 Thread Cousson, Benoit
On 5/2/2012 7:42 AM, Bedia, Vaibhav wrote: Hi Omar, On Tue, May 01, 2012 at 23:17:38, Omar Ramirez Luna wrote: To allow mailbox driver to function with device tree. Tested in OMAP4 and OMAP3. OMAP2 untested. I think the mailbox code needs a cleanup similar to what you had proposed earlier [1

Re: [PATCH v3 4/4] ARM: omap: pass minimal SoC/board data for UART from dt

2012-04-11 Thread Cousson, Benoit
Hi Omar, On 4/11/2012 2:16 AM, Ramirez Luna, Omar wrote: Hi, On Wed, Dec 14, 2011 at 5:55 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. ... diff --g

Re: [PATCH v3 0/2] Device tree support for TWL regulators

2012-02-27 Thread Cousson, Benoit
On 2/27/2012 11:17 PM, Grant Likely wrote: On Mon, Feb 27, 2012 at 6:52 AM, Cousson, Benoit wrote: Hi Mark, On 2/27/2012 2:41 PM, Mark Brown wrote: On Mon, Feb 27, 2012 at 06:01:20PM +0530, Rajendra Nayak wrote: Depending on what order Mark happens to pull them in, I am fine re-sending

Re: [PATCH v3 0/2] Device tree support for TWL regulators

2012-02-27 Thread Cousson, Benoit
On 2/27/2012 3:03 PM, Mark Brown wrote: On Mon, Feb 27, 2012 at 02:52:05PM +0100, Cousson, Benoit wrote: On 2/27/2012 2:41 PM, Mark Brown wrote: On Mon, Feb 27, 2012 at 06:01:20PM +0530, Rajendra Nayak wrote: Please can you guys come up with a single unified series for this stuff - I&#x

Re: [PATCH v3 0/2] Device tree support for TWL regulators

2012-02-27 Thread Cousson, Benoit
Hi Mark, On 2/27/2012 2:41 PM, Mark Brown wrote: On Mon, Feb 27, 2012 at 06:01:20PM +0530, Rajendra Nayak wrote: Depending on what order Mark happens to pull them in, I am fine re-sending adding support for the 2 twl6030 fixed regulators. Please can you guys come up with a single unified ser

Re: [PATCH v2 1/4] mmc: omap_hsmmc: Convert hsmmc driver to use device tree

2012-02-24 Thread Cousson, Benoit
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, 2012 at 5:31 PM, Rajendra Nayak wrote: ... +Required

Re: [PATCH v2 1/4] mmc: omap_hsmmc: Convert hsmmc driver to use device tree

2012-02-24 Thread Cousson, Benoit
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 to extract data (which was earlier passed as platform_data) fro

Re: [PATCH v2 4/4] arm/dts: OMAP3: Add mmc controller nodes and board data

2012-02-24 Thread Cousson, Benoit
On 2/24/2012 5:00 AM, Rajendra Nayak wrote: 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 { + compatible = "ti,omap2-hsmmc"; + ti,hwmods

Re: [PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver

2012-01-13 Thread Cousson, Benoit
On 1/12/2012 11:52 PM, Kevin Hilman wrote: Richard Zhao writes: [...] Do you have real case to need different voltage/clk? Sure, any system with independently scalable CPUs/clusters. AFAIK, in the ARM SoC world there is a least the MSM8660 that does support that today. Regards, Benoit

Re: [PATCH v3 4/4] ARM: omap: pass minimal SoC/board data for UART from dt

2011-12-16 Thread Cousson, Benoit
Hi Rajendra, Just one minor comment if you plan to repost. On 12/14/2011 12:55 PM, 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. Acked-by: Rob Herring Sign

Re: [PATCH v3 4/4] ARM: omap: pass minimal SoC/board data for UART from dt

2011-12-15 Thread Cousson, Benoit
On 12/15/2011 10:13 PM, Tony Lindgren wrote: * Cousson, Benoit [111215 01:34]: Hi Tony, On 12/15/2011 7:52 AM, Rajendra Nayak wrote: 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

Re: [PATCH v3 4/4] ARM: omap: pass minimal SoC/board data for UART from dt

2011-12-15 Thread Cousson, Benoit
Hi Tony, On 12/15/2011 7:52 AM, Rajendra Nayak wrote: 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 gene

Re: [PATCH] ARM: omap_hwmod: Add a new state to handle hwmods left enabled at init

2011-11-18 Thread Cousson, Benoit
Hi Kevin and Rajendra, On 11/18/2011 7:44 AM, Rajendra Nayak wrote: 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

Re: [PATCH] ARM: omap_hwmod: Add a new state to handle hwmods left enabled at init

2011-11-17 Thread Cousson, Benoit
+ 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 enable it at a later point, the hmwod framework throws a WARN() about ty

Re: [PATCH 1/3] ARM: omap_device: handle first time activation of console device

2011-11-17 Thread Cousson, Benoit
Hi Rajendra, On 11/17/2011 8:19 AM, Rajendra Nayak wrote: [...] +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 bef

Re: [PATCH 1/3] ARM: omap_device: handle first time activation of console device

2011-11-16 Thread Cousson, Benoit
On 11/16/2011 4:41 PM, Rob Herring wrote: Benoit, On 11/16/2011 09:14 AM, Cousson, Benoit wrote: Hi Rob, On 11/16/2011 3:50 PM, Rob Herring wrote: On 11/16/2011 05:02 AM, Rajendra Nayak wrote: console device on OMAP is never reset or idled by hwmod post initial setup, early during boot, for

Re: [PATCH 1/3] ARM: omap_device: handle first time activation of console device

2011-11-16 Thread Cousson, Benoit
Hi Rob, On 11/16/2011 3:50 PM, Rob Herring wrote: On 11/16/2011 05:02 AM, Rajendra Nayak wrote: console device on OMAP is never reset or idled by hwmod post initial setup, early during boot, for obvious reasons not to break early debug prints thrown on console. This leaves the console device en

Re: [PATCH 1/3] ARM: omap_device: handle first time activation of console device

2011-11-16 Thread Cousson, Benoit
Hi Rajendra, On 11/16/2011 12:02 PM, Rajendra Nayak wrote: > console device on OMAP is never reset or idled by hwmod post > initial setup, early during boot, for obvious reasons not to > break early debug prints thrown on console. > This leaves the console device enabled at boot and the first acti

Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement

2010-08-27 Thread Cousson, Benoit
Hi Vishwa, On 8/28/2010 12:08 AM, vishwanath.sripa...@linaro.org wrote: > From: Vishwanath BS > > This patch has instrumentation code for measuring latencies for > various CPUIdle C states for OMAP. Idea here is to capture the > timestamp at various phases of CPU Idle and then compute the sw > lat