Client Driver Registration
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
A Secure Digital (SD) client driver does not link directly to exported functions. Instead, the function calls are made accessible to the client driver through the client registration process.
During this process, the client driver passes information about itself to the bus driver and receives the information necessary to make calls to the SD peripheral functions. Macros are provided that enable a client driver to access these APIs after the registration process. Only these macros should be used by the client driver, and no reliance should be made on the underlying calling mechanism. For more information, see Secure Digital Card Driver Macros.
To complete the registration process, the client driver must send its local device context and a friendly name for the SD device to the bus driver using SDRegisterClient.
See Also
Reference
Secure Digital Card Driver Macros