1. 10 12月, 2013 2 次提交
    • M
      ARM: shmobile: Initial r8a7791 and Koelsch multiplatform support · 6d75bc64
      Magnus Damm 提交于
      Add Koelsch and r8a7791 to CONFIG_SHMOBILE_MULTI. At this
      point CCF is not yet supported so you cannot run this code
      yet. For CCF support to happen several different components
      are needed, and this is one simple portion that moves us
      forward. Other patches need to build on top of this one.
      
      Koelsch board support exists in 3 flavors:
      1) SHMOBILE_MULTI, MACH_KOELSCH - board-koelsch-reference.c (CCF + DT)
      2) SHMOBILE, MACH_KOELSCH_REFERENCE - board-koelsch-reference.c (DT)
      3) SHMOBILE, MACH_KOELSCH - board-koelsch.c (legacy C code)
      
      When CCF is done then 2) will be removed. When 1) includes same features
      as 3) then 3) will be removed.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      6d75bc64
    • L
      ARM: Rename ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY · bf98c1ea
      Laurent Pinchart 提交于
      SH-Mobile platforms are transitioning from non-multiplatform to
      multiplatform kernel. A new ARCH_SHMOBILE_MULTI configuration symbol has
      been created to group all multiplatform-enabled SH-Mobile SoCs. The
      existing ARCH_SHMOBILE configuration symbol groups SoCs that haven't
      been converted yet.
      
      This arrangement works fine for the arch/ code, but lots of drivers
      needed on both ARCH_SHMOBILE and ARCH_SHMOBILE_MULTI depend on
      ARCH_SHMOBILE only. In order to avoid changing them, rename
      ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY, and create a new boolean
      ARCH_SHMOBILE configuration symbol that is selected by both
      ARCH_SHMOBILE_LEGACY and ARCH_SHMOBILE_MULTI.
      Signed-off-by: NLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
      Acked-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      bf98c1ea
  2. 13 11月, 2013 1 次提交
  3. 11 11月, 2013 3 次提交
  4. 05 11月, 2013 1 次提交
  5. 04 11月, 2013 1 次提交
  6. 01 11月, 2013 5 次提交
  7. 31 10月, 2013 3 次提交
    • A
      ARM: mvebu: Add Netgear ReadyNAS 104 board · 45e8815f
      Arnaud Ebalard 提交于
      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: NArnaud Ebalard <arno@natisbad.org>
      Acked-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      45e8815f
    • H
      ARM: tegra: fix Tegra114 IOMMU register address · 4cca9593
      Hiroshi Doyu 提交于
      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: NHiroshi Doyu <hdoyu@nvidia.com>
      [swarren, wrote commit description]
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      4cca9593
    • T
      ARM: kirkwood: add support for OpenBlocks A7 platform · f24b56cb
      Thomas Petazzoni 提交于
      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: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Acked-by: NAndrew Lunn <andrew@lunn.ch>
      Acked-by: NGregory CLEMENT <gregory.clement@free-electrons.com>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      f24b56cb
  8. 30 10月, 2013 11 次提交
  9. 29 10月, 2013 2 次提交
    • G
      arm/versatile: Fix versatile irq specifications. · 0976c946
      Grant Likely 提交于
      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: NGrant Likely <grant.likely@linaro.org>
      0976c946
    • G
      of/irq: create interrupts-extended property · 79d97015
      Grant Likely 提交于
      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: NGrant Likely <grant.likely@linaro.org>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Acked-by: NKumar Gala <galak@codeaurora.org>
      [grant.likely: removed versatile platform hunks into separate patch]
      Cc: Rob Herring <rob.herring@calxeda.com>
      79d97015
  10. 24 10月, 2013 1 次提交
  11. 23 10月, 2013 10 次提交