Home
last modified time | relevance | path

Searched full:relate (Results 1 – 25 of 141) sorted by relevance

123456

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/opp/
Dopp-v2-base.yaml55 to relate the values to their clocks or the order in which the clocks
73 relate the values to their power supplies or the order in which the supplies
99 required. The OPP binding doesn't provide any provisions to relate the
114 required. The OPP binding doesn't provide any provisions to relate the
Dti,omap-opp-supply.yaml13 needed to describe such a hardware values and relate them to program
/kernel/linux/linux-6.6/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst5 Data flows that Relate some functions, and write packets
/kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst5 Data flows that Relate some functions, and write packets
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-envelope-detector39 to relate to the frequency of the input signal.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-envelope-detector39 to relate to the frequency of the input signal.
/kernel/linux/linux-5.10/arch/microblaze/mm/
Dconsistent.c35 * I have to use dcache values because I can't relate on ram size:
/kernel/linux/linux-5.10/fs/btrfs/
Dmisc.h63 * Simple bytenr based rb_tree relate structures
/kernel/linux/linux-5.10/Documentation/networking/
Dnetif-msg.rst15 practice and relate it to older driver source code.
/kernel/linux/linux-6.6/Documentation/networking/
Dnetif-msg.rst15 practice and relate it to older driver source code.
/kernel/linux/linux-6.6/drivers/net/ethernet/freescale/fman/
Dfman_sp.c84 * relate to it as 1). in fman_sp_build_buffer_struct()
/kernel/linux/linux-6.6/arch/s390/include/asm/trace/
Dzcrypt.h52 * is stored. Can be used as a unique id to relate together
/kernel/linux/linux-5.10/arch/s390/include/asm/trace/
Dzcrypt.h52 * is stored. Can be used as a unique id to relate together
/kernel/linux/linux-6.6/fs/btrfs/
Dmisc.h57 * Simple bytenr based rb_tree relate structures
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dpinmux-node.yaml75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dmsi.txt8 used with other busses, and hence a mechanism is required to relate devices on
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/
Dpinmux-node.yaml75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dmsi.txt8 used with other busses, and hence a mechanism is required to relate devices on
/kernel/linux/linux-6.6/arch/powerpc/include/asm/
Dlppaca.h12 * These definitions relate to hypervisors that only exist when using
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/vphn/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
/kernel/linux/linux-5.10/drivers/net/ethernet/freescale/fman/
Dfman_sp.c111 * relate to it as 1). in fman_sp_build_buffer_struct()
/kernel/linux/linux-5.10/scripts/dtc/libfdt/
Dlibfdt_internal.h98 * Note: Only checks that relate exclusively to the device tree itself
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/
Diommu.txt101 can be useful to describe how children on the bus relate to the IOMMU if they
/kernel/linux/linux-6.6/scripts/dtc/libfdt/
Dlibfdt_internal.h117 * Note: Only checks that relate exclusively to the device tree itself

123456