19 Nov, 2015
1 commit
-
Add CMD_GPIO to Kconfig and run tools/moveconfig.py .
Signed-off-by: Thomas Chou
Reviewed-by: Simon Glass
13 Aug, 2015
1 commit
-
Signed-off-by: Stefano Babic
Reviewed-by: Tom Rini
26 Jun, 2015
1 commit
-
This sets the default commands Kconfig to match
include/config_cmd_default.h commands in the common/Kconfig and removes
them from include/configs.Signed-off-by: Joe Hershberger
[trini: rastaban, am43xx_evm_usbhost_boot, am43xx_evm_ethboot updates]
Signed-off-by: Tom Rini
05 Mar, 2015
1 commit
-
Currently in some cases SDRAM init requires global_data to be available
and soon this will not be available prior to board_init_f(). Adjust the
code paths in these cases to be correct. In some cases we had the SPL
stack be in DDR as we might have large stacks (due to Falcon Mode +
Environment). In these cases switch to CONFIG_SPL_STACK_R. In other
cases we had simply been setting CONFIG_SPL_STACK into SRAM. In these
cases we no longer need to (CONFIG_SYS_INIT_SP_ADDR is used and is also
in SRAM) so drop those lines.Signed-off-by: Simon Glass
Tested on Beagleboard, Beagleboard xM
Tested-by: Matt Porter
Tested on Beaglebone Black, AM43xx GP EVM, OMAP5 uEVM, OMAP4 Pandaboard
Tested-by: Tom Rini
Signed-off-by: Tom Rini
Reviewed-by: Simon Glass
14 Jan, 2015
2 commits
-
Signed-off-by: Anthoine Bourgeois
06 Jan, 2015
1 commit
-
Signed-off-by: Anthoine Bourgeois
05 Dec, 2014
1 commit
-
CONFIG_SYS_MMC_SD_FS_BOOT_PARTITION ought to be called
CONFIG_SYS_MMCSD_FS_BOOT_PARTITION to keep it consistent with other config
options such as: CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR.In addition, it is not related to raw mode booting but to fs mode instead.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Tom Rini
27 Oct, 2014
1 commit
-
Rename some defines containing FAT in their name to be filesystem generic:
MMCSD_MODE_FAT => MMCSD_MODE_FS
CONFIG_SPL_FAT_LOAD_ARGS_NAME => CONFIG_SPL_FS_LOAD_ARGS_NAME
CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME => CONFIG_SPL_FS_LOAD_PAYLOAD_NAME
CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION => CONFIG_SYS_MMC_SD_FS_BOOT_PARTITIONSigned-off-by: Guillaume GARDET
Cc: Tom Rini
31 Aug, 2014
1 commit
-
Becuase the board select menu in arch/arm/Kconfig is too big,
move the OMAP3 board select menu to omap3/Kconfig.Move also common settings (CONFIG_SYS_CPU="armv7" and
CONFIG_SYS_SOC="omap3Signed-off-by: Masahiro Yamada
Reviewed-by: Tom Rini
31 Jul, 2014
1 commit
-
Now CONFIG_SPL and CONFIG_TPL are defined in Kconfig.
Remove the redundant definition in config headers.
Signed-off-by: Masahiro Yamada
Reviewed-by: Simon Glass
30 Jul, 2014
1 commit
-
We are about to switch to Kconfig in the next commit.
But there are something to get done beforehand.In Kconfig, include/generated/autoconf.h defines boolean
CONFIG macros as 1.CONFIG_SPL and CONFIG_TPL, if defined, must be set to 1.
Otherwise, when switching to Kconfig, the build log
would be sprinkled with warning messages like this:
warning: "CONFIG_SPL" redefined [enabled by default]Signed-off-by: Masahiro Yamada
Reviewed-by: Simon Glass
26 Jul, 2014
1 commit
-
PISMO_xx macros were used to define 'Platform Independent Storage MOdule'
related GPMC configurations. This patch
- Replaces these OMAP3 specific macros with generic CONFIG_xx macros as provided
by current u-boot infrastructure.
- Removes unused redundant macros, which are no longer required after
merging of common platform code in following commit
commit a0a37183bd75e74608bc78c8d0e2a34454f95a91
ARM: omap: merge GPMC initialization code for all platform+-----------------+-----------------------------------------------------------+
| Macro | Reason for removal |
+-----------------+-----------------------------------------------------------+
| PISMO1_NOR_BASE | duplicate of CONFIG_SYS_FLASH_BASE |
+-----------------+-----------------------------------------------------------+
| PISMO1_NAND_BASE| duplicate of CONFIG_SYS_NAND_BASE |
+-----------------+-----------------------------------------------------------+
| PISMO1_ONEN_BASE| duplicate of CONFIG_SYS_ONENAND_BASE |
+-----------------+-----------------------------------------------------------+
| PISMO1_NAND_SIZE| GPMC accesses NAND device via I/O mapped registers so |
| | configuring GPMC chip-select for smallest allowable |
| | segment (GPMC_SIZE_16M) is enough. |
+-----------------+-----------------------------------------------------------+
| PISMO1_ONEN_SIZE| OneNAND uses a fixed GPMC chip-select address-space of |
| | 128MB (GPMC_SIZE_128M) |
+-----------------+-----------------------------------------------------------+
+-----------------+-----------------------------------------------------------+
| PISMO1_NOR | Unused Macros |
| PISMO1_NAND | |
| PISMO2_CS0 | |
| PISMO2_CS1 | |
| PISMO1_ONENAND | |
| PISMO2_NAND_CS0 | |
| PISMO2_NAND_CS1 | |
| PISMO1_NOR_BASE | |
| PISMO1_NAND_BASE| |
| PISMO2_CS0_BASE | |
+-----------------+-----------------------------------------------------------+Signed-off-by: Pekon Gupta
07 Jun, 2014
1 commit
-
GPMC controller needs to be configured based on bus-width of the NAND device
connected to it. Also, dynamic detection of NAND bus-width from on-chip ONFI
parameters is not possible in following situations:
SPL: SPL NAND drivers does not support ONFI parameter reading.
U-boot: GPMC controller iniitalization is done in omap_gpmc.c:board_nand_init()
which is called before probing for devices, hence any ONFI parameter
information is not available during GPMC initialization.Thus, OMAP NAND driver expected board developers to explicitely write GPMC
configurations specific to NAND device attached on board in board files itself.
But this was troublesome for board manufacturers as they need to dive into
lengthy platform & SoC documents to find details of GPMC registers and
appropriate configurations to get NAND device working.This patch instead adds existing CONFIG_SYS_NAND_BUSWIDTH_16BIT to board config
hich indicates that connected NAND device has x16 bus-width. And then based on
this config GPMC driver itself initializes itself based on NAND bus-width. This
keeps board developers free from knowing GPMC controller specific internals.Signed-off-by: Pekon Gupta
05 Mar, 2014
1 commit
-
OMAP NAND driver can detect Page-size and OOB-size of NAND device from ONFI
params or nand_id[] table. And based on that it defines ECC layout.
This patch
1) removes following board configs used for defining NAND ECC layout
- GPMC_NAND_ECC_LP_x16_LAYOUT (for large page x16 NAND)
- GPMC_NAND_ECC_LP_x8_LAYOUT (for large page x8 NAND)
- GPMC_NAND_ECC_SP_x16_LAYOUT (for small page x16 NAND)
- GPMC_NAND_ECC_SP_x8_LAYOUT (for small page x8 NAND)2) removes unused #defines in common omap_gpmc.h depending on above configs
Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
Signed-off-by: Pekon Gupta
25 Nov, 2013
1 commit
22 Nov, 2013
1 commit
-
This patch adds new CONFIG_NAND_OMAP_ECCSCHEME, replacing other distributed
CONFIG_xx used for selecting NAND ecc-schemes.
This patch aims at solving following issues.1) Currently ecc-scheme is tied to SoC platform, which prevents user to select
other ecc-schemes also supported in hardware. like;
- most of OMAP3 SoC platforms use only 1-bit Hamming ecc-scheme, inspite
the fact that they can use higher ecc-schemes like 8-bit ecc-schemes with
software based error detection (OMAP_ECC_BCH4_CODE_HW_DETECTION_SW).
- most of AM33xx SoC plaforms use 8-bit BCH ecc-scheme for now, but hardware
supports BCH16 ecc-scheme also.2) Different platforms use different CONFIG_xx to select ecc-schemes, which
adds confusion for user while migrating platforms.
- *CONFIG_NAND_OMAP_ELM* which enables ELM hardware engine, selects only
8-bit BCH ecc-scheme with h/w based error-correction (OMAP_ECC_BCH8_CODE_HW)
whereas ELM hardware engine supports other ecc-schemes also like; BCH4,
and BCH16 (in future).
- *CONFIG_NAND_OMAP_BCH8* selects 8-bit BCH ecc-scheme with s/w based error
correction (OMAP_ECC_BCH8_CODE_HW_DETECTION_SW).
- *CONFIG_SPL_NAND_SOFTECC* selects 1-bit Hamming ecc-scheme using s/w libraryThus adding new *CONFIG_NAND_OMAP_ECCSCHEME* de-couples ecc-scheme dependency
on SoC platform and NAND driver. And user can select ecc-scheme independently
foreach board.
However, selection some hardware based ecc-schemes (OMAP_ECC_BCHx_CODE_HW) still
depends on presence of ELM hardware engine on SoC. (Refer doc/README.nand)Signed-off-by: Pekon Gupta
13 Nov, 2013
1 commit
-
- add omap24xx driver to new multibus/multiadpater support
- adapted all config files, which uses this driverTested on the am335x based siemens boards rut, dxr2 and pxm2
posted here:
http://patchwork.ozlabs.org/patch/263211/Signed-off-by: Heiko Schocher
Tested-by: Tom Rini
Cc: Lars Poeschel
Cc: Steve Sakoman
Cc: Thomas Weber
Cc: Tom Rix
Cc: Grazvydas Ignotas
Cc: Enric Balletbo i Serra
Cc: Luca Ceresoli
Cc: Igor Grinberg
Cc: Ilya Yanok
Cc: Stefano Babic
Cc: Nishanth Menon
Cc: Pali Rohár
Cc: Peter Barada
Cc: Nagendra T S
Cc: Michael Jones
Cc: Raphael Assenat
Acked-by: Igor Grinberg
Acked-by: Stefano Babic
05 Nov, 2013
1 commit
-
Remove platform CONFIG_SYS_HZ definition for configs a-z*.
Signed-off-by: Rob Herring
15 Oct, 2013
2 commits
-
Signed-off-by: Wolfgang Denk
[trini: Drop changes for PEP 4 following python tools]
Signed-off-by: Tom Rini -
Signed-off-by: Wolfgang Denk
15 Aug, 2013
1 commit
-
Adding a new CONFIG_OMAP_COMMON which is included by all boards
that needs to build cpu/armv7/omap-common folder.Signed-off-by: Lokesh Vutla
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
08 Jun, 2013
1 commit
-
Signed-off-by: Tom Rini
02 Mar, 2013
1 commit
-
CONFIG_SPL_OS_BOOT_KEY is used only in board files. It is
not required to have a general CONFIG_ option. Rename it and
define it in board directory.Signed-off-by: Stefano Babic
Reviewed-by: Tom Rini
29 Jan, 2013
1 commit
-
"CONFIG_SYS_I2C_BUS" and "CONFIG_SYS_I2C_BUS_SELECT" don't appear anywhere
outside of config files.Signed-off-by: Michael Jones
Acked-by: Igor Grinberg
27 Nov, 2012
1 commit
-
Some small SPLs do not use nand_base.c, and a subset of those also
require a special driver. Some SPLs need software ECC but others can't
fit it.All existing boards that specify CONFIG_SPL_NAND_SUPPORT have these
symbols added to preserve existing behavior.Signed-off-by: Scott Wood
--
v2: use positive logic for including bits of NAND, rather than
a MINIMAL symbol that excludes things.
23 Oct, 2012
1 commit
-
Fix usage of 'mmc rescan' by many configs. Proper use is
'mmc dev ${mmcdev}; mmc rescan' to set the mmc device and then rescan
the device. 'mmc rescan' itself does not take any arguments.Signed-off-by: Andrew Bradford
02 Oct, 2012
1 commit
-
Signed-off-by: Andreas Bießmann
cc: Thomas Weber
28 Sep, 2012
1 commit
-
Add a new flag, CONFIG_SPL_FRAMEWORK to opt into the common/spl SPL
framework, enable on all of the previously using boards. We move the
spl_ymodem.c portion to common/ and spl_mmc.c to drivers/mmc/. We leave
the NAND one in-place as we plan to replace it later in this series.We use common/spl to avoid linker problems with respect to merging
constant strings in objects. Otherwise all strings in common/ will be
linked in and kept which grows SPL in size too much.Signed-off-by: Tom Rini
01 Sep, 2012
3 commits
-
CONFIG_STACKSIZE is not referenced anywhere except on AVR32, but present
in most ARM board config files.IRQs are only enabled for 1 config, so remove the unused config options
for IRQ and FIQ stack size as well.Cc: Albert ARIBAUD
Signed-off-by: Rob Herring -
Signed-off-by: Marek Vasut
Cc: Wolfgang Denk
Cc: Albert Aribaud
Cc: U-Boot DM
Cc: Tom Rini
Acked-by: Tom Rini
Signed-off-by: Tom Rini -
This fixes the breakage with SPL on most OMAP boards after the GPIO
driver was moved.Signed-off-by: Marek Vasut
Cc: Wolfgang Denk
Cc: Albert Aribaud
Cc: U-Boot DM
Cc: Tom Rini
Acked-by: Tom Rini
Signed-off-by: Tom Rini
21 Jun, 2012
1 commit
-
Exactly one board has defined CONFIG_SYS_PROMPT_HUSH_PS2 to a value
different than "> " which is vision2. I have Cc'd the maintainer here
as I strongly suspect this is a bug rather than intentional behavior.Cc: Stefano Babic
Signed-off-by: Tom Rini
Acked-by: Stefano Babic
15 May, 2012
1 commit
-
With older toolchains it is possible to not fit entirely into the 45KB
that we had assigned to SPL. Adjust to allow for 8KB of stack (which
should be more than required) and 54KB of text/data.Cc: Vaibhav Hiremath
Cc: Nagendra T S
Cc: Thomas Weber
Cc: Ilya Yanok
Cc: Steve Sakoman
Cc: Stefano Babic
Signed-off-by: Tom Rini
Acked-by: Stefano Babic
Acked-by: Vaibhav Hiremath
28 Mar, 2012
2 commits
-
- Implements spl_start_uboot() for devkit8000
- Add configs to activate direct OS boot from SPLSigned-off-by: Simon Schwarz
CC: Tom Rini
CC: Stefano Babic
CC: Wolfgang Denk -
This adds some configs for devkit8000 to use the new spl command
Signed-off-by: Simon Schwarz
CC: Tom Rini
CC: Stefano Babic
CC: Wolfgang Denk
27 Jan, 2012
1 commit
-
Currently nand_spl_simple puts it's temp data at 0x10000 offset in SDRAM
which is likely to contain already loaded data.
The patch saves the oob data and the ecc on the stack replacing
the fixed address in RAM.Signed-off-by: Stefano Babic
CC: Ilya Yanok
CC: Scott Wood
CC: Tom Rini
CC: Simon Schwarz
CC: Wolfgang Denk
Signed-off-by: Scott Wood
07 Dec, 2011
2 commits
-
This moves CONFIG_SYS_TEXT_BASE one MB after beginning of SD-RAM. Move
CONFIG_SYS_SPL_MALLOC_START to have one MB of free space for the u-boot
image.CONFIG_SYS_TEXT_BASE was in the middle of the bss-section. This was the
reason for the problems with MMC boot described here:
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/118711Signed-off-by: Simon Schwarz
Tested-by: Thomas Weber
Signed-off-by: Tom Rini -
Add an SPL_BOARD_INIT hook and for OMAP3 have it turn on i2c. OMAP4
doesn't need i2c enabled in SPL. Enable SPL_BOARD_INIT on devkit8000.Cc: Frederik Kriewitz
Signed-off-by: Tom Rini