Skip to content
  1. May 13, 2014
    • Alexandre Courbot's avatar
      ARM: tegra: add device tree for SHIELD · e9d68f90
      Alexandre Courbot authored
      
      
      NVIDIA SHIELD is a portable Android console containing a Tegra 4 SoC with
      2GB RAM and a 720p panel.
      
      The following hardware is enabled by this device tree: UART, eMMC, USB
      (needs external power), PMIC, backlight, joystick, SD card, GPIO keys.
      
      DSI panel, HDMI output, charger, self-powered USB, audio, wifi bluetooth
      are not supported yet but might be by future patches (likely in that
      order).
      
      Touch panel and sensors will probably never be supported.
      
      Initrd addresses are hardcoded to match the static values used by the
      bootloader, since it won't add them for us. All the same, a kernel
      command-line is provided to replace the one passed by the
      bootloader which is filled with garbage.
      
      NVIDIA SHIELD is typically booted with an appended DTB to avoid
      modifications made by the bootloader.
      
      Signed-off-by: default avatarAlexandre Courbot <acourbot@nvidia.com>
      [swarren, fixed gpio-keys child node sort order, patch description]
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      e9d68f90
  2. May 07, 2014
  3. May 03, 2014
    • Alexandre Courbot's avatar
      ARM: tegra: add Tegra Note 7 device tree · 6f3df63f
      Alexandre Courbot authored
      
      
      Tegra Note 7 is a consumer tablet embedding a Tegra 4 SoC with 1GB RAM
      and a 720p panel.
      
      The following hardware is enabled by this device tree: UART, eMMC, USB
      (needs external power), PMIC, backlight, DSI panel, keys.
      
      SD card, HDMI, charger, self-powered USB, audio, wifi, bluetooth are not
      yet supported but might be by future patches (likely in that order).
      
      Touch panel, sensors & cameras will probably never be supported.
      
      Pinctrl is not set yet, as the bootloader-provided values allow us to
      use the currently supported hardware.
      
      Initrd addresses are hardcoded to match the static values used by the
      bootloader, since it won't add them for us. All the same, a kernel
      command-line is provided to replace the one passed by the bootloader
      which is filled with garbage.
      
      Signed-off-by: default avatarAlexandre Courbot <acourbot@nvidia.com>
      [treding@nvidia.com: DT fixes, DSI panel support]
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      6f3df63f
  4. Apr 30, 2014
  5. Apr 28, 2014
  6. Apr 17, 2014
  7. Apr 16, 2014
    • Stephen Warren's avatar
      ARM: tegra: define Jetson TK1 regulators · 22b35776
      Stephen Warren authored
      
      
      These are mostly identical to the Venice2 regulator definitions, since
      the board designs are very similar. Differences are:
      
      - Jetson TK1 doesn't have a built-in LCD panel, so on-board regulators
        are not present for the backlight, touchscreen, or panel.
      - +3.3V_RUN needs to be boot-on/always-on, since it's widely used. This
        change should likely be propagated to Venice2 for completeness,
        although it will have no practical effect there since various other
        regulators use +3.3V_RUN as their supply and are always-on.
      - +3.3V_LP0 needs to be boot-on as well as always-on. One reason
        is because it's used to driver the UART level-shifter; without this, I
        see a brief period of UART corruption during cold boots.I suspect this
        change needs to be propagated to Venice2, and we simply haven't noticed
        the need since there's no UART level-shifter on Venice2.
      - A few rails have different names in the schematics.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      22b35776
    • Stephen Warren's avatar
      ARM: tegra: add Jetson TK1 device tree · 15e524a4
      Stephen Warren authored
      
      
      Jetson TK1 is an NVIDIA Tegra124 development board, containing Tegra124,
      2GB RAM, eMMC, SD card, SPI flash, serial port, PCIe Ethernet, HDMI,
      audio, mini PCIe, JTAG, SATA, and an expansion IO connector containing
      GPIOs, I2C, SPI, CSI, eDP, etc.
      
      The following features work with this device tree: UART, SD card, eMMC,
      SPI flash, USB (full-size jack, and mini-PCIe), audio, AS3722 RTC, system
      power-off, suspend/resume (LP1) with wake via RTC alarm.
      
      The following features should work with this device tree, but are not
      validated: Expansion I2C, expansion SPI, expansion GPIO, gpio-key for the
      power button.
      
      The following features are not yet implemented in this device tree: Most
      voltage regulators, expansion UART, HDMI, eDP, PCIe (Ethernet, and mini-
      PCIe connector), CSI, SATA.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      15e524a4
  8. Apr 11, 2014
  9. Apr 09, 2014
  10. Apr 08, 2014
    • Russell King's avatar
      ARM: add missing system_misc.h include to process.c · 779dd959
      Russell King authored
      
      
      arm_pm_restart(), arm_pm_idle() and soft_restart() are all declared in
      system_misc.h, but this file is not included in process.c.  Add this
      missing include.  Found via sparse:
      
      arch/arm/kernel/process.c:98:6: warning: symbol 'soft_restart' was not declared. Should it be static?
      arch/arm/kernel/process.c:127:6: warning: symbol 'arm_pm_restart' was not declared. Should it be static?
      arch/arm/kernel/process.c:134:6: warning: symbol 'arm_pm_idle' was not declared. Should it be static?
      
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      779dd959
    • Uwe Kleine-König's avatar
      Kconfig: rename HAS_IOPORT to HAS_IOPORT_MAP · ce816fa8
      Uwe Kleine-König authored
      
      
      If the renamed symbol is defined lib/iomap.c implements ioport_map and
      ioport_unmap and currently (nearly) all platforms define the port
      accessor functions outb/inb and friend unconditionally.  So
      HAS_IOPORT_MAP is the better name for this.
      
      Consequently NO_IOPORT is renamed to NO_IOPORT_MAP.
      
      The motivation for this change is to reintroduce a symbol HAS_IOPORT
      that signals if outb/int et al are available.  I will address that at
      least one merge window later though to keep surprises to a minimum and
      catch new introductions of (HAS|NO)_IOPORT.
      
      The changes in this commit were done using:
      
      	$ git grep -l -E '(NO|HAS)_IOPORT' | xargs perl -p -i -e 's/\b((?:CONFIG_)?(?:NO|HAS)_IOPORT)\b/$1_MAP/'
      
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ce816fa8
  11. Apr 07, 2014
  12. Apr 04, 2014