1. 15 Jul, 2008 1 commit
    • Haavard Skinnemoen's avatar
      atmel-mci: Driver for Atmel on-chip MMC controllers · 7d2be074
      Haavard Skinnemoen authored
      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: default avatarHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      Signed-off-by: default avatarPierre Ossman <drzeus@drzeus.cx>
      7d2be074
  2. 27 Jun, 2008 3 commits
  3. 13 Feb, 2008 1 commit
  4. 25 Jan, 2008 5 commits
  5. 23 Oct, 2007 1 commit
  6. 11 Oct, 2007 3 commits
  7. 15 Aug, 2007 2 commits
  8. 18 Jul, 2007 4 commits
  9. 15 Jul, 2007 1 commit
  10. 23 Jun, 2007 1 commit
  11. 14 Jun, 2007 1 commit
  12. 15 May, 2007 1 commit
  13. 27 Apr, 2007 2 commits
  14. 16 Feb, 2007 1 commit
  15. 09 Feb, 2007 3 commits
  16. 08 Dec, 2006 2 commits
  17. 06 Nov, 2006 1 commit
    • Haavard Skinnemoen's avatar
      AVR32: Get rid of board_early_init · e9a43850
      Haavard Skinnemoen authored
      board_early_init() is left over from some early prototyping work
      where we had to initialize the SDRAM controller ourselves. This
      depends on the kernel being loaded into static RAM, which just
      isn't possible on any commercially available products today.
      
      In order to run without a boot loader, we need to create a zImage
      stub or have the debugger initialize the SDRAM for us (for really
      low-level debugging)
      Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
      e9a43850
  18. 04 Oct, 2006 1 commit
  19. 26 Sep, 2006 2 commits