From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: omap clock.h question Date: Tue, 7 Feb 2006 14:29:38 -0800 Message-ID: <20060207222938.GG27148@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 14:07]: > > 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. > > Like I was saying you could hide both the slot and the names. > > for(i=data.slot[slot].num_clks; i>0; i--) > { > ck = clk_get(data.slot.clk_name[i-1]) > if(ck != NULL) > clk_enabl(ck); > } > > That way we don't care the name or how many. It gets rid of some if > statements anyway. But one of the clocks can be off more often than the other from PM point of view. Tony