Introduction to topic for overview page or search
Hardware Resource Manager (HWRM) is a client-server solution, which utilizes ECom plug-ins to achieve device independency. ECom plug-ins convert the client requests into the hardware control commands.
HWRM performs the following functions:
Knowledge of the client-server architecture, asynchronous processing, and active objects feature of the Symbian system model architecture.
HWRM is made up of the following components:
HWRM provides client APIs that can control various hardware elements. It also provides callback pointers, so that the client applications can register to receive notification on the hardware status changes. Refer to the tutorials for information on how to use client APIs. Client APIs are useful for both application developers and the handset manufacturers.
HWRM server uses plug-in handlers to forward the client API requests to appropriate plug-ins. The client application communicates with HWRM server through the client APIs (Light API, Vibra API, and Power API). HWRM server defines the observer classes, which provide the callback pointers.
The server calls CHWRMPluginService::ProcessCommandL() function to forward the client requests to plug-ins. An ongoing ProcessCommandL() is cancelled by HWRM server using CHWRMPluginService::CancelCommandL() . The plug-ins process the server's request and pass the response by calling CHWRMPluginCallback::ProcessResponseL() function. The MHWRMPluginCallback::EventL() method is used to communicate various events that takes place in the plug-ins.
HWRM uses the central repository to store the various values and settings such as the light intensity, duration and delays.
The HWRM provides the following client APIs and plug-in APIs:
HWRM is used for the following:
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License v1.0.