u-boot.git/board/compulab, branch v2016.09

mx6: ddr: Allow changing REFSEL and REFR fields

2016-09-06T16:22:48+00:00

Currently MX6 SPL DDR initialization hardcodes the REF_SEL and
REFR fields of the MDREF register as 1 and 7, respectively for
DDR3 and 0 and 3 for LPDDR2.

Looking at the MDREF initialization done via DCD we see that
boards do need to initialize these fields differently:

$ git grep 0x021b0020 board/
board/bachmann/ot1200/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
board/ccv/xpress/imximage.cfg:DATA 4 0x021b0020 0x00000800 /* MMDC0_MDREF */
board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x7800
board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/mx6qp.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6sabresd/mx6dlsabresd.cfg:DATA 4      0x021b0020 0x00005800
board/freescale/mx6sabresd/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6slevk/imximage.cfg:DATA 4 0x021b0020 0x00001800
board/freescale/mx6sxsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00000800
board/freescale/mx6sxsabresd/imximage.cfg:DATA 4 0x021b0020 0x00000800
board/warp/imximage.cfg:DATA 4 0x021b0020 0x00001800

So introduce a mechanism for users to be able to configure
REFSEL and REFR fields as needed.

Keep all the mx6 SPL users in their current REF_SEL and REFR values,
so no functional changes for the existing users.

Signed-off-by: Fabio Estevam 
Reviewed-by: Eric Nelson

ARM: board: cm_fx6: fix mtd partition fixup

2016-09-06T16:22:48+00:00

ft_board_setup may return early in the case that the board revision
cannot be obtained. In that case it is assumed that no revision
specific correction in the fdt is neccessary. But the mtd partitions
will not be fixed up either altough they are not revision specific.

Move the call to fdt_fixup_mtdparts in front of the revision specific
part to ensure that the partitions are fixed up even if the board
revision cannot be obtained.

While on it, fix a spelling mistake in a comment introduced by the
same commit.

Fixes: 62d6bac66038 ("ARM: board: cm_fx6: fixup mtd partitions in the fdt")
Signed-off-by: Christopher Spinrath 
Reviewed-by: Stefano Babic 
Reviewed-by: Nikita Kiryanov

ARM: board: cm_fx6: fixup mtd partitions in the fdt

2016-07-19T17:52:13+00:00

The cm-fx6 module has an on-board st,m25p compatible spi flash chip
used for U-Boot (binary & environment). Overwrite the partitions in
the device tree by the partition table provided in the mtdparts
environment variable, if it is set.

This allows to specify a kernel independent partitioning in the
environment and provides a convient way for the user to adapt the
partition table.

Signed-off-by: Christopher Spinrath 
Acked-by: Igor Grinberg

ARM: board: cm-fx6: fix mmc for old revisions of utilite

2016-07-12T15:58:48+00:00

Old revisions of Utilite (based on cm-fx6) do not have a dedicated
card detect pin. But the card is removable by the user and card
detection can be realized with polling (e.g. supported by Linux).

Add the broken-cd property to the mmc device tree instead of the
non-removable property to make card detection possible if polling
is supported.

Signed-off-by: Christopher Spinrath 
Acked-by: Nikita Kiryanov

compulab: add support for layout aware eeprom commands

2016-05-20T21:02:07+00:00

Add layout definitions and implement functions for field printing/updating,
layout detection, layout assignment, and layout parsing.

Cc: Igor Grinberg 
Cc: Tom Rini 
Signed-off-by: Nikita Kiryanov

omap-common: Rename set_muxconf_regs_essential to set_muxconf_regs

2016-03-15T19:12:06+00:00

There is no distinction between essential and non-essential mux configuration,
so it doesn't make sense to have an "essential" prefix.

Signed-off-by: Paul Kocialkowski

arm: am437x: cm-t43: set MPU and CORE voltages on boot

2016-02-24T23:44:09+00:00

During boot, U-Boot raises the CPU frequency but the CORE and MPU regulators
are not updated. This is not a problem in cold boot since the default values
that the pmic outputs are correct, but if Linux were to switch the module to a
low power OPP, the new voltage values will be retained after a reboot and the
module will likely hang once U-Boot raises the CPU frequency back up.

Set both CORE and MPU regulators to to 1.1V on boot.

Cc: Tom Rini 
Cc: Albert Aribaud 
Cc: Igor Grinberg 
Signed-off-by: Nikita Kiryanov 
Reviewed-by: Tom Rini

arm: am437x: cm-t43: get rid of enable_vtt_regulator()

2016-02-24T23:44:08+00:00

CM-T43 does not have a vtt regulator. Remove the function that's supposed
to enable it.

Cc: Tom Rini 
Cc: Albert Aribaud 
Cc: Igor Grinberg 
Signed-off-by: Nikita Kiryanov 
Reviewed-by: Tom Rini

arm: am437x: cm-t43: set tps fseal bit

2016-02-24T23:44:08+00:00

Set TPS65218 FSEAL bit to 1 so that RTC could be powered using on-board
3V battery. This is necessary so that time and date will survive reboots and
power offs.

Cc: Tom Rini 
Cc: Albert Aribaud 
Cc: Igor Grinberg 
Signed-off-by: Nikita Kiryanov 
Reviewed-by: Tom Rini

arm: am437x: cm-t43: split board file

2016-02-24T23:44:06+00:00

Simplify the board file by splitting it to spl portion and u-boot portion.
Some unnecessary includes were identified and removed. No functional changes.

Cc: Tom Rini 
Cc: Albert Aribaud 
Cc: Igor Grinberg 
Signed-off-by: Nikita Kiryanov 
Reviewed-by: Tom Rini