29 May, 2017

1 commit


23 May, 2017

2 commits


18 May, 2017

1 commit

  • So far we were not using the FIT image format to its full potential:
    The SPL FIT loader was just loading the first image from the /images
    node plus one of the listed DTBs.
    Now with the refactored loader code it's easy to load an arbitrary
    number of images in addition to the two mentioned above.
    As described in the FIT image source file format description, iterate
    over all images listed at the "loadables" property in the configuration
    node and load every image at its desired location.
    This allows to load any kind of images:
    - firmware images to execute before U-Boot proper (for instance
    ARM Trusted Firmware (ATF))
    - firmware images for management processors (SCP, arisc, ...)
    - firmware images for devices like WiFi controllers
    - bit files for FPGAs
    - additional configuration data
    - kernels and/or ramdisks
    The actual usage of this feature would be platform and/or board specific.

    Also update the FIT documentation to mention the new SPL feature and
    provide an example .its file to demonstrate its features.

    Signed-off-by: Andre Przywara
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Simon Glass
    Tested-by: Heiko Stuebner
    Reviewed-by: Kever Yang
    Tested-by: Kever Yang
    Tested-by: Jagan Teki
    Reviewed-by: Jagan Teki

    Andre Przywara
     

17 May, 2017

1 commit

  • Now that we have ACPI S3 support on Intel MinnowMax board, document
    some generic information of S3 and how to test it.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass
    Tested-by: Stefan Roese

    Bin Meng
     

15 May, 2017

1 commit

  • While in theory this value could be used in places outside of "omap5"
    (such as OMAP4), we only make use of it today in OMAP5, so place the
    Kconfig entry there. Given that Kconfig lets us provide a default, we
    drop CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC entirely. The contents of
    doc/README.omap-reset-time make a good help entry, so adjust them
    slightly and delete the file. Move the comment about range to where we
    use the value now, and have Kconfig enforce the upper bound.

    Signed-off-by: Tom Rini

    Tom Rini
     

12 May, 2017

1 commit


11 May, 2017

3 commits


10 May, 2017

3 commits

  • This driver is a simplified version of linux/drivers/leds/leds-bcm6358.c

    Signed-off-by: Álvaro Fernández Rojas
    Reviewed-by: Simon Glass

    Álvaro Fernández Rojas
     
  • This driver is a simplified version of linux/drivers/leds/leds-bcm6328.c,
    simplified to remove HW leds and blink fallbacks.

    Signed-off-by: Álvaro Fernández Rojas
    Reviewed-by: Simon Glass

    Álvaro Fernández Rojas
     
  • In some boards like the Raspberry Pi the initial bootloader will pass
    a DT to the kernel. When using U-Boot as such kernel, the board code in
    U-Boot should be able to provide U-Boot with this, already assembled
    device tree blob.

    This patch introduces a new config option CONFIG_OF_BOARD to use instead
    of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT
    from a board-specific funtion instead of bundling one with U-Boot or as
    a separated file. This allows boards like the Raspberry Pi to reuse the
    device tree passed from the bootcode.bin and start.elf firmware
    files, including the run-time selected device tree overlays.

    Signed-off-by: Alex Deymo
    Reviewed-by: Simon Glass

    Alex Deymo
     

08 May, 2017

1 commit


15 Apr, 2017

1 commit


14 Apr, 2017

3 commits


13 Apr, 2017

2 commits


09 Apr, 2017

1 commit


06 Apr, 2017

1 commit


05 Apr, 2017

4 commits

  • MiQi is rk3288 based development board with 1 or 2 GB SDRAM, 16 GB eMMC,
    micro SD card interface, 4 USB 2.0 ports, HDMI, gigabit Ethernet and
    expansion ports.

    Signed-off-by: Jernej Skrabec
    Reviewed-by: Kever Yang
    Reviewed-by: Eddie Cai
    Acked-by: Simon Glass

    Jernej Skrabec
     
  • Sort rk3288 boards in alphabetical order.

    Signed-off-by: Jernej Skrabec
    Reviewed-by: Kever Yang
    Reviewed-by: Eddie Cai
    Acked-by: Simon Glass

    Jernej Skrabec
     
  • The RK3399 does not have any boot selection pins and the BootROM probes
    the boot interfaces using the following boot-order:
    1. SPI
    2. eMMC (sdhci in DTS)
    3. SD card (sdmmc in DTS)
    4. USB loader
    For ease of deployment, the SPL stage should mirror the boot order of
    the ROM and use the same probing order (assuming that valid images can
    be detected by SPL) unless instructed otherwise. The boot-order can
    then be configured via the 'u-boot,spl-boot-order' property in the
    chosen-node of the DTS.

    While this approach is easily extensible to other boards, it is only
    implemented for the RK3399 for now, as the large SRAM on the RK3399
    makes this easy to fit the needed infrastructure into SPL and our
    production setup already runs with DM, OF_CONTROL and BLK in SPL.

    The new boot-order property is expected to be used in conjunction with
    FIT images (and all legacy image formats disabled via Kconfig).

    A boot-sequence with probing and fallthroughs from SPI via eMMC to SD
    card (i.e. &spiflash, &sdhci, &sdmmc) has been validated on the RK3399-Q7.

    Signed-off-by: Philipp Tomsich
    Tested-by: Klaus Goger
    Tested-by: Philipp Tomsich
    Acked-by: Simon Glass

    Philipp Tomsich
     
  • Building sd images for rk3188 requires more steps due to the needed split
    into TPL and SPL as loaders. Describe how to build an image for it in a
    separate paragraph in the READER.rockchip file.

    Signed-off-by: Heiko Stuebner
    Reviewed-by: Kever Yang

    Heiko Stübner
     

26 Mar, 2017

1 commit

  • This patch adds support for having a "fixed-link" to some other MAC
    (like some embedded switch-device).

    For this purpose we introduce a new phy-driver, called "Fixed PHY".

    Fixed PHY works only with CONFIG_DM_ETH enabled, since the fixed-link is
    described with a subnode below ethernet interface.

    Most ethernet drivers (unfortunately not all are following same scheme
    for searching/attaching phys) are calling "phy_connect(...)" for getting
    a phy-device.
    At this point we link in, we search here for a subnode called "fixed-
    link", once found we start phy_device_create(...) with the special phy-
    id PHY_FIXED_ID (0xa5a55a5a).

    During init the "Fixed PHY" driver has registered with this id and now
    gets probed, during probe we get all the details about fixed-link out of
    dts, later on the phy reports this values.

    Signed-off-by: Hannes Schmelzer

    Signed-off-by: Hannes Schmelzer
    Acked-by: Joe Hershberger
    Reviewed-by: Christian Gmeiner

    Hannes Schmelzer
     

24 Mar, 2017

2 commits

  • This replaces legacy arch/arc/lib/timer.c implementation and allows us
    to describe ARC Timers in Device Tree. Among other things that way we
    may properly inherit Timer's clock from CPU's clock s they really run
    synchronously.

    Tom Rini
     
  • This commit introduces timer driver for ARC.

    ARC timers are configured via ARC AUX registers so we use special
    functions to access timer control registers.

    This driver allows utilization of either timer0 or timer1
    depending on which one is available in real hardware. Essentially
    only existing timers should be mentioned in board's Device Tree
    description.

    Signed-off-by: Vlad Zakharov
    Reviewed-by: Simon Glass

    Vlad Zakharov
     

23 Mar, 2017

3 commits

  • Certain boards come in different variations by way of utilizing daughter
    boards, for example. These boards might contain additional chips, which
    are added to the main board's busses, e.g. I2C.

    The device tree support for such boards would either, quite naturally,
    employ the overlay mechanism to add such chips to the tree, or would use
    one large default device tree, and delete the devices that are actually
    not present.

    Regardless of approach, even on the U-Boot level, a modification of the
    device tree is a prerequisite to have such modular families of boards
    supported properly.

    Therefore, we add an option to make the U-Boot device tree (the actual
    copy later used by the driver model) writeable, and add a callback
    method that allows boards to modify the device tree at an early stage,
    at which, hopefully, also the application of device tree overlays will
    be possible.

    Signed-off-by: Mario Six
    Reviewed-by: Simon Glass
    Signed-off-by: Stefan Roese

    mario.six@gdsys.cc
     
  • The USB device should linked to VBUS regulator through "vbus-supply"
    DTS property.
    This patch adds handling for "vbus-supply" property inside the USB
    device entry for turning on the VBUS regulator upon the host adapter probe.

    Signed-off-by: Konstantin Porotchkin
    Cc: Stefan Roese
    Cc: Marek Vasut
    Cc: Nadav Haklai
    Cc: Neta Zur Hershkovits
    Cc: Igal Liberman
    Cc: Haim Boot
    Acked-by: Marek Vasut
    Signed-off-by: Stefan Roese

    Konstantin Porotchkin
     
  • Add support for "marvell,reset-gpio" property to mvebu DW PCIe
    driver.
    This option is valid when CONFIG_DM_GPIO=y

    Change-Id: Ic17c500449050c2fbb700731f1a9ca8b83298986
    Signed-off-by: Konstantin Porotchkin
    Signed-off-by: Rabeeh Khoury
    Cc: Stefan Roese
    Cc: Nadav Haklai
    Cc: Neta Zur Hershkovits
    Cc: Igal Liberman
    Cc: Haim Boot
    Signed-off-by: Stefan Roese

    Konstantin Porotchkin
     

21 Mar, 2017

2 commits


18 Mar, 2017

3 commits


17 Mar, 2017

2 commits

  • RK3399 support DDR3, LPDDR3, DDR4 sdram, this patch is porting from
    coreboot, support 4GB lpddr3 in this version.

    Signed-off-by: Kever Yang
    Added rockchip: tag:
    Signed-off-by: Simon Glass

    Kever Yang
     
  • Right now the u-boot,dm-pre-reloc flag will make each marked node
    always appear in both spl and tpl. But systems needing an additional
    tpl might have special constraints for each, like the spl needing to
    be very tiny.

    So introduce two additional flags to mark nodes for only spl or tpl
    environments and introduce a function dm_fdt_pre_reloc to automate
    the necessary checks in code instances checking for pre-relocation
    flags.

    The behaviour of the original flag stays untouched and still marks
    a node for both spl and tpl.

    Signed-off-by: Heiko Stuebner
    Reviewed-by: Simon Glass
    Tested-by: Kever Yang

    Heiko Stübner
     

23 Feb, 2017

1 commit