Home
last modified time | relevance | path

Searched refs:control (Results 1 – 7 of 7) sorted by relevance

/lib/
Dmemcpy_kunit.c53 struct some_bytes control = { in memcpy_test() local
80 check(control, 0x20); in memcpy_test()
85 dest = control; in memcpy_test()
86 compare("direct assignment", dest, control); in memcpy_test()
93 dest = control; in memcpy_test()
98 dest = control; in memcpy_test()
111 struct some_bytes control = { in memmove_test() local
152 check(control, 0x99); in memmove_test()
157 dest = control; in memmove_test()
158 compare("direct assignment", dest, control); in memmove_test()
[all …]
DKconfig.kcsan71 framework for test thread control.
163 # The main purpose of the below options is to control reported data races, and
DKconfig.debug130 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
134 We refer the control file as: <debugfs>/dynamic_debug/control. This
149 nullarbor:~ # cat <debugfs>/dynamic_debug/control
159 <debugfs>/dynamic_debug/control
163 <debugfs>/dynamic_debug/control
167 <debugfs>/dynamic_debug/control
171 <debugfs>/dynamic_debug/control
175 <debugfs>/dynamic_debug/control
561 If you say Y here, you will have some control over the system even
1706 bool "Enable CPU hotplug state control"
[all …]
DKconfig.ubsan103 This option enables -fsanitize=unreachable which checks for control
DKconfig.kgdb113 0x0040 - allow flow control management (breakpoint, single step)
DKconfig38 in the data sheets of the peripherals they are in control of.
/lib/fonts/
DKconfig68 Small console font with PC-style control-character and high-half
76 Small console font with PC-style control characters and high-half