Home
last modified time | relevance | path

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

123

/linux-5.10/Documentation/admin-guide/blockdev/drbd/
Dfigures.rst5 Data flows that Relate some functions, and write packets
/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-envelope-detector39 to relate to the frequency of the input signal.
/linux-5.10/arch/microblaze/mm/
Dconsistent.c35 * I have to use dcache values because I can't relate on ram size:
/linux-5.10/fs/btrfs/
Dmisc.h63 * Simple bytenr based rb_tree relate structures
/linux-5.10/Documentation/networking/
Dnetif-msg.rst15 practice and relate it to older driver source code.
/linux-5.10/arch/s390/include/asm/trace/
Dzcrypt.h52 * is stored. Can be used as a unique id to relate together
/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dmsi.txt8 used with other busses, and hence a mechanism is required to relate devices on
/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dpinmux-node.yaml75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
/linux-5.10/tools/testing/selftests/powerpc/vphn/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
/linux-5.10/arch/powerpc/include/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
/linux-5.10/drivers/net/ethernet/freescale/fman/
Dfman_sp.c111 * relate to it as 1). in fman_sp_build_buffer_struct()
/linux-5.10/scripts/dtc/libfdt/
Dlibfdt_internal.h98 * Note: Only checks that relate exclusively to the device tree itself
/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
/linux-5.10/Documentation/crypto/
Dapi-intro.rst117 Also check for any RFCs which may relate to the use of specific algorithms,
/linux-5.10/Documentation/devicetree/bindings/devfreq/
Drk3399_dmc.txt24 Following properties relate to DDR timing:
/linux-5.10/drivers/net/ethernet/i825xx/
Dlasi_82596.c52 Most of my modifications relate to the braindead big-endian
/linux-5.10/arch/mips/include/asm/
Dsync.h78 * A GINV sync is a little different; it doesn't relate directly to loads or
/linux-5.10/Documentation/devicetree/bindings/opp/
Dopp.txt104 relate the values to their power supplies or the order in which the supplies
130 provide any provisions to relate the values to their power supplies or the
/linux-5.10/drivers/staging/comedi/drivers/ni_routing/
DREADME173 These are various notes that help to relate the naming conventions used in the
/linux-5.10/kernel/trace/
Dtracing_map.h20 * relate to the tracing_map API. The details of the algorithms
/linux-5.10/include/uapi/linux/
Ddm-ioctl.h321 * If set, any table information returned will relate to the inactive
/linux-5.10/Documentation/userspace-api/media/v4l/
Dopen.rst133 correctly relate a minor number to a device node number. I.e., you need
/linux-5.10/Documentation/core-api/
Dunaligned-memory-access.rst79 At first, the concepts above may seem a little hard to relate to actual
Dkernel-api.rst334 don't relate to timekeeping or real time clocks (RTCs), each of which
/linux-5.10/Documentation/sound/soc/
Ddapm.rst140 Stream Widgets relate to the stream power domain and only consist of ADCs

123