From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] Tegra114: Add arch-tegra114 include files
Date: Wed, 16 Jan 2013 14:39:33 -0800 [thread overview]
Message-ID: <20130116223933.GA16138@badger> (raw)
In-Reply-To: <1358370848-29469-2-git-send-email-twarren@nvidia.com>
On Wed, Jan 16, 2013 at 01:14:02PM -0800, Tom Warren wrote:
> Common Tegra files are in arch-tegra, shared between T20/T30/T114.
> Tegra114-specific headers are in arch-tegra114. Note that some of
> these will be filled in as more T114 support is added (drivers,
> WB/LP0 support, etc.).
>
> Signed-off-by: Tom Warren <twarren@nvidia.com>
> ---
> +#if defined(CONFIG_TEGRA20)
> #define OSC_FREQ_SHIFT 30
> #define OSC_FREQ_MASK (3U << OSC_FREQ_SHIFT)
> +#else /* Tegra30, Tegra114 */
> +#define OSC_FREQ_SHIFT 28
> +#define OSC_FREQ_MASK (0xF << OSC_FREQ_SHIFT)
> +#endif
Can this be a new define instead of a #ifdef? That makes it easier in
the future to make a single u-boot to boot on all tegras.
> index 953936c..670745f 100644
> --- a/arch/arm/include/asm/arch-tegra/tegra.h
> +++ b/arch/arm/include/asm/arch-tegra/tegra.h
> @@ -73,6 +73,7 @@ enum {
> SKU_ID_AP25E = 0x1b,
> SKU_ID_T25E = 0x1c,
> SKU_ID_T30 = 0x81, /* Cardhu value */
> + SKU_ID_T114 = 0x00, /* Dalmore value */
> };
Is that really the proper SKU id? Or is it just unprogrammed on the
early chips?
> diff --git a/arch/arm/include/asm/arch-tegra114/clock.h b/arch/arm/include/asm/arch-tegra114/clock.h
> new file mode 100644
> index 0000000..9e56f57
> --- /dev/null
> +++ b/arch/arm/include/asm/arch-tegra114/clock.h
> @@ -0,0 +1,24 @@
> +/*
> + * Copyright (c) 2010-2012, NVIDIA CORPORATION. All rights reserved.
2013, here and all new files
-Allen
--
nvpublic
next prev parent reply other threads:[~2013-01-16 22:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 21:14 [U-Boot] [PATCH 0/7] Add support for NVIDIA Tegra114 SoC Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 1/7] Tegra114: Add arch-tegra114 include files Tom Warren
2013-01-16 22:32 ` Stephen Warren
2013-01-17 17:51 ` Tom Warren
2013-01-17 22:23 ` Stephen Warren
2013-01-17 22:56 ` Tom Warren
2013-01-16 22:39 ` Allen Martin [this message]
2013-01-17 17:50 ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 2/7] Tegra114: Add AVP (arm720t) files Tom Warren
2013-01-16 22:42 ` Stephen Warren
2013-01-17 19:15 ` Tom Warren
2013-01-17 22:42 ` Stephen Warren
2013-01-16 23:01 ` Allen Martin
2013-01-17 19:28 ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 3/7] Tegra114: Add CPU (armv7) files Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 4/7] Tegra114: Add common CPU (shared) files Tom Warren
2013-01-16 22:46 ` Stephen Warren
2013-01-17 17:55 ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 5/7] Tegra114: Dalmore: Add DT files Tom Warren
2013-01-16 22:47 ` Stephen Warren
2013-01-17 17:58 ` Tom Warren
2013-01-17 22:25 ` Stephen Warren
2013-01-17 22:58 ` Tom Warren
2013-01-17 23:11 ` Stephen Warren
2013-01-17 23:29 ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 6/7] Tegra114: Add generic Tegra114 build support Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 7/7] Tegra114: Add/enable Dalmore build (T114 reference board) Tom Warren
2013-01-16 22:51 ` Stephen Warren
2013-01-17 18:01 ` Tom Warren
2013-01-21 23:07 ` Simon Glass
2013-01-22 20:47 ` Tom Warren
2013-01-22 20:56 ` Simon Glass
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=20130116223933.GA16138@badger \
--to=amartin@nvidia.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.