07 Apr, 2009

1 commit


01 Apr, 2009

1 commit


30 Mar, 2009

1 commit


27 Mar, 2009

3 commits

  • This patch will adjust the setup the DMA controller for the AC97
    Controller in the at32ap700x machine code. This setup matches the new
    ALSA driver for the AC97C.

    The struct ac97c_platform_data has been moved into its own header file
    located in the sound include path.

    Tested on ATSTK1006 + ATSTK1000.

    This patch will setup the AC97 controller properly for the adjusted
    machine code. Both EVKLCD10x and Hammerhead board has been updated.

    Tested on EVKLCD10x, and copied to Hammerhead board.

    Signed-off-by: Hans-Christian Egtvedt
    [haavard.skinnemoen@atmel.com: fold with board code update]
    Signed-off-by: Haavard Skinnemoen

    Hans-Christian Egtvedt
     
  • This patch will adjust the setup the DMA controller for the Audio
    Bistream DAC in the at32ap700x machine code. This setup matches the new
    ALSA driver for the ABDAC.

    Tested on ATSTK1006 + ATSTK1000.

    This patch will setup the needed platform data for the Audio Bistream
    DAC used by the Favr-32 board.

    Signed-off-by: Hans-Christian Egtvedt
    [haavard.skinnemoen@atmel.com: fold board code update]
    Signed-off-by: Haavard Skinnemoen

    Hans-Christian Egtvedt
     
  • Merisc is the family name for a range of AVR32-based boards.

    The boards are designed to be used in a man-machine interfacing
    environment, utilizing a touch-based graphical user interface. They host
    a vast range of I/O peripherals as well as a large SDRAM & Flash memory
    bank.

    For more information see: http://www.martinsson.se/merisc

    Signed-off-by: Jonas Larsson
    Signed-off-by: Haavard Skinnemoen

    Jonas Larsson
     

26 Mar, 2009

4 commits


24 Mar, 2009

1 commit


06 Jan, 2009

1 commit


05 Jan, 2009

7 commits


18 Dec, 2008

1 commit


23 Oct, 2008

2 commits


13 Oct, 2008

3 commits

  • Please consider the following patch which adds support for a new AVR32
    based board.

    The board is closely based on Atmel's NGW100 reference board, but has an
    extra 8MByte FLASH and 128KByte FRAM.

    Signed-off-by: Mark Jackson
    Signed-off-by: Haavard Skinnemoen

    Mark Jackson
     
  • This patch adds support for the Favr-32 board made by EarthLCD.

    This kit, which is also called ezLCD-101, has a 10.4" touch screen LCD panel,
    16 MB 32-bit SDRAM, 8 MB parallel flash, Ethernet, audio out, USB device,
    SD-card slot, USART and various other connectors for cennecting stuff to SPI,
    I2C, GPIO, etc.

    Signed-off-by: Hans-Christian Egtvedt
    Signed-off-by: Haavard Skinnemoen

    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: Hans-Christian Egtvedt
    Signed-off-by: Haavard Skinnemoen

    Hans-Christian Egtvedt
     

12 Oct, 2008

3 commits


06 Oct, 2008

1 commit

  • 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: Haavard Skinnemoen

    Haavard Skinnemoen
     

22 Sep, 2008

2 commits

  • The NGW100 board has jumper J15 (near the reset button) which
    is unused. This patch exports it through the GPIO sysfs support
    (as /sys/class/gpio/gpio62/value) so that it's easily queried
    by boot scripts or whatever might want to know if the jumper
    has been installed (value = 0) or not (value = 1, "default").

    Signed-off-by: David Brownell
    [haavard.skinnemoen@atmel.com: add missing include]
    Signed-off-by: Haavard Skinnemoen

    David Brownell
     
  • This replaces the pin_config param with an u64 pin_mask in
    at32_add_device_lcdc, allowing a board-maintainer to indivually select
    specific lcdc pins.

    Signed-off-by: Alex Raimondi
    Signed-off-by: Julien May
    Signed-off-by: Haavard Skinnemoen

    Julien May
     

20 Sep, 2008

1 commit


08 Aug, 2008

2 commits


05 Aug, 2008

1 commit


27 Jul, 2008

2 commits

  • Minor cleanups for the MMC/SD support on avr32:

    - Make at32_add_device_mci() properly initialize "missing"
    platform data ... so boards like STK1002 won't try GPIO 0.

    - Switch over to gpio_is_valid() instead of testing for only
    one designated value.

    - Provide STK1002 platform data for the unlikely case that
    switches are set so first Ethernet controller isn't in use.
    (That's the only way to get card detect and writeprotect
    switch sensing on the STK1000.)

    And get rid of one "unused variable" warning.

    Signed-off-by: David Brownell
    Signed-off-by: Haavard Skinnemoen

    David Brownell
     
  • Haavard Skinnemoen
     

25 Jul, 2008

1 commit


18 Jul, 2008

1 commit

  • Commit 7d2be0749a59096a334c94dc48f43294193cb8ed
    (atmel-mci: Driver for Atmel on-chip MMC controllers)
    causes build errors like:

    ...
    CC arch/avr32/boards/atstk1000/atstk1003.o
    /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/avr32/boards/atstk1000/atstk1003.c: In function 'atstk1003_init':
    /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/avr32/boards/atstk1000/atstk1003.c:157: error: too few arguments to function 'at32_add_device_mci'
    make[2]: *** [arch/avr32/boards/atstk1000/atstk1003.o] Error 1

    Reported-by: Adrian Bunk
    Signed-off-by: Adrian Bunk
    Signed-off-by: Haavard Skinnemoen

    Adrian Bunk
     

15 Jul, 2008

1 commit

  • 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=682

    Signed-off-by: Haavard Skinnemoen
    Signed-off-by: Pierre Ossman

    Haavard Skinnemoen