Difference between revisions of "CELF Project Proposal/Add behavior-oriented power management"

From eLinux.org
Jump to: navigation, search
(Comments)
 
(One intermediate revision by the same user not shown)
Line 39: Line 39:
  
 
== Comments ==
 
== Comments ==
Patrick Bellasi writes:
+
Alexander Voytov wrote:
<pre>
 
That's a really interesting project. Moreover, I think it should be
 
supported by an OpenSource HW reference platform which is cheap but
 
sufficiently powerful to replace a semi-professional DAQ.
 
...
 
  
I think that the signal acquisition layer should also support the "USB
+
QNX claims real time power supply management for its car application
test and measurement" (TMC) class driver, which is already supported
+
embedded solution.
by Linux: drivers/usb/class/usbtmc.c
+
 
</pre>
+
On the PC like laptop/desktop there is the ACPI standard which version
----
+
3 I'm not aware is implemented by anyone on any platform. The problem
Patrick also wrote:
+
with the PS(power supply) control is - it is an analog device in the
 +
most common case, but there is a growing market of the digital control
 +
PS. Means, you can control such devices like any other real time
 +
interfaces.
  
Probably the best one solution out there ''[for an OpenSource HW reference platform]''
+
I'm not aware about the PS behaviour control implementation, except
I know is the USB-DUXfast,
+
the RF board design. On majority the RFID boards there is a signal
which is already supported by the COMEDI framework... but is missing
+
strength pin to power up the board in case the RFID signal is
the MTD usb class support.
+
detected. This is a proprietry design to wake up all board drivers and
http://www.linux-usb-daq.co.uk/tech2_duxfast/
+
interfaces for converting an oncoming analog RF signal into, for
The board is relatively cheap compared to the offered features: up to
+
instance, the USB or a serial packet. On some such devices the Linux
3MHz continous rate and up to 30MHz in burst mode (256samples),
+
kernel is implemented, on majority I'm aware about - the home growth
unfortunately the firmware is not open.
+
SW state machine.
 
----
 
----
Alan Carvalho de Assis wrote:
 
 
I found this one: http://web.media.mit.edu/~msung/sak2.php
 
---
 
 
  
 
[[Category:Project proposals]]
 
[[Category:Project proposals]]

Latest revision as of 16:06, 16 December 2009

Summary 
Add behavior-oriented power management
Proposer 
Evgeny Ivashko

Description

Every user has behavioral patterns. Behavioral pattern is the sequence of actions, running applications and so on. Some of these patterns are common and the others are individual. Knowing the patterns the program (that should be developed as the result of the project) can optimize the OS's behaviour to reduce energy consumption, response time and etc.

For example (common pattern), if user starts a video in the full-screen mode the program can automatically suspend some subsystems (like USB or CD/DVD-rom). Also the program can "hibernate" unused applications. Another example (individual pattern): if the user usually runs OpenOffice.org after the game or two of Mahjong, the program can automatically prepare the OS to quick start of the OOo.

Base

The work should be based on such technologies as Data Mining and Behavior Analysis

Project's objectives

The main result of the project should be the program (daemon) that can in (semi)automatic way change the power and application profiles, that should get

  • reducing the device's energy consumption;
  • reducing the OS's response time;
  • reducing amount of used OS's resources.

Related work

This project should actively use results of such projects as:

The approach is well-proven in many different domains (http://en.wikipedia.org/wiki/Data_Mining#Notable_uses).

Scope 
This should take about 6 months.

Comments

Alexander Voytov wrote:

QNX claims real time power supply management for its car application embedded solution.

On the PC like laptop/desktop there is the ACPI standard which version 3 I'm not aware is implemented by anyone on any platform. The problem with the PS(power supply) control is - it is an analog device in the most common case, but there is a growing market of the digital control PS. Means, you can control such devices like any other real time interfaces.

I'm not aware about the PS behaviour control implementation, except the RF board design. On majority the RFID boards there is a signal strength pin to power up the board in case the RFID signal is detected. This is a proprietry design to wake up all board drivers and interfaces for converting an oncoming analog RF signal into, for instance, the USB or a serial packet. On some such devices the Linux kernel is implemented, on majority I'm aware about - the home growth SW state machine.