Searched full:encouraged (Results 1 – 25 of 64) sorted by relevance
123
2 future. Developers are encouraged to convert the drivers to use the
17 * Architectures are encouraged to implement read_current_timer
22 are encouraged to in the case where there is any manual configuration
139 Drivers are encouraged to implement ->apply() instead of the legacy145 state) is also encouraged for the same reason: letting the PWM user know
13 It is encouraged to use dt-binding for clock index definitions. SoC specific
45 Driver developers are encouraged to implement only selection API. The
131 this document. Driver developers are encouraged to keep padded rectangle
29 strongly encouraged to add their name to the description of
85 Most structs are typedefd, it's not encouraged in the kernel.
74 * on the sync_buf dma-buf can be taken. It is encouraged to re-use the same
79 # x86_64 users should be encouraged to install 32-bit libraries
26 combinations. However, implementations are encouraged to further
27 * project are encouraged to review the Maemo Diablo RX-34 and RX-44
15 memory for the buffer should be avoided, users are encouraged to use a scatter
45 Other bus layers are encouraged to do what has been done for the PCI layer.
104 * It is strongly encouraged to use CHECKSUM_COMPLETE for Rx to avoid the
85 You are strongly encouraged to use usbcore's facility,
83 application developers are encouraged to use UVCIOC_CTRL_QUERY instead.
14 implement this and users are encouraged to plug, if possible, into the
34 * Calibration at boot is strongly encouraged.
15 * encouraged once assigned by ANSI/INCITS T10).
93 input, and all clients are encouraged to use it.
79 * is strongly encouraged to return early and let the operation happen
14 encouraged to switch to the generic event (``evdev``) interface.
53 encouraged them to allow separation of the data and integrity metadata
