Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 17 4月, 2012 1 次提交
  3. 05 4月, 2012 1 次提交
  5. 23 2月, 2012 4 次提交
  7. 13 2月, 2012 1 次提交
  9. 01 12月, 2011 1 次提交
  11. 29 11月, 2011 1 次提交
  13. 28 11月, 2011 3 次提交
  15. 09 11月, 2011 1 次提交
  17. 11 9月, 2011 1 次提交
  19. 08 8月, 2011 1 次提交
  21. 25 6月, 2011 1 次提交
  23. 10 6月, 2011 1 次提交
  25. 25 5月, 2011 2 次提交
  27. 15 2月, 2009 1 次提交
    • A
      [ARM] 5390/1: AT91: Watchdog fixes · 2af29b78
      由 Andrew Victor 提交于 
      The recently merged AT91SAM9 watchdog driver uses the
AT91SAM9X_WATCHDOG config variable, whereas the original version of
the driver (and the platform support code) used AT91SAM9_WATCHDOG.
This causes the watchdog platform_device to never be registered, and
therefore the driver not to be initialized.

This patch:
- updates the platform support code to use AT91SAM9X_WATCHDOG.
- includes <linux/io.h> to fix compile error (same fix as was applied
to at91rm9200_wdt.c)
- fixes comment regarding watchdog clock-rates in at91rm9200.
Signed-off-by: NAndrew Victor <linux@maxim.org.za>
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      2af29b78
  29. 02 12月, 2008 1 次提交
  31. 07 8月, 2008 1 次提交
  33. 01 8月, 2008 1 次提交
    • P
      Fix rename of at91_nand -> atmel_nand · f6ed6f78
      由 Pieter du Preez 提交于 
      Structs called at91_nand_data where renamed to atmel_nand_data
and configs called *MTD_NAND_AT91* where renamed to
*MTD_NAND_ATMEL*. This was unfortunately not done consistently,
causing NAND chips not being initialised on several ARM boards.

I am aware that the author of the original change did not rename
MTD_NAND_AT91_BUSWIDTH to MTD_NAND_ATMEL_BUSWIDTH, for example.
All *MTD_NAND_AT91* where renamed to *MTD_NAND_ATMEL* in order
to keep naming consistency.

This patch was only tested on a MACH_SAM9_L9260, as this is the
only ARM board I have to my disposal.

Before this patch:

$ git-ls-files |xargs grep atmel_nand |wc -l
105
$ git-ls-files |xargs grep at91_nand |wc -l
4
$ git-ls-files |xargs grep MTD_NAND_ATMEL |wc -l
8
$ git-ls-files |xargs grep MTD_NAND_AT91 |wc -l
47

After this patch:

$ git-ls-files |xargs grep atmel_nand |wc -l
109
$ git-ls-files |xargs grep at91_nand |wc -l
0
$ git-ls-files |xargs grep MTD_NAND_ATMEL |wc -l
55
$ git-ls-files |xargs grep MTD_NAND_AT91 |wc -l
0
Signed-off-by: NPieter du Preez <pdupreez@gmail.com>
Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      f6ed6f78
  35. 10 7月, 2008 1 次提交
  37. 07 6月, 2008 1 次提交
  39. 15 5月, 2008 1 次提交
  41. 28 4月, 2008 1 次提交
    • H
      atmel_lcdfb: don't initialize a pre-allocated framebuffer · 01d3a5e7
      由 Haavard Skinnemoen 提交于 
      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
works.
Signed-off-by: NHaavard 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: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      01d3a5e7
  43. 17 4月, 2008 1 次提交
  45. 04 4月, 2008 3 次提交
  47. 26 1月, 2008 8 次提交
  49. 27 11月, 2007 1 次提交