Searched refs:implement (Results 1 – 25 of 404) sorted by relevance
12345678910>>...17
| /Linux-v5.4/drivers/staging/gasket/ |
| D | TODO | 7 UIO provides the necessary bits to implement user-space drivers. Meanwhile
9 MSI interrupts. Add these features to the UIO subsystem, then re-implement
|
| /Linux-v5.4/lib/mpi/ |
| D | mpicoder.c | 152 #error please implement for this limb size. in mpi_read_buffer()
181 #error please implement for this limb size. in mpi_read_buffer()
256 #error please implement for this limb size. in mpi_write_to_sgl()
298 #error please implement for this limb size. in mpi_write_to_sgl()
|
| /Linux-v5.4/Documentation/media/kapi/ |
| 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-v5.4/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
|
| D | sysfs-bus-hsi | 11 the protocols available in the system. Bus drivers implement
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | ptp.rst | 33 author of a clock driver need only implement the details of
50 implement the basic clock operations.
62 registration method. Clock drivers must implement all of the
|
| D | pwm.rst | 120 Currently there are two ways to implement pwm drivers. Traditionally
122 to implement the pwm_*() functions itself. This means that it's impossible
139 Drivers are encouraged to implement ->apply() instead of the legacy
148 Drivers should not implement any power management. In other words,
149 consumers should implement it as described in the "Using PWMs" section.
|
| 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-v5.4/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
252 of addresses of the system calls, implement an arch_syscall_addr to return
256 implement arch_syscall_match_sym_name with the appropriate logic to return
275 Once those are out of the way, you will need to implement:
329 implement your own stuff in assembly::
404 - implement:
|
| /Linux-v5.4/include/asm-generic/ |
| D | tlbflush.h | 10 #error need to implement an architecture specific asm/tlbflush.h
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 23 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
28 the operations that are mandatory to implement (REQ), optional
29 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
155 persist across client reboots). Thus we need not implement this for
|
| /Linux-v5.4/drivers/staging/rts5208/ |
| D | TODO | 4 - We will use the stack in drivers/mmc to implement
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | emc1403.rst | 61 The chips implement three limits for each sensor: low (tempX_min), high
62 (tempX_max) and critical (tempX_crit.) The chips also implement an
|
| /Linux-v5.4/arch/arc/kernel/ |
| D | entry-arcv2.S | 100 ; TODO: implement this
106 ; TODO: implement this
112 ; TODO: implement this
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/timer/ |
| D | renesas,8bit-timer.txt | 6 This implement only supported cascade mode.
|
| /Linux-v5.4/Documentation/driver-api/fpga/ |
| D | fpga-bridge.rst | 4 API to implement a new FPGA bridge
|
| /Linux-v5.4/Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Linux-v5.4/drivers/scsi/arm/ |
| D | Kconfig | 22 implement this properly, so the safe answer is N.
32 don't implement it properly, so the safe answer is N.
|
| /Linux-v5.4/Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 28 * implement formatting. IOCTls begin with 0x4600,
32 * do not implement IDEFLOPPY_CAPABILITIES_PAGE, and
|
| /Linux-v5.4/Documentation/networking/ |
| D | gtp.txt | 22 The phone itself does not implement GTP but uses some other
52 payload, called GTP-U. It does not implement the 'control plane',
76 implementations that implement GTP-C and can use the netlink interface
104 doesn't implement GTP-C, we don't have to worry about this. It's the
106 implement that.
|
| /Linux-v5.4/tools/testing/selftests/powerpc/include/ |
| D | utils.h | 110 #error implement UCONTEXT_NIA
|
| /Linux-v5.4/drivers/infiniband/sw/siw/ |
| D | Kconfig | 16 space verbs API, libibverbs. To implement RDMA over
|
| /Linux-v5.4/net/nfc/ |
| D | Kconfig | 26 This is needed by NFC chipsets whose firmware only implement
|
12345678910>>...17
