Skip to content
  1. 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
  2. Apr 16, 2014
    • 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
  3. Mar 19, 2014
  4. Mar 15, 2014
  5. Mar 13, 2014
  6. Mar 12, 2014
  7. Mar 07, 2014
  8. Mar 05, 2014
  9. Mar 04, 2014
  10. Mar 03, 2014
  11. Mar 01, 2014
  12. Feb 26, 2014
  13. Feb 23, 2014
  14. Feb 22, 2014
    • Ben Peddell's avatar
      ARM: Kirkwood: Add support for many Synology NAS devices · 2d0a7add
      Ben Peddell authored
      
      
      Add device tree fragments and files to support many of the kirkwood
      based Synology NAS devices. This is a modification of
      Andrew Lunn's <andrew@lunn.ch> translation of the board setup file
      maintained by Ben Peddell <klightspeed@killerwolves.net>
      
      The Ricoh RS5C372 RTC was used in all 2009 units and some 2010 units.
      All other Synology Kirkwood-based DiskStations and RackStations use
      the Seiko S35390A RTC.
      
      Most of the 1-bay and 2-bay units use the GPIOs that are multiplexed
      with the built-in SATA interface activity/presence pins on mpp 20-23,
      while the 4-bay units use ge01 and a PCIe SATA controller, and put the
      software controlled HDD leds on mpp 36-43.
      
      Most of the 6281 units with HDD power controls use mpp 29 and 31, while
      most of the 6282 units with HDD power controls use mpp 30, 34, 44 and 45
      and provide a model ID on mpp 28, 29, 46 and 47.  Pre-2012 units and
      most 4-bay units didn't have a separate power control for HDD1.  These
      power controls are presumably to limit startup current from the 12V
      brick power supply.
      
      Instead of using separate dtsi files in a synology directory, this
      patch uses a single dtsi file containing all of the modules for
      these boards, with all of the modules not common to all boards
      disabled.  The board dts files then enable the appropriate modules for
      their boards.
      
      Signed-off-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarBen Peddell <klightspeed@killerwolves.net>
      Tested-by: Ben Peddell <klightspeed@killerwolves.net> (ds211j)
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      2d0a7add
  15. Feb 20, 2014
    • Jason Cooper's avatar
      kbuild: dtbs_install: new make target · f4d4ffc0
      Jason Cooper authored
      
      
      Unlike other build products in the Linux kernel, there is no 'make
      *install' mechanism to put devicetree blobs in a standard place.
      
      This commit adds a new 'dtbs_install' make target which copies all of
      the dtbs into the INSTALL_DTBS_PATH directory. INSTALL_DTBS_PATH can be
      set before calling make to change the default install directory. If not
      set then it defaults to:
      
      	$INSTALL_PATH/dtbs/$KERNELRELEASE.
      
      This is done to keep dtbs from different kernel versions separate until
      things have settled down.  Once the dtbs are stable, and not so strongly
      linked to the kernel version, the devicetree files will most likely move
      to their own repo.  Users will need to upgrade install scripts at that
      time.
      
      v7: (reworked by Grant Likely)
      - Moved rules from arch/arm/Makefile to arch/arm/boot/dts/Makefile so
        that each dtb install could have a separate target and be reported as
        part of the make output.
      - Fixed dependency problem to ensure $KERNELRELEASE is calculated before
        attempting to install
      - Removed option to call external script. Copying the files should be
        sufficient and a build system can post-process the install directory.
        Despite the fact an external script is used for installing the kernel,
        I don't think that is a pattern that should be encouraged. I would
        rather see buildroot type tools post process the install directory to
        rename or move dtb files after installing to a staging directory.
        - Plus it is easy to add a hook after the fact without blocking the
          rest of this feature.
      - Move the helper targets into scripts/Makefile.lib with the rest of the
        common dtb rules
      
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      Signed-off-by: default avatarGrant Likely <grant.likely@linaro.org>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Rob Herring <robh+dt@kernel.org>
      f4d4ffc0
  16. Feb 19, 2014
  17. Feb 18, 2014
  18. Feb 17, 2014
  19. Feb 14, 2014
  20. Feb 13, 2014
  21. Feb 10, 2014
  22. Feb 09, 2014