| /OK3568_Linux_fs/kernel/crypto/ |
| H A 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()
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/ |
| H A 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 …]
|
| H A D | usage-model.rst | 17 The "Open Firmware Device Tree", or simply Device Tree (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 …]
|
| H A D | changesets.rst | 4 DT Changesets
7 A DT changeset is a method which allows one to apply changes
23 2. A number of DT tree change calls, of_changeset_attach_node(),
|
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/ |
| H A D | submitting-patches.rst | 4 Submitting devicetree (DT) binding patches
22 2) DT binding files are written in DT schema format using json-schema
23 vocabulary and YAML file format. The DT binding files must pass validation
30 3) DT binding files should be dual licensed. The preferred license tag is
37 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
38 all of the DT maintainers.
44 previously documented in the corresponding DT binding text file
49 ("checkpatch: add DT compatible string documentation checks"). ]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sifive/ |
| H A 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
|
| /OK3568_Linux_fs/u-boot/dts/ |
| H A D | Kconfig | 80 prompt "Provider of DTB for DT control"
84 bool "Separate DTB for DT control"
91 bool "Embedded DTB for DT control"
107 bool "Host filed DTB for DT control"
115 bool "Prior stage bootloader DTB for DT control"
117 If this option is enabled, the device tree used for DT
124 string "Default Device Tree for DT control"
127 This option specifies the default Device Tree used for DT control.
132 string "List of device tree files to include for DT control"
136 This option specifies a list of device tree files to use for DT
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/net/nfc/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/arm64/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/staging/board/ |
| H A D | TODO | 1 * replace platform device code with DT nodes once the driver supports DT
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pci/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/drivers/staging/comedi/drivers/ |
| H A D | dt3000.c | 719 { PCI_VDEVICE(DT, 0x0022), BOARD_DT3001 },
720 { PCI_VDEVICE(DT, 0x0023), BOARD_DT3002 },
721 { PCI_VDEVICE(DT, 0x0024), BOARD_DT3003 },
722 { PCI_VDEVICE(DT, 0x0025), BOARD_DT3004 },
723 { PCI_VDEVICE(DT, 0x0026), BOARD_DT3005 },
724 { PCI_VDEVICE(DT, 0x0027), BOARD_DT3001_PGL },
725 { PCI_VDEVICE(DT, 0x0028), BOARD_DT3003_PGL },
|
| /OK3568_Linux_fs/u-boot/doc/uImage.FIT/ |
| H A D | overlay-fdt-boot.txt | 7 of similar boards and their expansion options. The same kernel on DT enabled
8 platforms can support this easily enough by providing a DT blob upon boot
113 Device tree overlays can be applied to a base DT and result in the same blob
199 Note the minimum amount of different DT blobs, as well as the requirement for
200 the DT blobs to have a load address; the overlay application requires the blobs
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.nios2 | 61 (mysystem) Default Device Tree for DT control
63 There is a selection of "Provider of DTB for DT control" in the Device
66 ( ) Separate DTB for DT control, will cat the dtb to end of u-boot
71 ( ) Embedded DTB for DT control, will include the dtb inside the u-boot
|
| H A D | README.falcon | 34 After loading the desired legacy-format kernel image into memory (and DT as
36 area or the DT. U-Boot runs as when it boots the kernel, but stops before
202 To boot the Linux kernel from the SPL, the DT blob (fdt) needs to get
204 the DT binary (blob), e.g. autodetected memory size, MAC addresses,
205 clocks speeds etc. To generate this patched DT blob, you can use
214 3. Use "fdt" commands to patch the DT blob:
219 4. Display patched DT blob (optional):
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/ |
| H A D | s5p-mfc.txt | 40 SoC specific DT entry:
51 Reserved memory specific DT entry for given board (see reserved memory binding
72 Board specific DT entry:
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pwm/ |
| H A D | nvidia,tegra20-pwm.txt | 28 DT node as detailed in the pinctrl DT binding document
52 Following will be DT binding to achieve this:
|
| /OK3568_Linux_fs/kernel/Documentation/mips/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/cpufreq/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/thermal/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/xilinx/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sound/ |
| H A D | qcom,msm8916-wcd-analog.txt | 30 - vdd-cdc-io-supply: phandle to VDD_CDC_IO regulator DT node.
31 - vdd-cdc-tx-rx-cx-supply: phandle to VDD_CDC_TX/RX/CX regulator DT node.
32 - vdd-micbias-supply: phandle of VDD_MICBIAS supply's regulator DT node.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-multimedia/recipes-multimedia/dvb-apps/files/dvb-scan-table/dvb-t/ |
| H A D | gr-Athens | 33 [DT DIGITAL 01]
46 [DT DIGITAL 02]
|
| /OK3568_Linux_fs/u-boot/arch/arm/cpu/armv7/ls102xa/ |
| H A D | Kconfig | 24 string "PCIe compatible of Kernel DT"
28 This compatible is used to find pci controller node in Kernel DT
|