Searched refs:wrappers (Results 1 – 13 of 13) sorted by relevance
55 static struct legacy_wrapper wrappers[] = { variable61 for (unsigned int i = 0; i < ARRAY_SIZE(wrappers); i++) { in get_legacy_ops()62 if (wrappers[i].dev == dev) { in get_legacy_ops()63 return wrappers[i].legacy_ops; in get_legacy_ops()207 for (unsigned int i = 0; i < ARRAY_SIZE(wrappers); i++) { in usb_hid_register_device()208 if (wrappers[i].dev == dev) { in usb_hid_register_device()209 wrappers[i].legacy_ops = ops; in usb_hid_register_device()210 if (hid_device_register(dev, desc, size, wrappers[i].ops)) { in usb_hid_register_device()
16 transactions. The subsystem wrappers are responsible for extracting
117 If selected wrappers are generated for various C library functions118 using the cbprintf formatter underneath. The wrappers use the C
26 whitespace or other special characters through all the wrappers can be
689 The flash and debug commands use Python wrappers around various690 :ref:`flash-debug-host-tools`. These wrappers are all defined in a Python
28 These functions are basically wrappers around the flash API with additional
30 common cores, and CPU wrappers to create SoCs easily. The tool contains
217 simulator without ``west flash`` and ``west debug`` wrappers it's necessary to219 ``west debug`` it's done automatically by wrappers.
161 * Removed printf/printk wrappers.
187 The older mem_pool APIs are, by default, wrappers around this new
885 # For scipy or wrappers or benchmarks
318 However, it is recommended to use macro wrappers (:c:macro:`LOG_INIT` and
415 # The methods are wrappers around the CMake target_* functions. See657 # does not have wrappers over the other cmake target functions.731 # flashing and debugging supported boards. These are wrappers around a
