Searched full:implement (Results 1 – 25 of 454) sorted by relevance
12345678910>>...19
| /Documentation/w1/masters/ |
| 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…
|
| /Documentation/driver-api/media/ |
| 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
|
| /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
|
| /Documentation/core-api/ |
| D | floating-point.rst | 27 Several architectures implement the generic kernel floating-point API from
28 ``linux/fpu.h``, as described below. Some other architectures implement their
77 caller expects to nest critical sections, it must implement its own
|
| D | dma-attributes.rst | 14 Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
24 Since it is optional for platforms to implement DMA_ATTR_WRITE_COMBINE,
42 Since it is optional for platforms to implement
|
| /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
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
255 Once those are out of the way, you will need to implement:
309 implement your own stuff in assembly::
384 - implement:
|
| /Documentation/filesystems/iomap/ |
| 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)``
|
| /Documentation/userspace-api/media/v4l/ |
| 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
|
| /Documentation/filesystems/spufs/ |
| 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.
|
| 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.
|
| /Documentation/driver-api/ |
| 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.
|
| 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
|
| 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
|
| /Documentation/hwmon/ |
| 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
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 33 does not aim to implement every feature in the specification. Every additional
62 Sometimes implementations of open standards fail to correctly implement parts
|
| /Documentation/gpu/ |
| D | drm-usage-stats.rst | 122 of drm-cycles-<keystr>. For drivers that implement this interface, the engine
126 A driver may implement either this key or drm-maxfreq-<keystr>, but not both.
137 A driver may implement either this key or drm-total-cycles-<keystr>, but not
180 implement &drm_driver.show_fdinfo if they wish to provide any stats which
|
| /Documentation/arch/openrisc/ |
| D | todo.rst | 10 - Implement the rest of the DMA API... dma_map_sg, etc.
|
| /Documentation/ABI/removed/ |
| D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /Documentation/networking/devlink/ |
| 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``
|
| /Documentation/networking/ |
| D | sriov.rst | 20 will be accepted. New drivers should not implement the uncommon callbacks;
|
| 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.
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 271 the hierarchy. A child irq_chip may implement a required action by
282 1) Implement irq_domain_ops.alloc and irq_domain_ops.free
283 2) Optionally implement irq_domain_ops.activate and
285 3) Optionally implement an irq_chip to manage the interrupt controller
287 4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
|
| /Documentation/driver-api/fpga/ |
| D | fpga-bridge.rst | 4 API to implement a new FPGA bridge
|
12345678910>>...19