From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brian Swetland <swetland@google.com>
Subject: omap clock.h question
Date: Tue, 7 Feb 2006 10:59:51 -0800
Message-ID: <20060207185951.GA5897@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-omap-open-source-bounces@linux.omap.com>
Content-Disposition: inline
List-Unsubscribe: <http://linux.omap.com/mailman/listinfo/linux-omap-open-source>,
	<mailto:linux-omap-open-source-request@linux.omap.com?subject=unsubscribe>
List-Archive: <http://linux.omap.com/pipermail/linux-omap-open-source>
List-Post: <mailto:linux-omap-open-source@linux.omap.com>
List-Help: <mailto:linux-omap-open-source-request@linux.omap.com?subject=help>
List-Subscribe: <http://linux.omap.com/mailman/listinfo/linux-omap-open-source>,
	<mailto:linux-omap-open-source-request@linux.omap.com?subject=subscribe>
Sender: linux-omap-open-source-bounces@linux.omap.com
Errors-To: linux-omap-open-source-bounces@linux.omap.com
To: Linux-omap-open-source@linux.omap.com
List-Id: linux-omap@vger.kernel.org


I'm trying to get the MMC driver working on OMAP730 -- currently it
fails in probe because it can't obtain "mmc1_ck".  clocks.h has a
definition for this, but only for 1510/16xx/310.  OMAP730 appears to use
a different config register (PERSEUS_PCC_CONF) to enable this clock.

What's the correct way to support this?  Define another clock struct
with the same name, but setup for 730?  

Thanks,

Brian