Searched full:implement (Results 1 – 25 of 3275) sorted by relevance
12345678910>>...131
| /kernel/liteos_a/arch/arm/arm/include/ |
| D | los_atomic.h | 56 * This API is used to implement the atomic read and return the result value of the read.
79 * This API is used to implement the atomic setting operation.
103 * This API is used to implement the atomic addition and return the result value of the augend.
141 * This API is used to implement the atomic subtraction and return the result value of the minuend.
179 * This API is used to implement the atomic addSelf.
213 * This API is used to implement the atomic addSelf and return the result of addSelf.
249 * This API is used to implement the atomic auto-decrement.
283 * This API is used to implement the atomic auto-decrement and return the result of auto-decrement.
319 * This API is used to implement the atomic64 read and return the result value of the read.
351 * This API is used to implement the atomic64 setting operation.
[all …]
|
| /kernel/linux/linux-6.6/drivers/accel/ivpu/ |
| D | TODO | 2 - Implement support for BLOB IDs
5 - Implement HW based scheduling support
8 - Implement BO cache and MADVISE IOCTL
|
| /kernel/linux/linux-5.10/drivers/staging/gasket/ |
| D | TODO | 4 - Implement the gasket framework's functionality through UIO instead of
7 UIO provides the necessary bits to implement user-space drivers. Meanwhile
9 MSI interrupts. Add these features to the UIO subsystem, then re-implement
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | ftrace-design.rst | 30 - STACKTRACE_SUPPORT - implement save_stack_trace()
31 - TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
37 You will need to implement the mcount and the ftrace_stub functions.
120 mcount function to check ftrace graph function pointers, as well as implement
176 For information on how to implement prepare_ftrace_return(), simply look at the
244 of addresses of the system calls, implement an arch_syscall_addr to return
248 implement arch_syscall_match_sym_name with the appropriate logic to return
267 Once those are out of the way, you will need to implement:
321 implement your own stuff in assembly::
396 - implement:
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | ftrace-design.rst | 30 - STACKTRACE_SUPPORT - implement save_stack_trace()
31 - TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
37 You will need to implement the mcount and the ftrace_stub functions.
120 mcount function to check ftrace graph function pointers, as well as implement
176 For information on how to implement prepare_ftrace_return(), simply look at the
244 of addresses of the system calls, implement an arch_syscall_addr to return
248 implement arch_syscall_match_sym_name with the appropriate logic to return
267 Once those are out of the way, you will need to implement:
321 implement your own stuff in assembly::
396 - implement:
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_bridge.h | 372 * used to implement this hook.
389 * used to implement this hook.
501 * implement this hook.
524 * Bridges that implement this callback shall set the
541 * EDID shall leave @get_modes unimplemented and implement the
544 * This callback is optional. Bridges that implement it shall set the
565 * that support reading EDID shall implement this callback and leave
572 * This callback is optional. Bridges that implement it shall set the
596 * that support reading EDID shall implement this callback and leave
603 * This callback is optional. Bridges that implement it shall set the
[all …]
|
| /kernel/linux/linux-6.6/drivers/pci/controller/dwc/ |
| D | Kconfig | 39 implement the driver.
86 DesignWare core functions to implement the driver.
98 DesignWare core functions to implement the driver.
201 DesignWare core functions to implement the driver.
309 functions to implement the driver.
395 DesignWare core functions to implement the driver.
407 DesignWare core functions to implement the driver.
|
| /kernel/linux/linux-5.10/include/media/ |
| D | v4l2-dev.h | 81 * This allows those drivers to correctly implement the selection API,
182 * @read: operations needed to implement the read() syscall
183 * @write: operations needed to implement the write() syscall
184 * @poll: operations needed to implement the poll() syscall
185 * @unlocked_ioctl: operations needed to implement the ioctl() syscall
186 * @compat_ioctl32: operations needed to implement the ioctl() syscall for
190 * @mmap: operations needed to implement the mmap() syscall
191 * @open: operations needed to implement the open() syscall
192 * @release: operations needed to implement the release() syscall
440 * video_device_release_empty - helper function to implement the
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_bridge.h | 375 * used to implement this hook.
392 * used to implement this hook.
504 * implement this hook.
527 * Bridges that implement this callback shall set the
544 * EDID shall leave @get_modes unimplemented and implement the
547 * This callback is optional. Bridges that implement it shall set the
568 * that support reading EDID shall implement this callback and leave
575 * This callback is optional. Bridges that implement it shall set the
614 * implement it shall also implement the @hpd_disable callback and set
628 * implement it shall also implement the @hpd_enable callback and set
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 65 This format is adapted for stateless video decoders that implement an
119 This format is adapted for stateless video decoders that implement a
163 This format is adapted for stateless video decoders that implement an
185 This format is adapted for stateless video decoders that implement a
210 This format is adapted for stateless video decoders that implement a
266 This format is adapted for stateless video decoders that implement a AV1
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | pwm.rst | 120 Currently there are two ways to implement pwm drivers. Traditionally
122 to implement the pwm_*() functions itself. This means that it's impossible
139 Drivers are encouraged to implement ->apply() instead of the legacy
148 Drivers should not implement any power management. In other words,
149 consumers should implement it as described in the "Using PWMs" section.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | pwm.rst | 131 Currently there are two ways to implement pwm drivers. Traditionally
133 to implement the pwm_*() functions itself. This means that it's impossible
150 Drivers are encouraged to implement ->apply() instead of the legacy
159 Drivers should not implement any power management. In other words,
160 consumers should implement it as described in the "Using PWMs" section.
|
| /kernel/linux/linux-6.6/include/media/ |
| D | v4l2-dev.h | 81 * This allows those drivers to correctly implement the selection API,
182 * @read: operations needed to implement the read() syscall
183 * @write: operations needed to implement the write() syscall
184 * @poll: operations needed to implement the poll() syscall
185 * @unlocked_ioctl: operations needed to implement the ioctl() syscall
186 * @compat_ioctl32: operations needed to implement the ioctl() syscall for
190 * @mmap: operations needed to implement the mmap() syscall
191 * @open: operations needed to implement the open() syscall
192 * @release: operations needed to implement the release() syscall
439 * video_device_release_empty - helper function to implement the
|
| /kernel/linux/linux-5.10/lib/ |
| D | bug.c | 23 2. Implement BUG (and optionally BUG_ON, WARN, WARN_ON)
25 - Implement BUG() to generate a faulting instruction
30 3. Implement the trap
35 - You must implement the is_valid_bugaddr(bugaddr) callback which
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /kernel/linux/linux-5.10/drivers/rpmsg/ |
| D | rpmsg_internal.h | 27 * Indirection table for the operations that a rpmsg backend should implement.
51 * Indirection table for the operations that a rpmsg backend should implement.
52 * In addition to @destroy_ept, the backend must at least implement @send and
|
| /kernel/linux/linux-5.10/Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 22 * Implement low level formatting. Reimplemented
28 * implement formatting. IOCTls begin with 0x4600,
32 * do not implement IDEFLOPPY_CAPABILITIES_PAGE, and
|
| /kernel/linux/linux-5.10/drivers/staging/fwserial/ |
| D | TODO | 3 1. Implement retries for RCODE_BUSY, RCODE_NO_ACK and RCODE_SEND_ERROR
6 2. Implement _robust_ console on top of this. The existing prototype console
|
| /kernel/linux/linux-6.6/lib/ |
| D | bug.c | 22 2. Implement BUG (and optionally BUG_ON, WARN, WARN_ON)
24 - Implement BUG() to generate a faulting instruction
29 3. Implement the trap
34 - You must implement the is_valid_bugaddr(bugaddr) callback which
|
| /kernel/linux/linux-6.6/drivers/rpmsg/ |
| D | rpmsg_internal.h | 31 * Indirection table for the operations that a rpmsg backend should implement.
61 * Indirection table for the operations that a rpmsg backend should implement.
62 * In addition to @destroy_ept, the backend must at least implement @send and
|
| /kernel/linux/linux-6.6/Documentation/filesystems/spufs/ |
| D | spu_run.rst | 24 The spu_run system call is used on PowerPC machines that implement the
115 spu_run is meant to be used from libraries that implement a more
129 The code does not yet fully implement all features lined out here.
|
| D | spu_create.rst | 24 The spu_create system call is used on PowerPC machines that implement
102 spu_create is meant to be used from libraries that implement a more
122 The code does not yet fully implement all features lined out here.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/spufs/ |
| D | spu_run.rst | 24 The spu_run system call is used on PowerPC machines that implement the
115 spu_run is meant to be used from libraries that implement a more
129 The code does not yet fully implement all features lined out here.
|
| D | spu_create.rst | 24 The spu_create system call is used on PowerPC machines that implement
102 spu_create is meant to be used from libraries that implement a more
122 The code does not yet fully implement all features lined out here.
|
12345678910>>...131