Home
last modified time | relevance | path

Searched full:implement (Results 1 – 25 of 1689) sorted by relevance

12345678910>>...68

/Linux-v5.4/drivers/staging/gasket/
DTODO4 - 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
/Linux-v5.4/Documentation/trace/
Dftrace-design.rst30 - 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:
/Linux-v5.4/include/media/
Dv4l2-dev.h81 * This allows those drivers to correctly implement the selection API,
175 * @read: operations needed to implement the read() syscall
176 * @write: operations needed to implement the write() syscall
177 * @poll: operations needed to implement the poll() syscall
178 * @unlocked_ioctl: operations needed to implement the ioctl() syscall
179 * @compat_ioctl32: operations needed to implement the ioctl() syscall for
183 * @mmap: operations needed to implement the mmap() syscall
184 * @open: operations needed to implement the open() syscall
185 * @release: operations needed to implement the release() syscall
433 * video_device_release_empty - helper function to implement the
/Linux-v5.4/Documentation/driver-api/
Dpwm.rst120 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.
Dptp.rst33 author of a clock driver need only implement the details of
50 implement the basic clock operations.
62 registration method. Clock drivers must implement all of the
/Linux-v5.4/arch/arm/kvm/
Dvgic-v3-coproc.c15 * TODO: Implement for AArch32 in vgic_v3_has_cpu_sysregs_attr()
24 * TODO: Implement for AArch32 in vgic_v3_cpu_sysregs_uaccess()
/Linux-v5.4/lib/
Dbug.c23 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
/Linux-v5.4/drivers/rpmsg/
Drpmsg_internal.h27 * 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
/Linux-v5.4/Documentation/ide/
DChangeLog.ide-floppy.1996-200222 * Implement low level formatting. Reimplemented
28 * implement formatting. IOCTls begin with 0x4600,
32 * do not implement IDEFLOPPY_CAPABILITIES_PAGE, and
DChangeLog.ide-cd.1994-200442 * 3.00 Aug 22, 1995 -- Implement CDROMMULTISESSION ioctl.
43 * Implement CDROMREADAUDIO ioctl (UNTESTED).
49 * Implement CDROMEJECT_SW ioctl (off by default).
57 * Implement CDROMVOLREAD ioctl.
58 * Implement CDROMREADMODE1/2 ioctls.
120 * -- Implement CDROMMECHANISMSTATUS and CDROMSLOTTABLE
/Linux-v5.4/include/uapi/linux/
Dfalloc.h19 * 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
/Linux-v5.4/drivers/staging/fwserial/
DTODO3 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
/Linux-v5.4/drivers/pci/controller/dwc/
DKconfig119 DesignWare core functions to implement the driver.
131 DesignWare core functions to implement the driver.
187 DesignWare core functions to implement the driver.
237 implement the driver.
/Linux-v5.4/include/drm/
Ddrm_modeset_helper_vtables.h67 * This is used by the legacy CRTC helpers to implement DPMS
216 * also used by the transitional plane helpers to implement a
221 * program the new display mode (e.g. because they implement runtime PM)
258 * is only used to implement kgdb support.
283 * Atomic drivers don't need to implement it if there's no need to
414 * @atomic_disable. Atomic drivers don't need to implement it if there's
441 * need to implement it if there's no need to disable anything at the
478 * This is used by the legacy encoder helpers to implement DPMS
606 * the new display mode (because they implement runtime PM) should not
632 * the new display mode (because they implement runtime PM) should not
[all …]
/Linux-v5.4/arch/arm/nwfpe/
DChangeLog82 * single_cpdo.c - implement URD, NRM
83 * double_cpdo.c - implement URD, NRM
84 * extended_cpdo.c - implement URD, NRM
/Linux-v5.4/Documentation/media/kapi/
Ddtv-core.rst10 implement the digital demux logic (either in software or in hardware);
29 proposals. Currently, the DVB subsystem doesn't implement those standards.
Ddtv-demux.rst29 The functions that implement the abstract interface demux should be defined
31 access. It is not necessary to implement every function in the struct
61 The functions that implement the callback API need not be re-entrant: when
/Linux-v5.4/Documentation/ABI/testing/
Ddebugfs-cec-error-inj16 It is up to the driver to decide what commands to implement. The only
34 Drivers that implement this functionality must document the commands as
/Linux-v5.4/Documentation/
DIRQ-domain.txt244 the hierarchy. A child irq_chip may implement a required action by
255 1) Implement irq_domain_ops.alloc and irq_domain_ops.free
256 2) Optionally implement irq_domain_ops.activate and
258 3) Optionally implement an irq_chip to manage the interrupt controller
260 4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
/Linux-v5.4/Documentation/networking/
Dgtp.txt22 The phone itself does not implement GTP but uses some other
52 payload, called GTP-U. It does not implement the 'control plane',
76 implementations that implement GTP-C and can use the netlink interface
104 doesn't implement GTP-C, we don't have to worry about this. It's the
106 implement that.
/Linux-v5.4/arch/mips/include/asm/
Dprefetch.h29 * VR5500 (including VR5701 and VR7701) only implement load prefetch.
31 * Finally MIPS32 and MIPS64 implement all of the following hints.
/Linux-v5.4/Documentation/filesystems/
Dseq_file.txt38 * A set of canned file_operations which implement most operations on
69 Modules implementing a virtual file with seq_file must implement an
72 is able to move to a specific position - like the file they implement,
127 The next function to implement is called, amazingly, next(); its job is to
243 creation of a set of file_operations which implement the operations on that
245 most of the work. The virtual file author still must implement the open()
Dspufs.txt10 The SPU file system is used on PowerPC machines that implement the Cell
294 The spu_run system call is used on PowerPC machines that implement the
376 spu_run is meant to be used from libraries that implement a more
388 The code does not yet fully implement all features lined out here.
418 The spu_create system call is used on PowerPC machines that implement
493 spu_create is meant to be used from libraries that implement a more
510 The code does not yet fully implement all features lined out here.
/Linux-v5.4/security/
DKconfig54 implement socket and networking access controls.
74 implement Infiniband access controls.
83 implement per-packet access controls based on labels
96 implement pathname based access controls.
/Linux-v5.4/Documentation/filesystems/nfs/
Dnfs41-server.txt23 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
28 the operations that are mandatory to implement (REQ), optional
29 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
155 persist across client reboots). Thus we need not implement this for

12345678910>>...68