1. 14 Jul, 2016 1 commit
  2. 07 Jul, 2016 14 commits
  3. 06 Jul, 2016 8 commits
  4. 05 Jul, 2016 8 commits
  5. 01 Jul, 2016 2 commits
    • Jon Hunter's avatar
      bus: Add support for Tegra ACONNECT · 46a88534
      Jon Hunter authored
      Add a bus driver for the Tegra ACONNECT which is used to interface to
      various devices within the Audio Processing Engine (APE). The purpose
      of the bus driver is to register child devices that are accessed via
      the ACONNECT bus and through the device parent child relationship,
      ensure that the appropriate power domain and clocks are enabled for
      the ACONNECT when any of the child devices are active. Hence, the
      ACONNECT driver simply enables runtime-pm for the ACONNECT device
      so that when a child device is resumed, it will enable the power-domain
      and clocks associated with the ACONNECT.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      46a88534
    • Jon Hunter's avatar
      dt-bindings: bus: Add documentation for Tegra210 ACONNECT · 894b68e1
      Jon Hunter authored
      Add binding documentation for the Tegra ACONNECT bus that is part of the
      Audio Processing Engine (APE) on Tegra210. The ACONNECT bus is used to
      access devices within the APE subsystem. The APE is located in a
      separate power domain and so accesses made to the ACONNECT require the
      power domain to be enabled as well as some platform specific clocks.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Acked-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      894b68e1
  6. 30 Jun, 2016 7 commits
    • Thierry Reding's avatar
      soc/tegra: Stub out PCIe IRQ workaround on 64-bit ARM · 8582f6d1
      Thierry Reding authored
      The PCIe host controller found on Tegra20 has a hardware bug that causes
      PCIe interrupts to get lost when LP2 is enabled. Stub out the workaround
      on 64-bit ARM because none of the more recent Tegra SoC generations seem
      to have this bug anymore.
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      8582f6d1
    • Jon Hunter's avatar
      soc/tegra: pmc: Enable XUSB partitions on boot · 8df12745
      Jon Hunter authored
      The Tegra XHCI driver does not currently manage the Tegra XUSB power
      partitions and so it these partitions have not been enabled by the
      bootloader then the system will crash when probing the XHCI device.
      
      While proper support for managing the power partitions is being
      developed to the XHCI driver for Tegra, for now power on all the XUSB
      partitions for USB host and super-speed on boot if the XHCI driver is
      enabled.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      8df12745
    • Jon Hunter's avatar
      soc/tegra: pmc: Initialise power partitions early · e2d17960
      Jon Hunter authored
      If CONFIG_PM_GENERIC_DOMAINS is not enabled, then power partitions
      associated with a device will not be enabled automatically by the PM
      core when the device is in use. To avoid situations where a device in
      a power partition is to be used but the partition is not enabled,
      initialise the power partitions for Tegra early in the boot process and
      if CONFIG_PM_GENERIC_DOMAINS is not enabled, then power on all
      partitions defined in the device-tree blob.
      
      Note that if CONFIG_PM_GENERIC_DOMAINS is not enabled, after the
      partitions are turned on, the clocks and resets used as part of the
      sequence for turning on the partition are released again as they are no
      longer needed by the PMC driver. Another benefit of this is that this
      avoids any issues of sharing resets between the PMC driver and other
      device drivers that may wish to independently control a particular
      reset.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      e2d17960
    • Jon Hunter's avatar
      soc/tegra: pmc: Add specific error messages · c2710ac9
      Jon Hunter authored
      When initialising a powergate, only a single error message is shown if
      the initialisation fails. Add more error messages to give specific
      details of what failed if the initialisation failed and remove the
      generic failure message.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      c2710ac9
    • Thierry Reding's avatar
      soc/tegra: pmc: Use whitespace more consistently · da8f4b45
      Thierry Reding authored
      Use blank lines after blocks and before labels for consistency with the
      existing code in the file.
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      da8f4b45
    • Jon Hunter's avatar
      soc/tegra: pmc: Don't probe PMC if early initialisation fails · a83f1fc3
      Jon Hunter authored
      Commit 0259f522 ('soc/tegra: pmc: Restore base address on probe
      failure') fixes an issue where the PMC base address pointer is not
      restored on probe failure. However, this fix creates another problem
      where if early initialisation of the PMC driver fails and an initial
      mapping for the PMC address space is not created, then when the PMC
      device is probed, the PMC base address pointer will not be valid and
      this will cause a crash when tegra_pmc_init() is called and attempts
      to access a register.
      
      Although the PMC address space is mapped a 2nd time during the probe
      and so this could be fixed by populating the base address pointer
      earlier during the probe, this adds more complexity to the code.
      Moreover, the PMC probe also assumes the the soc data pointer is also
      initialised when the device is probed and if not will also lead to a
      crash when calling tegra_pmc_init_tsense_reset(). Given that if the
      early initialisation does fail then something bad has happen, it seems
      acceptable to allow the PMC device probe to fail as well. Therefore, if
      the PMC base address pointer or soc data pointer are not valid when
      probing the PMC device, WARN and return an error.
      
      Fixes: 0259f522 ('soc/tegra: pmc: Restore base address on probe failure')
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      a83f1fc3
    • Jon Hunter's avatar
      soc/tegra: pmc: Add missing of_node_put() · b69a6258
      Jon Hunter authored
      Add missing of_node_put() in PMC early initialisation function to avoid
      leaking the device nodes.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      [treding@nvidia.com: squash in a couple more of_node_put() calls]
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      b69a6258