Lines Matching full:that
7 maintenance and enhancements there are some general policies that should
20 pointer to another object that was referenced when the callback was
28 context that allows a shared callback function to locate additional
32 allowed when the callback itself was provided through a structure that
35 specific to the code that also defines the callback function. In those
48 The assumption here, as with :c:struct:`gpio_callback`, is that the
50 :c:macro:`CONTAINER_OF` that can provide additional context to the
71 APIs and libraries may provide features that are expensive in RAM or
72 code size but are optional in the sense that some applications can be
82 * Any data that is accessed only when the feature is enabled should be
85 applications that don't need the capability.
86 * Function declarations that are available only when the option is
88 description that the function is available only when the specified
93 * Where code specific to the feature is isolated in a source file that
94 has no other content that file should be conditionally included in
98 * Where code specific to the feature is part of a source file that has
110 implement only a subset of the functions that is required for minimal operation.
111 A distinction is needed between APIs that are not supported and those that are
114 - APIs that are supported but not implemented shall return ``-ENOSYS``.
116 - Optional APIs that are not supported by the hardware should be implemented and
122 hardware that supports only edge-triggered interrupts)