There is a device that doesn't work when P2CCLK's bit of TI PC1520 was disable.
This patch supports P2CCLK bit enabler for TI PC1520.

Signed-off-by: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
---
 drivers/pcmcia/Kconfig  |    5 +++++
 drivers/pcmcia/ti113x.h |    8 ++++++++
 2 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/drivers/pcmcia/Kconfig b/drivers/pcmcia/Kconfig
index 519b4ff..3d80888 100644
--- a/drivers/pcmcia/Kconfig
+++ b/drivers/pcmcia/Kconfig
@@ -134,6 +134,11 @@ config YENTA_ENE_TUNE
        bool "Auto-tune EnE bridges for CB cards" if EMBEDDED
        depends on YENTA_TI && CARDBUS
 
+config YENTA_TI_P2CCLK
+       default n
+       bool "Clock generated by internal oscillator" if EMBEDDED
+       depends on YENTA_TI && CARDBUS
+
 config YENTA_TOSHIBA
        default y
        bool "Special initialization for Toshiba ToPIC bridges" if EMBEDDED
diff --git a/drivers/pcmcia/ti113x.h b/drivers/pcmcia/ti113x.h
index d29657b..ea749e8 100644
--- a/drivers/pcmcia/ti113x.h
+++ b/drivers/pcmcia/ti113x.h
@@ -59,6 +59,7 @@
 #define  TI122X_SCR_SER_STEP           0xc0000000
 #define  TI122X_SCR_INTRTIE            0x20000000
 #define  TIXX21_SCR_TIEALL             0x10000000
+#define  TI122X_SCR_P2CCLK             0x08000000
 #define  TI122X_SCR_CBRSVD             0x00400000
 #define  TI122X_SCR_MRBURSTDN          0x00008000
 #define  TI122X_SCR_MRBURSTUP          0x00004000
@@ -822,6 +823,13 @@ static int ti12xx_override(struct yenta_socket *socket)
                printk(KERN_INFO "Yenta: Enabling burst memory read 
transactions\n");
                val |= TI122X_SCR_MRBURSTUP;
        }
+
+#ifdef CONFIG_YENTA_TI_P2CCLK
+       if ( !(val & TI122X_SCR_P2CCLK)) {
+               printk(KERN_INFO "Yenta: Clock generated by internal 
oscillator\n");
+               val |= TI122X_SCR_P2CCLK;
+       }
+#endif
        if (val_orig != val)
                config_writel(socket, TI113X_SYSTEM_CONTROL, val);
 
-- 
1.5.3.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to