Lines Matching full:client

27 Writing Client Drivers
35    client-api
41 Client drivers can be set up in two main ways, depending on how the
49 Non-SSAM Client Drivers
58 client device and controller (this can also be done separate via
60 that the returned controller is valid for use in the client driver for as
94 means, it should be provided as |ssam_device| via the SSAM client device
104 necessary, by use of |ssam_client_link| as is done for non-SSAM client
107 A client device must always be removed by the party which added the
111 unbinds. Client devices registered with the controller as parent are
113 relied upon, especially as this does not extend to client devices with a
117 SSAM Client Drivers
120 SSAM client device drivers are, in essence, no different than other device
129 The UID for SSAM client devices consists of a ``domain``, a ``category``,
134 (:c:type:`SSAM_DOMAIN_VIRTUAL <ssam_device_domain>`), such as client-device
140 (default) name of a client device is generated based on its UID.
147 The controller associated with a SSAM client device can be found in its
149 guaranteed to be valid for at least as long as the client driver is bound,
150 but should also be valid for as long as the client device exists. Note,
151 however, that access outside of the bound client driver must ensure that the
154 is guaranteed when the controller is accessed from inside the bound client
286 Additionally, variants for direct use with client devices, i.e.
304 in the client device. The full list of such macros for client devices is:
319 handle hot-removal of client devices.