Searched full:simplest (Results 1 – 25 of 53) sorted by relevance
123
| /Documentation/devicetree/bindings/misc/ |
| D | ti,j721e-esm.yaml | 19 simplest configuration the signals are just routed to reset the SoC.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm6345-l1-intc.txt | 37 /proc/irq/ interface. In the simplest possible configuration, only one
|
| D | brcm,bcm7038-l1-intc.yaml | 32 /proc/irq/ interface. In the simplest possible configuration, only one
|
| /Documentation/userspace-api/media/v4l/ |
| D | rw.rst | 22 However this is also the simplest I/O method, requiring little or no
|
| /Documentation/mm/ |
| D | memory-model.rst | 8 simplest case is when the physical memory starts at address 0 and
34 The simplest memory model is FLATMEM. This model is suitable for
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra30-mc.yaml | 26 Domains and Protocol Arbiters. In the simplest version of the system, the
|
| /Documentation/filesystems/ |
| D | automount-support.rst | 63 It may prove simplest to simply call this at regular intervals, using
|
| /Documentation/maintainer/ |
| D | messy-diffstat.rst | 36 result in the simplest case is a history that looks like::
|
| /Documentation/watchdog/ |
| D | watchdog-api.rst | 37 The simplest API
43 timeout or margin. The simplest way to ping the watchdog is to write
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 44 modify. For lilo the simplest setup looks like the following
|
| /Documentation/userspace-api/netlink/ |
| D | intro-specs.rst | 73 The simplest way to generate a new file based on a spec is to add
|
| D | specs.rst | 34 There are four schema levels for Netlink specs, from the simplest used
|
| /Documentation/networking/ |
| D | fib_trie.rst | 123 The lookup is in its simplest form just like fib_find_node(). We descend the
|
| D | msg_zerocopy.rst | 118 The below snippet demonstrates the API. In the simplest case, each
|
| D | iso15765-2.rst | 29 In its simplest form, ISO-TP is based on two kinds of addressing modes for the
|
| /Documentation/devicetree/bindings/regulator/ |
| D | ti-abb-regulator.txt | 68 Example #1: Simplest configuration (no efuse data, hard coded ABB table):
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 12 The recommended simplest form returns an opaque ktime_t, with variants
|
| D | cachetlb.rst | 23 First, the TLB flushing interfaces, since they are the simplest. The
|
| /Documentation/power/powercap/ |
| D | dtpm.rst | 107 description is the simplest one and it is supposed to give to user
|
| /Documentation/infiniband/ |
| D | opa_vnic.rst | 17 header generation and processing. In the simplest configuration all HFI
|
| /Documentation/crypto/ |
| D | devel-algos.rst | 52 This section describes the simplest of all transformation
|
| /Documentation/admin-guide/ |
| D | parport.rst | 270 because this is the simplest code path.
|
| /Documentation/leds/ |
| D | leds-class.rst | 5 In its simplest form, the LED class just allows control of LEDs from
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 79 The simplest way to build hierarchies of threads/processes which share a
|
| /Documentation/input/ |
| D | input-programming.rst | 5 The simplest example
|
123