| /Linux-v5.4/crypto/ |
| D | ansi_cprng.c | 42 unsigned char DT[DEFAULT_BLK_SZ]; member
90 hexdump("Input DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
105 memcpy(tmp, ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
163 ctx->DT[i] += 1; in _get_more_prng_bytes()
164 if (ctx->DT[i] != 0) in _get_more_prng_bytes()
171 hexdump("Output DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
277 const unsigned char *V, const unsigned char *DT) in reset_prng_context() argument
295 if (DT) in reset_prng_context()
296 memcpy(ctx->DT, DT, DEFAULT_BLK_SZ); in reset_prng_context()
298 memset(ctx->DT, 0, DEFAULT_BLK_SZ); in reset_prng_context()
|
| /Linux-v5.4/Documentation/devicetree/ |
| 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 …]
|
| D | usage-model.txt | 13 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
41 The DT was originally created by Open Firmware as part of the
53 and 64-bit support, the decision was made to require DT support on all
55 Firmware. To do this, a DT representation called the Flattened Device
59 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
62 existing non-DT aware firmware.
67 out of mainline (nios) have some level of DT support.
76 The most important thing to understand is that the DT is simply a data
90 Linux uses DT data for three major purposes:
[all …]
|
| D | changesets.txt | 1 A DT changeset is a method which allows one to apply changes
17 2. A number of DT tree change calls, of_changeset_attach_node(),
|
| /Linux-v5.4/drivers/staging/board/ |
| D | TODO | 1 * replace platform device code with DT nodes once the driver supports DT
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/net/nfc/ |
| 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.
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 2 Submitting devicetree (DT) binding patches
22 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
23 all of the DT maintainers.
29 previously documented in the corresponding DT binding text file
34 ("checkpatch: add DT compatible string documentation checks"). ]
|
| /Linux-v5.4/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
|
| D | samsung,exynos5440-pcie.txt | 23 SoC-specific DT Entry (with using PHY framework):
50 Board-specific DT Entry:
|
| /Linux-v5.4/Documentation/arm64/ |
| 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 …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| 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:
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | generic.txt | 7 via DT, USB controllers should default to their maximum
12 passed via DT, USB DRD controllers should default to
17 In case this isn't passed via DT, USB controllers should
|
| /Linux-v5.4/Documentation/devicetree/bindings/pwm/ |
| D | nvidia,tegra20-pwm.txt | 27 DT node as detailed in the pinctrl DT binding document
51 Following will be DT binding to achieve this:
|
| /Linux-v5.4/drivers/staging/comedi/drivers/ |
| D | dt3000.c | 721 { PCI_VDEVICE(DT, 0x0022), BOARD_DT3001 },
722 { PCI_VDEVICE(DT, 0x0023), BOARD_DT3002 },
723 { PCI_VDEVICE(DT, 0x0024), BOARD_DT3003 },
724 { PCI_VDEVICE(DT, 0x0025), BOARD_DT3004 },
725 { PCI_VDEVICE(DT, 0x0026), BOARD_DT3005 },
726 { PCI_VDEVICE(DT, 0x0027), BOARD_DT3001_PGL },
727 { PCI_VDEVICE(DT, 0x0028), BOARD_DT3003_PGL },
|
| /Linux-v5.4/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-v5.4/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-v5.4/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
|
| D | cpufreq-st.txt | 7 the DT and operate in the usual way.
9 For more information about the expected DT format [See: ../opp/opp.txt].
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | cs4271.txt | 1 Cirrus Logic CS4271 DT bindings
30 in the MODE2 register. This workaround can be enabled with this DT
|
| 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.
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/sifive/ |
| D | fu540-prci.txt | 26 /* under /, in PCB-specific DT data */
40 /* under /soc, in SoC-specific DT data */
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos7-decon.txt | 42 SoC specific DT entry:
59 Board specific DT entry:
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | serial.txt | 1 Generic Serial DT Bindings
5 the DT bindings for the actual device.
|
