u-boot.git/include/configs/km, branch v2016.01

sf: Move SPI flash drivers to defconfig

2015-11-25T15:06:05+00:00

There are already Kconfig options for SPI flash drivers, but we
have not moved them from config.h to defconfig files. This commit
does this in a batch.

Signed-off-by: Bin Meng

spi: Move SPI drivers to defconfig

2015-11-25T15:05:28+00:00

There are already Kconfig options for SPI drivers, but we
have not moved them from config.h to defconfig files. This
commit does this in a batch.

Signed-off-by: Bin Meng

eeprom: Zap CONFIG_SYS_I2C_MULTI_EEPROMS

2015-11-22T02:50:21+00:00

This option only complicates the code unnecessarily, just use
CONFIG_SYS_DEF_EEPROM_ADDR as the default address if there are
only five arguments to eeprom {read/write} if this is defined.
If CONFIG_SYS_DEF_EEPROM_ADDR is not defined, we mandate all
six arguments.

Signed-off-by: Marek Vasut 
Cc: Simon Glass 
Cc: Tom Rini 
Cc: Heiko Schocher 
Reviewed-by: Heiko Schocher

ns16550: move CONFIG_SYS_NS16550 to Kconfig

2015-11-22T02:50:18+00:00

Move CONFIG_SYS_NS16550 to Kconfig, and run moveconfig.py.

Signed-off-by: Thomas Chou

km8309: change the default QE_FW address

2015-11-18T20:28:57+00:00

It should be after the u-boot reserved sectors and before the env
sectors, since the solution used for kmvect1 (tell the linker to put the
firmware into the u-boot produced binary, at the end of the area) should
be the exception.

The #define is only "conditional" so that we can still support kmvect1.

Signed-off-by: Valentin Longchamp

km83xx: use CONFIG_ENV_ADDR for the newenv env command

2015-11-18T20:28:57+00:00

The hardcoded value are bad, since the address could change between
different boards.

Furthermore, the relevant #defines are set only if #undefined here, so
that they can be changed by some boards if required.

Signed-off-by: Valentin Longchamp

powerpc/km8309: define CONFIG_SYS_DDRCDR

2015-11-18T20:28:56+00:00

For consistency with all the other km83xx plaforms, this should also be
defined for km8309. The same settings as for km8321 are taken.

Signed-off-by: Valentin Longchamp

powerpc/km8321: define CONFIG_SYS_DDRCDR

2015-11-18T20:28:55+00:00

On the km8321 boards is CONFIG_SYS_DDRCDR not defined, which leads to
the DDRCDR not being configured at startup and still containing the
reset value.

The required settings for our km8321 hardware designs are different than
the reset value and must be set with CONFIG_SYS_DDRCDR, that is used
by mpc83xx's cpu_init_f function at early CPU initialization.

The important settings are the DDR2 internal voltage level and the
half-strength "drivers".

In our case where the DRAM chips are soldered on board and the routing
for these signals under control, half-strength is sufficient as a few
measurements done in the lasts have shown. Since all the hardware
qualification tests have been performed with half strength, the nominal
strength settings are removed in favor of the default reset half
strength settings.

Signed-off-by: Valentin Longchamp

km/powerpc: move open firmware defines to km-powerpc.h

2015-11-18T20:28:54+00:00

We use the same settings for open firmware defines on all our powerpc
targets, so move them from the CPU specific headers to the common
powerpc header.

Signed-off-by: Holger Brunck 
Signed-off-by: Valentin Longchamp

km/powerpc: increase space for kernel imange and FDT blob

2015-11-18T20:28:53+00:00

128kByte and 3,986MB may be in the future too little for kernel the fdt
blob respectively the kernel image. So increase the reserved areas here,
we have the space for this.

Signed-off-by: Holger Brunck 
Signed-off-by: Valentin Longchamp