23 Feb, 2018
1 commit
-
This seems to have been missed, possibly due to the inability to
enable TI_SECURE_DEVICE on Keystone2 devices previously.Fixes: bfebc8c965e4 ("env: Rename getenv_hex(), getenv_yesno(), getenv_ulong()")
Signed-off-by: Andrew F. Davis
Reviewed-by: Lokesh Vutla
08 Feb, 2018
1 commit
-
Add pinmux for QSPI pins on K2G ICE board.
Signed-off-by: Vignesh R
20 Jan, 2018
2 commits
-
All ddr3_emif declarations are not used outside ddr3_k2g.c
file. So make all of them as static.Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini -
Added support for K2G EVM with FlipChip SoC of which
ARM/DDR3 runs at 1GHz/1066 MT/s. The patch is also
backward compatible with old revision EVM and EVM
with WireBond SoC. Their ARM/DDR3 run at 600MHz/800 MT/s.The new SoC supports 2 different speeds at 1GHz and 600MHz.
Modyfied the CPU Name to show which SoC is used in the EVM.
Modified the DDR3 configuration to reflect New SoC supports
2 different CPU and DDR3 speeds, 1GHz/1066MT and 600MHz/800MT.Added new inline function board_it_k2g_g1() for the new FlipChip 1GHz,
and set the u-boot env variable board_name accordingly.Modified findfdt script in u-boot environment variable to include new k2g board type.
Signed-off-by: Rex Chang
Signed-off-by: Lokesh Vutla
06 Oct, 2017
1 commit
-
CONFIG_FIT_EMBED might be confused with CONFIG_OF_EMBED, rename it
MULTI_DTB_FIT as it is able to get a DTB from a FIT image containing
multiple DTBs. Also move the option to the Kconfig dedicated to the DTS
options and create a README for this feature.Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
Reviewed-by: Simon Glass
13 Sep, 2017
1 commit
-
The PMMC firmware should be bundled into a FIT image on HS
devices to allow authentication/decryption, add a handler to
process this PMMC firmware.Signed-off-by: Andrew F. Davis
16 Aug, 2017
2 commits
-
We are now using an env_ prefix for environment functions. Rename these
two functions for consistency. Also add function comments in common.h.Quite a few places use getenv() in a condition context, provoking a
warning from checkpatch. These are fixed up in this patch also.Suggested-by: Wolfgang Denk
Signed-off-by: Simon Glass -
We are now using an env_ prefix for environment functions. Rename setenv()
for consistency. Also add function comments in common.h.Suggested-by: Wolfgang Denk
Signed-off-by: Simon Glass
11 Aug, 2017
1 commit
-
Traditional KS2 devices supported NAND via the AEMIF peripheral. However,
66AK2G doesn't use the AEMIF but rather the GPMC for NAND. Therefore,
clarify some statements to indicate only certain devices have AEMIF and
in other places just say NAND instead of AEMIF NANDSigned-off-by: Franklin S Cooper Jr
Acked-by: Roger Quadros
11 Jul, 2017
12 commits
-
K2G ICE evm will have its own dtb. Therefore, add it to the list of dtbs
located in the appended U-boot dtb FIT image. Therefore, when swapping out
dtbs K2G ICE boards can grab the correct one.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Enable CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG to allow "board_name" to
be set depending on the board it is being ran on.Update findfdt to use this new dynamic board_name value to determine
which dtb should be used.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Certain peripherals used by K2G GP aren't used on K2G ICE evm. Or
configuration is slightly different. Therefore, use board detection to
deal with these variations.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Some code doesn't apply to K2G ICE evm. Therefore, use board detection to
wrap these calls.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Add configuration settings used by the K2G ICE evm. Also use board
detection to determine which DDR3 configuration to use.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Add basic pinmux data for new K2G ICE evm. Also add pinmuxing for a
generic K2G evm which includes I2C 0 and 1 used for board detection
purposes.Since multiple K2G boards are supported that means initially generic
pinmuxing should be used when board detection hasn't ran. Once board
detection runs the proper pinmuxing can be reran to match the board
being ran on.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Add a function that can be used to determine if the board being ran on is
a K2G Industrial Communication Engine EVM or K2G General Purpose EVM based
on values programmed on the EEPROM.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Different K2G evms may need to program the various
KS2_DDRPHY_DATX8_X_OFFSET registers in different ways. Therefore, use
the mask and val registers for each KS2_DDRPHY_DATAX_X_OFFSET to
properly program the register.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
K2G GP doesn't require the MR2 register to be programed since the
default is good enough. However, newer K2G boards do need to change
this register value. Therefore, instead of not writing this register if
ran on a K2G board just program the value to be written to match the
default/reset value.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Some K2G evms have their EEPROM programming while most do not. Therefore,
add EEPROM board detection to be used as the default method and fall back
to the alternative board detection when needed.Also reorder board configuration. Perform bare minimal configuration
initially since board detection hasn't ran. Finish board configuration
once the board has been identified.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
Now with support for U-boot runtime dtb selection each board needs to
define board_fit_config_name_match so U-boot can determine what the
correct dtb is within the FIT blob.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini -
For K2G, runtime DTB selection utilizes the embedded_dtb_select function.
Therefore, define the function which will perform a EEPROM read and then
retries selecting the correct dtb now that it can detect which board its
on. For other Keystone devices use an empty function since they will still
use the embedded FIT functionality but their FIT will only contain a single
dtb.Most production K2G boards do not have their EEPROM programmed. Therefore,
perform a test to verify a K2G GP is currently being used and if it is then
set the values normally set by a EEPROM read.Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Tom Rini
06 Jun, 2017
1 commit
-
Main pll is marked as arm plls for higher speeds. Fix this.
Signed-off-by: Lokesh Vutla
15 May, 2017
1 commit
-
Now CONFIG_GENERIC_MMC and CONFIG_MMC match for all defconfig.
We do not need two options for the same feature. Deprecate the
former.This commit was generated with the sed script 's/GENERIC_MMC/MMC/'
and manual fixup of drivers/mmc/Kconfig.Signed-off-by: Masahiro Yamada
09 May, 2017
2 commits
-
One some keystone2 platforms like K2G ICE, there is an option
to switch between 24MHz or 25MHz as sysclk. But the existing
driver assumes it is always 24MHz. Add support for getting
all reference clocks dynamically by reading boot pins.Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini -
K2G supports various sysclk frequencies which can be
determined using sysboot pins. PLLs should be configured
based on this sysclock frequency. Add PLL configurations
for all supported sysclk frequencies.Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
21 Mar, 2017
2 commits
-
PRU ethernet MAC address range is present in the
board EEPROM. Parse it and setup eth?addr
environment variables.Signed-off-by: Roger Quadros
Reviewed-by: Lokesh Vutla
Reviewed-by: Tom Rini -
In stead of defining the board EEPROM address in the board headers
let's define them in the board config files and make them
configurable by Kconfig.Signed-off-by: Roger Quadros
Reviewed-by: Tom Rini
20 Mar, 2017
1 commit
-
To keep a consistent MMC device mapping in SPL and in u-boot, let's
register the MMC controllers the same way in u-boot and in the SPL.
In terms of boot time, it doesn't hurt to register more controllers than
needed because the MMC device is initialized only prior being accessed for
the first time.
Having the same device mapping in SPL and u-boot allows us to use the
environment in SPL whatever the MMC boot device.Signed-off-by: Jean-Jacques Hiblot
29 Nov, 2016
1 commit
-
The config option TARGET_K2x_EVM is set by the k2x defconfigs to pick
a board target, but the header configs also set K2x_EVM. This config
is redundant, remove it and use TARGET_K2x_EVM everywhere in its place.Signed-off-by: Andrew F. Davis
Reviewed-by: Lokesh Vutla
14 Nov, 2016
1 commit
-
Only a certain set of PLLM/D values are recommended to configure the DDR
at the required speeds for a given clock input frequency. Updating these
values as specified in Data Sheet[1] Table 5-18[1] http://www.ti.com/lit/ds/symlink/66ak2g02.pdf
Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
02 Oct, 2016
1 commit
-
EEC is being enabled based on the ddr size populated by SPD data.
But not all keystone platforms have SPD data to detect ddr3 size.
So, enable ECC using the detected DDR size.Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
08 Sep, 2016
1 commit
-
Update the README to add support for K2G EVM. Also
- Add steps on how to use MMC boot
- Fix load address when using CCS
- Update build target to u-boot.bin from u-boot-dtb.bin as all ks2
platforms uses DT.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
03 Jun, 2016
1 commit
-
BOOTCFG_RSTMUX8 register controls the reset mux associated with the ARM.
Timer5(dedicated to ARM) when used as WatchDog timer, the events it
generates are routed to the above mux.Following are the 3 events that can controlled bt the reset mux:
- Device Reset
- An interrupt to the ARM_GIC
- An interrupt to the ARM_GIC followed by a device reset.Right now to give a default watchdog behaviour "Device reset" is
being selected.Signed-off-by: Lokesh Vutla
Acked-by: Nishanth Menon
28 May, 2016
1 commit
-
Since CONFIG_OF_BOARD_SETUP depends on CONFIG_OF_LIBFDT:
config OF_BOARD_SETUP
bool "Set up board-specific details in device tree before boot"
depends on OF_LIBFDT
...remove superfluous tests of CONFIG_OF_LIBFDT when testing for
CONFIG_OF_BOARD_SETUP.Signed-off-by: Robert P. J. Day
[trini: Typo fix: s/ifdefi/ifdef/]
Signed-off-by: Tom Rini
19 Apr, 2016
1 commit
-
Not all Keystone2 devices has AEMIF NAND controller. So adding Kconfig
entry for CONFIG_TI_AEMIF and enabling it in respective defconfigs on
platforms with AEMIF controller.Reported-by: Nishanth Menon
Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
23 Mar, 2016
1 commit
-
After power cycle of a K2G EVM dhcp fails due to a auto-negotiation
timeout. This commit increases the timeout to fix the issue.Signed-off-by: Vitaly Andrianov
Reviewed-by: Tom Rini
15 Mar, 2016
4 commits
-
Because KS2 u-boot works in 32 bit address space the existing ram_size
global data field cannot be used. The maximum, which the get_ram_size()
can detect is 2GB only. The ft_board_setup() needs the actual ddr3 size
to fix up dtb.This commit introduces the ddr3_get_size() which uses SPD data to
calculate the ddr3 size. This function replaces the "ddr3_size"
environment variable, which was used to get the SODIMM size.For platforms, which don't have SODIMM with SPD and ddr3 is populated to
a board a simple ddr3_get_size function that returns ddr3 size has to be
implemented. See hardware-k2l.hSigned-off-by: Vitaly Andrianov
Signed-off-by: Nishanth Menon
Reviewed-by: Tom Rini -
This commit replaces hard-coded EMIF and PHY DDR3 configurations for
predefined SODIMMs to a calculated configuration. The SODIMM parameters
are read from SODIMM's SPD and used to calculated the configuration.The current commit supports calculation for DDR3 with 1600MHz and 1333MHz
only.Signed-off-by: Vitaly Andrianov
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon
Reviewed-by: Tom Rini -
The maximum device and arm speeds can be determined by reading
EFUSE_BOOTROM register. As there is already a framework for reading this
register, adding support for all possible speeds on k2g devices.Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon
Reviewed-by: Tom Rini -
Its not compulsory that speed definition should be same on EFUSE_BOOTROM
register for all keystone 2 devices. So, allow for board specific
speed definitions.Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon
Reviewed-by: Tom Rini