Searched full:implement (Results 1 – 25 of 2070) sorted by relevance
12345678910>>...83
| /linux-6.12.1/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
232 of addresses of the system calls, implement an arch_syscall_addr to return
236 implement arch_syscall_match_sym_name with the appropriate logic to return
255 Once those are out of the way, you will need to implement:
309 implement your own stuff in assembly::
384 - implement:
|
| /linux-6.12.1/include/drm/ |
| D | drm_bridge.h | 374 * used to implement this hook.
391 * used to implement this hook.
503 * implement this hook.
526 * Bridges that implement this callback shall set the
543 * EDID shall leave @get_modes unimplemented and implement the
546 * This callback is optional. Bridges that implement it shall set the
567 * that support reading EDID shall implement this callback and leave
574 * 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 …]
|
| D | drm_modeset_helper_vtables.h | 72 * This is used by the legacy CRTC helpers to implement DPMS
224 * program the new display mode (e.g. because they implement runtime PM)
261 * is only used to implement kgdb support.
286 * Atomic drivers don't need to implement it if there's no need to
416 * @atomic_disable. Atomic drivers don't need to implement it if there's
439 * need to implement it if there's no need to disable anything at the
518 * This is used by the legacy encoder helpers to implement DPMS
646 * the new display mode (because they implement runtime PM) should not
672 * the new display mode (because they implement runtime PM) should not
695 * semantics. New drivers shouldn't use this and instead just implement
[all …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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.
353 functions to implement the driver.
439 DesignWare core functions to implement the driver.
451 DesignWare core functions to implement the driver.
|
| /linux-6.12.1/Documentation/w1/masters/ |
| D | w1-uart.rst | 15 the document `"Using a UART to Implement a 1-Wire Bus Master"`_.
17 .. _"Using a UART to Implement a 1-Wire Bus Master": https://www.analog.com/en/technical-articles/u…
|
| /linux-6.12.1/Documentation/filesystems/iomap/ |
| D | porting.rst | 53 The recommended approach is first to implement ``->iomap_begin`` (and
59 implement support for it and then to determine that the extent map
71 can be tested without needing to implement any iomap APIs.
91 The next thing to do is implement ``get_blocks(create == true)``
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | pwm.rst | 140 Currently there are two ways to implement pwm drivers. Traditionally
142 to implement the pwm_*() functions itself. This means that it's impossible
160 Drivers are encouraged to implement ->apply() instead of the legacy
169 Drivers should not implement any power management. In other words,
170 consumers should implement it as described in the "Using PWMs" section.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/core-api/ |
| D | floating-point.rst | 27 Several architectures implement the generic kernel floating-point API from
28 ``linux/fpu.h``, as described below. Some other architectures implement their
77 caller expects to nest critical sections, it must implement its own
|
| /linux-6.12.1/include/uapi/linux/ |
| D | falloc.h | 20 * Different filesystems may implement different limitations on the
52 * Different filesystems may implement different limitations on the granularity
69 * Different filesystems may implement different limitations on the
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/arch/arm/nwfpe/ |
| D | ChangeLog | 82 * single_cpdo.c - implement URD, NRM
83 * double_cpdo.c - implement URD, NRM
84 * extended_cpdo.c - implement URD, NRM
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 16 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-6.12.1/Documentation/driver-api/media/ |
| D | dtv-core.rst | 10 implement the digital demux logic (either in software or in hardware);
29 proposals. Currently, the DVB subsystem doesn't implement those standards.
|
| D | dtv-demux.rst | 29 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-6.12.1/Documentation/gpu/ |
| D | drm-usage-stats.rst | 122 of drm-cycles-<keystr>. For drivers that implement this interface, the engine
126 A driver may implement either this key or drm-maxfreq-<keystr>, but not both.
137 A driver may implement either this key or drm-total-cycles-<keystr>, but not
180 implement &drm_driver.show_fdinfo if they wish to provide any stats which
|
| /linux-6.12.1/arch/mips/include/asm/ |
| D | prefetch.h | 29 * VR5500 (including VR5701 and VR7701) only implement load prefetch.
31 * Finally MIPS32 and MIPS64 implement all of the following hints.
|
| /linux-6.12.1/Documentation/networking/ |
| D | gtp.rst | 28 The phone itself does not implement GTP but uses some other
59 payload, called GTP-U. It does not implement the 'control plane',
84 implementations that implement GTP-C and can use the netlink interface
114 doesn't implement GTP-C, we don't have to worry about this. It's the
116 implement that.
|
| /linux-6.12.1/Documentation/core-api/irq/ |
| D | irq-domain.rst | 271 the hierarchy. A child irq_chip may implement a required action by
282 1) Implement irq_domain_ops.alloc and irq_domain_ops.free
283 2) Optionally implement irq_domain_ops.activate and
285 3) Optionally implement an irq_chip to manage the interrupt controller
287 4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
|
| /linux-6.12.1/security/ |
| D | Kconfig | 81 implement socket and networking access controls.
90 implement Infiniband access controls.
99 implement per-packet access controls based on labels
112 implement pathname based access controls.
|
| /linux-6.12.1/arch/mips/cavium-octeon/crypto/ |
| D | octeon-crypto.h | 25 * Macros needed to implement MD5/SHA1/SHA256:
99 * Macros needed to implement SHA512:
173 * Macros needed to implement SHA512:
|
12345678910>>...83