r3845 - branches/src/target/kernel/2.6.24.x/patches

[werner at sita.openmoko.org]

Author: werner
Date: 2008-01-15 21:29:08 +0100 (Tue, 15 Jan 2008)
New Revision: 3845

Modified:
   branches/src/target/kernel/2.6.24.x/patches/smedia-glamo.patch
Log:
Applied "glamo-hold-engines-reset.patch",
http://git.openmoko.org/?p=kernel.git;a=commit;h=e669c89084dd131ad1329f3c251e4528e2e544c7

There seems to be a serious problem letting mfd engines out of reset
on the glamo.  It appears slowly clocked engines could block access
to the shared memory for long periods making problems for MMC.

Signed-off-by: Andy Green <andy at openmoko.com>

smedia-glamo.patch:
- drivers/mfd/glamo/glamo-core.c (glamo_init_script): do not let engines out of
  reset



Modified: branches/src/target/kernel/2.6.24.x/patches/smedia-glamo.patch
===================================================================
--- branches/src/target/kernel/2.6.24.x/patches/smedia-glamo.patch	2008-01-15 20:25:32 UTC (rev 3844)
+++ branches/src/target/kernel/2.6.24.x/patches/smedia-glamo.patch	2008-01-15 20:29:08 UTC (rev 3845)
@@ -1140,16 +1140,16 @@
 +	{ GLAMO_REG_CLOCK_MEMORY,	0x0000 },
 +	{ GLAMO_REG_CLOCK_LCD,		0x0000 },
 +	{ GLAMO_REG_CLOCK_MMC,		0x0000 },
-+	{ GLAMO_REG_CLOCK_ISP,		0x0000 },
-+	{ GLAMO_REG_CLOCK_ISP,		0x0000 },
-+	{ GLAMO_REG_CLOCK_JPEG,		0x0000 },
-+	{ GLAMO_REG_CLOCK_3D,		0x0000 },
-+	{ GLAMO_REG_CLOCK_3D,		0x0000 },
++//	{ GLAMO_REG_CLOCK_ISP,		0x0000 },
++//	{ GLAMO_REG_CLOCK_ISP,		0x0000 },
++//	{ GLAMO_REG_CLOCK_JPEG,		0x0000 },
++//	{ GLAMO_REG_CLOCK_3D,		0x0000 },
++//	{ GLAMO_REG_CLOCK_3D,		0x0000 },
 +	{ GLAMO_REG_CLOCK_2D,		0x0000 },
 +	{ GLAMO_REG_CLOCK_2D,		0x0000 },
-+	{ GLAMO_REG_CLOCK_RISC1,	0x0000 },
-+	{ GLAMO_REG_CLOCK_MPEG,		0x0000 },
-+	{ GLAMO_REG_CLOCK_MPEG,		0x0000 },
++//	{ GLAMO_REG_CLOCK_RISC1,	0x0000 },
++//	{ GLAMO_REG_CLOCK_MPEG,		0x0000 },
++//	{ GLAMO_REG_CLOCK_MPEG,		0x0000 },
 +	{ GLAMO_REG_CLOCK_MPROC,	0x000f },
 +		{ 0xfffe, 1 },
 +	{ GLAMO_REG_PLL_GEN1,		0x05db },	/* 48MHz */