| /kernel/linux/linux-5.10/scripts/dtc/ |
| D | livetree.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
19 if (streq(new->label, label)) { in add_label()
20 new->deleted = 0; in add_label()
26 new->label = label; in add_label()
27 new->next = *labels; in add_label()
36 label->deleted = 1; in delete_labels()
39 struct property *build_property(char *name, struct data val, in build_property()
42 struct property *new = xmalloc(sizeof(*new)); in build_property()
46 new->name = name; in build_property()
47 new->val = val; in build_property()
[all …]
|
| D | checks.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
12 fprintf(stderr, "=== %s: ", (c)->name); \
63 struct property *prop, in check_msg()
71 if (!(c->warn && (quiet < 1)) && !(c->error && (quiet < 2))) in check_msg()
74 if (prop && prop->srcpos) in check_msg()
75 pos = prop->srcpos; in check_msg()
76 else if (node && node->srcpos) in check_msg()
77 pos = node->srcpos; in check_msg()
83 } else if (streq(dti->outname, "-")) { in check_msg()
86 xasprintf(&str, "%s", dti->outname); in check_msg()
[all …]
|
| /kernel/linux/linux-6.6/scripts/dtc/ |
| D | livetree.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
19 if (streq(new->label, label)) { in add_label()
20 new->deleted = 0; in add_label()
26 new->label = label; in add_label()
27 new->next = *labels; in add_label()
36 label->deleted = 1; in delete_labels()
39 struct property *build_property(char *name, struct data val, in build_property()
42 struct property *new = xmalloc(sizeof(*new)); in build_property()
46 new->name = name; in build_property()
47 new->val = val; in build_property()
[all …]
|
| D | checks.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
12 fprintf(stderr, "=== %s: ", (c)->name); \
63 struct property *prop, in check_msg()
71 if (!(c->warn && (quiet < 1)) && !(c->error && (quiet < 2))) in check_msg()
74 if (prop && prop->srcpos) in check_msg()
75 pos = prop->srcpos; in check_msg()
76 else if (node && node->srcpos) in check_msg()
77 pos = node->srcpos; in check_msg()
83 } else if (streq(dti->outname, "-")) { in check_msg()
86 xasprintf(&str, "%s", dti->outname); in check_msg()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/ |
| D | writing-schema.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Writing DeviceTree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
12 ---------------
14 Each schema doc is a structured json-schema which is defined by a set of
15 top-level properties. Generally, there is one binding defined per file. The
16 top-level json-schema properties used are:
19 A json-schema unique identifier string. The string must be a valid
20 URI typically containing the binding's filename and path. For DT schema, it must
29 Indicates the meta-schema the schema file adheres to.
[all …]
|
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
34 maximize use of existing support code, but since property and node
44 ----------
45 The DT was originally created by Open Firmware as part of the
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
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
61 blob without requiring a real Open Firmware implementation. U-Boot,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ |
| D | writing-schema.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
11 Also see :ref:`example-schema`.
14 ---------------
16 Each schema doc is a structured json-schema which is defined by a set of
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
21 A json-schema unique identifier string. The string must be a valid
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
25 led-sources:
30 $ref: /schemas/types.yaml#/definitions/uint32-array
35 from the header include/dt-bindings/leds/common.h. If there is no
42 the header include/dt-bindings/leds/common.h. If there is no matching
48 function-enumerator:
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ |
| D | drm_of.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 #include <linux/media-bus-format.h>
20 * A set of helper functions to aid DRM drivers in parsing standard DT
25 * drm_of_crtc_port_mask - find the mask of a registered CRTC by port OF node
39 if (tmp->port == port) in drm_of_crtc_port_mask()
50 * drm_of_find_possible_crtcs - find the possible CRTCs for an encoder port
83 * drm_of_component_match_add - Add a component helper OF node match rule
101 * drm_of_component_probe - Generic probe function for a component based master
121 if (!dev->of_node) in drm_of_component_probe()
122 return -EINVAL; in drm_of_component_probe()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/ |
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
34 maximize use of existing support code, but since property and node
44 ----------
45 The DT was originally created by Open Firmware as part of the
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
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
61 blob without requiring a real Open Firmware implementation. U-Boot,
[all …]
|
| /kernel/linux/linux-6.6/drivers/video/ |
| D | of_display_timing.c | 1 // SPDX-License-Identifier: GPL-2.0-only
16 * parse_timing_property - parse timing_entry from device_node
17 * @np: device_node with the property
18 * @name: name of the property
28 struct property *prop; in parse_timing_property()
33 pr_err("%pOF: could not find property %s\n", np, name); in parse_timing_property()
34 return -EINVAL; in parse_timing_property()
39 ret = of_property_read_u32(np, name, &result->typ); in parse_timing_property()
40 result->min = result->typ; in parse_timing_property()
41 result->max = result->typ; in parse_timing_property()
[all …]
|
| /kernel/linux/linux-5.10/drivers/video/ |
| D | of_display_timing.c | 1 // SPDX-License-Identifier: GPL-2.0-only
16 * parse_timing_property - parse timing_entry from device_node
17 * @np: device_node with the property
18 * @name: name of the property
28 struct property *prop; in parse_timing_property()
33 pr_err("%pOF: could not find property %s\n", np, name); in parse_timing_property()
34 return -EINVAL; in parse_timing_property()
39 ret = of_property_read_u32(np, name, &result->typ); in parse_timing_property()
40 result->min = result->typ; in parse_timing_property()
41 result->max = result->typ; in parse_timing_property()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/ |
| D | marvell,xenon-sdhci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mmc/marvell,xenon-sdhci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 mmc-controller.yaml and the properties used by the Xenon implementation.
20 - Ulf Hansson <ulf.hansson@linaro.org>
25 - enum:
26 - marvell,armada-cp110-sdhci
27 - marvell,armada-ap806-sdhci
29 - items:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | arm-acpi.rst | 22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
40 while DT explicitly does not support this. For hardware vendors, being
44 - ACPI’s OSPM defines a power management model that constrains what the
48 - In the enterprise server environment, ACPI has established bindings (such
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
25 led-sources:
30 $ref: /schemas/types.yaml#definitions/uint32-array
35 from the header include/dt-bindings/leds/common.h. If there is no
42 the header include/dt-bindings/leds/common.h. If there is no matching
48 function-enumerator:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra186-bpmp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/nvidia,tegra186-bpmp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
25 - .../mailbox/mailbox.txt
26 - .../mailbox/nvidia,tegra186-hsp.yaml
32 - .../clock/clock-bindings.txt
33 - <dt-bindings/clock/tegra186-clock.h>
[all …]
|
| /kernel/linux/linux-6.6/arch/powerpc/include/asm/ |
| D | prom.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
10 * Copyright (C) 1996-2005 Paul Mackerras.
18 struct property;
22 #define OF_DT_PROP 0x3 /* Property: name off, size,
32 * The dt struct contains the device tree structure, full pathes and
33 * property contents. The dt strings contain a separate block with just
34 * the strings for the property names, and is fully page aligned and
36 * each property name appears only once in this page (cheap compression)
39 * passing it here instead of in the device-tree itself greatly simplifies
45 __be32 totalsize; /* total size of DT block */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/ |
| D | ti-pci.txt | 4 - compatible: Should be "ti,dra7-pcie" for RC (deprecated)
5 Should be "ti,dra7-pcie-ep" for EP (deprecated)
6 Should be "ti,dra746-pcie-rc" for dra74x/dra76 in RC mode
7 Should be "ti,dra746-pcie-ep" for dra74x/dra76 in EP mode
8 Should be "ti,dra726-pcie-rc" for dra72x in RC mode
9 Should be "ti,dra726-pcie-ep" for dra72x in EP mode
10 - phys : list of PHY specifiers (used by generic PHY framework)
11 - phy-names : must be "pcie-phy0", "pcie-phy1", "pcie-phyN".. based on the
12 number of PHYs as specified in *phys* property.
13 - ti,hwmods : Name of the hwmod associated to the pcie, "pcie<X>",
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | ti-pci.txt | 4 - compatible: Should be "ti,dra7-pcie" for RC (deprecated)
5 Should be "ti,dra7-pcie-ep" for EP (deprecated)
6 Should be "ti,dra746-pcie-rc" for dra74x/dra76 in RC mode
7 Should be "ti,dra746-pcie-ep" for dra74x/dra76 in EP mode
8 Should be "ti,dra726-pcie-rc" for dra72x in RC mode
9 Should be "ti,dra726-pcie-ep" for dra72x in EP mode
10 - phys : list of PHY specifiers (used by generic PHY framework)
11 - phy-names : must be "pcie-phy0", "pcie-phy1", "pcie-phyN".. based on the
12 number of PHYs as specified in *phys* property.
13 - ti,hwmods : Name of the hwmod associated to the pcie, "pcie<X>",
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/include/asm/ |
| D | prom.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
10 * Copyright (C) 1996-2005 Paul Mackerras.
27 #define OF_DT_PROP 0x3 /* Property: name off, size,
37 * The dt struct contains the device tree structure, full pathes and
38 * property contents. The dt strings contain a separate block with just
39 * the strings for the property names, and is fully page aligned and
41 * each property name appears only once in this page (cheap compression)
44 * passing it here instead of in the device-tree itself greatly simplifies
50 __be32 totalsize; /* total size of DT block */
59 __be32 dt_strings_size; /* size of the DT strings block */
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/st/ |
| D | stm32mp135f-dk.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
3 * Copyright (C) STMicroelectronics 2021 - All Rights Reserved
7 /dts-v1/;
9 #include <dt-bindings/gpio/gpio.h>
10 #include <dt-bindings/input/input.h>
11 #include <dt-bindings/leds/common.h>
12 #include <dt-bindings/regulator/st,stm32mp13-regulator.h>
15 #include "stm32mp13-pinctrl.dtsi"
18 model = "STMicroelectronics STM32MP135F-DK Discovery Board";
19 compatible = "st,stm32mp135f-dk", "st,stm32mp135";
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | example-schema.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 # All the top-level keys are standard json-schema keywords except for
10 $id: http://devicetree.org/schemas/example-schema.yaml#
11 # $schema is the meta-schema this schema should be validated with.
12 $schema: http://devicetree.org/meta-schemas/core.yaml#
17 - Rob Herring <robh@kernel.org>
20 A more detailed multi-line description of the binding.
29 # 'select' is a schema applied to a DT node to determine if this binding
36 # A dictionary of DT properties for this binding schema
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | arm-acpi.rst | 23 industry-standard Arm systems, they also apply to more than one operating
25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of
30 ----------------
33 exist in Linux for describing non-enumerable hardware, after all. In this
40 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
41 while DT explicitly does not support this. For hardware vendors, being
45 - ACPI’s OSPM defines a power management model that constrains what the
49 - In the enterprise server environment, ACPI has established bindings (such
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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/ |
| D | adi,adp5588.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nuno Sá <nuno.sa@analog.com>
14 https://www.analog.com/media/en/technical-documentation/data-sheets/ADP5588.pdf
17 - $ref: matrix-keymap.yaml#
18 - $ref: input.yaml#
23 - adi,adp5587
24 - adi,adp5588
29 vcc-supply:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/adc/ |
| D | qcom,spmi-vadc.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/qcom,spmi-vadc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
15 voltage. The VADC is a 15-bit sigma-delta ADC.
17 voltage. The VADC is a 16-bit sigma-delta ADC.
22 - items:
23 - const: qcom,pms405-adc
[all …]
|