14 Oct, 2016

1 commit

  • Sometimes devicetree nodes and or properties are added out of the u-boot
    console, maybe through some script or manual interaction.

    The devicetree as loaded or embedded is quite small, so the devicetree
    has to be resized to take up those new nodes/properties.

    In original the devicetree was only extended by effective
    4 * add_mem_rsv.

    With this commit we can add an argument to the "fdt resize" command,
    which takes the extrasize to be added.

    Signed-off-by: Hannes Schmelzer

    Signed-off-by: Hannes Schmelzer
    Acked-by: Simon Glass

    Hannes Schmelzer
     

24 Sep, 2016

1 commit


07 Sep, 2016

2 commits

  • 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

    Fabio Estevam
     
  • 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

    Christopher Spinrath
     

20 Jul, 2016

1 commit

  • 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

    Christopher Spinrath
     

12 Jul, 2016

1 commit

  • 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

    Christopher Spinrath
     

21 May, 2016

1 commit


16 Mar, 2016

1 commit


25 Feb, 2016

4 commits

  • 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

    Nikita Kiryanov
     
  • 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

    Nikita Kiryanov
     
  • 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

    Nikita Kiryanov
     
  • 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

    Nikita Kiryanov
     

13 Jan, 2016

1 commit


19 Nov, 2015

2 commits


16 Nov, 2015

2 commits


23 Oct, 2015

1 commit


13 Sep, 2015

5 commits


12 Sep, 2015

1 commit


02 Sep, 2015

2 commits

  • Print board revision for cm-fx6.

    Cc: Stefano Babic
    Cc: Igor Grinberg
    Signed-off-by: Nikita Kiryanov
    Acked-by: Igor Grinberg

    Nikita Kiryanov
     
  • On some CM-FX6 modules U-Boot attempts to configure the usb0 controller in
    device mode, which renders it unavailable:
    USB0: Port not available.
    and also causes usb stop to report an error
    EHCI failed to shut down host controller.

    This happens mostly on MX6 Dual based modules, and is caused by the USBPHY_CTRL
    register reporting USBPHY_CTRL_OTG_ID to be 1, even when it is pulled down.
    Since we do not support device mode in cm-fx6 u-boot, force all controllers to
    be configured as hosts.

    Cc: Stefano Babic
    Cc: Igor Grinberg
    Signed-off-by: Nikita Kiryanov
    Acked-by: Igor Grinberg

    Nikita Kiryanov
     

13 Aug, 2015

1 commit


05 Aug, 2015

1 commit


02 Aug, 2015

5 commits


28 Jul, 2015

1 commit

  • This introduces OMAP3 support for the common omap boot code, as well as a
    major cleanup of the common omap boot code.

    First, the omap_boot_parameters structure becomes platform-specific, since its
    definition differs a bit across omap platforms. The offsets are removed as well
    since it is U-Boot's coding style to use structures for mapping such kind of
    data (in the sense that it is similar to registers). It is correct to assume
    that romcode structure encoding is the same as U-Boot, given the description
    of these structures in the TRMs.

    The original address provided by the bootrom is passed to the U-Boot binary
    instead of a duplicate of the structure stored in global data. This allows to
    have only the relevant (boot device and mode) information stored in global data.
    It is also expected that the address where the bootrom stores that information
    is not overridden by the U-Boot SPL or U-Boot.

    The save_omap_boot_params is expected to handle all special cases where the data
    provided by the bootrom cannot be used as-is, so that spl_boot_device and
    spl_boot_mode only return the data from global data.

    All of this is only relevant when the U-Boot SPL is used. In cases it is not,
    save_boot_params should fallback to its weak (or board-specific) definition.
    save_omap_boot_params should not be called in that context either.

    Signed-off-by: Paul Kocialkowski

    Paul Kocialkowski
     

10 Jul, 2015

1 commit


14 May, 2015

1 commit

  • All the Tegra boards borrow the files from board/nvidia/common/
    directory, i.e., board/nvidia/common/* are not vendor-common files,
    but SoC-common files.

    Move NVIDIA common files to arch/arm/mach-tegra/ to clean up
    Makefiles.

    As arch/arm/mach-tegra/board.c already exists, this commit renames
    board/nvidia/common/board.c to arch/arm/mach-tegra/board2.c,
    expecting they will be consolidated as a second step.

    Signed-off-by: Masahiro Yamada
    Acked-by: Marcel Ziswiler
    Cc: Stephen Warren
    Cc: Tom Warren
    Cc: Simon Glass
    Acked-by: Simon Glass
    Signed-off-by: Tom Warren

    Masahiro Yamada
     

19 Apr, 2015

2 commits

  • Use "_ethaddr" at the end of variables and drop CamelCase.
    Make constant values actually 'const'.

    Signed-off-by: Joe Hershberger
    Acked-by: Simon Glass

    Joe Hershberger
     
  • As mentioned in the previous commit, adding default values in each
    Kconfig causes problems because it does not co-exist with the
    "depends on" syntax. (Please note this is not a bug of Kconfig.)
    We should not do so unless we have a special reason. Actually,
    for CONFIG_DM*, we have no good reason to do so.

    Generally, CONFIG_DM is not a user-configurable option. Once we
    convert a driver into Driver Model, the board only works with Driver
    Model, i.e. CONFIG_DM must be always enabled for that board.
    So, using "select DM" is more suitable rather than allowing users to
    modify it. Another good thing is, Kconfig warns unmet dependencies
    for "select" syntax, so we easily notice bugs.

    Actually, CONFIG_DM and other related options have been added
    without consistency: some into arch/*/Kconfig, some into
    board/*/Kconfig, and some into configs/*_defconfig.

    This commit prefers "select" and cleans up the following issues.

    [1] Never use "CONFIG_DM=n" in defconfig files

    It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
    It is more common to use "# CONFIG_FOO is not set". But here, we
    do not even have to do it.
    Less than half of OMAP3 boards have been converted to Driver Model.
    Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
    weird. Instead, add "select DM" only to appropriate boards, which
    eventually eliminates "CONFIG_DM=n", etc.

    [2] Delete redundant CONFIGs

    Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
    in configs/sandbox_defconfig.
    Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
    defines it also in omap3_beagle_defconfig and devkit8000_defconfig.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

25 Feb, 2015

1 commit


13 Feb, 2015

1 commit