| /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/drivers/pci/controller/dwc/ |
| H A D | Kconfig | 51 core functions to implement the driver.
62 implement the driver.
109 DesignWare core functions to implement the driver.
121 DesignWare core functions to implement the driver.
224 DesignWare core functions to implement the driver.
378 functions to implement the driver.
498 DesignWare core functions to implement the driver.
510 DesignWare core functions to implement the driver.
|
| /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/Documentation/userspace-api/media/v4l/ |
| H A 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/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/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/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/Documentation/filesystems/spufs/ |
| H A 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.
|
| H A 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.
|
| /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/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/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/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/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/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:
|
| /linux/rust/kernel/block/mq/ |
| H A D | operations.rs | 3 //! This module provides an interface for blk-mq drivers to implement.
19 /// Implement this trait to interface blk-mq as block devices.
21 /// To implement a block device driver, implement this trait as described in the
|
| /linux/rust/kernel/ |
| H A D | device.rs | 65 /// This section provides a guideline to implement bus specific devices, such as [`pci::Device`] or
82 /// In order to be able to implement the [`DeviceContext`] dereference hierarchy, bus device
91 /// In order to convert from a any [`Device<Ctx>`] to [`ARef<Device>`], bus devices can implement
98 /// Bus devices should also implement the following [`AsRef`] implementation, such that users can
128 /// Just like any device, class devices are reference counted and should hence implement
131 /// Class devices should also implement the following [`AsRef`] implementation, such that users can
444 /// Bus devices can automatically implement the dereference hierarchy by using
456 /// [`Device<Normal>`]. It is the only [`DeviceContext`] for which it is valid to implement
467 /// implementations can implement methods for [`Device<Core>`], such that they can only be called
539 /// Implement [`core::ops::Deref`] traits for allowed [`DeviceContext`] conversions of a (bus
[all …]
|