1QCOM device tree bindings
2-------------------------
3
4Some qcom based bootloaders identify the dtb blob based on a set of
5device properties like SoC and platform and revisions of those components.
6To support this scheme, we encode this information into the board compatible
7string.
8
9Each board must specify a top-level board compatible string with the following
10format:
11
12	compatible = "qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<board_version>]"
13
14The 'SoC' and 'board' elements are required. All other elements are optional.
15
16The 'SoC' element must be one of the following strings:
17
18	apq8016
19	apq8074
20	apq8084
21	apq8096
22	msm8916
23	msm8974
24	msm8992
25	msm8994
26	msm8996
27	mdm9615
28	ipq8074
29	sdm845
30
31The 'board' element must be one of the following strings:
32
33	cdp
34	liquid
35	dragonboard
36	mtp
37	sbc
38	hk01
39
40The 'soc_version' and 'board_version' elements take the form of v<Major>.<Minor>
41where the minor number may be omitted when it's zero, i.e.  v1.0 is the same
42as v1. If all versions of the 'board_version' elements match, then a
43wildcard '*' should be used, e.g. 'v*'.
44
45The 'foundry_id' and 'subtype' elements are one or more digits from 0 to 9.
46
47Examples:
48
49	"qcom,msm8916-v1-cdp-pm8916-v2.1"
50
51A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of version
522.1.
53
54	"qcom,apq8074-v2.0-2-dragonboard/1-v0.1"
55
56A dragonboard board v0.1 of subtype 1 with an apq8074 SoC version 2, made in
57foundry 2.
58