USB Device Control Plug-in APIChanges in USB Device Control Plug-in documentation
ChangesThis is initial version. This API is effective from S60 3.2. onwards. cusbdevicecontrolplugin.h
Related APIs
PurposeThis API is intended for routing vendor-specific messages from the host to target handler. The API allows to extend functionality by using the ECOM framework. Messages, sent to handlers, are control messages, and therefore sent through end-point zero (EP0). Host can send vendor-specific control messages to handlers, to call the needed functionality on the device side. API descriptionThe purpose of USB Device Control Plug-in API is to give standard extendable way for adding new functionality to devices, which communicates via USB, using vendor-specific commands. Handlers are added as plug-ins, using ECOM framework. Each added plug-in solves some specific problem, and host, when needs some functionality from device side, just sends vendor-specific message to a device. Through the API that message is received and processed by handler. Through the API handlers get access to USB Client API, RUsb API, USB Watcher API, USB Watcher Info API. There is no need for handlers to make own connection to the mentioned API handles. Some more information about the API can be found in USB Device Control Design Document. Use casesThere are two important use cases. The first use case is when USB Device Control initializes the handler with USB handles. Through those handles the handler can get access to USB Client API, RUsb API, USB Watcher API, USB Watcher Info API. The second use case is when handler receives a message, processes it, and returns the result. Internally, both of these use cases are handler specific. Only the interface is common. API class structureUSB Device Control API is an abstract class
Related APIs
Using USB Device Control Plug-in APIThis API is used so that handlers must implement interface's abstract methods. Functionality of the methods is handler specific. Error handlingHandlers must return the error
Related APIs
Memory overheadSince all API methods are implemented by clients, there is no memory overhead problem with this API.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: EPL
|