2018-05-06 21:58:06 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ */
|
2012-05-16 13:54:07 +00:00
|
|
|
/*
|
|
|
|
* (C) Copyright 2010-2012
|
|
|
|
* NVIDIA Corporation <www.nvidia.com>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __CONFIG_H
|
|
|
|
#define __CONFIG_H
|
|
|
|
|
2014-02-26 13:47:58 +00:00
|
|
|
#include <linux/sizes.h>
|
2012-08-31 08:30:00 +00:00
|
|
|
#include "tegra20-common.h"
|
2012-05-16 13:54:07 +00:00
|
|
|
|
|
|
|
/* High-level configuration options */
|
2012-09-05 00:00:24 +00:00
|
|
|
#define CONFIG_TEGRA_BOARD_STRING "Compulab Trimslice"
|
2012-05-16 13:54:07 +00:00
|
|
|
|
|
|
|
/* Board-specific serial config */
|
2012-09-05 00:00:24 +00:00
|
|
|
#define CONFIG_TEGRA_ENABLE_UARTA
|
|
|
|
#define CONFIG_TEGRA_UARTA_GPU
|
2012-05-16 13:54:07 +00:00
|
|
|
#define CONFIG_SYS_NS16550_COM1 NV_PA_APB_UARTA_BASE
|
|
|
|
|
|
|
|
#define CONFIG_MACH_TYPE MACH_TYPE_TRIMSLICE
|
|
|
|
|
2012-05-24 11:38:37 +00:00
|
|
|
/* SPI */
|
|
|
|
#define CONFIG_SF_DEFAULT_MODE SPI_MODE_0
|
|
|
|
|
2012-05-16 13:54:07 +00:00
|
|
|
/* I2C */
|
2012-10-30 07:28:53 +00:00
|
|
|
#define CONFIG_SYS_I2C_TEGRA
|
2012-05-16 13:54:07 +00:00
|
|
|
|
2012-05-24 11:38:37 +00:00
|
|
|
/* Environment in SPI */
|
|
|
|
#define CONFIG_ENV_SPI_MAX_HZ 48000000
|
|
|
|
#define CONFIG_ENV_SPI_MODE SPI_MODE_0
|
|
|
|
#define CONFIG_ENV_SECT_SIZE CONFIG_ENV_SIZE
|
ARM: tegra: fix trimslice environment location
Trimslice currently stores its environment at 512KiB into the SPI flash
chip. The U-Boot binary has grown such that the size of the boot image
(which includes the Tegra BCT, padding, and the U-Boot binary) is slightly
larger than 512K now. Consequently, writing the boot image to flash
corrupts the saved environment, and equally, writing to or erasing the
environment will corrupt the bootloader, which in turn will cause the
Tegra boot ROM to enter recovery mode during boot, making it look as if
the system is non-operational. Note that tegra-uboot-flasher writes to
the environment during the flashing process.
Solve this by moving the environment as high as possible in flash. This
will allow the U-Boot binary to roughly double in size before this problem
is hit again, at which point there's nothing we can do anyway since the
binary won't fit into flash.
99% of other Tegra boards store the environment in eMMC and use a negative
value for CONFIG_ENV_OFFSET, which already automatically places the
environment as near the end of boot flash as possible. The 1 remaining
board hard-codes CONFIG_ENV_OFFSET to 2MiB, which allows for plenty more
bloat.
Reported-by: Stephen L Arnold <nerdboy@gentoo.org>
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Tom Warren <twarren@nvidia.com>
2016-08-08 19:56:35 +00:00
|
|
|
/* 1MiB flash, environment located as high as possible */
|
|
|
|
#define CONFIG_ENV_OFFSET (SZ_1M - CONFIG_ENV_SIZE)
|
2012-05-16 13:54:07 +00:00
|
|
|
|
|
|
|
/* USB Host support */
|
|
|
|
#define CONFIG_USB_EHCI_TEGRA
|
|
|
|
|
|
|
|
/* USB networking support */
|
|
|
|
|
2014-12-10 05:25:14 +00:00
|
|
|
/* PCI host support */
|
|
|
|
|
2012-05-16 13:54:07 +00:00
|
|
|
/* General networking support */
|
|
|
|
|
2012-09-05 00:00:24 +00:00
|
|
|
#include "tegra-common-post.h"
|
2012-05-16 13:54:07 +00:00
|
|
|
|
|
|
|
#endif /* __CONFIG_H */
|