From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@wwwdotorg.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>,
"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 2/5] clk: tegra: Add periph regs bank X
Date: Thu, 10 Oct 2013 14:00:32 +0300 [thread overview]
Message-ID: <20131010110032.GR4233@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20131010104306.GB6735@ulmo.nvidia.com>
On Thu, Oct 10, 2013 at 12:43:07PM +0200, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Fri, Oct 04, 2013 at 12:12:41PM +0300, Peter De Schrijver wrote:
> > Tegra124 has an extra bank of peripheral clock registers. Add it to the
> > generic peripheral clock code.
> >
> > Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> > ---
> > drivers/clk/tegra/clk.c | 10 ++++++++++
> > 1 files changed, 10 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c
> > index c8c84ce..0240dc3 100644
> > --- a/drivers/clk/tegra/clk.c
> > +++ b/drivers/clk/tegra/clk.c
> > @@ -57,6 +57,8 @@
> > #define RST_DEVICES_CLR_V 0x434
> > #define RST_DEVICES_SET_W 0x438
> > #define RST_DEVICES_CLR_W 0x43c
> > +#define RST_DEVICES_SET_X 0x290
> > +#define RST_DEVICES_CLR_X 0x294
>
> Perhaps sort these numerically rather than alphabetically? Also I don't
Why? I think alphabetically makes more sense or possibly per bank.
> see where the CLK_OUT_ENB_X, CLK_OUT_ENB_{SET,CLR}_X or RST_DEVICES_X
> registers are defined. Perhaps they were part of some other patch or a
> series that this depends on?
>
Cheers,
Peter.
next prev parent reply other threads:[~2013-10-10 11: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 [this message]
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
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=20131010110032.GR4233@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--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=pgaikwad@nvidia.com \
--cc=pwalmsley@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--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
all inboxes | Powered by JetHome®