[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120613152658.GE32111@tbergstrom-lnx.Nvidia.com>
Date:	Wed, 13 Jun 2012 18:26:58 +0300
From:	Peter De Schrijver <pdeschrijver@...dia.com>
To:	Rob Herring <robherring2@...il.com>
CC:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"mturquette@...aro.org" <mturquette@...aro.org>,
	"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
	"sboyd@...eaurora.org" <sboyd@...eaurora.org>,
	Rob Herring <rob.herring@...xeda.com>
Subject: Re: [PATCH v3 0/4] DT clock bindings
On Tue, Jun 12, 2012 at 04:41:47PM +0200, Rob Herring wrote:
> From: Rob Herring <rob.herring@...xeda.com>
> 
> This series defines clock bindings for Device-Tree and adds kernel
> support using the common clock infrastructure. The last patch enables
> DT clock support for the Calxeda Highbank platform.
> 
> I'm posting this again to solicit further review. There has been some
> discussion[1], but no definite path forward. This series is not changed
> from the last post other than rebasing to v3.5-rc2.
> 
> Rob
> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/100932.html
> 
How would this binding work for clocks which can take a spinlock pointer as a
init parameter (eg. clk-gate).
Cheers,
Peter.
--
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
 
