soc: qcom: Add SoC info driver

The SoC info driver provides information such as Chip ID, Chip family, serial number and other such details about Qualcomm SoCs.

Signed-off-by Imran Khan <[email protected]>

+++ b/drivers/soc/qcom/socinfo.c

drivers/soc/qcom/socinfo.c new file +34 -0

+/*
+ * Qcom SoC IDs
+ */
+enum qcom_cpu_id {
+       MSM_UNKNOWN_ID,
+       MSM_8960_ID = 87,
+       APQ_8064_ID = 109,
+       MSM_8660A_ID = 122,
+       MSM_8260A_ID,
+       APQ_8060A_ID,
+       MSM_8974_ID = 126,
+       MPQ_8064_ID = 130,
+       MSM_8960AB_ID = 138,
+       APQ_8060AB_ID,
+       MSM_8260AB_ID,
+       MSM_8660AB_ID,
+       APQ_8084_ID = 178,
+       APQ_8074_ID = 184,
+       MSM_8274_ID,
+       MSM_8674_ID,
+       MSM_8974PRO_ID = 194,
+       MSM_8916_ID = 206,
+       APQ_8074_AA_ID = 208,
+       APQ_8074_AB_ID,
+       APQ_8074PRO_ID,
+       MSM_8274_AA_ID,
+       MSM_8274_AB_ID,
+       MSM_8274PRO_ID,
+       MSM_8674_AA_ID,
+       MSM_8674_AB_ID,
+       MSM_8674PRO_ID,
+       MSM_8974_AA_ID,
+       MSM_8974_AB_ID,
+       MSM_8996_ID = 246,

+#ifdef CONFIG_SOC_BUS

drivers/soc/qcom/socinfo.c new file +8 -0

+int qcom_socinfo_init(void *info)
+{
+       socinfo = info;
+
+       socinfo_select_format();
+
+       WARN(!socinfo_get_id(), "Unknown SOC ID!\n");
+

Quoted 5 lines · Imran Khan

The SoC info driver provides information such as Chip ID, Chip family, serial number and other such details about Qualcomm SoCs.

Signed-off-by Imran Khan <[email protected]>

I like this patch. It is good to know stuff about the hardware.

(...)

Quoted 1 line

+++ b/drivers/soc/qcom/socinfo.c

(...)

drivers/soc/qcom/socinfo.c line 27

Quoted 6 lines

drivers/soc/qcom/socinfo.c new file +6 -0

+#include <linux/export.h>
+#include <linux/module.h>
+#include <linux/err.h>
+#include <linux/of.h>
+#include <linux/platform_device.h>
+#include <linux/sys_soc.h>

Uses <linux/sys_soc.h> so you should definately get Lee Jones to review this.

Quoted 34 lines

drivers/soc/qcom/socinfo.c new file +34 -0

+/*
+ * Qcom SoC IDs
+ */
+enum qcom_cpu_id {
+       MSM_UNKNOWN_ID,
+       MSM_8960_ID = 87,
+       APQ_8064_ID = 109,
+       MSM_8660A_ID = 122,
+       MSM_8260A_ID,
+       APQ_8060A_ID,
+       MSM_8974_ID = 126,
+       MPQ_8064_ID = 130,
+       MSM_8960AB_ID = 138,
+       APQ_8060AB_ID,
+       MSM_8260AB_ID,
+       MSM_8660AB_ID,
+       APQ_8084_ID = 178,
+       APQ_8074_ID = 184,
+       MSM_8274_ID,
+       MSM_8674_ID,
+       MSM_8974PRO_ID = 194,
+       MSM_8916_ID = 206,
+       APQ_8074_AA_ID = 208,
+       APQ_8074_AB_ID,
+       APQ_8074PRO_ID,
+       MSM_8274_AA_ID,
+       MSM_8274_AB_ID,
+       MSM_8274PRO_ID,
+       MSM_8674_AA_ID,
+       MSM_8674_AB_ID,
+       MSM_8674PRO_ID,
+       MSM_8974_AA_ID,
+       MSM_8974_AB_ID,
+       MSM_8996_ID = 246,

drivers/soc/qcom/socinfo.c line 126

Quoted 10 lines

drivers/soc/qcom/socinfo.c new file +10 -0

+       APQ_8016_ID,
+       MSM_8216_ID,
+       MSM_8116_ID,
+       MSM_8616_ID,
+       APQ8096_ID = 291,
+       MSM_8996SG_ID = 305,
+       MSM_8996AU_ID = 310,
+       APQ_8096AU_ID,
+       APQ_8096SG_ID
+};

Seems to support everything and its dog. Good job!

Now I guess I first have to support smem on my pet peeves (MSM8660 and APQ8060) for this to work.

drivers/soc/qcom/socinfo.c line 161

Quoted 12 lines

drivers/soc/qcom/socinfo.c new file +12 -0

+enum hw_platform_type {
+       HW_PLATFORM_UNKNOWN,
+       HW_PLATFORM_SURF,
+       HW_PLATFORM_FFA,
+       HW_PLATFORM_FLUID,
+       HW_PLATFORM_SVLTE_FFA,
+       HW_PLATFORM_SVLTE_SURF,
+       HW_PLATFORM_MTP_MDM = 7,
+       HW_PLATFORM_MTP,
+       HW_PLATFORM_LIQUID,
+       /* Dragonboard platform id is assigned as 10 in CDT */
+       HW_PLATFORM_DRAGON,

I guess that is not "my" dragonboard generation 1 with the APQ8060 but rather the APQ8074 Dragonboard?

Is mine just a variant of SURF then... I dunno. Will be interesting to see what number it has in its hardware.

Quoted 1 line

+#ifdef CONFIG_SOC_BUS

Why not just select that in Kconfig and get rid of this #ifdef?

Quoted 8 lines

drivers/soc/qcom/socinfo.c new file +8 -0

+int qcom_socinfo_init(void *info)
+{
+       socinfo = info;
+
+       socinfo_select_format();
+
+       WARN(!socinfo_get_id(), "Unknown SOC ID!\n");
+

drivers/soc/qcom/socinfo.c line 1223

Quoted 10 lines

drivers/soc/qcom/socinfo.c new file +10 -0

+       WARN(socinfo_get_id() >= ARRAY_SIZE(cpu_of_id),
+               "New IDs added! ID => CPU mapping needs an update.\n");
+
+       socinfo_print();
+
+       socinfo_init_sysfs();
+
+       return 0;
+}
+EXPORT_SYMBOL(qcom_socinfo_init);

So something I've been adding to drivers that handle any kind of device-unique numbers is:

#include <linux/random.h>

/* Toss the unique data into the entropy pool */
add_device_randomness(buf, sizeof(buf));

Can you do this here in init() with the register that are *device unique* because I guess not all of them are?

Yours,
Linus Walleij