| /openbmc/qemu/docs/system/arm/ |
| H A D | sbsa.rst | 36 ``sbsa-ref`` is a static system that reports a very minimal devicetree to the 46 platform using minimalistic devicetree. This is not a Linux devicetree. It is 47 not even a firmware devicetree. 53 Ultimately this devicetree may be replaced by IPC calls to an emulated SCP. 55 DeviceTree information 58 The devicetree reports: 82 Devicetree holds information about CPUs, memory and platform version. 85 GIC information is present in devicetree. 88 GIC ITS information is present in devicetree. 94 CPU topology information is present in devicetree.
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/ |
| H A D | entity-manager_git.bb | 34 SYSTEMD_SERVICE:devicetree-vpd = "devicetree-vpd-parser.service" 41 ${@bb.utils.contains('PACKAGECONFIG', 'dts-vpd', 'devicetree-vpd', '', d)} \ 54 FILES:devicetree-vpd = "${bindir}/devicetree-vpd-parser" 58 ${@bb.utils.contains('PACKAGECONFIG', 'dts-vpd', 'devicetree-vpd', '', d)} \
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/files/corstone1000/ |
| H A D | 0003-dt-bindings-remoteproc-Add-Arm-remoteproc.patch | 14 create mode 100644 Documentation/devicetree/bindings/remoteproc/arm,rproc.yaml 16 diff --git a/Documentation/devicetree/bindings/remoteproc/arm,rproc.yaml b/Documentation/devicetree… 20 +++ b/Documentation/devicetree/bindings/remoteproc/arm,rproc.yaml 25 +$id: http://devicetree.org/schemas/remoteproc/arm,rproc.yaml# 26 +$schema: http://devicetree.org/meta-schemas/core.yaml# 99 +F: Documentation/devicetree/bindings/remoteproc/arm,rproc.yaml
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | devicetree.bbclass | 14 # The output of this class behaves similar to how kernel-devicetree.bbclass 15 # operates in that the output files are installed into /boot/devicetree. 17 # 'devicetree' subdirectory. This prevents clashes with the kernel-devicetree 40 SYSROOT_DIRS += "/boot/devicetree" 41 FILES:${PN} = "/boot/devicetree/*.dtb /boot/devicetree/*.dtbo" 148 install -Dm 0644 ${B}/${DTB_FILE} ${D}/boot/devicetree/${DTB_FILE} 154 install -Dm 0644 ${B}/${DTB_FILE} ${DEPLOYDIR}/devicetree/${DTB_FILE}
|
| H A D | linux-dummy.bbclass | 12 # set an empty package of kernel-devicetree 13 d.appendVar('PACKAGES', ' %s-devicetree' % kname) 14 d.setVar('ALLOW_EMPTY:%s-devicetree' % kname, '1')
|
| H A D | kernel-devicetree.bbclass | 10 d.appendVar("PACKAGES", " ${KERNEL_PACKAGE_NAME}-devicetree") 15 # recursivly search for devicetree files 16 FILES:${KERNEL_PACKAGE_NAME}-devicetree = " \ 23 # Generate kernel+devicetree bundle
|
| /openbmc/u-boot/include/dm/ |
| H A D | util.h | 45 * Devicetree nodes can be marked as needed to be bound 46 * in the loader stages via special devicetree properties. 61 * @blob: devicetree 71 * Devicetree nodes can be marked as needed to be bound 72 * in the loader stages via special devicetree properties.
|
| H A D | root.h | 51 * @pre_reloc_only: If true, bind only nodes with special devicetree properties, 65 * @pre_reloc_only: If true, bind only nodes with special devicetree properties, 79 * @pre_reloc_only: If true, bind only nodes with special devicetree properties, 92 * @pre_reloc_only: If true, bind only nodes with special devicetree properties,
|
| /openbmc/u-boot/doc/device-tree-bindings/leds/ |
| H A D | leds-gpio.txt | 11 Documentation/devicetree/bindings/gpio/gpio.txt. Active low LEDs should be 14 see Documentation/devicetree/bindings/leds/common.txt 16 see Documentation/devicetree/bindings/leds/common.txt
|
| /openbmc/openbmc/meta-facebook/meta-catalina/meta-clemente/conf/machine/ |
| H A D | clemente.conf | 3 # Set as Catalina's devicetree until Clemente devicetree is merged.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-dtschema_2025.2.bb | 1 SUMMARY = "Tooling for devicetree validation using YAML and jsonschema" 2 HOMEPAGE = "https://github.com/devicetree-org/dt-schema"
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0034-bootefi-Call-the-EVT_FT_FIXUP-event-handler.patch | 6 The bootefi command passes the devicetree to the kernel through the 7 EFI config table. Call the event handlers for fixing the devicetree 8 before jumping into the kernel. This removes any devicetree nodes
|
| /openbmc/entity-manager/service_files/ |
| H A D | meson.build | 4 ['devicetree-vpd-parser.service', 'devicetree-vpd'],
|
| H A D | devicetree-vpd-parser.service | 6 ExecStart=/usr/libexec/entity-manager/devicetree-vpd-parser
|
| /openbmc/u-boot/scripts/dtc/ |
| H A D | dtc-parser.y | 86 %type <node> devicetree 109 headers memreserves devicetree 160 devicetree: 165 | devicetree '/' nodedef 173 * versioninfo plugindecl memreserves devicetree 180 | devicetree DT_LABEL DT_REF nodedef 191 | devicetree DT_REF nodedef 200 * versioninfo plugindecl memreserves devicetree 210 | devicetree DT_DEL_NODE DT_REF ';'
|
| /openbmc/openbmc/meta-openpower/recipes-bsp/pdata/ |
| H A D | phal-devtree.bb | 1 SUMMARY = "Tools and libraries to manage the phal devicetree" 2 DESCRIPTION = "phal(power hardware abstraction layer) devicetree data \
|
| /openbmc/u-boot/doc/device-tree-bindings/phy/ |
| H A D | phy-stih407-usb.txt | 12 See: Documentation/devicetree/bindings/reset/st,sti-powerdown.txt 13 See: Documentation/devicetree/bindings/reset/reset.txt
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-acs/arm-systemready-scripts/ |
| H A D | 0002-check-sr-results-Device-tree-improvements.patch | 7 devicetree files, and pass these in the compat list given to 29 logging.debug(f"Check Devicetree `{filename}'") 45 if 'devicetree' in conffile:
|
| /openbmc/u-boot/arch/arm/include/asm/arch-fsl-layerscape/ |
| H A D | stream_id_lsch3.h | 30 * device tree (see Documentation/devicetree/bindings/pci/pci-msi.txt 33 * device tree (see Documentation/devicetree/bindings/pci/pci-iommu.txt 40 * device tree (see Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
|
| H A D | stream_id_lsch2.h | 29 * device tree (see Documentation/devicetree/bindings/pci/pci-msi.txt 32 * device tree (see Documentation/devicetree/bindings/pci/pci-iommu.txt
|
| /openbmc/u-boot/doc/device-tree-bindings/video/ |
| H A D | displaymode.txt | 21 There are different ways of describing a display mode. The devicetree 26 the devicetree has the clock in Hz instead of ps.
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | micrel-ksz90x1.txt | 40 specified in the devicetree are offset by the minimum value so they 41 can be represented as positive integers in the devicetree since it's 46 Pad Skew Value Delay (ps) Devicetree Value 84 Pad Skew Value Delay (ps) Devicetree Value
|
| /openbmc/docs/designs/ |
| H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 92 …https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter3-devicenodes.r… 94 …https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter4-device-bindin… 138 - A daemon in DeviceTree-VPD-Parser retrieves product data from known device 179 ### All VPD is exposed as devicetree attributes under /chosen/ 282 1. Proposal: xyz.openbmc_project.DeviceTree
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/boot-wrapper-aarch64/ |
| H A D | boot-wrapper-aarch64_git.bb | 23 # by default use the standard kernel devicetree 24 # This should be overwritten if the devicetree is not generated
|
| /openbmc/entity-manager/src/devicetree_vpd_parser/ |
| H A D | meson.build | 3 'devicetree-vpd-parser',
|