Searched full:ranges (Results 1 – 25 of 691) sorted by relevance
12345678910>>...28
| /Documentation/devicetree/bindings/bus/ |
| D | arm,integrator-ap-lm.yaml | 31 ranges: true
32 dma-ranges: true
40 in ranges and dma-ranges.
55 ranges = <0xc0000000 0xc0000000 0x40000000>;
56 dma-ranges;
60 ranges = <0x00000000 0xc0000000 0x10000000>;
62 dma-ranges = <0x00000000 0x80000000 0x10000000>;
|
| D | mvebu-mbus.txt | 24 - ranges: Must be set up to provide a proper translation for each child.
104 Following the above encoding, for each ranges entry for a MBus valid window
115 ranges = <0xf0010000 0 0 0xd0000000 0x100000
128 ranges = <0 0xf0010000 0 0x100000>;
139 In the shown example, the translation entry in the 'ranges' property is what
157 ranges = < MBUS_ID(0xf0, 0x01) 0 0 0xd0000000 0x100000
172 ranges = <0 MBUS_ID(0xf0, 0x01) 0 0x100000>;
198 The mbus-node ranges property defines a set of mbus windows that are expected
200 with one another or with the system memory ranges.
207 with the ones listed in the ranges, e.g. for mapping PCIe devices.
[all …]
|
| D | microsoft,vmbus.yaml | 20 ranges: true
30 - ranges
45 ranges;
51 ranges = <0x0f 0xf0000000 0x0f 0xf0000000 0x10000000>;
|
| D | palmbus.yaml | 33 ranges: true
52 - ranges
65 ranges = <0x0 0x1e000000 0x0fffff>;
72 gpio-ranges = <&pinctrl 0 0 95>;
|
| /Documentation/devicetree/bindings/gpio/ |
| D | socionext,uniphier-gpio.yaml | 44 gpio-ranges: true
46 gpio-ranges-group-names: true
48 socionext,interrupt-ranges:
69 - gpio-ranges
70 - socionext,interrupt-ranges
87 gpio-ranges = <&pinctrl 0 0 0>;
88 gpio-ranges-group-names = "gpio_range";
90 socionext,interrupt-ranges = <0 48 16>, <16 154 5>, <21 217 3>;
|
| D | gpio.txt | 152 the gpio-reserved-ranges binding. This property indicates the start and size
195 gpio-reserved-ranges = <0 4>, <12 2>;
256 2.2) Ordinary (numerical) GPIO ranges
260 controllers. The gpio-ranges property described below represents this with
261 a discrete set of ranges mapping pins from the pin controller local number space
274 ranges with just one pin-to-GPIO line mapping if the ranges are concocted, but
275 in practice these ranges are often lumped in discrete sets.
279 gpio-ranges = <&foo 0 20 10>, <&bar 10 50 20>;
293 gpio-ranges = <&pinctrl1 0 20 10>, <&pinctrl2 10 50 20>;
301 2.3) GPIO ranges from named pin groups
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | raideng.txt | 16 - ranges: standard ranges property specifying the translation
26 ranges = <0 0x320000 0x10000>;
36 - ranges: standard ranges property specifying the translation
44 ranges = <0x0 0x1000 0x1000>;
72 ranges = <0x0 0x1000 0x1000>;
|
| /Documentation/devicetree/bindings/pci/ |
| D | xgene-pci.txt | 14 - ranges: ranges for the outbound memory, I/O regions.
15 - dma-ranges: ranges for the inbound memory regions.
38 ranges = <0x01000000 0x00 0x00000000 0xe0 0x10000000 0x00 0x00010000 /* io */
40 dma-ranges = <0x42000000 0x80 0x00000000 0x80 0x00000000 0x00 0x80000000
|
| D | apple,pcie.yaml | 54 ranges:
66 msi-ranges:
83 - msi-ranges
128 msi-ranges = <&aic AIC_IRQ 704 IRQ_TYPE_EDGE_RISING 32>;
138 ranges = <0x43000000 0x6 0xa0000000 0x6 0xa0000000 0x0 0x20000000>,
152 ranges;
162 ranges;
172 ranges;
|
| D | mvebu-pci.txt | 15 - ranges: ranges describing the MMIO registers to control the PCIe
16 interfaces, and ranges describing the MBus windows needed to access
21 The ranges describing the MMIO registers have the following layout:
37 The ranges describing the MBus windows have the following layout:
53 hardware, and only determined in runtime, those ranges cover the full first
71 - ranges, translating the MBus windows ranges of the parent node into
102 ranges =
144 ranges = <0x82000000 0 0 0x82000000 0x1 0 1 0
165 ranges = <0x82000000 0 0 0x82000000 0x2 0 1 0
182 ranges = <0x82000000 0 0 0x82000000 0x3 0 1 0
[all …]
|
| D | v3-v360epc-pci.txt | 15 - ranges: this follows the standard PCI bindings in the IEEE Std
21 - dma-ranges: three ranges for the inbound memory region. The ranges must
24 as pre-fetchable. Two ranges are supported by the hardware.
43 ranges = 0x01000000 0 0x00000000 /* I/O space @00000000 */
49 dma-ranges = <0x02000000 0 0x20000000 /* EBI memory space */
|
| D | faraday,ftpci100.yaml | 22 "dual" variant has 64MiB. Take this into account when describing the ranges.
77 ranges:
80 dma-ranges:
83 three ranges for the inbound memory region. The ranges must
110 - dma-ranges
135 ranges = /* 1MiB I/O space 0x50000000-0x500fffff */
140 /* DMA ranges */
141 dma-ranges =
|
| D | brcm,stb-pcie.yaml | 41 ranges:
45 dma-ranges:
93 this information cannot be deduced from the dma-ranges.
110 - ranges
111 - dma-ranges
206 ranges = <0x02000000 0x0 0xf8000000 0x6 0x00000000 0x0 0x04000000>;
207 dma-ranges = <0x42000000 0x1 0x00000000 0x0 0x40000000 0x0 0x80000000>,
220 ranges;
|
| D | xlnx,axi-pcie-host.yaml | 25 ranges:
28 ranges for the PCI memory regions (I/O space region is not
56 - ranges
82 ranges = <0x02000000 0 0x60000000 0x60000000 0 0x10000000>;
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | qcom,pmic-gpio.yaml | 94 gpio-ranges:
101 gpio-reserved-ranges:
120 - gpio-ranges
136 gpio-reserved-ranges:
156 gpio-reserved-ranges:
174 gpio-reserved-ranges:
195 gpio-reserved-ranges:
212 gpio-reserved-ranges:
235 gpio-reserved-ranges:
250 gpio-reserved-ranges:
[all …]
|
| D | amlogic,meson-pinctrl-common.yaml | 16 ranges: true
25 - ranges
41 gpio-ranges:
56 - gpio-ranges
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | sata-uctl.txt | 23 - #address-cells, #size-cells, ranges and dma-ranges must be present and hold
31 ranges; /* Direct mapping */
32 dma-ranges;
|
| /Documentation/devicetree/bindings/mfd/ |
| D | st,stmfx.yaml | 48 gpio-ranges:
50 you should use gpio-ranges = <&stmfx_pinctrl 0 0 24>;
52 you should use gpio-ranges = <&stmfx_pinctrl 0 0 16>, <&stmfx_pinctrl 20 20 4>;
54 you should use gpio-ranges = <&stmfx_pinctrl 0 0 20>;
84 - gpio-ranges
112 gpio-ranges = <&stmfx_pinctrl 0 0 24>;
|
| D | adi,adp5585.yaml | 40 gpio-reserved-ranges: true
67 gpio-reserved-ranges: false
70 gpio-reserved-ranges:
93 gpio-reserved-ranges = <5 1>;
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 32 - ranges: Contains memory regions. There are two types of
33 ranges/partitions:
50 - clock-ranges: Empty property indicating that child nodes can inherit
66 - ranges: Empty property indicating that child nodes can inherit
69 - clock-ranges: Empty property indicating that child nodes can inherit
147 clock-ranges;
149 ranges = <0 0 0x70000000 0x10000000
160 clock-ranges;
161 ranges;
189 clock-ranges;
[all …]
|
| D | intel,ixp4xx-expansion-bus-controller.yaml | 51 ranges: true
52 dma-ranges: true
68 - ranges
69 - dma-ranges
82 ranges = <0 0x0 0x50000000 0x01000000>,
84 dma-ranges = <0 0x0 0x50000000 0x01000000>,
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,gicp.txt | 15 - marvell,spi-ranges: tuples of GIC SPI interrupts ranges available
25 marvell,spi-ranges = <64 64>, <288 64>;
|
| /Documentation/devicetree/bindings/usb/ |
| D | fsl,imx8mp-dwc3.yaml | 28 dma-ranges:
32 ranges: true
88 - dma-ranges
89 - ranges
113 dma-ranges = <0x40000000 0x40000000 0xc0000000>;
114 ranges;
|
| D | ti,keystone-dwc3.yaml | 28 ranges: true
57 dma-ranges: true
68 - ranges
84 ranges;
|
| /Documentation/devicetree/bindings/arm/stm32/ |
| D | st,mlahb.yaml | 31 dma-ranges:
51 - dma-ranges
61 ranges;
62 dma-ranges = <0x00000000 0x38000000 0x10000>,
|
12345678910>>...28