| /rk3399_ARM-atf/tools/cot_dt2c/cot_dt2c/ |
| H A D | dt_validator.py | 44 valid, tree = self.dtParseFile(input, printInfo)
55 if "/dts-v1/;" not in str(tree):
57 f.write(str(tree))
60 if str(tree) == "":
74 tree = Devicetree.parseStr(contents)
88 return True, tree
|
| H A D | cot_parser.py | 17 self.tree = Devicetree.parseFile(inputfile)
337 children = self.tree.children
343 children = self.tree.children
349 children = self.tree.children
353 children = self.tree.children
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | psci-pd-tree.rst | 9 populate a tree that describes the hierarchy of power domains in the
13 It would be much simpler for the platform to describe its power domain tree
17 tree. It also uses an MPIDR to find a node in the tree. The assumption that
20 levels in the power domain tree to four.
23 mechanism used to populate the power domain topology tree.
25 #. The current arrangement of the power domain tree requires a binary search
27 domain node. During a power management operation, the tree is traversed from
33 Therefore, there is a need to define data structures that implement the tree in
41 Therefore, there is a need to implement the tree in a way which facilitates this
50 Describing a power domain tree
[all …]
|
| H A D | index.rst | 13 psci-pd-tree
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | index.rst | 19 functionality for platforms that cannot / don't want to use device tree.
39 properties originate from a different backend source such as a device tree,
46 captures the hardware topology of the platform from the HW_CONFIG device tree.
49 configuration properties which is usually a device tree file.
90 Loading the property device tree
94 tb_fw_config devices tree containing the properties' values. This must be done
103 Once a valid device tree is available, the ``fconf_populate(config)`` function
|
| H A D | fconf_properties.rst | 4 This document describes the device tree format of |FCONF| properties. These
|
| /rk3399_ARM-atf/fdts/ |
| H A D | stm32mp257f-dk-ca35tdcid-rcc.dtsi | 8 * STM32MP25 Clock tree device tree configuration
|
| H A D | stm32mp257f-ev1-ca35tdcid-rcc.dtsi | 8 * STM32MP25 Clock tree device tree configuration
|
| H A D | juno-ethosn.dtsi | 8 * This device tree is only an example and some properties have been omitted.
10 * Refer to the Arm(R) Ethos(TM)-N driver stack for complete device tree examples.
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | xilinx-zynqmp.rst | 34 - ``XILINX_OF_BOARD_DTB_ADDR`` : Specifies the base address of Device tree.
52 above memory range will NOT be reserved in device tree.
54 To reserve the above memory range in device tree, the device tree base address
69 adding the reserved memory node, in the device tree, with the required address
70 range OR let TF-A modify the device tree on the run.
72 To let TF-A access and modify the device tree, the DTB address must be provided
114 The following power domain tree represents the power domain model used by TF-A
|
| H A D | hikey.rst | 21 `link <https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5>`__
24 `link <https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4>`__
27 `link <https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2>`__
30 `link <https://github.com/96boards-hikey/atf-fastboot/tree/master>`__
|
| H A D | hikey960.rst | 21 `link <https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5>`__
24 `link <https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4>`__
27 `link <https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2>`__
|
| H A D | rpi4.rst | 42 The BL31 code will patch the provided device tree blob in memory to advertise
72 But before doing that, it will also load a "kernel" and the device tree into
83 register x0. If the payload has other means of finding the device tree, it
|
| H A D | rpi3.rst | 11 port of TF-A can't boot a AArch64 kernel. The `Linux tree fork`_ maintained by
65 The device tree block is loaded by the VideoCore loader from an appropriate
69 specified in ``config.txt``. The `Linux kernel tree`_ has information about how
155 The `Linux kernel tree`_ has instructions on how to jump to the Linux kernel
326 to the Linux kernel tree maintained by the Raspberry Pi foundation. It modifes
364 1. Clone the `Linux tree fork`_ maintained by the Raspberry Pi Foundation. To
381 3. Copy the kernel image and the device tree to the SD card. Replace the path
456 .. _Linux kernel tree: https://github.com/torvalds/linux
457 .. _Linux tree fork: https://github.com/raspberrypi/linux
|
| /rk3399_ARM-atf/ |
| H A D | .checkpatch.conf | 13 --no-tree
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-internals.rst | 24 tb_fw_config device tree. This flag is defined only when
28 tb_fw_config device tree. This flag is defined only when
|
| H A D | initial-build.rst | 50 - Change to the root directory of the TF-A source tree and build.
88 - The build process creates products in a ``build`` directory tree, building
110 The build tree can be removed completely using:
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-build-options.rst | 7 build the topology tree within TF-A. By default TF-A is configured for dual
51 tree blob at build time. Takes an initrd size value in hex format
53 - ``INITRD_PATH`` : Enable the insertion of initrd properties to the device tree
|
| H A D | index.rst | 30 .. _model/: https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tree/model
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 25 and their respective device tree blobs.
53 - | ``DTB_FILE_NAME``: to precise board device-tree blob to be used.
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | platform-ports-policy.rst | 24 deprecated into their downstream tree.
39 to deprecate it to keep the projects' source tree clean and healthy. Deprecation
|
| /rk3399_ARM-atf/tools/memory/src/memory/ |
| H A D | summary.py | 347 def _move_up_tree(tree: Dict[str, Any], next_module: str) -> Dict[str, Any]:
348 tree.setdefault("children", [])
349 for child in tree["children"]:
354 tree["children"].append(new_module)
|
| H A D | memmap.py | 120 def tree(obj: Context, depth: int): function
|
| /rk3399_ARM-atf/docs/components/measured_boot/ |
| H A D | event_log.rst | 4 This document describes the device tree format of Event Log properties.
|
| /rk3399_ARM-atf/docs/tools/ |
| H A D | memory-layout-tool.rst | 153 A hierarchical view of the memory layout can be produced by passing the ``tree``
159 $ poetry run memory tree
207 instance, if you only require the tree up to the level showing segment data,
212 $ poetry run memory tree --depth 2
|