1. 25 3月, 2011 1 次提交
  2. 14 1月, 2011 1 次提交
  3. 15 12月, 2009 1 次提交
  4. 27 8月, 2009 1 次提交
  5. 08 6月, 2009 1 次提交
  6. 01 4月, 2009 1 次提交
  7. 26 3月, 2009 1 次提交
  8. 05 1月, 2009 1 次提交
  9. 23 10月, 2008 1 次提交
  10. 13 10月, 2008 1 次提交
    • H
      avr32: Add support for EVKLCD10X addon boards · a3bee42f
      Hans-Christian Egtvedt 提交于
      This patch lets the user enable support for EVKLCD100 and EVKLCD101
      (refered to by EVKLCD10X). By enabling EVKLCD10X support the LCD
      controller and AC97 controller platform devices are added.
      
      The user can also choose between the EVKLCD100 (QVGA display) and the
      EVKLCD101 (VGA display), this is added to automagically select the
      correct panel timing and resolution parameters.
      
      Enabling support for EVKLCD10X addon board will cripple the MCI platform
      device a bit since they share two GPIO lines (detect and write-protect).
      These two lines are disabled when EVKLCD10X is enabled.
      
      The default configurations are based upon ATNGW100, but with added AC97C
      and LCDC driver. Virtual terminal is also enabled by default for
      EVKLCD10X boards.
      
      Verified on hardware with a NGW100 + EVKLCD100/101.
      Signed-off-by: NHans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      a3bee42f
  11. 12 10月, 2008 1 次提交
  12. 06 10月, 2008 1 次提交
    • H
      atmel-mci: Platform code for supporting multiple mmc slots · 6b918657
      Haavard Skinnemoen 提交于
      Add the necessary platform infrastructure to support multiple mmc/sdcard
      slots all at once through a single controller. Currently, the driver
      will use the first valid slot it finds and stick with that, but later
      patches will add support for switching between several slots on the fly.
      
      Extend the platform data structure with per-slot information: MMC/SDcard
      bus width and card detect/write protect pins. This will affect the pin
      muxing as well as the capabilities announced to the mmc core.
      
      Note that board code is now required to supply a mci_platform_data
      struct to at32_add_device_mci().
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      6b918657
  13. 22 9月, 2008 1 次提交
  14. 08 8月, 2008 1 次提交
  15. 05 8月, 2008 1 次提交
  16. 15 7月, 2008 1 次提交
    • H
      atmel-mci: Driver for Atmel on-chip MMC controllers · 7d2be074
      Haavard Skinnemoen 提交于
      This is a driver for the MMC controller on the AP7000 chips from
      Atmel. It should in theory work on AT91 systems too with some
      tweaking, but since the DMA interface is quite different, it's not
      entirely clear if it's worth merging this with the at91_mci driver.
      
      This driver has been around for a while in BSPs and kernel sources
      provided by Atmel, but this particular version uses the generic DMA
      Engine framework (with the slave extensions) instead of an
      avr32-only DMA controller framework.
      
      This driver can also use PIO transfers when no DMA channels are
      available, and for transfers where using DMA may be difficult or
      impractical for some reason (e.g. the DMA setup overhead is usually
      not worth it for very short transfers, and badly aligned buffers or
      lengths are difficult to handle.)
      
      Currently, the driver only support PIO transfers. DMA support has been
      split out to a separate patch to hopefully make it easier to review.
      
      The driver has been tested using mmc-block and ext3fs on several SD,
      SDHC and MMC+ cards. Reads and writes work fine, with read transfer
      rates up to 3.5 MiB/s on fast cards with debugging disabled.
      
      The driver has also been tested using the mmc_test module on the same
      cards. All tests except 7, 9, 15 and 17 succeed. The first two are
      unsupported by all the cards I have, so I don't know if the driver
      handles this correctly. The last two fail because the hardware flags a
      Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
      with that.
      
      Documentation for this controller can be found in many data sheets from
      Atmel, including the AT32AP7000 data sheet which can be found here:
      
      http://www.atmel.com/dyn/products/datasheets.asp?family_id=682Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      7d2be074
  17. 27 6月, 2008 2 次提交
  18. 25 1月, 2008 1 次提交
  19. 11 10月, 2007 2 次提交
  20. 15 8月, 2007 1 次提交
  21. 16 7月, 2007 1 次提交
  22. 23 6月, 2007 1 次提交
  23. 27 4月, 2007 2 次提交
  24. 16 2月, 2007 1 次提交
  25. 09 2月, 2007 3 次提交
  26. 08 12月, 2006 2 次提交
  27. 05 10月, 2006 1 次提交
  28. 26 9月, 2006 1 次提交