Documentation/Maemo 5 Developer Guide/Architecture/System Software - Revision history

amigadave: reformat tables slightly

amigadave — Wed, 02 Mar 2011 10:32:54 GMT

reformat tables slightly

← Older revision		Revision as of 10:32, 2 March 2011
Line 111:		Line 111:

	{\| class="wikitable"		{\| class="wikitable"
		+	\|+ System control public interfaces
		+	\|-
	! Interface !! Purpose !! Interface type		! Interface !! Purpose !! Interface type
	\|-		\|-
Line 160:		Line 162:

	{\| class="wikitable"		{\| class="wikitable"
		+	\|+ Energy management public interfaces
		+	\|-
	! Interface !! Purpose !! Type		! Interface !! Purpose !! Type
	\|-		\|-
Line 191:		Line 195:

	===Components and descriptions===		===Components and descriptions===
-

	====Clock Framework====		====Clock Framework====
Line 199:		Line 202:
	;Responsibilities		;Responsibilities
	: <ul><li>Provides common means for turning HW clocks on and off.</li><li>Provides HW clock sanity checks and use counts.</li><li>Allows power management to probe HW clocks status.</li><li>Handles also clock and power domains, and wakeup and sleep dependencies.</li></ul>		: <ul><li>Provides common means for turning HW clocks on and off.</li><li>Provides HW clock sanity checks and use counts.</li><li>Allows power management to probe HW clocks status.</li><li>Handles also clock and power domains, and wakeup and sleep dependencies.</li></ul>
-

	====CPU Idle====		====CPU Idle====
Line 216:		Line 218:

	{\| class="wikitable"		{\| class="wikitable"
		+	\|+ Power management public interfaces
		+	\|-
	! Name !! Description		! Name !! Description
	\|-		\|-

amigadave: Reverted edits by 190.81.163.82 (Talk); changed back to last version by Amigadave

amigadave — Mon, 24 Jan 2011 09:13:30 GMT

Reverted edits by 190.81.163.82 (Talk); changed back to last version by Amigadave

← Older revision		Revision as of 09:13, 24 January 2011
Line 226:		Line 226:
	[[Category:Documentation]]		[[Category:Documentation]]
	[[Category:Fremantle]]		[[Category:Fremantle]]
-	~~ppppppp~~

190.81.163.82: /* Public Interfaces */

190.81.163.82 — Fri, 21 Jan 2011 18:24:47 GMT

Public Interfaces

← Older revision		Revision as of 18:24, 21 January 2011
Line 226:		Line 226:
	[[Category:Documentation]]		[[Category:Documentation]]
	[[Category:Fremantle]]		[[Category:Fremantle]]
		+	ppppppp

amigadave: /* Public Interfaces */ add alarm api link

amigadave — Thu, 02 Sep 2010 13:46:01 GMT

Public Interfaces: add alarm api link

← Older revision		Revision as of 13:46, 2 September 2010
Line 134:		Line 134:
	\| D-Bus		\| D-Bus
	\|-		\|-
-	\| Alarm API \|\| Requesting, changing and deleting alarms.	+	\| [[Documentation/Maemo 5 Developer Guide/Using Generic Platform Components/Alarm Framework\|Alarm API]] \|\| Requesting, changing and deleting alarms.
	\| D-Bus		\| D-Bus
	\|-		\|-
Line 140:		Line 140:
	\| Socket		\| Socket
	\|}		\|}
-

	==Energy Management==		==Energy Management==

amigadave: /* Device State Management Entity (DSME) */ reformat image

amigadave — Wed, 18 Aug 2010 13:10:05 GMT

Device State Management Entity (DSME): reformat image

← Older revision		Revision as of 13:10, 18 August 2010
Line 47:		Line 47:
	DSME is responsible of device state management , process lifeguard support, watch dogs and thermal management. DSME architecture is based on modular plugin architecture. DSME core provides message handling capabilities to modules. Each module is dynamically loaded library. DSME runs in a single process. The D-Bus interface provides services to request reboot, shutdown or powerup (from acting dead mode), indication of shutdown, thermal events and data save.		DSME is responsible of device state management , process lifeguard support, watch dogs and thermal management. DSME architecture is based on modular plugin architecture. DSME core provides message handling capabilities to modules. Each module is dynamically loaded library. DSME runs in a single process. The D-Bus interface provides services to request reboot, shutdown or powerup (from acting dead mode), indication of shutdown, thermal events and data save.

-	[[Image:DSME.png]]	+	[[Image:DSME.png\|frame\|center\|alt=Diagram of DSME components\|DSME components]]

amigadave: wikify slightly, reformat tables

amigadave — Mon, 19 Jul 2010 10:57:39 GMT

wikify slightly, reformat tables

Show changes

semi: /* Device State Management Entity (DSME) */

semi — Fri, 19 Feb 2010 12:34:16 GMT

Device State Management Entity (DSME)

← Older revision		Revision as of 12:34, 19 February 2010
Line 49:		Line 49:
	===Device State Management Entity (DSME)===		===Device State Management Entity (DSME)===
	DSME is responsible of device state management , process lifeguard support, watch dogs and thermal management.		DSME is responsible of device state management , process lifeguard support, watch dogs and thermal management.
-	DSME architecture is based on modular plugin architecture. DSME core provides message handling capabilities to modules. Each module is dynamically loaded library. DSME runs in single process ~~and is single threaded~~. The D-Bus interface provides services to request reboot, shutdown or powerup (from acting dead mode), indication of shutdown, thermal events and data save.	+	DSME architecture is based on modular plugin architecture. DSME core provides message handling capabilities to modules. Each module is dynamically loaded library. DSME runs in a single process. The D-Bus interface provides services to request reboot, shutdown or powerup (from acting dead mode), indication of shutdown, thermal events and data save.

	[[Image:DSME.png]] <br>		[[Image:DSME.png]] <br>
Line 63:		Line 63:
	\|'''Description'''\|\|Provides means for configuration and management interface. <br>Provides lifeguard CLI API for system service startup. <br>*Manages device state including display, watchdog and startup.		\|'''Description'''\|\|Provides means for configuration and management interface. <br>Provides lifeguard CLI API for system service startup. <br>*Manages device state including display, watchdog and startup.
	\|}		\|}
-

	===Mode Control Entity (MCE)===		===Mode Control Entity (MCE)===

amigadave: categorise

amigadave — Fri, 12 Feb 2010 12:03:00 GMT

categorise

← Older revision		Revision as of 12:03, 12 February 2010
Line 253:		Line 253:
	\|Contraints API\|\|Interface for drivers for setting constraints on bandwidth and latency to control the target sleep states.		\|Contraints API\|\|Interface for drivers for setting constraints on bandwidth and latency to control the target sleep states.
	\|}		\|}
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]

78.27.67.238: /* HAL battery addon */

78.27.67.238 — Sat, 06 Feb 2010 15:50:36 GMT

HAL battery addon

← Older revision		Revision as of 15:50, 6 February 2010
Line 176:		Line 176:
	\|'''Name'''\|\|'''HAL Battery addon'''		\|'''Name'''\|\|'''HAL Battery addon'''
	\|-		\|-
-	\|'''Purpose'''\|\|Provides ~~batery~~ information via HAL.	+	\|'''Purpose'''\|\|Provides battery information via HAL.
	\|-		\|-
	\|'''Description'''\|\|Provides battery status and type information via HAL.		\|'''Description'''\|\|Provides battery status and type information via HAL.
	\|}		\|}
-

	===Public Interfaces===		===Public Interfaces===

liox_lang_valid: /* System Software Architecture */

liox_lang_valid — Wed, 23 Sep 2009 11:57:20 GMT

System Software Architecture

← Older revision		Revision as of 11:57, 23 September 2009
Line 7:		Line 7:
	System control subsystem is responsible for device state management (DSME), mode control (MCE) and various UI components including system UI, control panel applets and status bar icons. In addition, the system control subsystem includes HAL component for hardware abstraction, maemo-launcher for application startup execution, alarmd for alarm event handling, clockd for time management, iphbd for synchronization and profiled for profile handling. The SC subsystem provides D-Bus interface towards other applications. All the system control components are located in user space.		System control subsystem is responsible for device state management (DSME), mode control (MCE) and various UI components including system UI, control panel applets and status bar icons. In addition, the system control subsystem includes HAL component for hardware abstraction, maemo-launcher for application startup execution, alarmd for alarm event handling, clockd for time management, iphbd for synchronization and profiled for profile handling. The SC subsystem provides D-Bus interface towards other applications. All the system control components are located in user space.

-	Energy management subsystem is responsible of battery charging. More specifically, the EM subsystem handles battery voltage monitoring and recognition, charging (via USB) and charger recognition. In addition, battery plugin for HAL is provided ~~in order~~ to provide standard D-Bus interface towards other applications. For example, the battery applet uses the HAL battery plugin to indicate the battery status in the UI. The EM subsystem components are located both in kernel and user space.	+	Energy management subsystem is responsible of battery charging. More specifically, the EM subsystem handles battery voltage monitoring and recognition, charging (via USB) and charger recognition. In addition, battery plugin for HAL is provided to provide standard D-Bus interface towards other applications. For example, the battery applet uses the HAL battery plugin to indicate the battery status in the UI. The EM subsystem components are located both in kernel and user space.

-	Power management subsystem is located entirely in kernel space. PM subsystem is responsible for putting the OMAP and peripherals into lowest possible power states as often as possible, without compromising performance. ~~In order to~~ achieve this, all the drivers in the system need to co-operate with the PM subsystem. The PM subsystem is build from standard linux kernel components including clock, CPUIdle and CPUFreq frameworks.	+	Power management subsystem is located entirely in kernel space. PM subsystem is responsible for putting the OMAP and peripherals into lowest possible power states as often as possible, without compromising performance. To achieve this, all the drivers in the system need to co-operate with the PM subsystem. The PM subsystem is build from standard linux kernel components including clock, CPUIdle and CPUFreq frameworks.

	==System Control==		==System Control==
Line 54:		Line 54:


-	''~~Note:~~ In Fremantle release onwards, DSME is not part of the initfs anymore. Instead, it is located in the rootfs and started after init.''	+	''N.B. In Fremantle release onwards, DSME is not part of the initfs anymore. Instead, it is located in the rootfs and started after init.''

	{\|cellspacing="0" border="1" width="70%"		{\|cellspacing="0" border="1" width="70%"
Line 252:		Line 252:
	\|CLK API\|\|Clock framework public API.		\|CLK API\|\|Clock framework public API.
	\|-		\|-
-	\|Contraints API\|\|Interface for drivers for setting constraints on bandwidth and latency ~~inorder~~ to control the target sleep states.	+	\|Contraints API\|\|Interface for drivers for setting constraints on bandwidth and latency to control the target sleep states.
	\|}		\|}