| /freebsd-src/usr.bin/dtc/ |
| H A D | dtc.1 | 1 .\"-
6 .\" Cambridge Computer Laboratory under DARPA/AFRL contract (FA8750-10-C-0237)
36 .Nd device tree compiler
43 .Op Fl E Ar [no-]checker_name
52 .Op Fl W Ar [no-]checker_name
58 utility converts between flattened device tree (FDT) representations.
59 It is most commonly used to generate device tree blobs (DTB), the binary
60 representation of an FDT, from device tree sources (DTS), the ASCII text source
64 The binary is identical to the in-memory representation and can be used
70 This format is most commonly used to produce a kernel specific to a device,
[all …]
|
| /freebsd-src/share/man/man4/ |
| H A D | fdt.4 | 33 .Nd Flattened Device Tree support
39 .Em Flattened Device Tree
48 Configuration data, which cannot be self discovered in run-time, has to be
50 The concept of a flattened device tree is a
52 The idea is inherited from Open Firmware IEEE 1275 device-tree notion, and has
55 .Bl -bullet
60 self-enumerating information is gathered.
64 into a binary object i.e. a flattened device tree
72 The flattened device tree mechanism in principle does not depend on any
73 particular first-stage bootloader or firmware features.
[all …]
|
| /freebsd-src/sys/contrib/libfdt/ |
| H A D | fdt_overlay.c | 2 * libfdt - Flat Device Tree manipulation
22 * MA 02110-1301 USA
60 * overlay_get_target_phandle - retrieves the target phandle of a fragment
61 * @fdto: pointer to the device tree overlay blob
66 * property) instead of a path (target-path property).
71 * -1, if the phandle was malformed
82 if ((len != sizeof(*val)) || (fdt32_to_cpu(*val) == (uint32_t)-1)) in overlay_get_target_phandle()
83 return (uint32_t)-1; in overlay_get_target_phandle()
89 * overlay_get_target - retrieves the offset of a fragment's target
90 * @fdt: Base device tree blob
[all …]
|
| H A D | libfdt.h | 4 * libfdt - Flat Device Tree manipulation
23 * MA 02110-1301 USA
67 /* FDT_ERR_NOSPACE: Operation needed to expand the device
68 * tree, but its buffer did not have sufficient space to
69 * contain the expanded tree. Use fdt_open_into() to move the
70 * device tree to a buffer with more space. */
75 * offset which is out-of-bounds, or which points to an
84 * length, or the phandle value was either 0 or -1, which are
87 /* FDT_ERR_BADSTATE: Function was passed an incomplete device
88 * tree created by the sequential-write functions, which is
[all …]
|
| /freebsd-src/share/man/man9/ |
| H A D | ofw_bus_status_okay.9 | 1 .\" -*- nroff -*-
36 .Nd check status of the device tree node
48 The "status" property of the device tree node indicates whether the device is
50 Multiple hardware versions might be built using the same base System-on-Chip
52 It is common to use SoC device tree and only enable/disable device nodes for
54 The device tree node is considered enabled only if it has "status" property
58 returns the value of the "status" property of the device tree node associated with the device
61 the device the function returns NULL.
64 returns 1 if the device tree node associated with the device
69 returns 1 if the device tree node
|
| H A D | ofw_bus_is_compatible.9 | 1 .\" -*- nroff -*-
37 .Nd check device tree nodes for compatibility with drivers
51 The "compatible" property of the device tree node is used to
52 identify the type of the device the node represents.
54 hardware types the device is compatible with.
57 and "hardware" is a device identifier, for instance, "fsl"
58 for "Freescale" and "imx6ul-i2c" for the I2C controller.
62 A device tree node can signal this compatibility by
72 value occurs in the "compatible" property list of the device
73 tree node associated with the device
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/fpga/ |
| H A D | fpga-region.txt | 1 FPGA Region Device Tree Binding
6 - Introduction
7 - Terminology
8 - Sequence
9 - FPGA Region
10 - Supported Use Models
11 - Device Tree Examples
12 - Constraints
19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree
22 This device tree binding document hits some of the high points of FPGA usage and
[all …]
|
| /freebsd-src/sys/tools/fdt/ |
| H A D | make_dtb.sh | 4 # Script generates dtb file ($3) from dts source ($2) in build tree S ($1)
9 if [ -z "$dts" ]; then
14 if [ -z "${MACHINE}" ]; then
15 MACHINE=$(uname -m)
24 …-P -x assembler-with-cpp -I "$S/dts/include" -I "$S/contrib/device-tree/include" -I "$S/dts/${MACH…
25 …${DTC} -@ -O dtb -o "$dtb" -b 0 -p 1024 -i "$S/dts/${MACHINE}" -i "$S/contrib/device-tree/src/${MA…
|
| /freebsd-src/sys/contrib/device-tree/Bindings/i3c/ |
| H A D | i3c.txt | 1 Generic device tree bindings for I3C busses
5 busses in a device tree.
8 -------------------
10 - #address-cells - should be <3>. Read more about addresses below.
11 - #size-cells - should be <0>.
12 - compatible - name of the I3C master controller driving the I3C bus
16 The node describing an I3C bus should be named i3c-master.
19 -------------------
24 - i3c-scl-hz: frequency of the SCL signal used for I3C transfers.
27 - i2c-scl-hz: frequency of the SCL signal used for I2C transfers.
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/display/bridge/ |
| H A D | dw_hdmi.txt | 4 This document defines device tree properties for the Synopsys DesignWare HDMI
5 TX Encoder (DWC HDMI TX). It doesn't constitue a device tree binding
6 specification by itself but is meant to be referenced by platform-specific
7 device tree bindings.
9 When referenced from platform device tree bindings the properties defined in
10 this document are defined as follows. The platform device tree bindings are
13 - reg: Memory mapped base address and length of the DWC HDMI TX registers.
15 - reg-io-width: Width of the registers specified by the reg property. The
19 - interrupts: Reference to the DWC HDMI TX interrupt.
21 - clocks: References to all the clocks specified in the clock-names property
[all …]
|
| H A D | synopsys,dw-hdmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/synopsys,dw-hdm
[all...] |
| H A D | snps,dw-mipi-dsi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/snps,dw-mipi-dsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Philippe CORNU <philippe.cornu@foss.st.com>
13 This document defines device tree properties for the Synopsys DesignWare MIPI
14 DSI host controller. It doesn't constitute a device tree binding specification
15 by itself but is meant to be referenced by platform-specific device tree
18 When referenced from platform device tree bindings the properties defined in
19 this document are defined as follows. The platform device tree bindings are
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
5 controllers. Each pin controller must be represented as a node in device tree,
9 designated client devices. Again, each client device must be represented as a
10 node in device tree, just like any other hardware module.
12 For a client device to operate correctly, certain pin controllers must
15 need to reconfigure pins at run-time, for example to tri-state pins when the
16 device is inactive. Hence, each client device can define a set of named
17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
27 in a single place, rather than splitting it across multiple client device
[all …]
|
| /freebsd-src/sys/xen/xenbus/ |
| H A D | xenbusb_if.m | 1 #-
46 * \param _type String indicating the device sub-tree (e.g. "vfb", "vif")
55 * for any device found in the XenStore.
64 * a split device whose local end is represented by ivars.
70 * \param _ivars Instance variables from the XenBus child device for
82 * \brief Handle a XenStore change detected in the peer tree of a child
83 * device of the bus.
86 * \param _child NewBus device_t for the child device whose peer XenStore
87 * tree has changed.
97 * \brief Handle a XenStore change detected in the local tree of a child
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/iio/ |
| H A D | common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jonathan Cameron <jic23@kernel.org>
11 - Guido Günther <agx@sigxcpu.org>
14 This document defines device tree properties common to several iio
15 sensors. It doesn't constitute a device tree binding specification by itself but
16 is meant to be referenced by device tree bindings.
18 When referenced from sensor tree bindings the properties defined in this
19 document are defined as follows. The sensor tree bindings are responsible for
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/iommu/ |
| H A D | iommu.txt | 1 This document describes the generic device tree binding for IOMMUs and their
5 IOMMU device node:
13 Example: 32-bit DMA to 64-bit physical addresses
15 * Implement scatter-gather at page level granularity so that the device does
26 Device nodes compatible with this binding represent hardware with some of the
29 IOMMUs can be single-master or multiple-master. Single-master IOMMU devices
30 typically have a fixed association to the master device, whereas multiple-
33 The device tree node of the IOMMU device's parent bus must contain a valid
34 "dma-ranges" property that describes how the physical address space of the
35 IOMMU maps to memory. An empty "dma-ranges" property means that there is a
[all …]
|
| /freebsd-src/usr.sbin/ofwdump/ |
| H A D | ofwdump.8 | 29 .Nd examine the Open Firmware device tree
39 .Op Fl -
44 utility is used to examine the Open Firmware device tree.
45 In the first synopsis form, the complete device tree is printed; in the
51 .Bl -tag -width ".Fl P Ar property"
53 Print the complete device tree.
76 Print the complete device tree:
78 .Dl "ofwdump -a"
80 Print the complete device subtree of the
84 .Dl "ofwdump -pr /pci"
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/display/panel/ |
| H A D | panel-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
14 This document defines device tree properties common to several classes of
15 display panels. It doesn't constitute a device tree binding specification by
16 itself but is meant to be referenced by device tree bindings.
18 When referenced from panel device tree bindings the properties defined in this
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/fsi/ |
| H A D | fsi.txt | 1 FSI bus & engine generic device tree bindings
4 The FSI bus is probe-able, so the OS is able to enumerate FSI slaves, and
6 nodes to probed engines. This allows for fsi engines to expose non-probeable
7 busses, which are then exposed by the device tree. For example, an FSI engine
8 that is an I2C master - the I2C bus can be described by the device tree under
9 the engine's device tree node.
13 the fsi-master-* binding specifications.
18 fsi-master {
19 /* top-level of FSI bus topology, bound to an FSI master driver and
22 fsi-slave@<link,id> {
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/iio/adc/ |
| H A D | adi,ad7606.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michael Hennerich <michael.hennerich@analog.com>
14 https://www.analog.com/media/en/technical-documentation/data-sheet
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | ti-aemif.txt | 1 * Device tree bindings for Texas instruments AEMIF controller
4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/display/ |
| H A D | dsi-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/dsi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 This document defines device tree properties common to DSI, Display
15 a device tree binding specification by itself but is meant to be referenced
16 by device tree bindings.
18 When referenced from panel device tree bindings the properties defined in
19 this document are defined as follows. The panel device tree bindings are
[all …]
|
| /freebsd-src/tools/tools/notescheck/ |
| H A D | notescheck.py | 18 print("Where 'path' is a path to a kernel source tree.", file=sys.stderr)
20 # These files are used to determine if a path is a valid kernel source tree.
30 # Format the contents of a set into a sorted, comma-separated string
43 for item in l[1:-1]:
45 s = "%s, and %s" % (s, l[-1])
53 # config(8) treats the names as case-insensitive.
95 # If the device is defined globally and is never tested, whine.
101 # If the device is defined globally and is tested on
108 # If a device is defined globally but is only tested on a
114 # If an option or device is never tested, whine.
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/arm/ |
| H A D | syna.txt | 1 Synaptics SoC Device Tree Bindings
3 According to https://www.synaptics.com/company/news/conexant-marvell
7 -------
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/ata/ |
| H A D | sata-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/ata/sata-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 This document defines device tree properties common to most Serial
14 AT attachment (SATA) storage devices. It doesn't constitute a device tree
15 binding specification by itself but is meant to be referenced by device
16 tree bindings.
18 The SATA controller-specific device tree bindings are responsible for
[all …]
|