From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 4/7] Tegra30: Add common CPU (shared) files
Date: Wed, 05 Dec 2012 13:37:27 -0700 [thread overview]
Message-ID: <50BFB087.5010402@wwwdotorg.org> (raw)
In-Reply-To: <1354578322-1834-5-git-send-email-twarren@nvidia.com>
On 12/03/2012 04:45 PM, Tom Warren wrote:
> These files are used by both SPL and main U-Boot.
> Also made minor changes to shared Tegra code to support
> T30 differences.
> diff --git a/arch/arm/cpu/tegra-common/ap.c b/arch/arm/cpu/tegra-common/ap.c
> + case CHIPID_TEGRA30:
> + switch (tegra_sku_id) {
> + case SKU_ID_T30:
> + /*
> + * T30 has two options. We will return TEGRA_SOC_T30
> + * until we have the fdt set up when it may change to
> + * TEGRA_SOC_T30_408MHZ depending on the PLLP freq.
> + */
> + if (clock_get_rate(CLOCK_ID_PERIPH) == 408000000)
> + return TEGRA_SOC_T30_408MHZ;
> + else
> + return TEGRA_SOC_T30;
Just for completeness, I'm going to mention again that I think this
should just return TEGRA_SOC_T30 all the time. Sorry if that's
belaboring the point!
I just noticed your recent email saying you got 408MHz working, so I
guess my comment is moot anyway:-)
> diff --git a/arch/arm/cpu/tegra-common/sys_info.c b/arch/arm/cpu/tegra-common/sys_info.c
> /* Print CPU information */
> int print_cpuinfo(void)
> {
> +#if defined(CONFIG_TEGRA20)
> puts("TEGRA20\n");
> -
> +#else /* Tegra30 */
> + puts("TEGRA30\n");
> +#endif
This is fine, but the following wouldn't require editing again for
future chips:
puts(CONFIG_SYS_SOC);
puts("\n");
(although it ends up being all lower-case; perhaps there's some other
variable that is upper-case?)
next prev parent reply other threads:[~2012-12-05 20:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 23:45 [U-Boot] [PATCH v2 0/7] Add support for NVIDIA Tegra30 SoC Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 1/7] Tegra30: Add arch-tegra30 include files Tom Warren
2012-12-04 0:22 ` Stephen Warren
2012-12-04 17:42 ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 2/7] Tegra30: Add AVP (arm720t) files Tom Warren
2012-12-04 0:34 ` Stephen Warren
2012-12-04 17:47 ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 3/7] Tegra30: Add CPU (armv7) files Tom Warren
2012-12-04 0:36 ` Stephen Warren
2012-12-03 23:45 ` [U-Boot] [PATCH V2 4/7] Tegra30: Add common CPU (shared) files Tom Warren
2012-12-05 20:37 ` Stephen Warren [this message]
2012-12-05 21:32 ` Tom Warren
2012-12-05 21:38 ` Stephen Warren
2012-12-05 21:43 ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 5/7] Tegra30: Cardhu: Add DT files Tom Warren
2012-12-04 0:40 ` Stephen Warren
2012-12-04 0:49 ` Simon Glass
2012-12-04 0:57 ` Stephen Warren
2012-12-04 1:01 ` Simon Glass
2012-12-04 20:29 ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 6/7] Tegra30: Add generic Tegra30 build support Tom Warren
2012-12-04 0:42 ` Stephen Warren
2012-12-04 19:48 ` Tom Warren
2012-12-03 23:45 ` [U-Boot] [PATCH v2 7/7] Tegra30: Add/enable Cardhu build (T30 reference board) Tom Warren
2012-12-04 0:53 ` Stephen Warren
2012-12-04 20:22 ` Tom Warren
2012-12-04 20:40 ` Lucas Stach
2012-12-04 21:28 ` Tom Warren
2012-12-04 22:41 ` Stephen Warren
2012-12-08 20:00 ` Simon Glass
2012-12-10 17:05 ` Tom Warren
2012-12-10 19:04 ` Simon Glass
2012-12-04 22:43 ` Stephen Warren
2012-12-05 20:30 ` Tom Warren
2012-12-04 0:07 ` [U-Boot] [PATCH v2 0/7] Add support for NVIDIA Tegra30 SoC Stephen Warren
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=50BFB087.5010402@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox