Skip to content
Snippets Groups Projects
  1. Sep 06, 2016
  2. Aug 15, 2016
  3. Aug 08, 2016
  4. Aug 04, 2016
  5. Jul 08, 2016
  6. Jun 19, 2016
    • Stephen Warren's avatar
      Add a reset driver framework/uclass · 89c1e2da
      Stephen Warren authored
      
      A reset controller is a hardware module that controls reset signals that
      affect other hardware modules or chips.
      
      This patch defines a standard API that connects reset clients (i.e. the
      drivers for devices affected by reset signals) to drivers for reset
      controllers/providers. Initially, DT is the only supported method for
      connecting the two.
      
      The DT binding specification (reset.txt) was taken from Linux kernel
      v4.5's Documentation/devicetree/bindings/reset/reset.txt.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      89c1e2da
  7. Jun 12, 2016
  8. May 31, 2016
    • Stephen Warren's avatar
      gpio: add Tegra186 GPIO driver · 074a1fdd
      Stephen Warren authored
      
      Tegra186's GPIO controller register layout is significantly different from
      previous chips, so add a new driver for it. In fact, there are two
      different GPIO controllers in Tegra186 that share a similar register
      layout, but very different port mapping. This driver covers both.
      
      The DT binding is already present in the Linux kernel (in linux-next via
      the Tegra tree so far).
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Reviewed-by: Simon Glass <sjg@chromium.org> # v1
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      074a1fdd
  9. May 27, 2016
    • Stephen Warren's avatar
      Add a mailbox driver framework/uclass · 6238935d
      Stephen Warren authored
      
      A mailbox is a hardware mechanism for transferring small message and/or
      notifications between the CPU on which U-Boot runs and some other device
      such as an auxilliary CPU running firmware or a hardware module.
      
      This patch defines a standard API that connects mailbox clients to mailbox
      providers (drivers). Initially, DT is the only supported method for
      connecting the two.
      
      The DT binding specification (mailbox.txt) was taken from Linux kernel
      v4.5's Documentation/devicetree/bindings/mailbox/mailbox.txt.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      6238935d
  10. May 24, 2016
  11. May 23, 2016
  12. May 20, 2016
  13. Apr 13, 2016
  14. Apr 06, 2016
  15. Apr 01, 2016
  16. Mar 22, 2016
  17. Mar 17, 2016
    • Simon Glass's avatar
      x86: broadwell: Add a pinctrl driver · b24f5c4f
      Simon Glass authored
      
      GPIO pins need to be set up on start-up. Add a driver to provide this,
      configured from the device tree.
      
      The binding is slightly different from the existing ICH6 binding, since that
      is quite verbose. The new binding should be just as extensible.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: default avatarBin Meng <bmeng.cn@gmail.com>
      b24f5c4f
    • Simon Glass's avatar
      x86: dts: Update the pinctrl binding a little · c13dcb3d
      Simon Glass authored
      
      Make a few minor updates to make the meaning clearer.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarBin Meng <bmeng.cn@gmail.com>
      c13dcb3d
    • Simon Glass's avatar
      x86: Add an ICH6 pin configuration driver · 7ac99be6
      Simon Glass authored
      
      Add a driver which sets up the pin configuration on x86 devices with an ICH6
      (or later) Platform Controller Hub.
      
      The driver is not in the pinctrl uclass due to some oddities of the way x86
      devices work:
      
      - The GPIO controller is not present in I/O space until it is set up
      - This is done by writing a register in the PCH
      - The PCH has a driver which itself uses PCI, another driver
      - The pinctrl uclass requires that a pinctrl device be available before any
      other device can be probed
      
      It would be possible to work around the limitations by:
      - Hard-coding the GPIO address rather than reading it from the PCH
      - Using special x86 PCI access to set the GPIO address in the PCH
      
      However it is not clear that this is better, since the pin configuration
      driver does not actually provide normal pin configuration services - it
      simply sets up all the pins statically when probed. While this remains the
      case, it seems better to use a syscon uclass instead. This can be probed
      whenever it is needed, without any limitations.
      
      Also add an 'invert' property to support inverting the input.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarBin Meng <bmeng.cn@gmail.com>
      7ac99be6
  18. Mar 14, 2016
  19. Feb 01, 2016
  20. Jan 28, 2016
  21. Jan 27, 2016
Loading