Skip to content
  1. Nov 26, 2013
    • Tony Lindgren's avatar
      ARM: dts: Add basic support for omap3 LDP zoom1 labrador · bd5fc6fa
      Tony Lindgren authored
      Basic things like serial, Ethernet, MMC, NAND, DSS, touchscreen
      and GPIO keys work.
      
      For twl4030-keypad we're still missing the binding, but
      support for that should be trivial to add once the driver
      has been updated.
      
      MUSB I'm pretty sure I got got to enumerate once, but I
      suspect the battery charging somehow disrupts it and it's
      not enumerating in general for some reason.
      
      Patches are welcome to improve things if people are
      still using this board.
      
      For reference, here's some more info on this old board:
      http://www.openomap.org/wiki/tiki-index.php?page=HardwareInfo
      
      
      
      Cc: devicetree@vger.kernel.org
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      bd5fc6fa
    • Tony Lindgren's avatar
      ARM: dts: Add basic Nokia N8X0 support · a900f516
      Tony Lindgren authored
      
      
      Add minimal device tree support for n8x0 boards so we
      can make omap2 device tree only. Note that we still need
      to initialize various platform data quirks to keep
      things working until n8x0 drivers support device tree.
      
      Here's a rough todo list for the people using n8x0:
      
      1. Update menelaus for device tree and set up
         regulators at least for the MMC driver
      
      2. Remove the MMC regulator platform data callback
         by using the Menlaus regulators directly in the
         driver passed from the .dts file
      
      3. Update GPMC connected devices for onenand and
         tusb6010 for device tree
      
      We're planning to remove all legacy platform data
      for mach-omap2 over next few merge cycles, so if
      people are still using n8x0, please fix the issues
      above.
      
      Cc: devicetree@vger.kernel.org
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Tested-by: default avatarAaro Koskinen <aaro.koskinen@iki.fi>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      a900f516
    • Tony Lindgren's avatar
      ARM: dts: Add basic device tree support for omap2430 sdp · 04a25dfb
      Tony Lindgren authored
      
      
      I doubt that there are many people using 2430 sdp, but as
      that's been historically an important acid test platform
      for omap2+ related changes, let's add minimal device
      tree support for it.
      
      If anybody is using it beyond minimal boot testing, patches
      for more complete device tree support are welcome.
      
      Cc: devicetree@vger.kernel.org
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      04a25dfb
  2. Nov 13, 2013
  3. Nov 11, 2013
  4. Nov 05, 2013
  5. Nov 04, 2013
  6. Nov 01, 2013
  7. Oct 31, 2013
    • Arnaud Ebalard's avatar
      ARM: mvebu: Add Netgear ReadyNAS 104 board · 45e8815f
      Arnaud Ebalard authored
      
      
      Main hardware parts of the (Armada 370 based) NETGEAR ReadyNAS 104 are
      supported by mainline kernel (USB 3.0 rear ports, USB 2.0 front port,
      Gigabit controller and PHYs, serial port, LEDs, buttons, SATA ports,
      G762 fan controller) and referenced in provided .dts file. Some additonal
      work remains for:
      
       - Intersil ISL12057 I2C RTC and Alarm chip: working driver but needs
         to be splitted for submission of RTC part first;
       - Front LCD (Winstar 1602G): driver needs to be written
       - Armada NAND controller (to access onboard 128MB of NAND): support
         being pushed by @free-electrons people
       - 4 front SATA LEDs controlled via GPIO brought by NXP PCA9554:
         driver is available upstream. Not referenced/tested yet.
      
      but the device is usable w/o those.
      
      Signed-off-by: default avatarArnaud Ebalard <arno@natisbad.org>
      Acked-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      45e8815f
    • Hiroshi Doyu's avatar
      ARM: tegra: fix Tegra114 IOMMU register address · 4cca9593
      Hiroshi Doyu authored
      
      
      The IOMMU node's reg property contains completely bogus values! Somehow,
      this had no practical effect, despite the fact the IOMMU driver appears
      to be writing to those registers. I suppose that since no HW modules is
      actually at that address, the writes simply had no effect.
      
      Note that I'm not CCing stable here, even though the problem exists as
      far back as v3.9, simply because this patch doesn't fix any observed
      issue, and I don't want to run the risk of suddenly writing to some
      registers and causing a regression.
      
      Signed-off-by: default avatarHiroshi Doyu <hdoyu@nvidia.com>
      [swarren, wrote commit description]
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      4cca9593
    • Thomas Petazzoni's avatar
      ARM: kirkwood: add support for OpenBlocks A7 platform · f24b56cb
      Thomas Petazzoni authored
      
      
      The OpenBlocks A7 board is designed and sold by PlatHome, and based on
      a Kirkwood 6283 Marvell SoC. It is quite similar to the OpenBlocks A6
      already supported in the kernel, with the following main differences:
      
       - The A6 uses a RTC on I2C, while the A7 uses the internal SoC RTC.
      
       - The A6 has one Ethernet port, while the A7 has two Ethernet ports
      
       - The A6 has only one USB port, while the A7 integrates a USB hub,
         which provides two front-side USB port, and an internal USB port as
         well.
      
       - The A6 has 512 MB of RAM, while the A7 has 1 GB of RAM.
      
       - Slightly different GPIOs for some functions.
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Acked-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Acked-by: default avatarGregory CLEMENT <gregory.clement@free-electrons.com>
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      f24b56cb
  8. Oct 30, 2013
  9. Oct 29, 2013
    • Grant Likely's avatar
      arm/versatile: Fix versatile irq specifications. · 0976c946
      Grant Likely authored
      
      
      Two of the versatile irq definitions are incorrect, mostly because two
      devices have connections to more than one interrupt controller. Fix them
      by using the new interrupts-extended property to fan out without using
      an awful interrupt-map nexus node.
      
      Signed-off-by: default avatarGrant Likely <grant.likely@linaro.org>
      0976c946
    • Grant Likely's avatar
      of/irq: create interrupts-extended property · 79d97015
      Grant Likely authored
      
      
      The standard interrupts property in device tree can only handle
      interrupts coming from a single interrupt parent. If a device is wired
      to multiple interrupt controllers, then it needs to be attached to a
      node with an interrupt-map property to demux the interrupt specifiers
      which is confusing. It would be a lot easier if there was a form of the
      interrupts property that allows for a separate interrupt phandle for
      each interrupt specifier.
      
      This patch does exactly that by creating a new interrupts-extended
      property which reuses the phandle+arguments pattern used by GPIOs and
      other core bindings.
      
      Signed-off-by: default avatarGrant Likely <grant.likely@linaro.org>
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      Acked-by: default avatarKumar Gala <galak@codeaurora.org>
      [grant.likely: removed versatile platform hunks into separate patch]
      Cc: Rob Herring <rob.herring@calxeda.com>
      79d97015
  10. Oct 24, 2013
  11. Oct 23, 2013