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:53:01 -0800 Message-ID: <20060207215301.GF27148@atomide.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: 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: "Woodruff, Richard" Cc: Linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Woodruff, Richard [060207 13:42]: > > > > 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. > > Is that what RMK meant... I was wondering if he meant you stash away a > number of clocks and a list of them in the dev structure. That way you > could just call clock enable for all need clocks based on private data. > Who is to say 2 is enough, or 3, in the future. > > I wasn't all that clear on exactly what was meant, but that was my first > thought. I believe he meant just to hide the clock number for mmc 1 or 2. But I guess we still need to have different naming for omap1 and omap2. Tony