1 # SPDX-License-Identifier: GPL-2.0
4 $id: http://devicetree.org/schemas/bindings/arm/qcom.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: QCOM device tree bindings
10 - Stephen Boyd <sboyd@codeaurora.org>
13 Some qcom based bootloaders identify the dtb blob based on a set of
14 device properties like SoC and platform and revisions of those components.
15 To support this scheme, we encode this information into the board compatible
18 Each board must specify a top-level board compatible string with the following
21 compatible = "qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<board_version>]"
23 The 'SoC' and 'board' elements are required. All other elements are optional.
25 The 'SoC' element must be one of the following strings:
40 The 'board' element must be one of the following strings:
49 The 'soc_version' and 'board_version' elements take the form of v<Major>.<Minor>
50 where the minor number may be omitted when it's zero, i.e. v1.0 is the same
51 as v1. If all versions of the 'board_version' elements match, then a
52 wildcard '*' should be used, e.g. 'v*'.
54 The 'foundry_id' and 'subtype' elements are one or more digits from 0 to 9.
58 "qcom,msm8916-v1-cdp-pm8916-v2.1"
60 A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of version
63 "qcom,apq8074-v2.0-2-dragonboard/1-v0.1"
65 A dragonboard board v0.1 of subtype 1 with an apq8074 SoC version 2, made in
78 - qcom,apq8064-cm-qs600
79 - qcom,apq8064-ifc6410
84 - qcom,apq8074-dragonboard
89 - qcom,apq8060-dragonboard
102 - const: qcom,msm8960
105 - const: qcom,msm8916-mtp/1
106 - const: qcom,msm8916-mtp
107 - const: qcom,msm8916
110 - const: qcom,msm8996-mtp
113 - const: qcom,ipq4019
118 - const: qcom,ipq8064
123 - const: qcom,ipq8074