Re: [PATCH RFC 25/27] devicetree: bindings: Document qcom,msm-id and qcom,board-id

2015-11-19 Thread Lina Iyer 

On Thu, Nov 19 2015 at 07:37 -0700, Rob Herring wrote:

On Tue, Nov 17, 2015 at 4:37 PM, Lina Iyer  wrote:

From: Kumar Gala 

The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.


See [1] and the link there to the prior version which is like this one.


Thanks Rob. Andy Gross sent me that link and I am waiting on the changes
along with the dtb tool to make it. These patches will go away after
Stephen's changes. I just put it in here for completeness.

Thanks,
Lina


[1] https://lkml.org/lkml/2015/10/26/651

--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH RFC 25/27] devicetree: bindings: Document qcom,msm-id and qcom,board-id

2015-11-19 Thread Rob Herring 
On Tue, Nov 17, 2015 at 4:37 PM, Lina Iyer  wrote:
> From: Kumar Gala 
>
> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
> on Qualcomm MSM platforms to determine which device tree should be
> utilized and passed to the kernel.

See [1] and the link there to the prior version which is like this one.

Rob

[1] https://lkml.org/lkml/2015/10/26/651
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH RFC 25/27] devicetree: bindings: Document qcom,msm-id and qcom,board-id

2015-11-17 Thread Lina Iyer 
From: Kumar Gala 

The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.

Cc: 
Signed-off-by: Kumar Gala 
---
 Documentation/devicetree/bindings/arm/msm/ids.txt | 65 +++
 include/dt-bindings/arm/qcom-ids.h| 33 
 2 files changed, 98 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/msm/ids.txt
 create mode 100644 include/dt-bindings/arm/qcom-ids.h

diff --git a/Documentation/devicetree/bindings/arm/msm/ids.txt 
b/Documentation/devicetree/bindings/arm/msm/ids.txt
new file mode 100644
index 000..9ee8428
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/msm/ids.txt
@@ -0,0 +1,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:  ( [,  ..])
+   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:  ( [,  
..])
+   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>;
diff --git a/include/dt-bindings/arm/qcom-ids.h 
b/include/dt-bindings/arm/qcom-ids.h
new file mode 100644
index 000..a18f34e
--- /dev/null
+++ b/include/dt-bindings/arm/qcom-ids.h
@@ -0,0 +1,33 @@
+/* Copyright (c) 2015, The Linux Foundation. All rights reserved.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 and
+ * only version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ */
+#ifndef __DT_BINDINGS_QCOM_IDS_H
+#define __DT_BINDINGS_QCOM_IDS_H
+
+/* qcom,msm-id */
+#define QCOM_ID_MSM8916206
+#define QCOM_ID_APQ8016247
+#define QCOM_ID_MSM8216248
+#define QCOM_ID_MSM8116249
+#define QCOM_ID_MSM8616250
+
+/* qcom,board-id */
+#define QCOM_BRD_ID(a, major, minor) \
+   (((major & 0xff) << 16) | ((minor & 0xff) << 8) | QCOM_BRD_ID_##a)
+
+#define QCOM_BRD_ID_MTP8
+#define QCOM_BRD_ID_DRAGONBRD  10
+#define QCOM_BRD_ID_SBC24
+
+#define QCOM_BRD_SUBTYPE_DEFAULT   0
+#define QCOM_BRD_SUBTYPE_MTP8916_SMB1360   1
+
+#endif
-- 
2.1.4

--
To unsubscribe from this list: send the line