Lines Matching full:request

138  * of long startup time and low power consumption. Multiple modules can request
145 /** @brief Request high frequency clock from Bluetooth Controller.
149  * any confirmation when clock is ready because it assumes that request is
192 	int (*request)(const struct device *dev,  member
203  * @brief Request a reservation to use a given clock with specified attributes.
206  * an operation to request the clock be made available. If initiation of the
207  * operation succeeds, the result of the request operation is provided through
211  * request fails. Always check the operation completion result.
221  *            expectations and how to notify the client when the request
226  *                      with the clock machine at the time the request was
242 	return api->request(dev, spec, cli);  in nrf_clock_control_request()
246  * @brief Synchronously request a reservation to use a given clock with specified attributes.
248  * Function can only be called from thread context as it blocks until request is completed.
253  * @param timeout Request timeout.
255  * @retval 0 if request is fulfilled.
256  * @retval -EWOULDBLOCK if request is called from the interrupt context.
268  *             in the reservation request (so that the clock control module
272  *                      with the clock machine at the time the request was
288  * @brief Safely cancel a reservation request.
290  * It may be that a client has issued a reservation request but needs to
291  * shut down before the request has completed. This function attempts to
292  * cancel the request and issues a release if cancellation fails because
293  * the request was completed. This synchronously ensures that ownership
294  * data reverts to the client so is available for a future request.
298  *             in the reservation request.
320 /** @brief Request the HFXO from Zero Latency Interrupt context.
324  * user must put the request early enough to make sure the HFXO