[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080708142823.GA5590@doriath.ww600.siemens.net>
Date: Tue, 8 Jul 2008 18:28:23 +0400
From: Dmitry Baryshkov <dbaryshkov@...il.com>
To: Ben Dooks <ben-linux@...ff.org>
Cc: linux-kernel@...r.kernel.org, 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>,
ian <spyro@....com>
Subject: Re: [PATCH 0/3] Genclk: generic framework for clocks managing
[v3.1]
On Tue, Jul 08, 2008 at 03:07:15PM +0100, Ben Dooks wrote:
> On Tue, Jul 08, 2008 at 05:42:42PM +0400, Dmitry Baryshkov wrote:
> > Hi,
> >
> > This is again a set of patches to unify the management of clocks and
> > allow easy registration and unregistration of them. This is neccessary
> > to cleanly support such devices as toshiba mobile companion chips,
> > sa1111 companion, ASIC3 companion, etc. Also it brings code unification,
> > especially for a lot of arm sub-arches which share nearly the same code.
>
> Any particular reason why you've not changed the enable and disable
> methods to one single method taking a bool?
Please read my previous mail. This was specifically requested by Andrew
Morton.
>
> > Changes from the previous patchset:
> > * Change the name as requested by Ben: clocklib -> generic clk (genclk)
> > * Move from lib/clocklib.c to kernel/genclk/*
> > * Fix locking in generic code
> >
> > * Rebase PXA patch to the current Russell's tree.
> > * Interlock access to CKEN registers on PXA.
>
> --
> Ben (ben@...ff.org, http://www.fluff.org/)
>
> 'a smiley only costs 4 bytes'
--
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