04 Dec, 2017

1 commit

  • This header was renamed to rawnand.h in Linux.

    The following is the corresponding commit in Linux.

    commit d4092d76a4a4e57b65910899948a83cc8646c5a5
    Author: Boris Brezillon
    Date: Fri Aug 4 17:29:10 2017 +0200

    mtd: nand: Rename nand.h into rawnand.h

    We are planning to share more code between different NAND based
    devices (SPI NAND, OneNAND and raw NANDs), but before doing that
    we need to move the existing include/linux/mtd/nand.h file into
    include/linux/mtd/rawnand.h so we can later create a nand.h header
    containing all common structure and function prototypes.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

06 Nov, 2017

1 commit

  • As part of my usual round of build testing, output about missing
    MAINTAINERS information was not logged, and thus often overlooked.
    Correct that mistake by ensuring that I log the output of
    genboardscfg.py every time. As part of that, address a number of
    missing MAINTAINERS entires. In the case of a missing file, I have put
    the original submitter down. In the rest of the cases I have added the
    config (and sometimes relevant header file) to the existing set of file
    globs.

    Signed-off-by: Tom Rini

    Tom Rini
     

27 Aug, 2017

2 commits

  • Update igep00x0 code with the following features:
    - Add board and revision detection for the boards:
    - IGEP0020-RF
    - IGEP0020-RC
    - IGEP0030-RG
    - IGEP0030-RE
    - Merge IGEP0020 and IGEP0030 mux tables
    - Add suport to use GPIO_126, GPIO_127 and GPIO_129
    - board_name and board_rev environment variables display board and
    revision informations
    - Move dtb name selection from code to boot script

    Signed-off-by: Pau Pajuelo
    Signed-off-by: Ladislav Michl
    Tested-by: Pau Pajuelo

    Pau Pajuelo
     
  • Avoid cluttering board file with CONFIG_SPL_BUILD ifdefs
    by moving SPL related functions into separate file.

    Signed-off-by: Ladislav Michl
    Tested-by: Pau Pajuelo
    Acked-by: Enric Balletbo i Serra

    Ladislav Michl
     

16 Aug, 2017

3 commits


07 Jul, 2017

1 commit


15 May, 2017

1 commit


08 May, 2017

3 commits

  • The IGEP SMARC AM335x is an industrial processor module with
    following highlights:

    o AM3352 TI processor (Up to AM3359)
    o Cortex-A8 ARM CPU
    o SMARC form factor module
    o Up to 512 MB DDR3 SDRAM / 512 MB FLASH
    o WiFi a/b/g/n and Bluetooth v4.0 on-board
    o Ethernet 10/100/1000 Mbps and 10/100 Mbps controller on-board
    o JTAG debug connector available
    o Designed for industrial range purposes

    Signed-off-by: Pau Pajuelo
    Signed-off-by: Ladislav Michl
    Tested-by: Pau Pajuelo

    Pau Pajuelo
     
  • Convert IGEP board to use UBI volumes for U-Boot, its environment and
    kernel. With exception of first four sectors read by SoC BootROM whole
    NAND is UBI managed.

    Signed-off-by: Ladislav Michl
    Reviewed-by: Heiko Schocher
    Tested-by: Pau Pajuelo

    Ladislav Michl
     
  • Rename igep0033 to igep003x as IGEP SMARC AM335x module (igep0034)
    can use the same source files.

    Signed-off-by: Ladislav Michl
    Tested-by: Pau Pajuelo

    Ladislav Michl
     

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

    Jean-Jacques Hiblot
     

15 Mar, 2017

1 commit


22 Jan, 2017

1 commit

  • Move all of the status LED feature to drivers/led/Kconfig.
    The LED status definitions were moved from the board configuration
    files to the defconfig files.

    TBD: Move all of the definitions in the include/status_led.h to the
    relevant board's defconfig files.

    Tested boards: CL-SOM-AM57x, CM-T335

    Signed-off-by: Uri Mashiach

    Uri Mashiach
     

20 Jan, 2017

1 commit

  • commit: 65f83802b7a5b "serial: 16550: Add getfcr accessor"
    breaks u-boot commandline working with long commands
    sending to the board.

    Since the above patch, you have to setup the fcr register.

    For board/archs which enable OF_PLATDATA, the new field
    fcr in struct ns16550_platdata is not filled with a
    default value ...

    This leads in not setting up the uarts fifo, which ends
    in problems, when you send long commands to u-boots
    commandline.

    Detected this issue with automated tbot tests on am335x
    based shc board.

    The error does not popup, if you type commands. You need
    to copy&paste a long command to u-boots commandshell
    (or send a long command with tbot)

    Possible boards/plattforms with problems:
    ./arch/arm/cpu/arm926ejs/lpc32xx/devices.c
    ./arch/arm/mach-tegra/board.c
    ./board/overo/overo.c
    ./board/quipos/cairo/cairo.c
    ./board/logicpd/omap3som/omap3logic.c
    ./board/logicpd/zoom1/zoom1.c
    ./board/timll/devkit8000/devkit8000.c
    ./board/lg/sniper/sniper.c
    ./board/ti/beagle/beagle.c
    ./drivers/serial/serial_rockchip.c

    Signed-off-by: Heiko Schocher
    Signed-off-by: Ladislav Michl
    Tested-by: Adam Ford
    Reviewed-by: Tom Rini

    Heiko Schocher
     

15 Jan, 2017

2 commits


14 Nov, 2016

2 commits

  • Tested on IGEPv2 with Micron MT29F4G16ABBDA3W and
    Hynix H27S4G6F2DKA-BM

    Signed-off-by: Ladislav Michl
    Reviewed-by: Javier Martinez Canillas
    Tested-by: Javier Martinez Canillas

    Ladislav Michl
     
  • As a single U-Boot binary can now run on various board modifications,
    drop CONFIG_DISPLAY_BOARDINFO as it prints flash memory information
    too early to give us chance to easily detect it. Also saves few bytes
    as a bonus.

    Signed-off-by: Ladislav Michl
    Reviewed-by: Javier Martinez Canillas
    Tested-by: Javier Martinez Canillas

    Ladislav Michl
     

23 Jul, 2016

7 commits


15 Mar, 2016

1 commit

  • A few boards still use ns16550_platdata structures, but assume the structure
    is going to be in a specific order. By explicitly naming each entry,
    this should also help 'future-proof' in the event the structure changes.

    Tested on the Logic PD Torpedo + Wireless.

    I only changed a handful of devices that used the same syntax as the Logic
    board. Appologies if I missed one or stepped on toes. Thanks to Derald Woods
    and Alexander Graf.

    Signed-off-by: Adam Ford

    V6: Add fix to arch/arm/cpu/armv7/am33xx/board.c

    V5: Add fix to arch/arm/cpu/arm926ejs/lpc32xx/devices.c

    V4: Fix subject heading

    V3: Remove reg_offset out in all the structs. It was reverted out, and and if
    it did exist, it would get initialized to 0 by default.

    V2: I hastily copy-pasted the boards without looking at the UART number.
    This addresses 3 boards that use UART3 and not UART1.
    Reviewed-by: Mugunthan V N
    Reviewed-by: Simon Glass

    Adam Ford
     

20 Jan, 2016

1 commit

  • - move chip reset to separate function
    - use CONFIG_SMC911X_BASE instead of hardcoded value
    - remove unneeded local variable from board_eth_init.

    Signed-off-by: Ladislav Michl
    Reviewed-by: Tom Rini
    Acked-by: Enric Balletbo Serra
    Reviewed-by: Heiko Schocher

    Ladislav Michl
     

22 Nov, 2015

1 commit


23 Oct, 2015

1 commit


12 Sep, 2015

2 commits


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


30 Jan, 2015

1 commit

  • Use the STATUS_LED APIs for indicating a boot progress instead of
    show_boot_progress.

    This patch also fixes a problem introduced with commit b3f4ca1135 (dm: omap3:
    Move to driver model for GPIO and serial). After that commit the board doesn't
    boot. Looks like the problem is the gpio_request call inside the function
    show_boot_progress.

    Signed-off-by: Enric Balletbo i Serra

    Enric Balletbo i Serra
     

05 Dec, 2014

1 commit

  • Boards using the TWL4030 regulator may not all use the LDOs the same way
    (e.g. MMC2 power can be controlled by another LDO than VMMC2).
    This delegates TWL4030 MMC power initializations to board-specific functions,
    that may still call twl4030_power_mmc_init for the default behavior.

    Signed-off-by: Paul Kocialkowski
    Reviewed-by: Tom Rini
    [trini: Fix omap3_evm warning, add twl4030.h]
    Signed-off-by: Tom Rini

    Paul Kocialkowski
     

29 Oct, 2014

1 commit

  • 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