| /linux/Documentation/devicetree/bindings/opp/ |
| H A D | opp-v2-base.yaml | 55 to relate the values to their clocks or the order in which the clocks
71 relate the values to their power supplies or the order in which the supplies
97 required. The OPP binding doesn't provide any provisions to relate the
112 required. The OPP binding doesn't provide any provisions to relate the
|
| H A D | ti,omap-opp-supply.yaml | 13 needed to describe such a hardware values and relate them to program
|
| /linux/Documentation/admin-guide/blockdev/drbd/ |
| H A D | figures.rst | 5 Data flows that Relate some functions, and write packets
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-adc-envelope-detector | 39 to relate to the frequency of the input signal.
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | defaults.sh | 4 # Set standard production config values that relate to TCP behavior.
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | gpio-v2-lineinfo-changed-read.rst | 42 These events relate to changes in a line's request state or configuration,
|
| H A D | gpio-lineinfo-changed-read.rst | 46 These events relate to changes in a line's request state or configuration,
|
| /linux/Documentation/networking/ |
| H A D | netif-msg.rst | 15 practice and relate it to older driver source code.
|
| /linux/Documentation/devicetree/bindings/soc/renesas/ |
| H A D | renesas-soc.yaml | 57 # Compatibles with the Renesas vendor prefix that do not relate to any SoC
|
| /linux/drivers/net/ethernet/freescale/fman/ |
| H A D | fman_sp.c | 84 * relate to it as 1). in fman_sp_build_buffer_struct()
|
| /linux/arch/s390/include/asm/trace/ |
| H A D | zcrypt.h | 52 * is stored. Can be used as a unique id to relate together
|
| /linux/fs/btrfs/ |
| H A D | misc.h | 59 * Simple bytenr based rb_tree relate structures
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinmux-node.yaml | 75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | msi.txt | 8 used with other busses, and hence a mechanism is required to relate devices on
|
| /linux/arch/powerpc/include/asm/ |
| H A D | lppaca.h | 12 * These definitions relate to hypervisors that only exist when using
|
| /linux/Documentation/crypto/ |
| H A D | api-intro.rst | 117 Also check for any RFCs which may relate to the use of specific algorithms,
|
| /linux/scripts/dtc/libfdt/ |
| H A D | libfdt_internal.h | 117 * Note: Only checks that relate exclusively to the device tree itself
|
| /linux/arch/mips/include/asm/ |
| H A D | sync.h | 78 * A GINV sync is a little different; it doesn't relate directly to loads or
|
| /linux/drivers/net/ethernet/i825xx/ |
| H A D | lasi_82596.c | 53 Most of my modifications relate to the braindead big-endian
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | iommu.txt | 119 can be useful to describe how children on the bus relate to the IOMMU if they
|
| /linux/kernel/trace/ |
| H A D | tracing_map.h | 20 * relate to the tracing_map API. The details of the algorithms
|
| /linux/drivers/comedi/drivers/ni_routing/ |
| H A D | README | 173 These are various notes that help to relate the naming conventions used in the
|
| /linux/Documentation/ |
| H A D | atomic_t.txt | 283 compact code. The functions relate like:
|
| /linux/Documentation/trace/ |
| H A D | timerlat-tracer.rst | 50 ID field serves to relate the *irq* execution to its respective *thread*
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | open.rst | 133 correctly relate a minor number to a device node number. I.e., you need
|