All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: omap3:  Update cpuinfo for DM3730, DM3725, AM3715, and AM3703
Date: Thu, 19 Jan 2017 14:04:11 -0600	[thread overview]
Message-ID: <1484856251-7442-1-git-send-email-aford173@gmail.com> (raw)

The check for OMAP3630/3730 only checks for 800MHz 3630/3730, but
anything else is lumped into 36XX/37XX with an assumed 1GHz speed.

Based on the DM3730 TRM bit 9 shows the MPU Frequency (800MHz/1GHZ).
This also adds the ability to distinguish between the DM3730, DM3725,
AM3715, and AM3703 and correctly display their maximum speed.

Signed-off-by: Adam Ford <aford173@gmail.com>

diff --git a/arch/arm/include/asm/arch-omap3/omap.h b/arch/arm/include/asm/arch-omap3/omap.h
index 417ff89..a70a426 100644
--- a/arch/arm/include/asm/arch-omap3/omap.h
+++ b/arch/arm/include/asm/arch-omap3/omap.h
@@ -230,6 +230,14 @@ struct gpio {
 #define AM3517			0x1c00
 
 #define OMAP3730		0x0c00
+#define OMAP3725		0x4c00
+#define AM3715			0x1c00
+#define AM3703			0x5c00
+
+#define OMAP3730_1GHZ	0x0e00
+#define OMAP3725_1GHZ	0x4e00
+#define AM3715_1GHZ		0x1e00
+#define AM3703_1GHZ		0x5e00
 
 /*
  * ROM code API related flags
diff --git a/arch/arm/mach-omap2/omap3/sys_info.c b/arch/arm/mach-omap2/omap3/sys_info.c
index 6818fab..99c9120 100644
--- a/arch/arm/mach-omap2/omap3/sys_info.c
+++ b/arch/arm/mach-omap2/omap3/sys_info.c
@@ -295,16 +295,54 @@ int print_cpuinfo (void)
 		max_clk = "600 Mhz";
 		break;
 	case CPU_OMAP36XX:
-		cpu_family_s = "OMAP";
 		switch (get_cpu_type()) {
+		case AM3703:
+			cpu_family_s = "AM";
+			cpu_s = "3703";
+			max_clk = "800 MHz";
+			break;
+		case AM3703_1GHZ:
+			cpu_family_s = "AM";
+			cpu_s = "3703";
+			max_clk = "1 GHz";
+			break;
+		case AM3715:
+			cpu_family_s = "AM";
+			cpu_s = "3715";
+			max_clk = "800 MHz";
+			break;
+		case AM3715_1GHZ:
+			cpu_family_s = "AM";
+			cpu_s = "3715";
+			max_clk = "1 GHz";
+			break;
+		case OMAP3725:
+			cpu_family_s = "OMAP";
+			cpu_s = "3625/3725";
+			max_clk = "800 MHz";
+			break;
+		case OMAP3725_1GHZ:
+			cpu_family_s = "OMAP";
+			cpu_s = "3625/3725";
+			max_clk = "1 GHz";
+			break;
 		case OMAP3730:
+			cpu_family_s = "OMAP";
 			cpu_s = "3630/3730";
+			max_clk = "800 MHz";
+			break;
+		case OMAP3730_1GHZ:
+			cpu_family_s = "OMAP";
+			cpu_s = "3630/3730";
+			max_clk = "1 GHz";
 			break;
 		default:
+			cpu_family_s = "OMAP/AM";
 			cpu_s = "36XX/37XX";
+			max_clk = "1 GHz";
 			break;
 		}
-		max_clk = "1 Ghz";
+
 		break;
 	default:
 		cpu_family_s = "OMAP";
-- 
2.7.4

             reply	other threads:[~2017-01-19 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 20:04 Adam Ford [this message]
     [not found] ` <20170120103225.bpnlifuf3pzwwrsf@lenoch>
2017-01-20 11:23   ` [U-Boot] [PATCH] arm: omap3: Update cpuinfo for DM3730, DM3725, AM3715, and AM3703 Adam Ford
2017-01-20 13:03     ` [U-Boot] [PATCH 1/2] arm: omap3: Fix cpuinfo frequency spelling Ladislav Michl
2017-01-28 22:44       ` [U-Boot] [U-Boot, " Tom Rini
2017-01-20 13:03     ` [U-Boot] [PATCH v2 2/2] arm: omap3: Update cpuinfo for DM3730, DM3725, AM3715, and AM3703 Ladislav Michl
2017-01-28 22:44       ` [U-Boot] [U-Boot, v2, " Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1484856251-7442-1-git-send-email-aford173@gmail.com \
    --to=aford173@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.