public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Mike Turquette <mturquette@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Paul Walmsley <pwalmsley@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 4/5] clk: tegra124: Add new peripheral clocks
Date: Wed, 09 Oct 2013 10:00:18 -0600	[thread overview]
Message-ID: <52557D92.9050200@wwwdotorg.org> (raw)
In-Reply-To: <20131009081123.GB3973@tbergstrom-lnx.Nvidia.com>

On 10/09/2013 02:11 AM, Peter De Schrijver wrote:
> On Wed, Oct 09, 2013 at 12:31:35AM +0200, Stephen Warren wrote:
>> On 10/04/2013 03:12 AM, Peter De Schrijver wrote:
>>> Tegra124 introduces a number of new peripheral clocks. This patch adds those
>>> to the common peripheral clock code.
>>
>> Don't you need to add AFC[0..5] in this patch and/or patch 5?
> 
> AFC[0..5] are reset only nodes afaik. Up to now, we haven't done that.
> The goal is to include them once we move to the reset framework.

No, we've always added clock entries for all reset-only clocks into the
clock driver. Since the port to the reset framework is not available
yet, we need to continue to do this. Otherwise, we won't be able to
upstream audio support.


  reply	other threads:[~2013-10-09 16:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04  9:12 [PATCH 0/5] Tegra124 clock support Peter De Schrijver
2013-10-04  9:12 ` [PATCH 1/5] clk: tegra: Add support for PLLSS Peter De Schrijver
2013-10-10 10:39   ` Thierry Reding
2013-10-10 10:59     ` Peter De Schrijver
2013-10-14 15:03     ` Peter De Schrijver
2013-10-04  9:12 ` [PATCH 2/5] clk: tegra: Add periph regs bank X Peter De Schrijver
2013-10-10 10:43   ` Thierry Reding
2013-10-10 11:00     ` Peter De Schrijver
2013-10-04  9:12 ` [PATCH 3/5] clk: tegra124: Add common clk IDs to clk-id.h Peter De Schrijver
2013-10-08 22:29   ` Stephen Warren
2013-10-04  9:12 ` [PATCH 4/5] clk: tegra124: Add new peripheral clocks Peter De Schrijver
2013-10-08 22:31   ` Stephen Warren
2013-10-09  8:11     ` Peter De Schrijver
2013-10-09 16:00       ` Stephen Warren [this message]
2013-10-10  8:51         ` Peter De Schrijver
2013-10-04  9:12 ` [PATCH 5/5] clk: tegra124: Add support for Tegra124 clocks Peter De Schrijver
2013-10-08 22:31 ` [PATCH 0/5] Tegra124 clock support Stephen Warren

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=52557D92.9050200@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ian.campbell@citrix.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@linaro.org \
    --cc=pawel.moll@arm.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=pwalmsley@nvidia.com \
    --cc=rob.herring@calxeda.com \
    --cc=thierry.reding@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox