qcom.txt 1.4 KB

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