Searched full:implement (Results 1 – 25 of 3058) sorted by relevance
12345678910>>...123
| /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-4.19/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/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-4.19/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
252 of addresses of the system calls, implement an arch_syscall_addr to return
256 implement arch_syscall_match_sym_name with the appropriate logic to return
275 Once those are out of the way, you will need to implement:
329 implement your own stuff in assembly::
404 - 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-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-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-4.19/include/media/ |
| D | v4l2-dev.h | 166 * @read: operations needed to implement the read() syscall
167 * @write: operations needed to implement the write() syscall
168 * @poll: operations needed to implement the poll() syscall
169 * @unlocked_ioctl: operations needed to implement the ioctl() syscall
170 * @compat_ioctl32: operations needed to implement the ioctl() syscall for
174 * @mmap: operations needed to implement the mmap() syscall
175 * @open: operations needed to implement the open() syscall
176 * @release: operations needed to implement the release() syscall
424 * video_device_release_empty - helper function to implement the
|
| /kernel/linux/linux-4.19/Documentation/ptp/ |
| D | ptp.txt | 29 author of a clock driver need only implement the details of
45 implement the basic clock operations.
56 registration method. Clock drivers must implement all of the
|
| /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-4.19/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-4.19/drivers/rpmsg/ |
| D | rpmsg_internal.h | 27 * Indirection table for the operations that a rpmsg backend should implement.
50 * Indirection table for the operations that a rpmsg backend should implement.
51 * In addition to @destroy_ept, the backend must at least implement @send and
|
| /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-4.19/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/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-4.19/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-4.19/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-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-4.19/arch/arm/kvm/ |
| D | vgic-v3-coproc.c | 23 * TODO: Implement for AArch32 in vgic_v3_has_cpu_sysregs_attr()
32 * TODO: Implement for AArch32 in vgic_v3_cpu_sysregs_uaccess()
|
| /kernel/linux/linux-4.19/drivers/staging/rtlwifi/halmac/ |
| D | halmac_pwr_seq_cmd.h | 27 * Note : dirver shall implement this function by read & msk
34 * Note: driver shall implement this cmd by read & msk after write
40 * Note: driver shall implement this cmd by
|
| /kernel/linux/linux-5.10/Documentation/filesystems/spufs/ |
| 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.
|
| 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.
|
| /kernel/linux/linux-4.19/Documentation/media/kapi/ |
| D | dtv-core.rst | 8 implement the digital demux logic (either in software or in hardware);
27 proposals. Currently, the DVB subsystem doesn't implement those standards.
|
12345678910>>...123