- ACTION: ARM to discuss giving out internal Eclipse based tool (similar to powertop) (no ETA as of now)
The tool is an Eclipse-based generic event viewer. Internally, we're displaying 'power events,' such as those that Srinivas' recent ftrace patches around cpufreq/cpuidle. There is no ETA (or commitment) for providing this tool externally at the moment, but it's under discussion.
Is this tool included or based on ARM's DS-5 kit?
I'll let ARM talk about this.
The tool currently has no relation to DS-5, other than it's also Eclipse based..
HTH - let me know if you need more.
-Bobby
-----Original Message----- From: linaro-dev-bounces@lists.linaro.org [mailto:linaro-dev-bounces@lists.linaro.org] On Behalf Of Amit Kucheria Sent: 20 August 2010 08:11 To: Christian Robottom Reis Cc: Srinivas Kalaga; linaro-dev@lists.linaro.org Subject: Re: [PM] 18/08/10 - Minutes for the Power Management WG weekly call
On 10 Aug 19, Christian Robottom Reis wrote:
On Wed, Aug 18, 2010 at 12:35:31PM +0300, Amit Kucheria wrote:
- ACTION: Amit A to document details on power supply
class (battery
info) to PowerTOP internal wiki page
Is there an internal wiki for PowerTOP, or is this an
internal page on
the Linaro wiki?
This shouldn't have contained the word 'internal'. Everything is public at https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/Powertop
- ACTION: ARM to discuss giving out internal Eclipse
based tool (similar to powertop) (no ETA as of now)
Is this tool included or based on ARM's DS-5 kit?
I'll let ARM talk about this.
- Power management differentiation
- Discussion with Robin from ARM about common frameworks
- Robin not convinced about all the consolidation
effort, since some of it is seen as competetive differentiator
* Amit K believes Mechanism should be commonamongst vendors so that can use common tools and design patterns.
* Policies can be different to allow differentiation * e.g. have a cpufreq and cpuidle driver allowsall vendors to use powertop tool. If current frameworks don't suit the needs, we can work with upstream to extend them.
This is the correct approach; mechanism should be common
and provided
by the upstream kernel. Policy should be implemented by vendors and deployed in the way which makes most sense for their projects.
Cheers, Amit
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.