[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080608091954.GA11200@doriath.ww600.siemens.net>
Date: Sun, 8 Jun 2008 13:19:54 +0400
From: Dmitry Baryshkov <dbaryshkov@...il.com>
To: linux-kernel@...r.kernel.org
Cc: akpm@...ux-foundation.org,
Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
Russell King <rmk+lkml@....linux.org.uk>,
Paul Mundt <lethal@...ux-sh.org>,
pHilipp Zabel <philipp.zabel@...il.com>,
Pavel Machek <pavel@....cz>, tony@...mide.com, paul@...an.com,
David Brownell <david-b@...bell.net>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: [RFC][PATCH 0/3] Clocklib: generic clocks management framework
Hi,
Here is second attempt to introduce clocks management framework based on
kobjects. This attempt goes a bit further. I've removed the global
spinlock. All add/remove operations are guarded via built into clocks kset
spinlock. And all per-clock operations are guided by built-in atomic
counter variable. I can split it into counter and per-clock spinlock,
but I think it will be a waste of space.
Also as suggested by Andrew Morton, I've split the set_mode operation
back to enable/disable.
--
With best wishes
Dmitry
--
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