1. 13 Mar, 2017 1 commit
  2. 28 Jan, 2017 1 commit
  3. 29 Dec, 2016 1 commit
    • Masahiro Yamada's avatar
      mmc: complete unfinished move of CONFIG_MMC · c2726995
      Masahiro Yamada authored
      Commit 7a777f6d ("mmc: Add generic Kconfig option") created
      a Kconfig entry for this option without any actual moves, then
      commit 44c79879 ("sunxi: Use Kconfig CONFIG_MMC") moved
      instances only for SUNXI.
      We generally do not like such partial moves.  This kind of work
      is automated by tools/moveconfig.py, so it is pretty easy to
      complete this move.
      I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
      This shortens the configs and will ease new board porting.
      This commit was created as follows:
      [1] Edit Kconfig (remove the "depends on", add the "default",
          copy the prompt and help message from Linux)
      [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarJaehoon Chung <jh80.chung@samsung.com>
  4. 28 Oct, 2016 1 commit
  5. 12 Oct, 2016 1 commit
  6. 26 Sep, 2016 1 commit
  7. 19 Sep, 2016 1 commit
  8. 16 Sep, 2016 7 commits
  9. 09 Sep, 2016 1 commit
  10. 07 Sep, 2016 1 commit
  11. 09 Jun, 2016 1 commit
  12. 25 Apr, 2016 2 commits
  13. 14 Jan, 2016 3 commits
    • Phil Sutter's avatar
      mvebu: Support Synology DS414 · aefb8f4c
      Phil Sutter authored
      This adds support for the MV78230 based DS414 NAS by Synology. The
      relevant bits have been extracted from the 'synogpl-5004-armadaxp'
      package Synology kindly published, garnished with a fair amount of
      Sadly, support is far from perfect. The major parts I have failed in
      are SATA and XHCI support. Details about these and some other things
      Device Tree
      The device tree file armada-xp-synology-ds414.dts has been copied from
      Linux and enhanced by recent U-Boot specific changes to
      SATA Support
      There is a Marvell 88SX7042 controller attached to PCIe which is
      supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
      I'm not sure if extending the latter to support PCI devices is worth the
      effort at all. Porting sata_mv from Linux exceeded my brain's
      capacities. :(
      XHCI Support
      There is an EtronTech EJ168A XHCI controller attached to PCIe which
      drives the two rear USB3 ports. After a bit of playing around I managed
      to get it recognized by xhci-pci, but never was able to access any
      devices attached to it. Enabling it in ds414 board config shows that it
      does not respond to commands for whatever reason. The (somewhat) bright
      side to it is that it is not even supported in Synology's customized
      U-Boot, but that also means nowhere to steal the relevant bits from.
      EHCI Support
      This seems functional after issuing 'usb start'. At least it detects USB
      storage devices, and IIRC reading from them was OK. OTOH Linux fails to
      register the controller if 'usb start' wasn't given before in U-Boot.
      According to Synology sources, this board seems to support USB device
      (gadget?) mode. Though I didn't play around with it.
      PCIe Support
      This is fine, but trying to gate the clocks of unused lanes will hang
      PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.
      DDR3 Training
      Marvell/Synology uses eight PUPs instead of four. Does not look like
      this is meant to be customized in mainline U-Boot at all. OTOH I have
      no idea what a "PUP" actually is.
      PEX Init
      Synology uses different values than mainline U-Boot with this patch:
      pex_max_unit_get returns 2, pex_max_if_get returns 7 and
      max_serdes_lines is set to 7. Not changing this seems to not have an
      impact, although I'm not entirely sure it does not cause issues I am not
      aware of.
      Static Environment
      This allows to boot stock Synology firmware at least. In order to be a
      little more flexible when it comes to booting custom kernels, do not
      only load zImage partition, but also rd.gz into memory. This way it is
      possible to use about 7MB for kernel with piggyback initramfs.
      Signed-off-by: default avatarPhil Sutter <phil@nwl.cc>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
    • Stefan Roese's avatar
      arm: mvebu: Add armada-xp-maxbcm.dts for maxbcm board · 18c1272f
      Stefan Roese authored
      This is needed for the upcoming ethernet DM conversion of the maxbcm
      board. The configuration of the PHY is then extracted from the DT
      instead of using the defines from the config header.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Luka Perkov <luka.perkov@sartura.hr>
    • Stefan Roese's avatar
      arm: mvebu: Add DM and OF_CONTROL support to SPL · 6451223a
      Stefan Roese authored
      This patch adds full DM support to the SPL on MVEBU. Currently
      only serial is supported. Other drivers will follow.
      This patch also adds the necessary config values for the DEBUG UART
      to the MVEBU defconfig files. This came in handy while implementing
      this DM support.
      Additionally, the mvebu specific SPL linker script is removed and
      this common one is used instead:
      This common linker script already handles all special cases. No need
      to reinvent the wheel for MVEBU here.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Luka Perkov <luka.perkov@sartura.hr>
      Cc: Dirk Eibach <dirk.eibach@gdsys.cc>
      Cc: Simon Glass <sjg@chromium.org>
  14. 25 Nov, 2015 1 commit
  15. 22 Nov, 2015 1 commit
  16. 21 Oct, 2015 1 commit
    • Stefan Roese's avatar
      arm: mvebu: Add DM (driver model) support · 9cffb233
      Stefan Roese authored
      This patch adds driver model support for some Marvell MVEBU SoC's. Including
      Armada XP and 38x. All 3 currently mainlined boards are converted. DM is now
      selected automatically for MVEBU platforms.
      With this DM support now available for MVEBU, hardcoding the base addresses
      and other information is not necessary any more. Probing should be done
      by using the values provided via the device tree now instead. For this
      the driver also need to be converted to DM. Patches for some of the drivers
      will follow.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Luka Perkov <luka.perkov@sartura.hr>
  17. 20 Oct, 2015 1 commit
  18. 01 Jul, 2015 1 commit
  19. 26 Jun, 2015 2 commits
  20. 01 Jun, 2015 1 commit
  21. 12 May, 2015 1 commit
  22. 15 Mar, 2015 1 commit
  23. 06 Feb, 2015 1 commit
  24. 23 Oct, 2014 1 commit