Re: CoreSight framework and drivers

2012-12-20 Thread Jean Pihet
Hi Pratik, On Thu, Dec 20, 2012 at 8:51 PM, Pratik Patel wrote: > On Thu, Dec 20, 2012 at 11:46:13AM -0600, Jon Hunter wrote: >> >> On 12/19/2012 03:24 PM, Pratik Patel wrote: >> >> [snip] >> >> > Currently we use the CoreSight virtual bus to conveniently list >> > sysfs configuration attributes

Re: [RFC 1/5] ARM: CORESIGHT: Add generic lock/unlock helpers

2012-12-13 Thread Jean Pihet
Hi Jon, Will, On Thu, Dec 13, 2012 at 8:18 PM, Jon Hunter wrote: > > On 12/13/2012 08:58 AM, Will Deacon wrote: >> Hi Jon, >> >> On Wed, Dec 12, 2012 at 09:43:04PM +, Jon Hunter wrote: >>> The Cross Trigger Interface (CTI) helpers in cti.h include definitions >>> for the Coresight Lock Access

Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information

2012-06-13 Thread Jean Pihet
Hi Amit, Peter, On Wed, Jun 13, 2012 at 2:47 PM, Peter Zijlstra wrote: > On Wed, 2012-06-13 at 18:14 +0530, Amit Kucheria wrote: >> Various discussions around power-aware scheduling have amplified the >> need for the scheduler to have some knowledge of DVFS. This would then >> require the schedul

Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information

2012-06-13 Thread Jean Pihet
Vincent, On Tue, Jun 12, 2012 at 2:02 PM, Vincent Guittot wrote: > Use cpu compatibility field and clock-frequency field of DT to > estimate the capacity of each core of the system > > Signed-off-by: Vincent Guittot > --- >  arch/arm/kernel/topology.c |  122 > ++

Re: [RFC 1/4] ARM: topology: Add arch_scale_freq_power function

2012-06-13 Thread Jean Pihet
Hi Vincent, On Tue, Jun 12, 2012 at 2:02 PM, Vincent Guittot wrote: > Add infrastructure to be able to modify the cpu_power of each core > > Signed-off-by: Vincent Guittot > --- >  arch/arm/include/asm/topology.h |    2 ++ >  arch/arm/kernel/topology.c      |   36 +++

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Jean Pihet
Hi, On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi wrote: > Hi, > > On Thu, Jul 21, 2011 at 04:52:13PM -0700, Kevin Hilman wrote: >> Board code should not touch omap_device internals.  To get the MPU/IVA >> devices, >> use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device(). >> >> Sign

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Jean Pihet
Hi, On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi wrote: > Hi, > > On Thu, Jul 21, 2011 at 04:52:13PM -0700, Kevin Hilman wrote: >> Board code should not touch omap_device internals.  To get the MPU/IVA >> devices, >> use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device(). >> >> Sign