1. 29 5月, 2013 3 次提交
  2. 18 5月, 2013 1 次提交
    • V
      ARM: tegra: update device trees for USB binding rework · 4c94c8b5
      Venu Byravarasu 提交于
      This patch updates all Tegra board files so that they contain all the
      properties required by the updated USB DT binding. Note that this patch
      only adds the new properties and does not yet remove the old properties,
      in order to maintain bisectability. The old properties will be removed
      once the driver has been updated to assume the new bindings.
      Signed-off-by: NVenu Byravarasu <vbyravarasu@nvidia.com>
      [swarren: fixed some newly added regulator-name properties to better
      match schematic, avoided duplicate regulator-name on Whistler.]
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      4c94c8b5
  3. 05 4月, 2013 1 次提交
  4. 04 4月, 2013 1 次提交
  5. 12 3月, 2013 1 次提交
  6. 29 1月, 2013 1 次提交
  7. 17 11月, 2012 1 次提交
  8. 16 11月, 2012 2 次提交
  9. 06 11月, 2012 1 次提交
  10. 20 9月, 2012 1 次提交
  11. 07 9月, 2012 1 次提交
    • S
      ARM: dt: tegra: paz00: add regulators · 217b8f0f
      Stephen Warren 提交于
      The Toshiba AC100/PAZ00 uses a TPS6586x regulator. Instantiate this.
      
      Three data sources were used for the data encoded here:
      * The HW defaults, as extracted from real HW.
      * The schematic, which specifies a voltage for each rail in the signal
        names.
      * The AC100 kernel used by the Ubuntu port:
      
        repo git://gitorious.org/~marvin24/ac100/marvin24s-kernel.git
        branch chromeos-ac100-3.0
        file arch/arm/mach-tegra/board-paz00-power.c
      
        For many rails, the constraints in that tree specified differing min
        and max voltages. In all cases, the min value was ignored, since
        there's no need currently to vary any of the voltages at run-time.
        DVFS might change this in the future.
      
      In most cases these sources all matched. Differences are:
      
      sm0: HW defaults and schematic match at 1.2v. marvin24's kernel had a max
      of 1.3v, but this higher voltage was only applied to HW by DVFS code,
      which isn't currently supported in mainline.
      
      sm1: HW defaults and schematic match at 1.0v. marvin24's kernel had a max
      of 1.125v, but this higher voltage was only applied to HW by DVFS code,
      which isn't currently supported in mainline.
      
      ldo3: The HW default is on. marvin24's kernel didn't specify always-on,
      but since the board wasn't marked as having fully constrained regulators,
      the rail was not turned off, so the difference had no effect. The rail
      is needed for USB.
      
      ldo6: The HW default is 2.85v. The schematics indicate 2.85v. However,
      since this regulator is used for the same purpose as on other boards that
      require 1.8v, this is set to 1.8v. Note that this regulator feeds the CRT
      VDAC on Tegra, and so in practice is unlikely to be used, even though it
      is actaully hooked up in HW.
      
      Portions based on work by Laxman Dewangan <ldewangan@nvidia.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Tested-by: Marc Dietrich <marvin24@gmx.de> # v2
      Acked-by: NLaxman Dewangan <ldewangan@nvidia.com>
      217b8f0f
  12. 21 6月, 2012 1 次提交
    • S
      ARM: dt: tegra: rename board files to match SoC · 702b0e4f
      Stephen Warren 提交于
      Most ARM ${board}.dts files are already named ${soc}-${board}.dts. This
      change modifies the Tegra board files to be named the same way for
      consistency.
      
      Once a related change is made in U-Boot, this will cause both U-Boot and
      the kernel to use the same names for the .dts files and SoC identifiers,
      thus allowing U-Boot's recently added "soc" and "board" environment
      variables to be used to construct the name of Tegra .dtb files, and hence
      allow board-generic U-Boot bootcmd scripts to be written.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      702b0e4f
  13. 12 6月, 2012 1 次提交
  14. 15 5月, 2012 7 次提交
  15. 26 4月, 2012 2 次提交
    • S
      ARM: dt: tegra: pinmux changes for USB ULPI · 563da21b
      Stephen Warren 提交于
      Ensure that the USB ULPI signals are not tri-stated, and have no pull-
      up or pull-down.
      
      Ensure that the pingroup hosting the USB ULPI reset signal (GPIO PV0 or
      PV1 depending on the board, so UAC) is not tri-stated, and has no pull-
      up or pull-down.
      
      This change appears larger than it is due to the grouping and sorting of
      the pin configuration data.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      563da21b
    • S
      ARM: tegra: add USB ULPI PHY reset GPIO to device tree · aa607ebf
      Stephen Warren 提交于
      ULPI PHYs have a reset signal, and different boards use a different GPIO
      for this task. Add a property to device tree to represent this.
      
      I'm not sure if adding this property to the EHCI controller node is
      entirely correct; perhaps eventually we should have explicit separate
      nodes for the various PHYs. However, we don't have that right now, so this
      binding seems like a reasonable choice.
      
      Cc: <devicetree-discuss@lists.ozlabs.org>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: <linux-usb@vger.kernel.org>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      aa607ebf
  16. 19 4月, 2012 1 次提交
  17. 05 3月, 2012 1 次提交
  18. 07 2月, 2012 10 次提交
  19. 08 12月, 2011 3 次提交
    • P
      arm/tegra: convert tegra20 to GIC devicetree binding · 0d4f7479
      pdeschrijver@nvidia.com 提交于
      Convert tegra20 IRQ intialization to the GIC devicetree binding. Modify the
      interrupt definitions in the dts files according to
      Documentation/devicetree/bindings/arm/gic.txt
      
      v3 (swarren):
      * Moved of_irq_init() call into board-dt.c to avoid ifdef'ing it.
        - Even with a dummy replacement if !CONFIG_OF, the reference from
          tegra_dt_irq_match[] to gic_of_init() would still have to be ifdef'd
        - It's plausible that tegra_dt_irq_match[] may need to contain more
          entries in the future, and defining what they are seems more suitable
          for board-dt.c than irq.c
      v2 (swarren):
      * Removed some stale GIC init code from board-dt.c
      * Undid some accidental 0x -> 0x0 search/replace.
      Signed-off-by: NPeter De Schrijver <pdeschrijver@nvidia.com>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      [olof: added include of <asm/hardware/gic.h> for compile to pass]
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      0d4f7479
    • S
      arm/dt: tegra: Remove /chosen node · 492f204d
      Stephen Warren 提交于
      The command-lines present in the existing /chosen node are not necessarily
      correct for all users. Ideally, we should simply use the command-line
      supplied by the boot-loader.
      
      In fact, using the boot-loader's cmdline is quite easy; either the
      bootloader fully supports DT, in which case it can modify the DT passed
      to the kernel to include its command-line, or CONFIG_APPENDED_DTB can
      be used in conjunction with CONFIG_ARM_ATAG_DTB_COMPAT, and the kernel
      will substitute the bootloader's command-line into the DT.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      492f204d
    • S
      arm/dt: tegra: Remove /memreserve/ from device-tree files · 5a854265
      Stephen Warren 提交于
      There are no drivers in the kernel at present which can make use of the
      memory reserved by /memreserve/, so there is no point reserving it. Remove
      /memreserve/ to allow the user more memory. It's also unclear whether any
      future driver would actually require /memreserve/, or allocate memory
      through some other mechanism.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      5a854265