From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: omap clock.h question Date: Tue, 7 Feb 2006 13:27:12 -0800 Message-ID: <20060207212712.GE27148@atomide.com> References: <20060207185951.GA5897@localhost.localdomain> <20060207205222.GD27148@atomide.com> <20060207211002.GB5897@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060207211002.GB5897@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Brian Swetland Cc: Linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Brian Swetland [060207 13:10]: > [Tony Lindgren ] > > * Brian Swetland [060207 11:06]: > > > > > > 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? > > > > Yes, just add another clock for 730. BTW, the mmc driver is about to > > change where you just request mmc_ick and mmc_fck on all omaps. > > The mach-omap1/clock.h has no reference to _ick or _fck clocks right > now. This will be coming as part of the change? Oh yeah, just call it mmc_ck. It will change to figure out the mmc 1 or 2 clock based on the dev entry. Tony