From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from trinity.fluff.org (trinity.fluff.org [89.16.178.74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id CC10FB7C63 for ; Wed, 13 Jan 2010 01:44:35 +1100 (EST) Date: Tue, 12 Jan 2010 14:27:47 +0000 From: Ben Dooks To: Russell King - ARM Linux Subject: Re: [RFC,PATCH 1/7 v2] Add a common struct clk Message-ID: <20100112142747.GE18532@trinity.fluff.org> References: <1263279511.160551.332624337260.1.gpush@pororo> <4B4C376C.6080705@st.com> <20100112090149.GB26435@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20100112090149.GB26435@n2100.arm.linux.org.uk> Cc: Francesco VIRLINZI , Jeremy Kerr , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Jan 12, 2010 at 09:01:49AM +0000, Russell King - ARM Linux wrote: > On Tue, Jan 12, 2010 at 09:48:44AM +0100, Francesco VIRLINZI wrote: > > Hi Jeremy > > In November I already sent a proposal on > > a generic linux clk framework. > > On that I would suggest: > > > >> > >> +struct clk { > >> + const struct clk_operations *ops; > >> > > spinlock_t lock; > > const char *name; > > int id; > > Name and ID are totally pointless, unless you insist on using the clk > API in the wrong way (like S3C does.) I assume by this you mean that a number of the s3c drives use clk_get with their platform device and a name? if so, I agree this needs to get sorted out. -- Ben Q: What's a light-year? A: One-third less calories than a regular year.