Eric Lee / smarc-uboot

06 Oct, 2016

3 commits

24 Sep, 2016

1 commit

07 Sep, 2016

1 commit

  • edf009373   mx6: ddr: Allow changing REFSEL and REFR fields ... Browse Code »
    20

    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
     

12 Jul, 2016

1 commit

28 May, 2016

1 commit

02 Oct, 2015

1 commit

  • 931a1d2a1   vf610: add support for Phytec PCM052 ... Browse Code »

    Devices supported are:
    - NFC (NAND FLASH)
    - MMC
    - QSPI (SPI NOR FLASH)
    - I2C (only bus 2)
    - I2C RTC
    - I2C EEPROM
    - FEC

    Patch-series: 2
    - remove useless CONFIG_SYS_SPD_BUS_NUM from config
    - remove include of config_cmd_default.h
    - remove duplicate CONFIG_CMD_NET

    Signed-off-by: Albert ARIBAUD (3ADEV)

    Albert ARIBAUD \(3ADEV\)
     

05 Aug, 2015

1 commit

19 Apr, 2015

2 commits

  • 0adb5b761   net: cosmetic: Name ethaddr variables consistently ... Browse Code »

    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
     
  • 58d423b88   dm: select CONFIG_DM* options ... Browse Code »

    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

21 Nov, 2014

1 commit

  • e895a4b06   fdt: Allow ft_board_setup() to report failure ... Browse Code »

    This function can fail if the device tree runs out of space. Rather than
    silently booting with an incomplete device tree, allow the failure to be
    detected.

    Unfortunately this involves changing a lot of places in the code. I have
    not changed behvaiour to return an error where one is not currently
    returned, to avoid unexpected breakage.

    Eventually it would be nice to allow boards to register functions to be
    called to update the device tree. This would avoid all the many functions
    to do this. However it's not clear yet if this should be done using driver
    model or with a linker list. This work is left for later.

    Signed-off-by: Simon Glass
    Acked-by: Anatolij Gustschin

    Simon Glass
     

29 Oct, 2014

1 commit

  • 2e07c249a   kconfig: arm: introduce symbol for ARM CPUs ... Browse Code »
    215

    This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     

14 Sep, 2014

1 commit

  • 461be2f96   kconfig: remove redundant "string" type in arch and board Kconfigs ... Browse Code »
    43

    Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
    are specified in arch/Kconfig.

    We can delete the ones in arch and board Kconfig files.

    This commit can be easily reproduced by the following command:

    find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
    /config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
    }
    '

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

30 Jul, 2014

2 commits

  • 93d4334f7   Add board MAINTAINERS files ... Browse Code »

    We have switched to Kconfig and the boards.cfg file is going to
    be removed. We have to retrieve the board status and maintainers
    information from it.

    The MAINTAINERS format as in Linux Kernel would be nice
    because we can crib the scripts/get_maintainer.pl script.

    After some discussion, we chose to put a MAINTAINERS file under each
    board directory, not the top-level one because we want to collect
    relevant information for a board into a single place.

    TODO:
    Modify get_maintainer.pl to scan multiple MAINTAINERS files.

    Signed-off-by: Masahiro Yamada
    Suggested-by: Tom Rini
    Acked-by: Simon Glass

    Masahiro Yamada
     
  • dd84058d2   kconfig: add board Kconfig and defconfig files ... Browse Code »

    This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

04 Mar, 2014

1 commit

19 Dec, 2013

1 commit

  • 965de8b91   ARM: AM33xx+: Update ioregs to pass different values ... Browse Code »

    Currently same value is programmed for all ioregs. This is not
    the case for all SoC's like AM4372. So adding a structure for ioregs
    and updating in all board files. And also return from config_cmd_ctrl()
    and config_ddr_data() functions if data is not passed.

    Signed-off-by: Lokesh Vutla
    [trini: Fixup dxr2, cm_t335, adapt pcm051 rev3]
    Signed-off-by: Tom Rini

    Lokesh Vutla
     

11 Dec, 2013

1 commit

04 Dec, 2013

2 commits

  • 39245c869   am33xx: Stop modifying certain EMIF4D registers ... Browse Code »

    Based on the definitive guide to EMIF configuration[1] certain registers
    that we have been modifying (and are documented registers) should be
    left in their reset values rather than modified. This has been tested
    on AM335x GP EVM and Beaglebone White.

    [1]: http://processors.wiki.ti.com/index.php/AM335x_EMIF_Configuration_tips
    Cc: Enric Balletbo i Serra
    Cc: Javier Martinez Canillas
    Cc: Heiko Schocher
    Cc: Lars Poeschel
    Signed-off-by: Tom Rini
    Tested-by: Matt Porter

    Tom Rini
     
  • 7aecdb07a   pcm051: Support for revision 3 ... Browse Code »

    Phytec sells revision or version 3 of pcm051. It is labeled 1358.3 on
    the board. The difference for u-boot is that is has other DDR3 RAM on it:
    1 x MT41K256M16HA125E instead of 2 x MT41J256M8HX15E on revisions 1 and
    2. Both configurations are 512 MiB.
    Configure your u-boot build with pcm051_rev3 for the new RAM and
    pcm051_rev1 for the old RAM configuration. Board revision 2 has to use
    pcm051_rev1 also.

    Signed-off-by: Lars Poeschel

    Lars Poeschel
     

13 Nov, 2013

1 commit

  • 6789e84ec   i2c, omap24xx: convert driver to new mutlibus/mutliadapter framework ... Browse Code »

    - add omap24xx driver to new multibus/multiadpater support
    - adapted all config files, which uses this driver

    Tested 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

    Heiko Schocher
     

01 Nov, 2013

2 commits

07 Oct, 2013

1 commit

  • 6478cde61   pcm051/igep0033: Supply bd_ram_ofs for cpsw driver ... Browse Code »

    Since 2bf36ac638ab2db9f0295aa47064976eeebf80c1 the BD ram address is
    not hardcoded inside cpsw driver any more. Platforms have to supply
    their bd_ram_ofs in the platform data to the driver. This commit does
    this for pcm051 and igep0033 boards.

    Tested-by: Enric Balletbo i Serra
    Acked-by: Mugunthan V N
    Signed-off-by: Lars Poeschel

    Lars Poeschel
     

28 Aug, 2013

1 commit

16 Aug, 2013

1 commit

  • 73feefdc1   am33xx: Stop using PHYS_DRAM_1 define ... Browse Code »

    We defined PHYS_DRAM_1 to 0x80000000 (start of DRAM) and then used this
    for CONFIG_SYS_SDRAM_BASE. But then we kept on referencing PHYS_DRAM_1
    in other places. Change to directly setting CONFIG_SYS_DRAM_BASE and
    then using that name in code.

    Signed-off-by: Tom Rini

    Tom Rini
     

15 Aug, 2013

2 commits

  • 0660481a5   ARM: AM33xx: Move s_init to a common place ... Browse Code »

    s_init has the same outline for all the AM33xx based
    board. So making it generic.
    This also helps in addition of new Soc with minimal changes.

    Signed-off-by: Lokesh Vutla
    Signed-off-by: Heiko Schocher
    Signed-off-by: Tom Rini
    Tested-by: Heiko Schocher
    Acked-by: Heiko Schocher

    Heiko Schocher
     
  • 94d77fb65   ARM: AM33xx: Cleanup dplls data ... Browse Code »

    Locking sequence for all the dplls is same.
    In the current code same sequence is done repeatedly
    for each dpll. Instead have a generic function
    for locking dplls and pass dpll data to that function.

    This is derived from OMAP4 boards.

    Signed-off-by: Lokesh Vutla
    Tested-by: Heiko Schocher
    Acked-by: Heiko Schocher

    Lokesh Vutla
     

24 Jul, 2013

1 commit

18 Jun, 2013

2 commits

05 Jun, 2013

1 commit

  • 4596dcc1d   am33xx/omap: Move save_omap_boot_params to omap-common/boot-common.c ... Browse Code »

    We need to call the save_omap_boot_params function on am33xx/ti81xx and
    other newer TI SoCs, so move the function to boot-common. Only OMAP4+
    has the omap_hw_init_context function so add ifdefs to not call it on
    am33xx/ti81xx. Call save_omap_boot_params from s_init on am33xx/ti81xx
    boards.

    Reviewed-by: R Sricharan
    Signed-off-by: Tom Rini

    Tom Rini
     

08 Apr, 2013

1 commit

  • cecac32a0   pcm051: Enable DDR PHY dynamic power down bit ... Browse Code »

    This is done already for am335x in
    59dcf970d11ebff5d9f4bbbde79fda584e9e7ad4 and also applies for pcm051.

    It powers down the IO receiver when not performing read which helps
    reducing the overall power consuption in low power states
    (suspend/standby).

    Signed-off-by: Lars Poeschel

    Lars Poeschel
     

25 Mar, 2013

2 commits

19 Feb, 2013

1 commit

07 Feb, 2013

1 commit