Searched full:relate (Results 1 – 25 of 71) sorted by relevance
123
55 to relate the values to their clocks or the order in which the clocks73 relate the values to their power supplies or the order in which the supplies99 required. The OPP binding doesn't provide any provisions to relate the114 required. The OPP binding doesn't provide any provisions to relate the
13 needed to describe such a hardware values and relate them to program
5 Data flows that Relate some functions, and write packets
39 to relate to the frequency of the input signal.
15 practice and relate it to older driver source code.
57 * Simple bytenr based rb_tree relate structures
52 * is stored. Can be used as a unique id to relate together
84 * relate to it as 1). in fman_sp_build_buffer_struct()
75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
8 used with other busses, and hence a mechanism is required to relate devices on
12 * These definitions relate to hypervisors that only exist when using
117 Also check for any RFCs which may relate to the use of specific algorithms,
117 * Note: Only checks that relate exclusively to the device tree itself
53 Most of my modifications relate to the braindead big-endian
78 * A GINV sync is a little different; it doesn't relate directly to loads or
119 can be useful to describe how children on the bus relate to the IOMMU if they
166 * Many of the values relate to the PAR/PCS clock conversion registers. For
20 * relate to the tracing_map API. The details of the algorithms
283 compact code. The functions relate like:
173 These are various notes that help to relate the naming conventions used in the
133 correctly relate a minor number to a device node number. I.e., you need
79 At first, the concepts above may seem a little hard to relate to actual
335 * If set, any table information returned will relate to the inactive
140 Stream Widgets relate to the stream power domain and only consist of ADCs
50 ID field serves to relate the *irq* execution to its respective *thread*