about n810 integration status

2011-06-25 Thread Kim HeungJun
Hi everyone, Does anybody knows about n810 integration status on Kernel? I have one n810, and I try to update the newest kernel and filesystem image freely. And, if anyone know about , please let me know. The information which I know is just the flasher from Nokia is needed for updating. And,

Re: [PATCH] USB: OTG: Use work_queue in set_vbus for TWL6030 transciever

2011-06-25 Thread Todd Poynor
On Fri, Jun 24, 2011 at 10:14:03AM -0500, Moiz Sonasath wrote: ... + if (enabled) + twl-vbus_enable = 1; + else + twl-vbus_enable = 0; + Suggest twl-vbus_enable = enabled; /* * Start driving VBUS. Set OPA_MODE bit in CHARGERUSB_CTRL1

Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents

2011-06-25 Thread Koen Kooi
Op 24 jun 2011, om 18:23 heeft Sanjeev Premi het volgende geschreven: The current selection of the GPTIMER on was result of a hardware issue in early versions of the Beagleboards (Ax and B1 thru B4). [1] [2] Its been long since the hardware issue has been fixed. This patch uses GPTIMER 1

Re: [RFC/PATCH 9/9] OMAP2+: cpuidle only influences the MPU state

2011-06-25 Thread Santosh Shilimkar
On 6/24/2011 7:38 AM, jean.pi...@newoldbits.com wrote: From: Jean Pihetj-pi...@ti.com Since cpuidle is a CPU centric framework it decides the MPU next power state based on the MPU exit_latency and target_residency figures. The rest of the power domains get their next power state programmed

Re: [linux-pm] Runtime PM discussion notes

2011-06-25 Thread Rafael J. Wysocki
Hi, On Friday, June 24, 2011, Paul Walmsley wrote: (Arve cc'ed, also adding Magnus and Kevin back to cc) Thanks, my mailer is playing tricks on me. :-) Hi Rafael, On Thu, 23 Jun 2011, Rafael J. Wysocki wrote: On Thursday, June 23, 2011, Alan Stern wrote: On Thu, 23 Jun 2011, Paul

RE: [PATCHv2] omap2+: pm: cpufreq: Fix loops_per_jiffy calculation

2011-06-25 Thread Premi, Sanjeev
-Original Message- From: Hilman, Kevin Sent: Saturday, June 25, 2011 1:44 AM To: Russell King - ARM Linux Cc: Premi, Sanjeev; linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org Subject: Re: [PATCHv2] omap2+: pm: cpufreq: Fix loops_per_jiffy calculation Russell

RE: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents

2011-06-25 Thread Premi, Sanjeev
-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Koen Kooi Sent: Saturday, June 25, 2011 1:47 PM To: linux-omap@vger.kernel.org List Cc: linux-arm-kernel; Paul Walmsley Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi

RE: [PATCHv2] omap2+: pm: cpufreq: Fix loops_per_jiffy calculation

2011-06-25 Thread Premi, Sanjeev
-Original Message- From: Shilimkar, Santosh Sent: Saturday, June 25, 2011 12:18 AM To: Russell King - ARM Linux Cc: Premi, Sanjeev; linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org; Hilman, Kevin Subject: Re: [PATCHv2] omap2+: pm: cpufreq: Fix loops_per_jiffy

Re: [linux-pm] Runtime PM discussion notes

2011-06-25 Thread Alan Stern
On Fri, 24 Jun 2011, Paul Walmsley wrote: But suspend users don't know this either, since they can't predict when the next external wakeup can happen. But they do know (or should know) that they don't intend to use the system in the near future. It might be good to have a separate

Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents

2011-06-25 Thread Koen Kooi
Op 25 jun 2011, om 20:51 heeft Premi, Sanjeev het volgende geschreven: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Koen Kooi Sent: Saturday, June 25, 2011 1:47 PM To: linux-omap@vger.kernel.org List Cc:

RE: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents

2011-06-25 Thread Paul Walmsley
On Sun, 26 Jun 2011, Premi, Sanjeev wrote: [sp] I didn't include a reason - because the problem may not be reproducible on the public trees. During tests performed in internal development trees, the BogoMIPS calculations @ 1GHz wouldn't go beyond 830-850 range. While

Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents

2011-06-25 Thread Paul Walmsley
On Fri, 24 Jun 2011, Sanjeev Premi wrote: The current selection of the GPTIMER on was result of a hardware issue in early versions of the Beagleboards (Ax and B1 thru B4). [1] [2] Its been long since the hardware issue has been fixed. This patch uses GPTIMER 1 for all newer board revisions

Re: [RFC 0/8] Introducing a generic AMP/IPC framework

2011-06-25 Thread Ohad Ben-Cohen
Hi Stephen, On Fri, Jun 24, 2011 at 11:16 PM, Stephen Boyd sb...@codeaurora.org wrote: This sounds a lot like SMD (shared memory driver) on MSM. The main difference I see is that SMD uses the platform bus instead of the virtio bus and it has its own protocol for channel allocation. Yeah,

Re: [RFC 0/8] Introducing a generic AMP/IPC framework

2011-06-25 Thread Brian Swetland
On Sat, Jun 25, 2011 at 6:11 PM, Ohad Ben-Cohen o...@wizery.com wrote: Hi Stephen, On Fri, Jun 24, 2011 at 11:16 PM, Stephen Boyd sb...@codeaurora.org wrote: This sounds a lot like SMD (shared memory driver) on MSM. The main difference I see is that SMD uses the platform bus instead of the