Searched full:gaps (Results 1 – 15 of 15) sorted by relevance
19 property allows you to have "gaps" between the channel
56 Report IDs, the gaps and offset in Report IDs can not be supported.
20 * Note that some devices may have instance gaps, hence the need to keep them in the array.
16 are allowed to contain gaps between the partitions, but this is discouraged.
725 bool "Don't fill gaps in generated hex/s19 files [DEPRECATED]."735 bool "Fill gaps in hex files"738 Fill gaps in hex based files.775 bool "Fill gaps in s19 files"778 Fill gaps in s19 based files.
76 # elfconvert_flag_gapfill : Flag for specifying the value to fill in gaps between sections
36 * regions. This ensures that in the worst-case where there are gaps between
188 * it up to the capacity of the entry specified in @ref psa_ps_create(), but cannot create gaps.
192 initializers must be in order (gaps are allowed).
642 /* No gaps allowed */ in btp_cap_broadcast_source_setup()
1125 /* No gaps allowed */ in btp_bap_unicast_group_create()
24 /* there are no gaps on the stack */27 /* there are no gaps on the stack */
1554 /* Compact the fragments, so that gaps will be filled */ in compress_ipv6_header()
1380 * :github:`14121` - gaps between app shared memory partitions can waste a lot of space
3210 * :github:`52506` - GPIO multiple gaps cause incorrect pinout check
