An error occurred fetching the project authors.
  1. 19 Mar, 2013 1 commit
  2. 11 Mar, 2013 2 commits
  3. 29 Jan, 2013 1 commit
  4. 28 Jan, 2013 5 commits
  5. 15 Nov, 2012 5 commits
  6. 17 Sep, 2012 1 commit
  7. 14 Sep, 2012 5 commits
    • Stephen Warren's avatar
      ARM: tegra: remove dead code · bab53ce3
      Stephen Warren authored
      Now that all boards are converted to device tree, devices.[ch] and
      board-pinmux.[ch] are no longer used. So, remove them.
      
      The only exception is the EHCI platform data in devices.h. Move that
      data to board-dt-tegra20.c - the only places it's used.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      bab53ce3
    • Laxman Dewangan's avatar
      ARM: dt: tegra: harmony: add regulators · 3cc404de
      Laxman Dewangan authored
      Harmony uses a TPS6586x regulator. Instantiate this, and hook up a
      couple of fixed GPIO-controlled regulators too.
      
      Based on Ventana regulator patch by Stephen Warren <swarren@nvidia.com>
      and converted to Harmony.
      
      swarren made the following changes:
      * Added ldo0 regulator configuration to device tree, and updated
        board-harmony-pcie.c for the new regulator name.
      * Fixed vdd_1v05's voltage from 10.5V to 1.05V.
      * Modified board-harmony-pcie.c to obtain the en_vdd_1v05 GPIO number at
        run-time from device tree instead of hard-coding it.
      * Removed board-harmony{-power.c,.h} now that they're unused.
      * Disabled vdd_1v05 regulator; the code in board-harmony-pcie.c hijacks
        this GPIO for now. This will be fixed when the PCIe driver is re-
        written as a driver. The code can't regulator_get("vdd_1v05") right
        now, because the vdd_1v05 regulator's probe gets deferred due to its
        supply being the PMIC, which gets probed after the regulator the first
        time around, and this dependency is only resolved by repeated probing,
        which happens when deferred_probe_initcall() is called, which happens
        in a late initcall, whose runtime order relative to harmony_pcie_init()
        is undefined, since that's also called from a late initcall.
      * Removed unused harmony_pcie_initcall().
      Signed-off-by: default avatarLaxman Dewangan <ldewangan@nvidia.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      3cc404de
    • Stephen Warren's avatar
      ARM: tegra: remove board (but not DT) support for Harmony · bb25af81
      Stephen Warren authored
      Harmony can be booted using device tree with equal functionality as when
      booted using a board file. Remove as much of the board file as is
      possible, since it's no longer needed.
      
      Two special-cases are still left in board-dt-tegra20.c, since the Tegra
      PCIe driver doesn't support device tree yet, and the Harmony .dts file
      doesn't yet describe regulators which are needed for PCIe. This logic is
      now enabled unconditionally rather than via CONFIG_MACH_HARMONY. While
      this is more code than other boards, it's still unlikely to be much of a
      problem, and both regulators and PCIe should be supported via device tree
      in the near future, allowing the remaining code to be removed.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      bb25af81
    • Stephen Warren's avatar
      ARM: tegra: remove board (but not DT) support for Paz00 · cff1dfbf
      Stephen Warren authored
      Paz00 (Toshiba AC100) can be booted using device tree with equal
      functionality as when booted using a board file. Remove as much of the
      board file as is possible, since it's no longer needed.
      
      One special-case is still left in board-dt-tegra20.c, since there is no
      way to create a WiFi rfkill device from device tree yet. This logic is
      now enabled unconditionally rather than via CONFIG_MACH_PAZ00. The extra
      cases where it's enabled (.configs which did not enable Paz00 support)
      shouldn't impact much since the amount of code is tiny.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-By: default avatarMarc Dietrich <marvin24@gmx.de>
      cff1dfbf
    • Stephen Warren's avatar
      ARM: tegra: remove board (but not DT) support for TrimSlice · be6a9194
      Stephen Warren authored
      TrimSlice can be booted using device tree with equal functionality as
      when booted using a board file. Remove the board file since it's no
      longer needed.
      
      One special-case is still left in board-dt-tegra20.c, since the Tegra
      PCIe driver doesn't support device tree yet. This logic is now enabled
      by CONFIG_TEGRA_PCI rather than via CONFIG_MACH_TRIMSLICE. The extra
      cases where it's enabled (.configs which did not enable TrimSlice
      support) shouldn't impact much since the amount of code is tiny.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      be6a9194
  8. 13 Sep, 2012 2 commits
  9. 06 Sep, 2012 3 commits
  10. 05 Sep, 2012 1 commit
  11. 06 Jul, 2012 1 commit
  12. 20 Jun, 2012 3 commits
    • Stephen Warren's avatar
      ARM: tegra: remove Seaboard board files · 98a1405e
      Stephen Warren authored
      The Seaboard device tree supports all the features that the Seaboard
      board files support. Hence, there's no need to keep the board files
      around any more; all users should convert to device tree.
      
      MACH_KAEN and MACH_WARIO are also removed. While tegra-seaboard.dts
      doesn't support those explicitly, it would be trivial to create device
      trees for those boards if anyone cares.
      
      The Seaboard device tree is now compiled if Tegra2 support is enabled,
      rather than when Seaboard support is enabled.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      98a1405e
    • Stephen Warren's avatar
      ARM: tegra: remove CONFIG_MACH_TEGRA_DT · 2c95b7e0
      Stephen Warren authored
      * Make ARCH_TEGRA select USE_OF; DT is the way forward.
      * Build board-dt-tegra*.c when the relevant Tegra SoC support is enabled,
        rather than requiring a specific config option for this.
      * The board-specific config options already build board-*-pinmux.o, and
        when booting from device tree these files are no longer needed, so we
        can remove some Makefile commands related to those files.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      2c95b7e0
    • Wolfram Sang's avatar
      ARM: tegra: build powergate unconditionally · 95ef9958
      Wolfram Sang authored
      powergate functions are needed for tegra30 as well (see common.c), so
      build it always. Fixes:
      
      arch/arm/mach-tegra/built-in.o: In function `tegra30_init_early':
      apbio.c:(.init.text+0x78): undefined reference to `tegra_powergate_init'
      
      (using "allnoconfig" with tegra30 enabled)
      Signed-off-by: default avatarWolfram Sang <w.sang@pengutronix.de>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      95ef9958
  13. 18 Apr, 2012 1 commit
  14. 13 Mar, 2012 1 commit
  15. 04 Mar, 2012 1 commit
  16. 26 Feb, 2012 3 commits
  17. 07 Feb, 2012 2 commits
    • Stephen Warren's avatar
      ARM: tegra: Add a simple PMC driver · d3b8bdd5
      Stephen Warren authored
      This PMC driver is enough to parse the nvidia,invert-interrupt property
      from device tree, and configure the PMC's to honor that.
      
      In the future, this file could expand to centralize all other PMC accesses
      within the mach-tegra code.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      d3b8bdd5
    • Olof Johansson's avatar
      ARM: tegra: use APB DMA for accessing APB devices · e2f91578
      Olof Johansson authored
      Tegra2 hangs if APB registers are accessed from the cpu during an
      apb dma operation. The workaround is to use apb dma to read/write the
      registers instead.
      
      There is a dependency loop between fuses, clocks, and APBDMA.  If dma
      is enabled, fuse reads must go through APBDMA to avoid corruption due
      to a hw bug.  APBDMA requires a clock to be enabled.  Clocks must read
      a fuse to determine allowable cpu frequencies.
      
      Separate out the fuse DMA initialization, and allow the fuse read
      and write functions to be called without using DMA before the DMA
      initialization has been completed.  Access to the fuses before APBDMA
      is initialized won't hit the hardware bug because nothing else can be
      using DMA.
      
      Original fuse registar access code from Varun Wadekar
      <vwadekar@nvidia.com>, improved by Colin Cross <ccross@android.com>
      and later moved to separate driver by Jon Mayo <jmayo@nvidia.com>.
      
      Major refactoring/cleanup by Olof Johansson <olof@lixom.net>.
      
      Changes since v1:
      
      * fix 'return false' on error condition
      * dequeue dma ops in case of timeout
      
      From: Jon Mayo <jmayo@nvidia.com>.
      Signed-off-by: Jon Mayo <jmayo@nvidia.com>.
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      e2f91578
  18. 06 Feb, 2012 2 commits