| /linux-6.12.1/Documentation/translations/zh_CN/devicetree/ |
| D | usage-model.rst | 26 "Open Firmware Device Tree"，或简称为Devicetree（DT），是一种用于描述硬
30 从结构上看，DT是一棵树，或者说是带有命名节点的无环图，节点可以有任意数量的命名
46 DT最初是由Open Firmware创建的，作为将数据从Open Firmware传递给客户程序
55 Powerpc平台上要求DT支持，无论它们是否使用Open Firmware。为了做到这一点，
56 我们创建了一个叫做扁平化设备树（FDT）的DT表示法，它可以作为一个二进制的blob
58 被修改，以支持传递设备树二进制（dtb）和在引导时修改dtb。DT也被添加到PowerPC
60 支持引导现有的非DT察觉的固件。
64 有某种程度的DT支持。
72 最重要的是要明白，DT只是一个描述硬件的数据结构。它没有什么神奇之处，也不会神
81 Linux使用DT数据有三个主要目的:
[all …]
|
| D | overlay-notes.rst | 89 如果基础DT不是用-@选项编译的，那么“&ocp”标签将不能用于将覆盖节点解析到基础
90 DT中的适当位置。在这种情况下，可以提供目标路径。通过标签的目标位置的语法是比
91 较好的，因为不管标签在DT中出现在哪里，覆盖都可以被应用到任何包含标签的基础DT上。
|
| D | of_unittest.rst | 48 用于将DT源文件（testcases.dts）编译成二进制blob（testcases.dtb），也被称为扁平化的DT。
|
| D | changesets.rst | 28 2. 一些DT树变化的调用，of_changeset_attach_node(), of_changeset_detach_node(),
|
| /linux-6.12.1/crypto/ |
| D | ansi_cprng.c | 43 unsigned char DT[DEFAULT_BLK_SZ]; member
91 hexdump("Input DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
106 memcpy(tmp, ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
164 ctx->DT[i] += 1; in _get_more_prng_bytes()
165 if (ctx->DT[i] != 0) in _get_more_prng_bytes()
172 hexdump("Output DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
278 const unsigned char *V, const unsigned char *DT) in reset_prng_context() argument
296 if (DT) in reset_prng_context()
297 memcpy(ctx->DT, DT, DEFAULT_BLK_SZ); in reset_prng_context()
299 memset(ctx->DT, 0, DEFAULT_BLK_SZ); in reset_prng_context()
|
| /linux-6.12.1/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 4 Submitting Devicetree (DT) binding patches
27 2) DT binding files are written in DT schema format using json-schema
28 vocabulary and YAML file format. The DT binding files must pass validation
36 3) DT binding files should be dual licensed. The preferred license tag is
43 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
44 all of the DT maintainers.
50 previously documented in the corresponding DT binding file
55 ("checkpatch: add DT compatible string documentation checks"). ]
|
| D | writing-schema.rst | 22 URI typically containing the binding's filename and path. For DT schema, it must
37 A DT specific property. Contains a list of email address(es)
57 A set of sub-schema defining all the DT properties for the
62 A property can also define a child DT node with child properties defined
71 A list of DT properties from the 'properties' section that
105 The 'properties' section of the schema contains all the DT properties for a
108 validation of DT files.
118 The Devicetree schemas don't exactly match the YAML-encoded DT data produced by
145 The DT schema project must be installed in order to validate the DT schema
146 binding documents and validate DTS files using the DT schema. The DT schema
[all …]
|
| /linux-6.12.1/Documentation/translations/zh_CN/power/ |
| D | energy-model.rst | 95 提供的回调函数可以自由地从任何相关位置（DT、固件......）以及以任何被认为是
106 使用DT的EM注册
109 EM也可以使用OPP框架和DT "操作点-v2 "中的信息注册。DT中的每个OPP条目都可
110 以用一个包含微瓦特功率值的属性 "op-microwatt "来扩展。这个OPP DT属性允
|
| /linux-6.12.1/Documentation/devicetree/ |
| D | usage-model.rst | 17 The "Open Firmware Device Tree", or simply Devicetree (DT), is a data
23 Structurally, the DT is a tree, or acyclic graph with named nodes, and
45 The DT was originally created by Open Firmware as part of the
57 and 64-bit support, the decision was made to require DT support on all
59 Firmware. To do this, a DT representation called the Flattened Device
63 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
66 existing non-DT aware firmware.
71 out of mainline (nios) have some level of DT support.
80 The most important thing to understand is that the DT is simply a data
94 Linux uses DT data for three major purposes:
[all …]
|
| D | overlay-notes.rst | 85 If the base DT was not compiled with the -@ option then the "&ocp" label
87 in the base DT. In this case, the target path can be provided. The target
89 any base DT containing the label, no matter where the label occurs in the DT.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | arm-acpi.rst | 41 while DT explicitly does not support this. For hardware vendors, being
50 as for RAS) which are currently used in production systems. DT does not.
51 Such bindings could be defined in DT at some point, but doing so means Arm
57 both DT and ACPI if they want to support multiple operating systems. And,
81 in place. DT does exactly what Linux needs it to when working with vertically
83 server vendors need. Linux could potentially get there with DT, but doing so
85 the hardware vendors need, Microsoft won’t collaborate on DT, and hardware
113 exclusive with DT support at compile time.
118 Regardless of whether DT or ACPI is used, the kernel must always be capable
129 When an Arm system boots, it can either have DT information, ACPI tables,
[all …]
|
| /linux-6.12.1/drivers/comedi/drivers/ |
| D | dt3000.c | 718 { PCI_VDEVICE(DT, 0x0022), BOARD_DT3001 },
719 { PCI_VDEVICE(DT, 0x0023), BOARD_DT3002 },
720 { PCI_VDEVICE(DT, 0x0024), BOARD_DT3003 },
721 { PCI_VDEVICE(DT, 0x0025), BOARD_DT3004 },
722 { PCI_VDEVICE(DT, 0x0026), BOARD_DT3005 },
723 { PCI_VDEVICE(DT, 0x0027), BOARD_DT3001_PGL },
724 { PCI_VDEVICE(DT, 0x0028), BOARD_DT3003_PGL },
|
| /linux-6.12.1/sound/soc/generic/ |
| D | Kconfig | 18 with OF-graph DT bindings.
27 with OF-graph DT bindings.
|
| /linux-6.12.1/Documentation/arch/mips/ |
| D | booting.rst | 11 Similar to the arch/arm case (b), a DT-aware bootloader is expected to
24 DT block. In this case, Linux will look for a builtin DTB, selected via
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/devicetree/bindings/media/xilinx/ |
| D | xlnx,video.txt | 9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
|
| /linux-6.12.1/Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-dt.txt | 3 It is a generic DT based cpufreq driver for frequency management. It supports
15 details. OPPs *must* be supplied either via DT, i.e. this property, or
|
| /linux-6.12.1/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 15 specifier - a list of DT cells that represents the reset signal within the
23 the DT node of each affected HW block, since if activated, an unrelated block
24 may be reset. Instead, reset signals should be represented in the DT node
|
| /linux-6.12.1/Documentation/translations/it_IT/devicetree/bindings/ |
| D | submitting-patches.rst | 8 Sottomettere patch per devicetree (DT) *binding*
|
| /linux-6.12.1/Documentation/translations/zh_CN/arch/arm64/ |
| D | booting.txt | 198 - 设备树（DT）或 ACPI 表必须描述一个 GICv3 中断控制器。
205 - 设备树（DT）或 ACPI 表必须描述一个 GICv2 中断控制器。
|
| /linux-6.12.1/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-h616-orangepi-zero.dtsi | 5 * DT nodes common between Orange Pi Zero 2 and Orange Pi Zero 3.
121 * need to adjust the DT accordingly: dr_mode set to "host",
|
| /linux-6.12.1/arch/arm/boot/dts/st/ |
| D | stm32mp157a-avenger96.dts | 10 /* This DT is here only for backward compatibility */
|
| /linux-6.12.1/Documentation/translations/zh_CN/arch/mips/ |
| D | booting.rst | 31 传统bootloaders不会使用这样的约定，并且它们不传入DT块。
|