Skip to content

L
linux-davinci
Switch branch/tag
  1. 26 Jun, 2009 1 commit
  3. 01 Jul, 2009 1 commit
  5. 29 Jun, 2009 2 commits
  7. 26 Jun, 2009 2 commits
  9. 29 Jun, 2009 1 commit
  11. 26 Jun, 2009 2 commits
  13. 14 Jul, 2009 1 commit
  15. 26 Jun, 2009 2 commits
  17. 25 Jul, 2009 1 commit
  19. 21 Jul, 2009 1 commit
  21. 20 Aug, 2009 1 commit
    • Pablo Bitton's avatar
      Add support for SPI in DaVinci DM6446 (and try to keep support for · 96836edc
      Pablo Bitton authored 
      DM355/DM365/DM6467 and DA8xx).  Mostly the same as the patch by Sandeep
Paulraj.

This has been tested on the DM6446 by defining a spidev device and using a
scope (to check correctness) and a hardware loopback.

This was NOT tested on DM355, DM365 and DM6467 - in fact, it will probably
not work "as is" because its default mode is CS low-inactive (default mode
of SPI in kernel) - need to set CS_HIGH mode to work as in the previous
patch.

Changes from the patch by Sandeep Paulraj:

Bug fixes:
 * Additional word written with chip select up after each transfer.
   Particulary problematic with NO_CS mode where this word can't be
   distiguished from correct words. Problem was in davinci_chip_select.
 * setup() for one chip select may interfere with transfer for another
 * Small nitpicks (bits that can be changed only on VERSION_2)

Features added:
 * Support DM6446
 * Support CS_HIGH mode (using SPIDEF register). Note that CS low is default.

Other:
 * Less accesses to registers used.
 * Once-per-device configuration is done only in probe(), not each transfer.

Uglyness still there:
 * VERSION_X definitions for different SPI controllers - added VERSION_3
   for the dm6446, which is ugly.

NOTE:
This patch is based on following patches:

SPI: DaVinci: Adding SPI driver for DM3xx/DM6467/DA8xx

 The patch adds support for SPI in DaVinci
 DM355/DM365/DM6467 and DA8xx.

 This has been tested on the DM355, DM365 and DM6467 EVMs using
 the EEPROM connected to SPI0
Signed-off-by: default avatarSandeep Paulraj <s-paulraj@ti.com>

DaVinci: DM646x: Adding Support for SPI

 The patch does the following

 1) Adds a clock for SPI
 2) Defines resources specific to DM646x SOC
Signed-off-by: default avatarSandeep Paulraj <s-paulraj@ti.com>
Signed-off-by: default avatarPablo Bitton <pablo.bitton@gmail.com>
Cc: Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
Cc: Russell King <rmk@arm.linux.org.uk>
Cc: David Brownell <david-b@pacbell.net>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      96836edc
  23. 14 Aug, 2009 5 commits
  25. 31 Jul, 2009 1 commit
  27. 10 Aug, 2009 1 commit
  29. 31 Jul, 2009 5 commits
  31. 24 Jun, 2009 1 commit
  33. 23 Jul, 2009 1 commit
  35. 18 Jul, 2009 3 commits
  37. 24 Jun, 2009 1 commit
  39. 25 Jul, 2009 1 commit
  41. 18 Jul, 2009 1 commit
  43. 20 Aug, 2009 2 commits
  45. 17 Aug, 2009 1 commit
    • Andrew Morton's avatar
      ERROR: "foo * bar" should be "foo *bar" · aa43fdfe
      Andrew Morton authored 
      #357: FILE: fs/proc/kcore.c:486:
+static int open_kcore(struct inode * inode, struct file *filp)

total: 1 errors, 0 warnings, 309 lines checked

./patches/kcore-use-registerd-physmem-information.patch has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.

Please run checkpatch prior to sending patches

Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      aa43fdfe
  47. 21 Aug, 2009 1 commit
    • Andrew Morton's avatar
      fs/proc/kcore.c: In function 'kcore_update_ram': · efb89699
      Andrew Morton authored 
      fs/proc/kcore.c:144: error: 'max_low_pfn' undeclared (first use in this function)
fs/proc/kcore.c:144: error: (Each undeclared identifier is reported only once
fs/proc/kcore.c:144: error: for each function it appears in.)

Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: WANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      efb89699
  49. 17 Aug, 2009 1 commit
    • KAMEZAWA Hiroyuki's avatar
      For /proc/kcore, each arch registers its memory range by kclist_add(). · 884a2e28
      KAMEZAWA Hiroyuki authored 
      In usual,

	- range of physical memory
	- range of vmalloc area
	- text, etc...

are registered but "range of physical memory" has some troubles.  It
doesn't updated at memory hotplug and it tend to include unnecessary
memory holes.  Now, /proc/iomem (kernel/resource.c) includes required
physical memory range information and it's properly updated at memory
hotplug.  Then, it's good to avoid using its own code(duplicating
information) and to rebuild kclist for physical memory based on
/proc/iomem.
Signed-off-by: default avatarKAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: WANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      884a2e28