Home
last modified time | relevance | path

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

12345678910>>...56

/linux/Documentation/trace/
H A 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
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
251 Once those are out of the way, you will need to implement:
305 implement your own stuff in assembly::
380 - implement:
/linux/include/uapi/linux/
H A Dfalloc.h20 * 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
89 * Different filesystems may implement different limitations on the
/linux/Documentation/w1/masters/
H A Dw1-uart.rst15 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/Documentation/filesystems/iomap/
H A Dporting.rst53 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/Documentation/driver-api/
H A Dpwm.rst140 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.
H A Drfkill.rst68 Drivers for radio transmitters normally implement an rfkill driver.
70 Platform drivers might implement input devices if the rfkill button is just
72 implement an rfkill driver instead. This also applies if the platform provides
H A Dptp.rst34 author of a clock driver need only implement the details of
51 implement the basic clock operations.
63 registration method. Clock drivers must implement all of the
/linux/Documentation/edac/
H A Dmemory_repair.rst136 implement CXL.mem protocol. A sparing maintenance operation requests the
139 implement sparing maintenance operations.
144 devices that implement CXL.mem protocol. A PPR maintenance operation
147 may implement PPR Maintenance operations. Soft PPR (sPPR) is a temporary
/linux/rust/kernel/
H A Dfmt.rs33 /// A copy of [`core::fmt::Display`] that allows us to implement it for foreign types.
35 /// Types should implement this trait rather than [`core::fmt::Display`]. Together with the
37 /// core) which do not implement [`core::fmt::Display`] directly.
/linux/arch/arm/nwfpe/
H A DChangeLog82 * single_cpdo.c - implement URD, NRM
83 * double_cpdo.c - implement URD, NRM
84 * extended_cpdo.c - implement URD, NRM
/linux/drivers/cache/
H A DKconfig8 These drivers implement support for noncoherent DMA master devices
40 These drivers implement cache management for flows where it is necessary
/linux/lib/
H A Dbug.c22 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/Documentation/driver-api/media/
H A 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
H A 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.
/linux/rust/kernel/debugfs/
H A Dcallback_adapters.rs25 /// To implement this trait, it must be safe to cast a `&Self` to a `&Inner`.
31 /// Adapter to implement `Reader` via a callback with the same representation as `T`.
67 /// Adapter to implement `Writer` via a callback with the same representation as `T`.
/linux/Documentation/networking/
H A Dgtp.rst28 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/security/
H A DKconfig105 implement socket and networking access controls.
114 implement Infiniband access controls.
123 implement per-packet access controls based on labels
136 implement pathname based access controls.
/linux/arch/mips/include/asm/
H A Dprefetch.h29 * VR5500 (including VR5701 and VR7701) only implement load prefetch.
31 * Finally MIPS32 and MIPS64 implement all of the following hints.
/linux/arch/mips/include/asm/octeon/
H A Dcrypto.h25 * Macros needed to implement MD5/SHA1/SHA256:
99 * Macros needed to implement SHA512:
173 * Macros needed to implement SHA512:
/linux/tools/docs/
H A Dget_feat.py135 """Implement rest argparse subparser"""
152 """Implement list argparse subparser"""
167 """Implement validate argparse subparser"""
/linux/rust/syn/
H A Dspanned.rs18 //! If the field type does *not* implement `Sync` as required, we want the
54 //! our macro, the user's code will fail to compile if `ty` does not implement
90 /// This trait is automatically implemented for all types that implement
/linux/drivers/staging/rtl8723bs/include/
H A DHalPwrSeqCmd.h19 /* note: dirver shall implement this function by read & msk */
25 /* note: driver shall implement this cmd by read & msk after write */
31 /* note: driver shall implement this cmd by */
/linux/Documentation/leds/
H A Dleds-class.rst154 support this feature, a LED driver can optionally implement the
157 will check and implement software fallback if necessary.
177 To support this feature, a LED needs to implement various additional
188 LED driver must implement the following API to support hw control:
/linux/arch/riscv/errata/sifive/
H A Derrata.c27 * Implement ID: 0x20181004 <= impid <= 0x20191105 in errata_cip_453_check_func()
40 * Implement ID: mimpid[23:0] <= 0x200630 and mimpid != 0x01200626 in errata_cip_1200_check_func()
/linux/include/media/
H A Ddvb_frontend.h410 * @diseqc_reset_overload: callback function to implement the
412 * @diseqc_send_master_cmd: callback function to implement the
414 * @diseqc_recv_slave_reply: callback function to implement the
416 * @diseqc_send_burst: callback function to implement the
418 * @set_tone: callback function to implement the
420 * @set_voltage: callback function to implement the
422 * @enable_high_lnb_voltage: callback function to implement the
424 * @dishnetwork_send_legacy_command: callback function to implement the
493 * These callbacks are for devices that implement their own

12345678910>>...56