From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] spi: tegra114: add spi driver
Date: Thu, 21 Feb 2013 17:29:51 +0000 [thread overview]
Message-ID: <20130221172950.GA1766@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130221095654.GH23234@tbergstrom-lnx.Nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-21 17:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 13:38 [PATCH] spi: tegra114: add spi driver Laxman Dewangan
2013-02-19 13:38 ` Laxman Dewangan
2013-02-19 18:16 ` Stephen Warren
2013-02-20 12:29 ` Laxman Dewangan
[not found] ` <5124C18F.6070108-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-20 13:11 ` Mark Brown
2013-02-20 13:11 ` Mark Brown
2013-02-20 13:26 ` Laxman Dewangan
[not found] ` <5124CEF5.3060605-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-20 13:34 ` Mark Brown
2013-02-20 13:34 ` Mark Brown
2013-02-20 17:25 ` Stephen Warren
2013-02-20 17:25 ` Stephen Warren
[not found] ` <512506F9.2030508-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-20 17:31 ` Mark Brown
2013-02-20 17:31 ` Mark Brown
[not found] ` <20130220173109.GU2726-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2013-02-20 17:36 ` Stephen Warren
2013-02-20 17:36 ` Stephen Warren
[not found] ` <512509A9.6020208-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-20 17:57 ` Mark Brown
2013-02-20 17:57 ` Mark Brown
[not found] ` <20130220175721.GW2726-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2013-02-20 18:00 ` Stephen Warren
2013-02-20 18:00 ` Stephen Warren
2013-02-21 5:48 ` Laxman Dewangan
2013-02-21 9:56 ` Peter De Schrijver
2013-02-21 9:56 ` Peter De Schrijver
2013-02-21 17:29 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130221172950.GA1766@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.