Lines Matching refs:be
8 be followed when developing a new capability or interface.
14 configuration structure. The following policies should be followed when
17 * The first parameter should be a pointer to the object most closely
19 would be ``const struct device *dev``. For library functions it may be a
23 * The next parameter(s) should be additional information specific to the
27 * The final parameter should be a ``void *user_data`` pointer carrying
31 An exception to providing ``user_data`` as the last parameter may be
33 will be embedded in another structure. An example of such a case is
64 occurred, as well as user context which may or may not be the
72 code size but are optional in the sense that some applications can be
77 enabling the features is to be controllable through a Kconfig option.
79 In the case where a feature is determined to be optional the following
80 practices should be followed.
82 * Any data that is accessed only when the feature is enabled should be
87 enabled should be provided unconditionally. Add a note in the
91 of the function shall be excluded from compilation, so references to
94 has no other content that file should be conditionally included in
99 other content the feature-specific code should be conditionally
102 The Kconfig flag used to enable the feature should be added to the
116 - Optional APIs that are not supported by the hardware should be implemented and
117 the return code in this case shall be ``-ENOTSUP``.
120 requested in the call cannot be satisfied by the implementation the call shall