aboutsummaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/arm/msm/ids.txt
blob: 9ee8428f4670e20e579fbe6a98dd86c1c9c2b919 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
* MSM-ID

The qcom,msm-id entry specifies the MSM chipset and hardware revision.  It can
optionally be an array of these to indicate multiple hardware that use the same
device tree.  It is expected that the bootloader will use this information at
boot-up to decide which device tree to use when given multiple device trees,
some of which may not be compatible with the actual hardware.  It is the
bootloader's responsibility to pass the correct device tree to the kernel.

PROPERTIES

- qcom,msm-id:
	Usage: required
	Value type: <prop-encoded-array> (<chipset_id, rev_id> [, <c2, r2> ..])
	Definition:
		The "chipset_id" consists of three fields as below:

		bits 0-15  = The unique MSM chipset id.
		bits 16-31 = Reserved.  Should be 0

		chipset_id is an exact match value

		The "rev_id" is a chipset specific 32-bit id that represents
		the version of the chipset.

		The rev_id is a best match id.  The bootloader will look for
		the closest possible patch.

* BOARD-ID

The qcom,board-id entry specifies the board type and revision information.  It
can optionally be an array of these to indicate multiple boards that use the
same device tree.  It is expected that the bootloader will use this information
at boot-up to decide which device tree to use when given multiple device trees,
some of which may not be compatible with the actual hardware.  It is the
bootloader's responsibility to pass the correct device tree to the kernel.

PROPERTIES

- qcom,board-id:
	Usage: required
	Value type: <prop-encoded-array> (<board_id, subtype_id> [, <b2, s2> ..])
	Definition:
		The "board_id" consists of three fields as below:

		bits 31-24 = Unusued.
		bits 23-16 = Platform Version Major
		bits 15-8  = Platfrom Version Minor
		bits 7-0   = Platform Type

		Platform Type field is an exact match value.  The Platform
		Major/Minor field is a best match.  The bootloader will look
		for the closest possible match.

		The "subtype_id" is unique to a Platform Type/Chipset ID.  For
		a given Platform Type, there will typically only be a single
		board and the subtype_id will be 0.  However in some cases board
		variants may need to be distinquished by different subtype_id
		values.

		subtype_id is an exact match value.

EXAMPLE:
	qcom,board-id = <15 2>;
	qcom,msm-id = <0x1007e 0>;