1. 15 4月, 2016 1 次提交
  2. 14 4月, 2016 8 次提交
  3. 12 4月, 2016 6 次提交
    • H
      sunxi: Add defconfig and dts file for Orange Pi One SBC · ec770dba
      Hans de Goede 提交于
      The Orange Pi One SBC, is a stripped down version of the popular
      Orange Pi PC. The one is a H3 based SBC, with 512M of RAM,
      micro-sd slot, 1 host usb, 1 otg usb, hdmi and 100Mbit ethernet.
      
      The dts is identical to the dts submitted to the upstream kernel.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Acked-by: NIan Campbell <ijc@hellion.org.uk>
      ec770dba
    • H
      sunxi: Enable CMD_GPIO on all sunxi boards · 88bb800d
      Hans de Goede 提交于
      We have CONFIG_CMD_GPIO=y in almost all sunxi boards, but after
      its Kconfig conversion it has ended up missing on some recently
      added boards.
      
      Simply select it for ARCH_SUNXI, so that we get it on all
      sunxi boards for both a consistent user experience and simpler
      defconfig files.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Acked-by: NIan Campbell <ijc@hellion.org.uk>
      88bb800d
    • H
      sunxi: Enable usb ports on the Sinovoip BPI M3 · b24f7f00
      Hans de Goede 提交于
      DLDO3 is used to provide Port-D power and PD is used for the
      usb-hub / sata-5v enable pins. The 2.5V comes from the schematic
      and matches the factory image fex file.
      
      The dts changes are the minimal changes needed for u-boot to
      pick-up the usb host controllers. The upstream kernel does not
      (yet) have usb host support.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Acked-by: NIan Campbell <ijc@hellion.org.uk>
      b24f7f00
    • H
      sunxi: Set DCDC1 to 3.3V on the Sinovoip BPI M3 · e6c9cec4
      Hans de Goede 提交于
      This is the value used in the fex file of the manufacturer images,
      and also the DCDC1 default. Sometimes lower values are used to save
      battery power, but that does not apply to a SBC.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Acked-by: NIan Campbell <ijc@hellion.org.uk>
      e6c9cec4
    • S
      ARM: add Raspberry Pi 3 64-bit config · d22a7657
      Stephen Warren 提交于
      On all Pis so far, the VC FW provides a short stub to set up the ARM CPU
      before entering the kernel (a/k/a U-Boot for us). This feature is not
      currently supported by the VC FW when booting in 64-bit mode. However,
      this feature will likely appear in the near future, and this U-Boot port
      assumes that such a feature is in place. Without that feature, or a
      temporary workaround described below, U-Boot will not boot.
      
      Once the VC FW does provide the ARM stub, u-boot.bin built for rpi_3 can
      be used drectly as kernel7.img, in the same way as any other RPi port. The
      following config.txt is required:
      
          # Fix mini UART input frequency, and setup/enable up the UART.
          # Without this option, U-Boot will not boot, even if you don't care
          # about the serial console. This option will always be required for
          # all RPi3 use-cases, unless the PL011 UART is used, which is not
          # yet supported by rpi_3* builds of U-Boot.
          enable_uart=1
          # Boot in AArch64 (64-bit) mode.
          # It is possible that a future VC FW will remove the need for this
          # option, instead auto-setting 32-/64-bit mode based on the "kernel"
          # filename present on the SD card.
          arm_control=0x200
      
      Prior to the VC FW providing the ARM boot stub, you can use the following
      steps to build an equivalent stub into the U-Boot binary:
      
      git clone https://github.com/swarren/rpi-3-aarch64-demo.git \
          ../rpi-3-aarch64-demo
      (cd ../rpi-3-aarch64-demo && ./build.sh)
      Build U-Boot for rpi_3 in the usual way
      cat ../rpi-3-aarch64-demo/armstub64.bin u-boot.bin > u-boot.bin.stubbed
      Use u-boot.bin.stubbed as kernel7.img on the Pi SD card.
      
      In this case, the following additional entries are required in config.txt:
      
          # Tell the FW to load the kernel image at address 0, the reset vector.
          kernel_old=1
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      d22a7657
    • S
      arm: socfpga: sr1500: Remove USB_GADGET · 4861be7e
      Sam Protsenko 提交于
      "buildman" tool revealed that USB_GADGET was enabled by mistake for this
      board in process of moving that option to Kconfig. Remove it to bring
      things back to correct state.
      Signed-off-by: NSam Protsenko <semen.protsenko@linaro.org>
      Acked-by: NStefan Roese <sr@denx.de>
      4861be7e
  4. 10 4月, 2016 2 次提交
  5. 07 4月, 2016 1 次提交
  6. 05 4月, 2016 3 次提交
  7. 04 4月, 2016 2 次提交
  8. 02 4月, 2016 5 次提交
    • M
      board: Add Qualcomm Dragonboard 410C support · 626f048b
      Mateusz Kulikowski 提交于
      This commit add support for 96Boards Dragonboard410C.
      It is board based on APQ8016 Qualcomm SoC, complying with
      96boards specification.
      Features (present out of the box):
      - 4x Cortex A53 (ARMv8)
      - 2x USB Host port
      - 1x USB Device port
      - 4x LEDs
      - 1x HDMI connector
      - 1x uSD connector
      - 3x buttons (Power, Vol+, Vol-/Reset)
      - WIFI, Bluetooth with integrated antenna
      - 8GiB eMMC
      
      U-Boot boots chained with fastboot in 64-bit mode.
      For detailed build instructions see readme.txt in board directory.
      Signed-off-by: NMateusz Kulikowski <mateusz.kulikowski@gmail.com>
      Tested-by: NSimon Glass <sjg@chromium.org>
      626f048b
    • M
      spmi: Add sandbox test driver · d33776e4
      Mateusz Kulikowski 提交于
      This patch adds emulated spmi bus controller with part of
      pm8916 pmic on it to sandbox and tests validating SPMI uclass.
      Signed-off-by: NMateusz Kulikowski <mateusz.kulikowski@gmail.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      d33776e4
    • M
      Migrate CONFIG_ULPI* to Kconfig · 5493a32c
      Mateusz Kulikowski 提交于
      Move CONFIG_USB_ULPI* from headers to defconfigs for boards that use it.
      Also - add CONFIG_USB where necesarry - all boards use it,
      but some are not defining it explicitly.
      
      Affected boards:
      colibri_t20, harmony, mcx, mt_ventoux, twister,
      zynq_(picozed, zc702, zc706, zed, zybo)
      Signed-off-by: NMateusz Kulikowski <mateusz.kulikowski@gmail.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      5493a32c
    • P
      kc1: Select libfdt to allow running devicetree-based kernels · 163d8764
      Paul Kocialkowski 提交于
      Selecting CONFIG_OF_LIBFDT allows running recent mainline kernels.
      Signed-off-by: NPaul Kocialkowski <contact@paulk.fr>
      163d8764
    • S
      rpi: BCM2837 and Raspberry Pi 3 32-bit support · f031f501
      Stephen Warren 提交于
      The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
      the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
      or 64-bit mode. 32-bit mode is the current default selected by the
      VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
      U-Boot for the Raspberry Pi 3.
      
      >From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
      change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
      only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
      UART to connect to the SoC. By default, the PL011 is used for this purpose
      since it has larger FIFOs than the other "mini" UART. However, this can
      be configured via the VideoCore firmware's config.txt file. This patch
      hard-codes use of the mini UART in the RPi 3 port. If your system uses the
      PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
      port instead. A future change might determine which UART to use at
      run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
      together.
      
      The mini UART has some limitations. One externally visible issue in the
      BCM2837 integration is that the UART divides the SoC's "core clock" to
      generate the baud rate. The core clock is typically variable, and under
      control of the VideoCore firmware for thermal management reasons. If the
      VC FW does modify the core clock rate, UART communication will be
      corrupted since the baud rate will vary from the expected value. This was
      not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
      work around this, the VideoCore firmware can be told not to modify the SoC
      core clock. However, the only way this can happen and be thermally safe is
      to limit the core clock to a low/minimum frequency. This leaves
      performance on the table for use-cases that don't care about a UART
      console. Consequently, use of the mini UART console must be explicitly
      requested by entering the following line into config.txt:
      
          enable_uart=1
      
      A recent version of the VC firmware is required to ensure that the mini
      UART is fully and correctly initialized by the VC FW; at least
      firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
      core clock See: https://github.com/raspberrypi/firmware/issues/572".
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      f031f501
  9. 01 4月, 2016 3 次提交
  10. 31 3月, 2016 6 次提交
  11. 29 3月, 2016 1 次提交
  12. 27 3月, 2016 1 次提交
  13. 26 3月, 2016 1 次提交