Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 06 11月, 2012 1 次提交
  3. 03 4月, 2012 1 次提交
    • P
      avr32: fix build failures from mis-naming of atmel_nand.h · 3d92e051
      由 Paul Gortmaker 提交于 
      Commit bf4289cb ("ATMEL: fix nand ecc support") indicated that it
wanted to "Move platform data to a common header
include/linux/platform_data/atmel_nand.h" and the new header even had
re-include protectors with:

    #ifndef __ATMEL_NAND_H__

However, the file that was added was simply called atmel.h
and this caused avr32 defconfig to fail with:

  In file included from arch/avr32/boards/atstk1000/setup.c:22:
  arch/avr32/mach-at32ap/include/mach/board.h:10:44: error: linux/platform_data/atmel_nand.h: No such file or directory
  In file included from arch/avr32/boards/atstk1000/setup.c:22:
  arch/avr32/mach-at32ap/include/mach/board.h:121: warning: 'struct atmel_nand_data' declared inside parameter list
  arch/avr32/mach-at32ap/include/mach/board.h:121: warning: its scope is only this definition or declaration, which is probably not what you want
  make[2]: *** [arch/avr32/boards/atstk1000/setup.o] Error 1

It seems the scope of the file contents will expand beyond
just nand, so ignore the original intention, and fix up the
users who reference the bad name with the _nand suffix.

CC: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
CC: David Woodhouse <dwmw2@infradead.org>
Acked-by: NHans-Christian Egtvedt <egtvedt@samfundet.no>
Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      3d92e051
  5. 15 3月, 2012 1 次提交
  7. 22 11月, 2011 1 次提交
  9. 11 9月, 2011 1 次提交
  11. 25 5月, 2011 1 次提交
  13. 27 7月, 2010 1 次提交
  15. 27 8月, 2009 1 次提交
    • P
      avr32: function for independently setting up SPI slaves · 07084203
      由 Peter Ma 提交于 
      at32ap_spi_setup_slaves() is exposed to allow the addition of SPI slaves
to a SPI bus that has already been registered.  This is especially
useful for add-on cards, which have their own board setup function.
at32ap_spi_add_device() has been slightly re-organized, but should be
transparent to existing users.

So to add a SPI slave, after a SPI bus has already been registered:

	/* Configure the list of slaves on SPI controller "id" */
	at32_spi_setup_slaves(id,spi_board_info,ARRAY_SIZE(spi_board_info));
 	/* Register the list of slaves */
 	spi_register_board_info(spi_board_info,ARRAY_SIZE(spi_board_info));
Signed-off-by: NPeter Ma <pma@mediamatech.com>
[haavard.skinnemoen@atmel.com: trivial whitespace fix]
Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      07084203
  17. 03 6月, 2009 1 次提交
  19. 01 4月, 2009 1 次提交
  21. 27 3月, 2009 2 次提交
  23. 17 2月, 2009 1 次提交
  25. 23 10月, 2008 1 次提交
  27. 22 9月, 2008 1 次提交
  29. 05 8月, 2008 1 次提交
  31. 24 7月, 2008 1 次提交
  33. 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
  35. 27 6月, 2008 3 次提交
  37. 07 6月, 2008 1 次提交
  39. 20 4月, 2008 1 次提交
  41. 07 4月, 2008 1 次提交
  43. 09 2月, 2008 1 次提交
  45. 23 10月, 2007 3 次提交
  47. 11 10月, 2007 1 次提交
  49. 19 7月, 2007 1 次提交
  51. 17 7月, 2007 1 次提交
  53. 15 5月, 2007 1 次提交
  55. 16 2月, 2007 1 次提交
  57. 08 12月, 2006 1 次提交
    • H
      [AVR32] Remove mii_phy_addr and eth_addr from eth_platform_data · c164b901
      由 Haavard Skinnemoen 提交于 
      The macb driver will probe for the PHY chip and read the mac address
from the MACB registers, so we don't need them in eth_platform_data
anymore.

Since u-boot doesn't currently initialize the MACB registers with the
mac addresses, the tag parsing code is kept but instead of sticking
the information into eth_platform_data, it uses it to initialize
the MACB registers (in case the boot loader didn't do it.) This code
should be unnecessary at some point in the future.
Signed-off-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      c164b901
  59. 05 10月, 2006 3 次提交
  61. 26 9月, 2006 1 次提交