linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/2] davinci: mityomapl138: Use correct id for NAND controller
@ 2011-03-23 12:15 Michael Williamson
  2011-03-23 12:15 ` [PATCH 2/2] davinci: mityomapl138: Use auto-probe to determine attached PHY ID Michael Williamson
  2011-03-30 15:49 ` [PATCH 1/2] davinci: mityomapl138: Use correct id for NAND controller Nori, Sekhar
  0 siblings, 2 replies; 3+ messages in thread
From: Michael Williamson @ 2011-03-23 12:15 UTC (permalink / raw)
  To: linux-arm-kernel

For the MityDSP-L138/MityARM-1808 SOMS, the NAND controller id (which needs
to correspond to the chipselect, and is used for controlling the HW ECC
computation) is not correct.  Fix it.

Signed-off-by: Michael Williamson <michael.williamson@criticallink.com>
---
 arch/arm/mach-davinci/board-mityomapl138.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-davinci/board-mityomapl138.c b/arch/arm/mach-davinci/board-mityomapl138.c
index 2aa79c5..e5d554c 100644
--- a/arch/arm/mach-davinci/board-mityomapl138.c
+++ b/arch/arm/mach-davinci/board-mityomapl138.c
@@ -414,7 +414,7 @@ static struct resource mityomapl138_nandflash_resource[] = {
 
 static struct platform_device mityomapl138_nandflash_device = {
 	.name		= "davinci_nand",
-	.id		= 0,
+	.id		= 1,
 	.dev		= {
 		.platform_data	= &mityomapl138_nandflash_data,
 	},
-- 
1.7.0.4

^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-03-30 15:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-23 12:15 [PATCH 1/2] davinci: mityomapl138: Use correct id for NAND controller Michael Williamson
2011-03-23 12:15 ` [PATCH 2/2] davinci: mityomapl138: Use auto-probe to determine attached PHY ID Michael Williamson
2011-03-30 15:49 ` [PATCH 1/2] davinci: mityomapl138: Use correct id for NAND controller Nori, Sekhar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).