1. 04 3月, 2014 1 次提交
  2. 26 2月, 2014 1 次提交
  3. 23 2月, 2014 1 次提交
  4. 27 1月, 2014 2 次提交
  5. 04 1月, 2014 2 次提交
  6. 03 1月, 2014 1 次提交
  7. 25 12月, 2013 1 次提交
  8. 24 12月, 2013 1 次提交
  9. 23 12月, 2013 1 次提交
  10. 21 12月, 2013 1 次提交
  11. 20 12月, 2013 1 次提交
  12. 19 12月, 2013 5 次提交
  13. 18 12月, 2013 1 次提交
  14. 17 12月, 2013 1 次提交
  15. 16 12月, 2013 1 次提交
  16. 13 12月, 2013 2 次提交
  17. 11 12月, 2013 1 次提交
  18. 10 12月, 2013 5 次提交
  19. 09 12月, 2013 1 次提交
  20. 02 12月, 2013 2 次提交
    • A
      ARM: kirkwood: Add support for NETGEAR ReadyNAS NV+ v2 · 46ca506c
      Arnaud Ebalard 提交于
      Almost all hardware parts of the NETGEAR ReadyNAS NV+ v2 ([1] for more
      details) are supported by mainline kernel. The only missing elements in
      provided .dts file are:
      
       - the front LCD module (Winstar WINSTAR WH1602): driver development is
         ongoing. This is the same LCD module as on ReadyNAS 104.
       - the Macronix MX25L512 512Kbit SPI flash: no time to play with it yet.
      
      The device is the big brother (4 vs 2 bay) of the ReadyNAS Duo v2. The
      main differences are some additional LEDs for the disks, a Marvell
      88SM4140 SATA Port multiplier (no driver required to access the disk)
      and previously described LCD module. Otherwise, it shares the same SoC
      (kirkwood 88F6282), RAM (256MB), NAND (128MB), RTC chip (Ricoh rs5c372a),
      fan controller (GMT G762), XHCI controller (NEC/Renesas µPD720200).
      
      [1]: http://natisbad.org/NAS5/Signed-off-by: NArnaud Ebalard <arno@natisbad.org>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      46ca506c
    • A
      ARM: mvebu: Add Netgear ReadyNAS 2120 board · 8aa0b019
      Arnaud Ebalard 提交于
      All hardware parts of the (mv78230 Armada XP based) NETGEAR ReadyNAS
      2120 are supported by mainline kernel (USB 3.0 and eSATA rear ports,
      USB 2.0 front port, Gigabit controller and PHYs for the two rear ports,
      serial port, LEDs, Buttons, 88SE9170 SATA controllers, three G762 fan
      controllers, G751 temperature sensor) except for:
      
       - the Intersil ISL12057 I2C RTC Chip,
       - the Armada NAND controller.
      
      Support for both of those is currently work in progress and does not
      prevent boot.
      Signed-off-by: NArnaud Ebalard <arno@natisbad.org>
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      8aa0b019
  21. 26 11月, 2013 3 次提交
    • T
      ARM: dts: Add basic support for omap3 LDP zoom1 labrador · bd5fc6fa
      Tony Lindgren 提交于
      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: NTony Lindgren <tony@atomide.com>
      bd5fc6fa
    • T
      ARM: dts: Add basic Nokia N8X0 support · a900f516
      Tony Lindgren 提交于
      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: NAaro Koskinen <aaro.koskinen@iki.fi>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      a900f516
    • T
      ARM: dts: Add basic device tree support for omap2430 sdp · 04a25dfb
      Tony Lindgren 提交于
      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: NTony Lindgren <tony@atomide.com>
      04a25dfb
  22. 01 11月, 2013 1 次提交
  23. 31 10月, 2013 2 次提交
    • 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
    • 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
  24. 22 10月, 2013 1 次提交
  25. 19 10月, 2013 1 次提交