Searched full:dt (Results 1 – 25 of 512) sorted by relevance
12345678910>>...21
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 26 "include/dt-bindings/power/px30-power.h" - for PX30 type power domain.
27 "include/dt-bindings/power/rk3036-power.h" - for RK3036 type power domain.
28 "include/dt-bindings/power/rk3066-power.h" - for RK3066 type power domain.
29 "include/dt-bindings/power/rk3128-power.h" - for RK3128 type power domain.
30 "include/dt-bindings/power/rk3188-power.h" - for RK3188 type power domain.
31 "include/dt-bindings/power/rk3228-power.h" - for RK3228 type power domain.
32 "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power domain.
33 "include/dt-bindings/power/rk3328-power.h" - for RK3328 type power domain.
34 "include/dt-bindings/power/rk3366-power.h" - for RK3366 type power domain.
35 "include/dt-bindings/power/rk3368-power.h" - for RK3368 type power domain.
[all …]
|
| /Documentation/devicetree/ |
| D | writing-schema.rst | 20 URI typically containing the binding's filename and path. For DT schema, it must
35 A DT specific property. Contains a list of email address(es)
55 A set of sub-schema defining all the DT properties for the
59 A property can also define a child DT node with child properties defined
68 A list of DT properties from the 'properties' section that
80 The 'properties' section of the schema contains all the DT properties for a
83 validation of DT files.
93 The Devicetree schemas don't exactly match the YAML encoded DT data produced by
114 The DT schema project must be installed in order to validate the DT schema
115 binding documents and validate DTS files using the DT schema. The DT schema
[all …]
|
| D | usage-model.txt | 13 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
41 The DT was originally created by Open Firmware as part of the
53 and 64-bit support, the decision was made to require DT support on all
55 Firmware. To do this, a DT representation called the Flattened Device
59 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
62 existing non-DT aware firmware.
67 out of mainline (nios) have some level of DT support.
76 The most important thing to understand is that the DT is simply a data
90 Linux uses DT data for three major purposes:
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 2 Submitting devicetree (DT) binding patches
9 1) The Documentation/ and include/dt-bindings/ portion of the patch should
12 "dt-bindings: <binding dir>: ..."
22 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
23 all of the DT maintainers.
29 previously documented in the corresponding DT binding text file
34 ("checkpatch: add DT compatible string documentation checks"). ]
|
| D | Makefile | 2 DT_DOC_CHECKER ?= dt-doc-validate
3 DT_EXTRACT_EX ?= dt-extract-example
4 DT_MK_SCHEMA ?= dt-mk-schema
23 -name '*.example.dt.yaml' \) \
30 extra-y += $(patsubst $(src)/%.yaml,%.example.dt.yaml, $(DT_SCHEMA_FILES))
|
| /Documentation/devicetree/bindings/clock/ |
| D | maxim,max77686.txt | 4 multi-function device. More information can be found in MFD DT binding
12 dt-bindings/clock/maxim,max77686.h.
17 dt-bindings/clock/maxim,max77802.h.
21 dt-bindings/clock/maxim,max77620.h.
38 Clocks are defined as preprocessor macros in above dt-binding header for
45 #include <dt-bindings/clock/maxim,max77686.h>
70 #include <dt-bindings/clock/maxim,max77802.h>
96 #include <dt-bindings/clock/maxim,max77620.h>
|
| D | alphascale,acc.txt | 13 It is encouraged to use dt-binding for clock index definitions. SoC specific
14 dt-binding should be included to the device tree descriptor. For example
16 #include <dt-bindings/clock/alphascale,asm9260.h>
|
| /Documentation/devicetree/bindings/power/ |
| D | actions,owl-sps.txt | 10 include/dt-bindings/power/owl-s500-powergate.h for S500
11 include/dt-bindings/power/owl-s700-powergate.h for S700
12 include/dt-bindings/power/owl-s900-powergate.h for S900
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | adi,adxl372.yaml | 35 #include <dt-bindings/gpio/gpio.h>
36 #include <dt-bindings/interrupt-controller/irq.h>
50 #include <dt-bindings/gpio/gpio.h>
51 #include <dt-bindings/interrupt-controller/irq.h>
|
| D | adi,adxl345.yaml | 41 #include <dt-bindings/gpio/gpio.h>
42 #include <dt-bindings/interrupt-controller/irq.h>
56 #include <dt-bindings/gpio/gpio.h>
57 #include <dt-bindings/interrupt-controller/irq.h>
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 1 DT compatible string versioning for SiFive open-source IP blocks
3 This document describes the version specification for DT "compatible"
9 IP block-specific DT compatible strings are contained within the HDL,
28 DT data authors, when writing data for a particular SoC, should
|
| /Documentation/devicetree/bindings/thermal/ |
| D | max77620_thermal.txt | 15 For more details, please refer generic thermal DT binding document
18 Please refer <devicetree/bindings/mfd/max77620.txt> for mfd DT binding
23 #include <dt-bindings/mfd/max77620.h>
24 #include <dt-bindings/thermal/thermal.h>
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | scpsys.txt | 12 - include/dt-bindings/power/mt8173-power.h
13 - include/dt-bindings/power/mt6797-power.h
14 - include/dt-bindings/power/mt2701-power.h
15 - include/dt-bindings/power/mt2712-power.h
16 - include/dt-bindings/power/mt7622-power.h
|
| /Documentation/arm64/ |
| D | arm-acpi.rst | 40 while DT explicitly does not support this. For hardware vendors, being
49 as for RAS) which are currently used in production systems. DT does not.
50 Such bindings could be defined in DT at some point, but doing so means ARM
56 both DT and ACPI if they want to support multiple operating systems. And,
80 in place. DT does exactly what Linux needs it to when working with vertically
82 server vendors need. Linux could potentially get there with DT, but doing so
84 the hardware vendors need, Microsoft won’t collaborate on DT, and hardware
112 exclusive with DT support at compile time.
117 Regardless of whether DT or ACPI is used, the kernel must always be capable
128 When an ARMv8 system boots, it can either have DT information, ACPI tables,
[all …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | oxnas,reset.txt | 18 Reset indices are in dt-bindings include files :
19 - For OX810SE: include/dt-bindings/reset/oxsemi,ox810se.h
20 - For OX820: include/dt-bindings/reset/oxsemi,ox820.h
|
| D | fsl,imx7-src.txt | 50 <dt-bindings/reset/imx7-reset.h> for i.MX7,
51 <dt-bindings/reset/imx8mq-reset.h> for i.MX8MQ and
52 <dt-bindings/reset/imx8mq-reset.h> for i.MX8MM
|
| /Documentation/devicetree/bindings/net/nfc/ |
| D | st95hf.txt | 4 ST95HF node should be defined in DT as SPI slave device of SPI
6 The properties defined below are required to be the part of DT
26 phandle to ST95HF transceiver's regulator supply node in DT.
|
| /Documentation/devicetree/bindings/net/ |
| D | ti,dp83867.txt | 5 - ti,rx-internal-delay - RGMII Receive Clock Delay - see dt-bindings/net/ti-dp83867.h
8 - ti,tx-internal-delay - RGMII Transmit Clock Delay - see dt-bindings/net/ti-dp83867.h
11 - ti,fifo-depth - Transmitt FIFO depth- see dt-bindings/net/ti-dp83867.h
36 - ti,clk-output-sel - Muxing option for CLK_OUT pin. See dt-bindings/net/ti-dp83867.h
|
| /Documentation/devicetree/bindings/clock/sifive/ |
| D | fu540-prci.txt | 17 macros defined in include/dt-bindings/clock/sifive-fu540-prci.h.
26 /* under /, in PCB-specific DT data */
40 /* under /soc, in SoC-specific DT data */
|
| /Documentation/devicetree/bindings/pwm/ |
| D | nvidia,tegra20-pwm.txt | 27 DT node as detailed in the pinctrl DT binding document
51 Following will be DT binding to achieve this:
53 #include <dt-bindings/pinctrl/pinctrl-tegra.h>
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 14 To be able to integrate the ATL clocks with DT clock tree.
17 for the DT clock tree, the IP driver is needed to handle the actual configuration
46 For valid word select signals, see the dt-bindings/clk/ti-dra7-atl.h include
86 #include <dt-bindings/clk/ti-dra7-atl.h>
|
| /Documentation/devicetree/bindings/pci/ |
| D | ti-pci.txt | 36 - ti,syscon-unaligned-access: phandle to the syscon DT node. The 1st argument
54 - ti,syscon-unaligned-access: phandle to the syscon DT node. The 1st argument
63 NOTE: Two DT nodes may be added for each PCI controller; one for host
65 work in host mode, EP mode DT node should be disabled and in order to PCI to
66 work in EP mode, host mode DT node should be disabled. Host mode and EP
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-max77620.txt | 13 For more details, please refer generic GPIO DT binding document
18 #include <dt-bindings/mfd/max77620.h>
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | ad5592r.txt | 22 can be found in <dt-bindings/iio/adi,ad5592r.h>.
39 <dt-bindings/iio/adi,ad5592r.h>.
56 cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>.
60 #include <dt-bindings/iio/adi,ad5592r.h>
125 #include <dt-bindings/iio/adi,ad5592r.h>
|
| /Documentation/devicetree/bindings/usb/ |
| D | generic.txt | 7 via DT, USB controllers should default to their maximum
12 passed via DT, USB DRD controllers should default to
17 In case this isn't passed via DT, USB controllers should
|
12345678910>>...21