[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130221172950.GA1766@opensource.wolfsonmicro.com>
Date: Thu, 21 Feb 2013 17:29:51 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Peter De Schrijver <pdeschrijver@...dia.com>
Cc: Stephen Warren <swarren@...dotorg.org>,
Laxman Dewangan <ldewangan@...dia.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"spi-devel-general@...ts.sourceforge.net"
<spi-devel-general@...ts.sourceforge.net>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] spi: tegra114: add spi driver
On Thu, Feb 21, 2013 at 11:56:54AM +0200, Peter De Schrijver wrote:
> On Wed, Feb 20, 2013 at 06:25:13PM +0100, Stephen Warren wrote:
> > OK, so that's certainly an argument for requesting a specific clock name
> > rather than NULL.
> The list of possible parents for each clock is determined by the SoC and is
> already known to CCF, so maybe we just need to add a function to CCF to allow
> the drivers to query the list of possible parents?
Assuming that "CCF" is the clock framework that's pretty much what I was
suggesting, yes.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists