| /linux/Documentation/trace/ |
| H A 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 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 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 89 * Different filesystems may implement different limitations on the
|
| /linux/include/drm/ |
| H A D | drm_bridge.h | 388 * used to implement this hook. 405 * used to implement this hook. 517 * implement this hook. 540 * Bridges that implement this callback shall set the 558 * EDID shall leave @get_modes unimplemented and implement the 561 * This callback is optional. Bridges that implement it shall set the 582 * that support reading EDID shall implement this callback and leave 589 * This callback is optional. Bridges that implement it shall set the 630 * implement it shall also implement the @hpd_disable callback and set 644 * implement it shall also implement the @hpd_enable callback and set [all …]
|
| /linux/Documentation/w1/masters/ |
| H A 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/Documentation/filesystems/iomap/ |
| H A 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/Documentation/driver-api/ |
| H A 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.
|
| H A D | rfkill.rst | 68 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 D | ptp.rst | 34 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 D | memory_repair.rst | 136 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 D | fmt.rs | 33 /// 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 D | ChangeLog | 82 * 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 D | Kconfig | 8 These drivers implement support for noncoherent DMA master devices 40 These drivers implement cache management for flows where it is necessary
|
| /linux/Documentation/driver-api/media/ |
| H A 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
|
| H A 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.
|
| /linux/rust/kernel/debugfs/ |
| H A D | callback_adapters.rs | 25 /// 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 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/security/ |
| H A D | Kconfig | 107 implement socket and networking access controls. 116 implement Infiniband access controls. 125 implement per-packet access controls based on labels 138 implement pathname based access controls.
|
| /linux/lib/ |
| H A 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/arch/mips/include/asm/octeon/ |
| H A D | crypto.h | 25 * Macros needed to implement MD5/SHA1/SHA256: 99 * Macros needed to implement SHA512: 173 * Macros needed to implement SHA512:
|
| /linux/tools/docs/ |
| H A D | get_feat.py | 135 """Implement rest argparse subparser""" 152 """Implement list argparse subparser""" 167 """Implement validate argparse subparser"""
|
| /linux/rust/syn/ |
| H A D | spanned.rs | 18 //! 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/arch/mips/include/asm/ |
| H A 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/Documentation/filesystems/ |
| H A D | seq_file.rst | 43 * A set of canned file_operations which implement most operations on 76 Modules implementing a virtual file with seq_file must implement an 79 is able to move to a specific position - like the file they implement, 136 The next function to implement is called, amazingly, next(); its job is to 278 creation of a set of file_operations which implement the operations on that 280 most of the work. The virtual file author still must implement the open()
|
| /linux/drivers/staging/rtl8723bs/include/ |
| H A D | HalPwrSeqCmd.h | 19 /* 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 D | leds-class.rst | 154 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:
|