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>
  2. 04 Jul, 2008 1 commit
  3. 02 Jul, 2008 9 commits
  4. 28 Jun, 2008 2 commits
  5. 27 Jun, 2008 12 commits
  6. 27 May, 2008 1 commit
  7. 26 May, 2008 3 commits
  8. 24 May, 2008 1 commit
  9. 16 May, 2008 1 commit
  10. 03 May, 2008 1 commit
    • Ulrich Drepper's avatar
      unified (weak) sys_pipe implementation · d35c7b0e
      Ulrich Drepper authored
      This replaces the duplicated arch-specific versions of "sys_pipe()" with
      one unified implementation.  This removes almost 250 lines of duplicated
      It's marked __weak, so that *if* an architecture wants to override the
      default implementation it can do so by simply having its own replacement
      version, since many architectures use alternate calling conventions for
      the 'pipe()' system call for legacy reasons (ie traditional UNIX
      implementations often return the two file descriptors in registers)
      I still haven't changed the cris version even though Linus says the BKL
      isn't needed.  The arch maintainer can easily do it if there are really
      no obstacles.
      Signed-off-by: default avatarUlrich Drepper <drepper@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  11. 29 Apr, 2008 2 commits
  12. 28 Apr, 2008 1 commit
    • Haavard Skinnemoen's avatar
      atmel_lcdfb: don't initialize a pre-allocated framebuffer · 01d3a5e7
      Haavard Skinnemoen authored
      If the user specified a fixed framebuffer address on the command line, it may
      have been initialized already with a splash image or something, so we
      shouldn't clear it.
      Therefore, we should only initialize the framebuffer if we allocated it
      ourselves.  This patch also updates the AVR32 setup code to clear the
      framebuffer if it allocated it itself, i.e.  the user didn't provide a fixed
      address or the reservation failed.
      I've updated the at91 platform code as well so that it initializes the
      framebuffer if it is located in SRAM, but I haven't tested that it actually
      Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Cc: Nicolas FERRE <nicolas.ferre@rfo.atmel.com>
      Cc: Andrew Victor <andrew@sanpeople.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  13. 19 Apr, 2008 5 commits