Eric Lee / smarc-uboot

12 Aug, 2015

1 commit

08 Aug, 2015

1 commit

06 Aug, 2015

4 commits

  • bcd5dfffe   dm: video: Add support for the Parade PS8622/625 bridge ... Browse Code »

    This chip provides an eDP to LVDS bridge which is useful for SoCs that don't
    support LVDS displays (or it would waste scarce pins). The setup is included
    in the device tree.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • b725dc458   i2c: Add a mux for GPIO-based I2C bus arbitration ... Browse Code »

    While I2C supports multi-master buses this is difficult to get right.
    The implementation on the master side in software is quite complex.
    Clock-stretching and the arbitrary time that an I2C transaction can take
    make it difficult to share the bus fairly in the face of high traffic.
    When one or more masters can be reset independently part-way through a
    transaction it is hard to know the state of the bus.

    This driver provides a scheme based on two 'claim' GPIOs, one driven by the
    AP (Application Processor, meaning the main CPU) and one driven by the EC
    (Embedded Controller, a small CPU aimed at handling system tasks). With
    these they can communicate and reliably share the bus. This scheme has
    minimal overhead and involves very little code. It is used on snow to
    permit the EC and the AP to share access to the main system PMIC and
    battery. The scheme can survive reboots by either side without difficulty.
    This scheme has been tested in the field with millions of devices.

    Since U-Boot runs on the AP, the terminology used is 'our' claim GPIO,
    meaning the AP's, and 'their' claim GPIO, meaning the EC's. This terminology
    is used by the device tree bindings in Linux also.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • 3d1957f0e   dm: i2c: Add support for multiplexed I2C buses ... Browse Code »
    37

    Add a new I2C_MUX uclass. Devices in this class can multiplex between
    several I2C buses, selecting them one at a time for use by the system.
    The multiplexing mechanism is left to the driver to decide - it may be
    controlled by GPIOs, for example.

    The uclass supports only two methods: select() and deselect().

    The current mux state is expected to be stored in the mux itself since
    it is the only thing that knows how to make things work. The mux can
    record the current state and then avoid switching unless it is necessary.
    So select() can be skipped if the mux is already in the correct state.
    Also deselect() can be made a nop if required.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • 12c7510f1   x86: Document how to write PIRQ information in the device tree ... Browse Code »

    Document the development flow on figuring out PIRQ information
    during the U-Boot porting.

    Signed-off-by: Bin Meng
    Acked-by: Simon Glass

    Bin Meng
     

05 Aug, 2015

5 commits

01 Aug, 2015

1 commit

29 Jul, 2015

1 commit

28 Jul, 2015

1 commit

25 Jul, 2015

1 commit

23 Jul, 2015

3 commits

22 Jul, 2015

6 commits

15 Jul, 2015

7 commits

09 Jul, 2015

1 commit

03 Jul, 2015

1 commit

01 Jul, 2015

2 commits

  • cdc9dd075   spi: zynq_spi: Add fdt support in driver ... Browse Code »

    Now zynq spi driver platform data is controlled by devicetree,
    enable the status by saying "okay" on respective board dts to use
    the devicetree generated platdata.

    Ex:
    &spi1 {
    status = "okay";
    };

    Signed-off-by: Jagan Teki
    Acked-by: Simon Glass
    Cc: Michal Simek
    Cc: Siva Durga Prasad Paladugu
    Tested-by: Jagan Teki

    Jagan Teki
     
  • a8a8fc9ce   dts: zynq: Add zynq spi controller nodes ... Browse Code »

    This patch adds zynq spi controller nodes in zynq-7000.dtsi.

    Signed-off-by: Jagan Teki
    Acked-by: Simon Glass
    Cc: Michal Simek
    Cc: Siva Durga Prasad Paladugu
    Tested-by: Jagan Teki

    Jagan Teki
     

11 Jun, 2015

1 commit

  • 0592115d4   README.scrapyard: add entries for dead AVR32 boards ... Browse Code »

    Some AVR32 boards were dropped by the following commits:
    9eb45aabe078 (avr32: delete non generic board favr-32-ezkit)
    e36930764471 (avr32: delete non generic board hammerhead)
    c62d2f8fc5c6 (avr32: delete non generic board mimc200)
    e5354b8a9e2a (avr32: delete non generic board's atstk100{3, 4, 6})

    Acked-by: Andreas Bießmann
    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

08 Jun, 2015

1 commit

  • 2d908fa08   autoboot.c: Remove CONFIG_AUTOBOOT_STOP_STR2 and CONFIG_AUTOBOOT_DELAY_STR2 ... Browse Code »

    These defines for a 2nd autoboot stop and delay string are nearly unused. Only
    sc3 defines CONFIG_AUTOBOOT_DELAY_STR2. And a patch to remove this most likely
    unmaintained board is also posted to the list.

    By removing these defines the code will become cleaner and moving the remaining
    compile options to Kconfig will get easier.

    Signed-off-by: Stefan Roese
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass
    Cc: Wolfgang Denk
    Cc: Heiko Schocher

    Stefan Roese
     

06 Jun, 2015

1 commit

05 Jun, 2015

1 commit

  • 10be5b5d3   fdt: Pass the device serial number through devicetree ... Browse Code »

    Before device-tree, the device serial number used to be passed to the kernel
    using ATAGs (on ARM). This is now deprecated and all the handover to the kernel
    should now be done using device-tree. Thus, this passes the serial-number
    property to the kernel using the serial-number property of the root node, as
    expected by the kernel.

    The serial number is a string that somewhat represents the device's serial
    number. It might come from some form of storage (e.g. an eeprom) and be
    programmed at factory-time by the manufacturer or come from identification
    bits available in e.g. the SoC.

    Signed-off-by: Paul Kocialkowski
    Reviewed-by: Simon Glass

    Paul Kocialkowski
     

04 Jun, 2015

1 commit