Eric Lee / smarc-uboot

02 Dec, 2014

1 commit

30 Jun, 2014

1 commit

  • 7feb8533f   ENGR00320125 iMX6: Change to use dynamical mmcroot ... Browse Code »

    The kernel changes to fix the mmcblk index with USDHC controllers
    as below:
    mmcblk0 ---> USDHC1
    mmcblk1 ---> USDHC2
    mmcblk2 ---> USDHC3
    mmcblk3 ---> USDHC4

    So in u-boot, the "mmcroot" must be updated together.

    When booting from SD/MMC device, change the "mmcroot" to
    dynamically set according to the boot USDHC controller.
    It is the same mechanism as "mmcdev" used for kernel image loading.
    Therefore, the uboot, kernel image, dtb and rootfs are required
    in same SD/MMC card.
    To disable the mmc dynamical detection, set the "mmcautodetect" to "no",
    then "mmcroot" and "mmcdev" will not be overwritten.

    When booting from other devices which needs to load kernel, dtb and
    rootfs from SD/MMC card, their "mmcdev" reset vaule is
    CONFIG_SYS_MMC_ENV_DEV and "mmcroot" reset value is CONFIG_MMCROOT.

    Signed-off-by: Ye.Li

    Ye.Li
     

20 Jun, 2014

1 commit

17 Jun, 2014

12 commits

13 Jun, 2014

3 commits

  • 230871db5   ENGR00315499-16 I2C: add I2C support on Sabre- board ... Browse Code »

    - add I2C support on Sabresd ,Sabreauto board.
    - add pfuze init code based on I2C transfer in Sabre* board file.

    Signed-off-by: Robin Gong
    Signed-off-by: Nitin Garg

    Nitin Garg
     
  • caf940dcc   ENGR00315499-11 ARM:imx6 Change static environment SD/MMC storage to dynamic ... Browse Code »

    imx6 boards (sabresd, sabreauto, arm2 and slevk) have multiple SD/MMC ports to boot.
    But current uboot hard code the SD/MMC port for environment variables storage. So
    if customer changes a port without modifying the configuration "CONFIG_SYS_MMC_ENV_DEV",
    error will issue at saving and loading environment.

    Implement a mechanism to detect SD/MMC port from SRC SMBR register, and override the
    default "mmc_get_env_devno". The "board_late_mmc_env_init" is used to set "mmcdev"
    when booting from SD/MMC port. Finally after booting from SD/MMC, the environment storage
    device and "mmcdev" are both set to current SD/MMC port. Customers don't need to re-build
    the image if booting from different SD/MMC port.

    This patch also adds SD1 and SD3 support to imx6slevk BSP, and adds support for sabreauto
    SD1 slot on base board.

    Signed-off-by: Ye.Li
    Signed-off-by: Nitin Garg

    Nitin Garg
     
  • 624f87698   ENGR00315499-10 ARM:imx6:sabresd/sabreauto Add android fastboot supporting ... Browse Code »

    Support android features:
    fastboot, booti command and recovery for sabresd SD, sabresd eMMC,
    sabreauto SD, sabreauto NAND.

    For all booting media (SD, eMMC, NAND), inherits the partitions layout
    from v2009.08. Fastboot will detect the booting media to replace
    hardcoding fastboot device. SATA is not supported.

    FDT is supported to use the "unused" fields in bootimg header which
    requires the FDT to be combined into the boot.img.
    For non-FDT boot.img, the "unused" fields should left to NULL and is
    compatible to boot.

    Signed-off-by: Ye.Li
    Signed-off-by: Nitin Garg

    Nitin Garg
     

28 May, 2014

2 commits

13 Jan, 2014

1 commit

18 Dec, 2013

1 commit

  • b47abc36a   i.MX6 (DQ/DLS): use macros for mux and pad declarations ... Browse Code »
    46

    This allows the use of either or both declarations from
    the files mx6q_pins.h and mx6dl_pins.h.

    All board files should include
    with one of the following defined in boards.cfg
    MX6Q - for boards targeting i.MX6Q or i.MX6D
    MX6DL - for boards targeting i.MX6DL
    MX6S - for boards targeting i.MX6S
    MX6QDL - for boards that support any of the above with
    run-time detection

    Pad declarations will be MX6_PAD_x for single-variant boards
    and MX6Q_PAD_x and MX6DL_PAD_x for boards supporting both
    processor classes.

    Signed-off-by: Eric Nelson
    Acked-by: Stefano Babic

    Eric Nelson
     

13 Nov, 2013

1 commit

20 Sep, 2013

1 commit

24 Jul, 2013

1 commit

03 Jun, 2013

2 commits

28 Apr, 2013

2 commits

  • 7e2173cf8   imx: iomux-v3: Include PKE and PUE to pad control pull definitions ... Browse Code »

    PUE requires PKE to mean something, as do pull values with PUE, so do not
    compell users to explicitly use PKE and PUE everywhere. This is also what is
    done on Linux and what has already been done for i.MX51.

    By the way, remove some unused pad control definitions.

    There is no change of behavior.

    Note that SPI_PAD_CTRL was defined by several boards with a pull value, but
    without PKE or PUE, which means that no pull was actually enabled in the pad.
    This might be a bug in those boards, but this patch does not change the
    behavior, so it just removes the meaningless pull value from those definitions.

    Signed-off-by: Benoît Thébaudeau

    Benoît Thébaudeau
     
  • 8f3ff11c1   imx: Homogenize and fix fuse register definitions ... Browse Code »

    IIM:
    - Homogenize prg_p naming (the reference manuals are not always self-consistent
    for that).
    - Add missing SCSx and bank registers.
    - Fix the number of banks on i.MX53.

    OCOTP:
    - Rename iim to ocotp in order to avoid confusion.
    - Rename fuse_data to read_fuse_data, and sticky to sw_sticky, according to the
    reference manual.
    - Merge the existing spinoff gp1 fuse definition on i.MX6.
    - Fix the number of banks on i.MX6.

    Signed-off-by: Benoît Thébaudeau
    Acked-by: Stefano Babic

    Benoît Thébaudeau
     

03 Apr, 2013

1 commit

07 Mar, 2013

1 commit

  • cfb8b9d33   i.MX6: consolidate pad names for multi-CPU boards ... Browse Code »

    Rename all i.MX6 pad declarations to MX6_PAD_x, so a board
    may support either i.MX6Quad/Dual (MX6Q) or i.MX6Dual-Lite/Solo
    (MX6DL) by including the proper header.

    Boards mx6qarm2, mx6qsabreauto, mx6qsabrelite, and mx6qsabresd
    only support MX6Q, so they include mx6q_pins.h.

    Signed-off-by: Eric Nelson

    Eric Nelson
     

16 Oct, 2012

5 commits