Eric Lee / smarc-uboot

19 Feb, 2014

2 commits

06 Feb, 2014

1 commit

  • f016f8ca3   usb: mv_udc: Rename to ci_udc ... Browse Code »

    The mv_udc is not marvell-specific anymore. The mv_udc is used to drive
    generic ChipIdea CI13xxx series OTG cores, so rename the driver to ci_udc
    instead.

    Signed-off-by: Marek Vasut
    Cc: Eric Nelson
    Cc: Stefano Babic

    Marek Vasut
     

26 Jan, 2014

2 commits

18 Dec, 2013

1 commit

13 Nov, 2013

1 commit

10 Nov, 2013

1 commit

  • 85b8c5c4b   Merge branch 'iu-boot/master' into 'u-boot-arm/master' ... Browse Code »

    Conflicts:
    arch/arm/cpu/arm926ejs/mxs/Makefile
    board/compulab/cm_t35/Makefile
    board/corscience/tricorder/Makefile
    board/ppcag/bg0900/Makefile
    drivers/bootcount/Makefile
    include/configs/omap4_common.h
    include/configs/pdnb3.h

    Makefile conflicts are due to additions/removals of
    object files on the ARM branch vs KBuild introduction
    on the main branch. Resolution consists in adjusting
    the list of object files in the main branch version.
    This also applies to two files which are not listed
    as conflicting but had to be modified:

    board/compulab/common/Makefile
    board/udoo/Makefile

    include/configs/omap4_common.h conflicts are due to
    the OMAP4 conversion to ti_armv7_common.h on the ARM
    side, and CONFIG_SYS_HZ removal on the main side.
    Resolution is to convert as this icludes removal of
    CONFIG_SYS_HZ.

    include/configs/pdnb3.h is due to a removal on ARM side.
    Trivial resolution is to remove the file.

    Note: 'git show' will also list two files just because
    they are new:

    include/configs/am335x_igep0033.h
    include/configs/omap3_igep00x0.h

    Albert ARIBAUD
     

01 Nov, 2013

2 commits

  • a79854a90   board: arm: convert makefiles to Kbuild style ... Browse Code »

    Signed-off-by: Masahiro Yamada
    Cc: Albert ARIBAUD
    Cc: Andreas Bießmann
    Cc: Stefano Babic
    Cc: Prafulla Wadaskar
    Cc: Minkyu Kang
    Cc: Vipin Kumar
    Cc: Tom Warren
    Cc: Tom Rini

    Masahiro Yamada
     
  • 8f8b8949e   i.MX6: nitrogen6x: fix erase size in 6x_upgrade.txt ... Browse Code »

    The 6x_upgrade script is used to upgrade U-Boot in SPI-NOR
    on Nitrogen6x/SABRE Lite boards using U-Boot's 'sf' command.

    U-Boot is placed at offset 0x400 in flash, and the script
    currently only erases 0x50000 bytes. Since the current
    head is 319k, any additional features enabled in the
    configuration will exceed the space erased and cause errors
    re-programming the device.

    This patch increases the erase size to the full size of
    the region allocated for the U-Boot binary.

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

    Eric Nelson
     

21 Oct, 2013

2 commits

15 Oct, 2013

2 commits

11 Sep, 2013

1 commit

01 Sep, 2013

1 commit

22 Aug, 2013

1 commit

  • 8907c2c50   i.MX6: nitrogen6x: force HDMI onto IPU0/DI0 ... Browse Code »

    Our Linux kernel switches the HDMI connector onto IPU0/DI1,
    but the U-Boot display driver only supports IPU0/DI0 for the
    time being.

    Because of this, a soft re-boot will leave the HDMI output
    connected to the wrong display port and prevent video from
    being displayed.

    Signed-off-by: Eric Nelson

    Eric Nelson
     

31 Jul, 2013

1 commit

27 Jul, 2013

2 commits

  • 10f779da5   imx: nitrogen6x: mx6qsabrelite: Add support for DVI monitors ... Browse Code »

    A little background is probably appropriate for this patch.

    Since "the beginning" of usage of the SABRE Lite and Nitrogen6x
    boards, DVI detection has been somewhat broken.

    Some (most) DVI monitors don't produce the "HPD" bit in
    the PHY_STAT0 register, but do show proper toggling of the
    RX_SENSE0..3 bits.

    Creating a new the bit-mask to include all five bits and
    modifying the 'hdmidet' command and internal detection
    routines allows these monitors to function properly in U-Boot.

    A related patch to our kernels allows things to work under
    Linux:
    https://github.com/boundarydevices/linux-imx6/commit/7d8752905c118af9063738a533227de0b2f6ecd4

    Signed-off-by: Robert Winkler
    Acked-by: Stefano Babic

    Robert Winkler
     
  • 5ea7f0e32   mx6: Factor out common HDMI setup code ... Browse Code »

    Instead of duplicating HDMI setup code for every mx6 board, factor out the common code

    Signed-off-by: Pardeep Kumar Singla
    Acked-By: Eric Nelson

    Pardeep Kumar Singla
     

26 Jul, 2013

1 commit

24 Jul, 2013

1 commit

21 Jul, 2013

1 commit

  • fdf86c202   ddr cfg: DRAM_RESET needs 0x00020030 ... Browse Code »

    The old value of 0x000e0030 will cause ethernet
    timeout issues on the sabrelite and possibly other
    boards using the KSZ9021.
    I have no explanation as to why.

    But this is a correct change, the TRM will be updated
    to show that 00b is the only valid setting for bits
    19-18 of DRAM_RESET.

    My thanks go to Liu Hui(Jason) for this information.

    Acked-by: Fabio Estevam
    Acked-by: Stefano Babic
    Signed-off-by: Troy Kisky

    Troy Kisky
     

08 Jun, 2013

1 commit

03 Jun, 2013

1 commit

  • 0c54f4b7c   mx6: mx6qsabrelite/nitrogen6x: Remove incorrect setting of gpio CS signal ... Browse Code »

    The number of gpio signal is packed inside CONFIG_SF_DEFAULT_CS macro
    (shifted and or'ed with chip select), so it's incorrect to pass
    that macro directly as an argument to gpio_direction_output() call.

    Also, SPI driver sets the direction and initial value of a gpio,
    used as a chip select signal, before any actual activity happens
    on the bus.

    So, it is safe to just remove the gpio_direction_output call,
    that works incorrectly, thus making no effect, anyway.

    Signed-off-by: Andrew Gabbasov
    Tested-by: Robert Winkler
    Acked-by: Dirk Behme

    Andrew Gabbasov
     

30 May, 2013

1 commit

10 May, 2013

1 commit

  • b1e6c4c3d   Fix references to the documentation files ... Browse Code »

    Many boot image configuration files refer to the
    appropriate documentation file, but these references
    contain typos in the directory and file name. Fix
    them. Also fix reference to doc/README.SPL file.

    Signed-off-by: Anatolij Gustschin
    Cc: Prafulla Wadaskar
    Cc: Stefano Babic
    Acked-by: Stefano Babic

    Anatolij Gustschin
     

28 Apr, 2013

1 commit

  • 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
     

26 Apr, 2013

1 commit

  • 492938a33   nitrogen6x: Setup CCM_CCOSR register ... Browse Code »

    CKO1 drives sgtl5000 codec clock on nitrogen boards and wandboard.

    Doing this setup in the bootloader will allow us to remove a lot of code in
    arch/arm/mach-imx/mach-imx6q.c from the mainline kernel.

    Also, according to Eric Nelson: "enabling the clock will
    remove squeal after an ungraceful reboot (watchdog) if hooked up to speakers."

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

03 Apr, 2013

2 commits

  • 38e700772   mx6: Fix get_board_rev() for the mx6 solo case ... Browse Code »

    When booting a Freescale kernel 3.0.35 on a Wandboard solo, the get_board_rev()
    returns 0x62xxx, which is not a value understood by the VPU
    (Video Processing Unit) library in the kernel and causes the video playback to
    fail.

    The expected values for get_board_rev are:
    0x63xxx: For mx6quad/dual
    0x61xxx: For mx6dual-lite/solo

    So adjust get_board_rev() accordingly and make it as weak function, so that we
    do not need to define it in every mx6 board file.

    Signed-off-by: Fabio Estevam
    Acked-by: Dirk Behme
    Acked-by: Eric Nelson

    Fabio Estevam
     
  • aad4659a2   mmc: i.MX6: fsl_esdhc: Define maximum bus width supported by a board ... Browse Code »

    Maximum bus width supported by some i.MX6 boards is not 8bit like
    others. In case where both host controller and card support 8bit transfers,
    they agree to communicate on 8bit interface while some boards support only 4bit interface.
    Due to this reason the mmc 8bit default mode fails on these boards. To rectify this,
    define maximum bus width supported by these boards (4bit). If max_bus_width is not
    defined, it is 0 by default and 8bit width support will be enabled in host
    capabilities otherwise host capabilities are modified accordingly.

    It is tested with a MMCplus card.

    Signed-off-by: Abbas Raza
    cc: stefano Babic
    cc: Andy Fleming
    Acked-by: Dirk Behme
    Acked-by: Andrew Gabbasov

    Abbas Raza
     

15 Mar, 2013

1 commit

13 Mar, 2013

1 commit