[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080327093301.GB32396@flint.arm.linux.org.uk>
Date: Thu, 27 Mar 2008 09:33:01 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
Cc: Dmitry <dbaryshkov@...il.com>, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, hskinnemoen@...el.com,
domen.puncer@...argo.com, lethal@...ux-sh.org, tony@...mide.com,
paul@...an.com
Subject: Re: [PATCH 1/3] Clocklib: add generic framework for managing clocks.
On Thu, Mar 27, 2008 at 10:26:48AM +0100, Haavard Skinnemoen wrote:
> You can extend the struct, put the rate there and use the same
> getrate() function for all the clocks that need to keep track of the
> current rate this way.
Well, if you're really concerned about size, you could do what I did with
PXA and introduce a struct clk_ops to contain all the constant function
pointers, rather than mashing the function pointers together - which
saves far more than trying to combine them.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists