From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/8] Tegra124: Add Venice2 (T124) build
Date: Tue, 08 Oct 2013 16:06:02 -0600 [thread overview]
Message-ID: <525481CA.30309@wwwdotorg.org> (raw)
In-Reply-To: <1381185778-25722-8-git-send-email-twarren@nvidia.com>
On 10/07/2013 04:42 PM, Tom Warren wrote:
> These are the board files for Venice2 (t124), plus the AS3722
> PMIC files. PMIC init will be moved to pmic_common_init later.
>
> This builds/boots on Venice2, SPI/MMC/USB/I2C all work. Audio
> and display and WB/LP0 are not supported yet.
> diff --git a/board/nvidia/venice2/venice2.c b/board/nvidia/venice2/venice2.c
> +void board_sdmmc_voltage_init(void)
> +{
> +#if defined(VENICE2_LATE_PMIC_INIT)
> + /*
> + * TODO(twarren at nvidia.com):
> + * Find out why writing the SDMMC LDO this late hangs the CPU
> + * Maybe it's the re-write of the enable bit? (already set by OTP)
> + */
Wouldn't it be better to only include the active code? We can always
just make a patch to move to different code later if we want.
> +Active arm armv7:arm720t tegra124 nvidia venice2 venice2 - Tom Warren <twarren@nvidia.com>
> Active arm armv7:arm720t tegra114 nvidia dalmore dalmore - Tom Warren <twarren@nvidia.com>
That doesn't seem sorted. I would have expected tegra114 before
tegra124? Same if it's sorted by board name.
> diff --git a/include/configs/tegra124-common.h b/include/configs/tegra124-common.h
> +#ifndef _TEGRA124_COMMON_H_
> +#define _TEGRA124_COMMON_H_
> +#include "tegra-common.h"
A blank line is typical after the include guard.
> +#define CONFIG_TEGRA124 /* in a NVidia Tegra124 core */
NVIDIA not NVidia.
> +#define CONFIG_SPL_LDSCRIPT "$(CPUDIR)/tegra124/u-boot-spl.lds"
I don't think that's used upstream. Perhaps diff these files against the
Tegra114 versions and check for unexpected differences?
> diff --git a/include/configs/venice2.h b/include/configs/venice2.h
> +/* Use memory controller SDRAM size instead of ODMDATA */
> +#define CONFIG_TEGRA_USE_EMC_DRAM_SIZE
We should either always do that or never; boards shouldn't make the
decision. Rather, the core Tegra code should make the decision based on
the SoC ID.
Also, CONFIG_TEGRA_USE_EMC_DRAM_SIZE doesn't exist upstream.
> +/* Environment in eMMC, at the end of 2nd "boot sector" */
> +#define CONFIG_ENV_IS_IN_MMC
> +#define CONFIG_SYS_MMC_ENV_DEV 0
> +#define CONFIG_SYS_MMC_ENV_PART 2
> +#define CONFIG_ENV_OFFSET ((4096 * 1024) - CONFIG_ENV_SIZE)
Dalmore says:
#define CONFIG_ENV_OFFSET (-CONFIG_ENV_SIZE)
... which seems a bit more self-managing.
next prev parent reply other threads:[~2013-10-08 22:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 22:42 [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files Tom Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 2/8] Tegra124: Add changes to common arch-tegra header files Tom Warren
2013-10-08 7:16 ` Thierry Reding
2013-10-07 22:42 ` [U-Boot] [PATCH 3/8] Tegra124: Add SPL/AVP (arm720t) cpu files Tom Warren
2013-10-08 8:13 ` Thierry Reding
2013-10-08 21:34 ` Stephen Warren
2014-01-22 23:12 ` Stephen Warren
2013-10-08 21:36 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 4/8] Tegra124: Add CPU (armv7) files Tom Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 5/8] Tegra124: Add common CPU (shared) files Tom Warren
2013-10-08 21:43 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 6/8] Tegra124: Add generic T124 build support Tom Warren
2013-10-08 21:45 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 7/8] Tegra124: Venice2: fdt: Add device-tree files Tom Warren
2013-10-08 21:55 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 8/8] Tegra124: Add Venice2 (T124) build Tom Warren
2013-10-08 22:06 ` Stephen Warren [this message]
2013-10-08 7:14 ` [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files Thierry Reding
2013-10-08 21:29 ` 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=525481CA.30309@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 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.