|
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
|
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2010-2013, NVIDIA CORPORATION. All rights reserved.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _TEGRA114_COMMON_H_
|
|
|
|
|
#define _TEGRA114_COMMON_H_
|
|
|
|
|
#include "tegra-common.h"
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* NS16550 Configuration
|
|
|
|
|
*/
|
|
|
|
|
#define V_NS16550_CLK 408000000 /* 408MHz (pllp_out0) */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Miscellaneous configurable options
|
|
|
|
|
*/
|
|
|
|
|
#define CONFIG_STACKBASE 0x82800000 /* 40MB */
|
|
|
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------
|
|
|
|
|
* Physical Memory Map
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Memory layout for where various images get loaded by boot scripts:
|
|
|
|
|
*
|
|
|
|
|
* scriptaddr can be pretty much anywhere that doesn't conflict with something
|
|
|
|
|
* else. Put it above BOOTMAPSZ to eliminate conflicts.
|
|
|
|
|
*
|
|
|
|
|
* pxefile_addr_r can be pretty much anywhere that doesn't conflict with
|
|
|
|
|
* something else. Put it above BOOTMAPSZ to eliminate conflicts.
|
|
|
|
|
*
|
|
|
|
|
* kernel_addr_r must be within the first 128M of RAM in order for the
|
|
|
|
|
* kernel's CONFIG_AUTO_ZRELADDR option to work. Since the kernel will
|
|
|
|
|
* decompress itself to 0x8000 after the start of RAM, kernel_addr_r
|
|
|
|
|
* should not overlap that area, or the kernel will have to copy itself
|
|
|
|
|
* somewhere else before decompression. Similarly, the address of any other
|
|
|
|
|
* data passed to the kernel shouldn't overlap the start of RAM. Pushing
|
|
|
|
|
* this up to 16M allows for a sizable kernel to be decompressed below the
|
|
|
|
|
* compressed load address.
|
|
|
|
|
*
|
|
|
|
|
* fdt_addr_r simply shouldn't overlap anything else. Choosing 32M allows for
|
|
|
|
|
* the compressed kernel to be up to 16M too.
|
|
|
|
|
*
|
|
|
|
|
* ramdisk_addr_r simply shouldn't overlap anything else. Choosing 33M allows
|
|
|
|
|
* for the FDT/DTB to be up to 1M, which is hopefully plenty.
|
|
|
|
|
*/
|
ARM: tegra: CONFIG_{SYS_, }LOAD{_, }ADDR rationalization
As best I can tell, CONFIG_SYS_LOAD_ADDR and CONFIG_LOADADDR/$loadaddr
serve essentially the same purpose. Roughly, if a command takes a load
address, then CONFIG_SYS_LOAD_ADDR or $loadaddr (or both) are the default
if the command-line does not specify the address. Different U-Boot
commands are inconsistent re: which of the two default values they use.
As such, set the two to the same value, and move the logic that does this
into tegra-common-post.h so it's not duplicated. A number of other non-
Tegra boards do this too.
The values chosen for these macros are no longer consistent with anything
in MEM_LAYOUT_ENV_SETTINGS. Regain consistency by setting $kernel_addr_r
to CONFIG_LOADADDR. Older scripts tend to use $loadaddr for the default
kernel load address, whereas newer scripts and features tend to use
$kernel_addr_r, along with other variables for other purposes such as
DTBs and initrds. Hence, it's logical they should share the same value.
I had originally thought to make the $kernel_addr_r and CONFIG_LOADADDR
have different values. This would guarantee no interference if a script
used the two variables for different purposes. However, that scenario is
unlikely given the semantic meaning associated with the two variables.
The lowest available value is 0x90200000; see comments for
MEM_LAYOUT_ENV_SETTINGS in tegra30-common-post.h for details. However,
that value would be problematic for a script that loaded a raw zImage to
$loadaddr, since it's more than 128MB beyond the start of SDRAM, which
would interfere with the kernel's CONFIG_AUTO_ZRELADDR. So, let's not do
that.
The only potential fallout I could foresee from this patch is if someone
has a script that loads the kernel to $loadaddr, but some other file
(DTB, initrd) to a hard-coded address that the new value of $loadaddr
interferes with. This seems unlikely. A user should not do that; they
should either hard-code all load addresses, or use U-Boot-supplied
variables for all load addresses. Equally, any fallout due to this change
is trivial to fix; simply modify the load addresses in that script.
Cc: Paul Walmsley <pwalmsley@nvidia.com>
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Paul Walmsley <pwalmsley@nvidia.com>
Reviewed-by: Simon Glass
Signed-off-by: Tom Warren <twarren@nvidia.com>
9 years ago
|
|
|
#define CONFIG_LOADADDR 0x81000000
|
|
|
|
|
#define MEM_LAYOUT_ENV_SETTINGS \
|
|
|
|
|
"scriptaddr=0x90000000\0" \
|
|
|
|
|
"pxefile_addr_r=0x90100000\0" \
|
ARM: tegra: CONFIG_{SYS_, }LOAD{_, }ADDR rationalization
As best I can tell, CONFIG_SYS_LOAD_ADDR and CONFIG_LOADADDR/$loadaddr
serve essentially the same purpose. Roughly, if a command takes a load
address, then CONFIG_SYS_LOAD_ADDR or $loadaddr (or both) are the default
if the command-line does not specify the address. Different U-Boot
commands are inconsistent re: which of the two default values they use.
As such, set the two to the same value, and move the logic that does this
into tegra-common-post.h so it's not duplicated. A number of other non-
Tegra boards do this too.
The values chosen for these macros are no longer consistent with anything
in MEM_LAYOUT_ENV_SETTINGS. Regain consistency by setting $kernel_addr_r
to CONFIG_LOADADDR. Older scripts tend to use $loadaddr for the default
kernel load address, whereas newer scripts and features tend to use
$kernel_addr_r, along with other variables for other purposes such as
DTBs and initrds. Hence, it's logical they should share the same value.
I had originally thought to make the $kernel_addr_r and CONFIG_LOADADDR
have different values. This would guarantee no interference if a script
used the two variables for different purposes. However, that scenario is
unlikely given the semantic meaning associated with the two variables.
The lowest available value is 0x90200000; see comments for
MEM_LAYOUT_ENV_SETTINGS in tegra30-common-post.h for details. However,
that value would be problematic for a script that loaded a raw zImage to
$loadaddr, since it's more than 128MB beyond the start of SDRAM, which
would interfere with the kernel's CONFIG_AUTO_ZRELADDR. So, let's not do
that.
The only potential fallout I could foresee from this patch is if someone
has a script that loads the kernel to $loadaddr, but some other file
(DTB, initrd) to a hard-coded address that the new value of $loadaddr
interferes with. This seems unlikely. A user should not do that; they
should either hard-code all load addresses, or use U-Boot-supplied
variables for all load addresses. Equally, any fallout due to this change
is trivial to fix; simply modify the load addresses in that script.
Cc: Paul Walmsley <pwalmsley@nvidia.com>
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Paul Walmsley <pwalmsley@nvidia.com>
Reviewed-by: Simon Glass
Signed-off-by: Tom Warren <twarren@nvidia.com>
9 years ago
|
|
|
"kernel_addr_r=" __stringify(CONFIG_LOADADDR) "\0" \
|
|
|
|
|
"fdt_addr_r=0x82000000\0" \
|
|
|
|
|
"ramdisk_addr_r=0x82100000\0"
|
|
|
|
|
|
|
|
|
|
/* Defines for SPL */
|
|
|
|
|
#define CONFIG_SPL_TEXT_BASE 0x80108000
|
|
|
|
|
#define CONFIG_SYS_SPL_MALLOC_START 0x80090000
|
|
|
|
|
#define CONFIG_SPL_STACK 0x800ffffc
|
|
|
|
|
|
|
|
|
|
/* For USB EHCI controller */
|
|
|
|
|
#define CONFIG_EHCI_IS_TDI
|
|
|
|
|
#define CONFIG_USB_EHCI_TXFIFO_THRESH 0x10
|
|
|
|
|
|
|
|
|
|
#endif /* _TEGRA114_COMMON_H_ */
|
