Lines Matching full:api

3  * Kernel space API for accessing WiMAX devices
24 * The WiMAX stack provides an API for controlling and managing the
25 * system's WiMAX devices. This API affects the control plane; the
28 * Parts of the WiMAX stack API and notifications are exported to
33 * The API is standarized for all WiMAX devices and different drivers
41 * devices show in the market. This API is designed to be growable in
55 * Remember this is a very low level API that will to provide all of
57 * are the expected clients of it. They offer a higher level API that
74 * WiMAX devices have a state, and a kernel-only API allows the
78 * Most API calls will set the state automatically; in most cases
82 * All API operations are 'atomic', serialized through a mutex in the
87 * The API is exported to user space using generic netlink (other
99 * sent from user space to kernel space means executing the WiMAX API
130 * this WiMAX API.
149 * - Major versions: needs to be increased if an existing message/API
153 * - Minor version: needs to be increased if new messages/API calls are
162 * might be missing API calls; user space shall be ready to handle
332 * devices from different vendors and provides a common API as well as
362 * some API calls that shouldn't work until the device is ready
380 * The stack provides a mutex for each device that will disallow API
386 * the API have to check for wimax_dev_is_ready() to return 0 before
413 struct mutex mutex; /* Protects all members and API calls */
436 * WiMAX stack public API for device drivers
505 * WiMAX stack user space API
508 * This API is what gets exported to user space for general