[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201102220729.13708.jeremy.kerr@canonical.com>
Date: Tue, 22 Feb 2011 07:29:11 +0800
From: Jeremy Kerr <jeremy.kerr@...onical.com>
To: Ryan Mallon <ryan@...ewatersys.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Dima Zavin <dmitriyz@...gle.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Vincent Guittot <vincent.guittot@...aro.org>,
linux-sh@...r.kernel.org,
Ben Herrenchmidt <benh@...nel.crashing.org>,
"Uwe Kleine-König"
<u.kleine-koenig@...gutronix.de>,
Sascha Hauer <s.hauer@...gutronix.de>,
Paul Mundt <lethal@...ux-sh.org>,
Saravana Kannan <skannan@...eaurora.org>,
Ben Dooks <ben-linux@...ff.org>,
Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH 2/2] clk: Generic support for fixed-rate clocks
Hi Ryan,
> If we never need to dynamically create fixed clocks (which seems
> unlikely) then rate can be const.
There's been a few cases where I've needed to set the rate of a fixed clock
during boot - for example when a clock rate varies between boards, it may be
defined in a platform-wide file, but have the rate modified early (ie,
clk_foo.rate = 32678) in a board file.
Also, if we're parsing clocks from the device tree (or any other discovery
mechanism), we'll need to modify rate.
Cheers,
Jeremy
--
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