Eric Lee / smarc-fsl-linux-kernel

22 Nov, 2011

1 commit

  • 84e0cdb0a   macb: unify at91 and avr32 platform data ... Browse Code »

    Both at91 and avr32 defines its own platform data structure for
    the macb driver and both share common structures though at91
    includes a currently unused phy_irq_pin. Create a common
    macb_platform_data for macb that both at91 and avr32 can use. In
    future we can use this to support other architectures that use the
    same IP block with the macb driver.

    v2: rename eth_platform_data to macb_platform_data and allow at91_ether
    to share the platform data with macb.

    Signed-off-by: Jamie Iles
    Acked-by: Nicolas Ferre
    Tested-by: Jean-Christophe PLAGNIOL-VILLARD

    Jamie Iles
     

11 Sep, 2011

1 commit

  • 1754aab9b   mtd: ATMEL, AVR32: inline nand partition table access ... Browse Code »
    43

    Currently atmel_nand driver used by AT91 and AVR32 calls a special callback
    which return nand partition table and number of partitions. However in all
    boards this callback returns just static data. So drop this callback and
    make atmel_nand use partition table provided statically via platform_data.

    Nicolas Ferre: I am in favor for a mainline inclusion through linux-mtd tree.
    Hans-Christian Egtvedt: I'm fine by sending the changes for AVR32 through linux-mtd

    Signed-off-by: Dmitry Eremin-Solenikov
    Acked-by: Hans-Christian Egtvedt
    Acked-by: Nicolas Ferre
    Acked-by: Jean-Christophe PLAGNIOL-VILLARD
    Signed-off-by: Artem Bityutskiy

    Dmitry Eremin-Solenikov
     

25 Mar, 2011

1 commit

14 Jan, 2011

1 commit

15 Dec, 2009

1 commit

  • 3550b9313   avr32: add support for ATNGW100 mkII board ... Browse Code »

    This patch adds board support for ATNGW100 mkII. This board is an upgrade of
    the ATNGW100 where the difference is an additional 256 MB NAND flash device and
    128 MB 32-bit SDRAM instead of the 32 MB 16-bit SDRAM on ATNGW100.

    Tested on ATNGW100 mkII, duh (-:

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

    Hans-Christian Egtvedt
     

27 Aug, 2009

1 commit

08 Jun, 2009

1 commit

01 Apr, 2009

1 commit

26 Mar, 2009

1 commit

05 Jan, 2009

1 commit

23 Oct, 2008

2 commits

13 Oct, 2008

1 commit

  • a3bee42f0   avr32: Add support for EVKLCD10X addon boards ... Browse Code »

    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

2 commits

06 Oct, 2008

1 commit

  • 6b918657b   atmel-mci: Platform code for supporting multiple mmc slots ... Browse Code »

    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

1 commit

  • 96706600d   ngw100: export J15 through sysfs ... Browse Code »

    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
     

08 Aug, 2008

1 commit

05 Aug, 2008

1 commit

15 Jul, 2008

1 commit

  • 7d2be0749   atmel-mci: Driver for Atmel on-chip MMC controllers ... Browse Code »

    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
     

27 Jun, 2008

2 commits

  • 7ef31e9c4   avr32: improve NGW100 I2C/PMBus setup ... Browse Code »

    Basic I2C initialization for the NGW100 board:

    - Provide empty i2c device table. Daughtercards may add devices,
    and the ATtiny24 could do stuff too.

    - Set up EXTINT(3) so the ATtiny24 can interrupt the AP7000.

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

    David Brownell
     
  • 60ed7951d   avr32: Allow board to define oscillator rates ... Browse Code »

    On our custom board we have other oscillator rates than on atngw100 and
    atstk100x.

    Currently these rates are hardcoded in arch/avr32/mach-at32ap/at32ap700x.c.

    This patch moves them into board specific code.

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

    alex
     

25 Jan, 2008

1 commit

  • 438ff3f3c   [AVR32] Add support for AT32AP7001 and AT32AP7002 ... Browse Code »

    These are derivatives of the AT32AP7000 chip, which means that most of
    the code stays the same. Rename a few files, functions, definitions
    and config symbols to reflect that they apply to all AP700x chips, and
    exclude some platform devices from chips where they aren't present.

    Signed-off-by: Haavard Skinnemoen

    Haavard Skinnemoen
     

11 Oct, 2007

2 commits

  • 82c54f864   [AVR32] ngw100 i2c-gpio tweaks ... Browse Code »

    Make the NGW100 bitbang i2c use open drain signaling.

    Also, speed it up, so it's closer to 100 kHz ... the code paths seem
    to be long enough that the udelay isn't dominating bit times. The
    peak bit rate I observed was around 125 kHz, but that's with large
    delays (usually before ACK/NAK) which hold the overall rate down to
    around 80 kHz (call it 100 usec/byte on average).

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

    David Brownell
     
  • 6fcf06151   [AVR32] Wire up USBA device ... Browse Code »

    Implement at32_add_device_usba() and use it to wire up the USBA device
    on ATSTK1000 and ATNGW100.

    Signed-off-by: Haavard Skinnemoen

    Haavard Skinnemoen
     

15 Aug, 2007

1 commit

16 Jul, 2007

1 commit

23 Jun, 2007

1 commit

27 Apr, 2007

1 commit