1. 12 Aug, 2016 1 commit
  2. 25 Jul, 2016 1 commit
  3. 11 Jul, 2016 5 commits
  4. 05 Jul, 2016 1 commit
  5. 12 Jun, 2016 1 commit
  6. 31 May, 2016 1 commit
    • Stephen Warren's avatar
      mmc: tegra: add basic Tegra186 support · 39f63332
      Stephen Warren authored
      Tegra186's MMC controller needs to be explicitly identified. Add another
      compatible value for it.
      Tegra186 will use an entirely different clock/reset control mechanism to
      existing chips, and will use standard clock/reset APIs rather than the
      existing Tegra-specific custom APIs. The driver support for that isn't
      ready yet, so simply disable all clock/reset usage if compiling for
      Tegra186. This must happen at compile time rather than run-time since the
      custom APIs won't even be compiled in on Tegra186. In the long term, the
      plan would be to convert the existing custom APIs to standard APIs and get
      rid of the ifdefs completely.
      The system's main eMMC will work without any clock/reset support, since
      the firmware will have already initialized the controller in order to
      load U-Boot. Hence the driver is useful even in this apparently crippled
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
  7. 17 Mar, 2016 2 commits
  8. 14 Mar, 2016 1 commit
  9. 16 Feb, 2016 1 commit
  10. 06 Feb, 2016 1 commit
  11. 24 Jan, 2016 1 commit
  12. 21 Jan, 2016 1 commit
  13. 13 Jan, 2016 1 commit
  14. 12 Jan, 2016 1 commit
    • Simon Glass's avatar
      dm: serial: Convert ns16550 driver to use driver model PCI API · fcc0a877
      Simon Glass authored
      Use the driver model version of the function to find the BAR. This updates
      the fdtdec function, of which ns16550 is the only user.
      The fdtdec_get_pci_bdf() function is dropped for several reasons:
      - with driver model we should use 'struct udevice *' rather than passing the
         device tree offset explicitly
      - there are no other users in the tree
      - the function parses for information which is already available in the PCI
      device structure (specifically struct pci_child_platdata which is available
      at dev_get_parent_platdata(dev)
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarBin Meng <bmeng.cn@gmail.com>
      Tested-by: default avatarBin Meng <bmeng.cn@gmail.com>
  15. 20 Dec, 2015 1 commit
    • Marek Vasut's avatar
      arm: socfpga: Allow DWC2 UDC probing from OF · ef4b01b2
      Marek Vasut authored
      The USB gadget framework does not support DM yet, so add this bit
      to let DWC2 UDC probe from OF on platforms which support it.
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Chin Liang See <clsee@altera.com>
      Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
      Cc: Lukasz Majewski <l.majewski@majess.pl>
      Cc: Lukasz Majewski <l.majewski@samsung.com>
  16. 01 Dec, 2015 1 commit
  17. 20 Nov, 2015 1 commit
  18. 12 Nov, 2015 1 commit
  19. 04 Nov, 2015 2 commits
  20. 23 Oct, 2015 1 commit
  21. 03 Oct, 2015 2 commits
    • Przemyslaw Marczak's avatar
      fdtdec: fix parsing 'reg' property with zero value in '#size-cells' · ff0a6358
      Przemyslaw Marczak authored
      After rework of lib/fdtdec.c by:
      commit: 02464e38 fdt: add new fdt address parsing functions
      the function fdtdec_get_addr() doesn't work as previous,
      because the implementation assumes that properties '#address-cells'
      and '#size-cells' are equal to 1, which can be not true sometimes.
      The new API introduced fdtdec_get_addr_size_auto_parent() for the 'reg'
      property parsing, but the implementation assumes, that #size-cells
      can't be less than 1.
      This causes that the following children's 'reg' property can't be reached:
      parent@0x0 {
           #address-cells = <1>;
           #size-cells = <0>;
           children@0x100 {
               reg = < 0x100 >;
      Change the condition value from '1' to '0', which allows parsing property
      with at least zero #size-cells, fixes the issue.
      Now, fdtdec_get_addr_size_auto_parent() works properly.
      Tested on: Odroid U3/X2, Trats, Trats2, Odroid XU3, Snow (by Simon).
      Signed-off-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Tested-by: default avatarSimon Glass <sjg@chromium.org>
    • Stephen Warren's avatar
      fdt: fix fdtdec_get_addr_size not to require any size cells · d93b9a07
      Stephen Warren authored
      fdtdec_get_addr_size() may be used in two cases:
      a) With sizep supplied, in which case both an address and a size are
      parsed from DT. In this case, the DT property must be large enough to
      contain both values.
      b) With sizep NULL, in which case only an address is parsed from DT.
      In this case, the DT property only need be large enough to contain this
      address value. Commit 02464e38 "fdt: add new fdt address parsing
      functions" broke this relaxed checking, and required the DT property to
      contain both an address and a size value in all cases.
      Fix fdtdec_get_addr_size() to vary ns based on whether the size value
      is being parsed from the DT or not. This is safe since the function only
      parses the first entry in the property, so the overall value of (na + ns)
      need not be accurate, since it is never used to step through the property
      data to find other entries. Besides, this fixed behaviour essentially
      matches the original behaviour before the patch this patch fixes. (The
      original code validated that the property was exactly the length of
      either na or (na + ns), whereas the current code only validates that the
      property is at least that long. For non-failure cases, the two behaviours
      are identical).
      Cc: Przemyslaw Marczak <p.marczak@samsung.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Thierry Reding <treding@nvidia.com>
      Cc: Bin Meng <bmeng.cn@gmail.com>
      Cc: Michal Suchanek <hramrach@gmail.com>
      Fixes: 02464e38 ("fdt: add new fdt address parsing functions")
      Reported-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Tested-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
  22. 15 Sep, 2015 1 commit
    • Stephen Warren's avatar
      fdt: add new fdt address parsing functions · 02464e38
      Stephen Warren authored
      fdtdec_get_addr_size() hard-codes the number of cells used to represent
      an address or size in DT. This is incorrect in many cases depending on
      the DT binding for a particular node or property (e.g. it is incorrect
      for the "reg" property). In most cases, DT parsing code must use the
      properties #address-cells and #size-cells to parse addres properties.
      This change splits up the implementation of fdtdec_get_addr_size() so
      that the core logic can be used for both hard-coded and non-hard-coded
      cases. Various wrapper functions are implemented that support cases
      where hard-coded cell counts should or should not be used, and where
      the client does and doesn't know the parent node ID that contains the
      properties #address-cells and #size-cells.
      dev_get_addr() is updated to use the new functions.
      Core functionality in fdtdec_get_addr_size_fixed() is widely tested via
      fdtdec_get_addr_size(). I tested fdtdec_get_addr_size_auto_noparent() and
      dev_get_addr() by manually modifying the Tegra I2C driver to invoke them.
      Much of the core implementation of fdtdec_get_addr_size_fixed(),
      fdtdec_get_addr_size_auto_parent(), and
      fdtdec_get_addr_size_auto_noparent() comes from Thierry Reding's
      previous commit "fdt: Fix fdtdec_get_addr_size() for 64-bit".
      Based-on-work-by: default avatarThierry Reding <treding@nvidia.com>
      Cc: Thierry Reding <treding@nvidia.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Michal Suchanek <hramrach@gmail.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Dropped #define DEBUG at the top of fdtdec.c:
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  23. 04 Sep, 2015 1 commit
    • Marek Vasut's avatar
      mmc: dw_mmc: Probe the MMC from OF · 129adf5b
      Marek Vasut authored
      Rework the driver to probe the MMC controller from Device Tree
      and make it mandatory. There is no longer support for probing
      from the ancient qts-generated header files.
      This patch now also removes previous temporary workaround.
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
      Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
      Cc: Tom Rini <trini@konsulko.com>
  24. 31 Aug, 2015 1 commit
  25. 26 Aug, 2015 1 commit
  26. 18 Aug, 2015 1 commit
  27. 14 Aug, 2015 2 commits
  28. 08 Aug, 2015 1 commit
    • Marek Vasut's avatar
      arm: socfpga: misc: Reset ethernet from OF · 6ab00db2
      Marek Vasut authored
      Reset the GMAC ethernets based on the "resets" OF node instead of ad-hoc
      hardcoded values in the U-Boot code. Since we don't have a proper reset
      framework in place yet, we have to do this slightly ad-hoc parsing of the
      OF tree instead.
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
  29. 06 Aug, 2015 3 commits
  30. 05 Aug, 2015 1 commit