| /linux/lib/crypto/mpi/ |
| H A D | mpicoder.c | 153 #error please implement for this limb size. in mpi_read_buffer()
182 #error please implement for this limb size. in mpi_read_buffer()
257 #error please implement for this limb size. in mpi_write_to_sgl()
299 #error please implement for this limb size. in mpi_write_to_sgl()
|
| /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/Documentation/driver-api/media/ |
| 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.
|
| 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
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfs41-server.rst | 25 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
30 the operations that are mandatory to implement (REQ), optional
31 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
238 persist across client reboots). Thus we need not implement this for
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| H A D | sysfs-bus-hsi | 11 the protocols available in the system. Bus drivers implement
|
| /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/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/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/include/asm-generic/ |
| H A D | tlbflush.h | 10 #error need to implement an architecture specific asm/tlbflush.h
|
| /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 | 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
|
| 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
|
| /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/arch/arc/kernel/ |
| H A D | entry-arcv2.S | 101 ; TODO: implement this
107 ; TODO: implement this
113 ; TODO: implement this
|
| /linux/drivers/pci/controller/dwc/ |
| H A D | Kconfig | 50 core functions to implement the driver.
61 implement the driver.
108 DesignWare core functions to implement the driver.
120 DesignWare core functions to implement the driver.
223 DesignWare core functions to implement the driver.
376 functions to implement the driver.
472 DesignWare core functions to implement the driver.
484 DesignWare core functions to implement the driver.
|
| /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/hwmon/ |
| H A D | emc1403.rst | 72 The chips implement three limits for each sensor: low (tempX_min), high
73 (tempX_max) and critical (tempX_crit.) The chips also implement an
|
| /linux/drivers/tee/tstee/ |
| H A D | Kconfig | 11 doesn't implement a user space interface directly.
|
| /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/Documentation/networking/devlink/ |
| H A D | devlink-region.rst | 29 requested snapshots must implement the ``.snapshot`` callback for the region
38 region should implement the ``.read`` callback in the ``devlink_region_ops``
|
| /linux/Documentation/ABI/removed/ |
| H A D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /linux/Documentation/litmus-tests/locking/ |
| H A D | DCL-broken.litmus | 7 * correctly implement double-checked locking.
|