From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
"Stephen Warren" <swarren@nvidia.com>,
Russell King <linux@arm.linux.org.uk>,
<linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v1 0/3] Tegra30 clockframework
Date: Mon, 2 Jan 2012 17:18:02 +0200 [thread overview]
Message-ID: <1325517486-22458-1-git-send-email-pdeschrijver@nvidia.com> (raw)
This patchset introduces the tegra30 clockframework. Clocks which require
voltage scaling are not included in this version. The implementation doesn't
use the generic clock code yet. It's the intention to move to it, once the
semantics are fully clarified.
Peter De Schrijver (3):
arm/tegra: add support for new clock framework features
arm/tegra: implement basic tegra30 clock framework
arm/tegra: enable tegra30 clock framework
arch/arm/mach-tegra/Makefile | 1 +
arch/arm/mach-tegra/clock.c | 22 +
arch/arm/mach-tegra/clock.h | 15 +
arch/arm/mach-tegra/common.c | 1 +
arch/arm/mach-tegra/include/mach/clk.h | 10 +
arch/arm/mach-tegra/tegra30_clocks.c | 3080 ++++++++++++++++++++++++++++++++
6 files changed, 3129 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/mach-tegra/tegra30_clocks.c
--
1.7.7.rc0.72.g4b5ea.dirty
next reply other threads:[~2012-01-02 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:18 Peter De Schrijver [this message]
2012-01-02 15:18 ` [PATCH v1 1/3] arm/tegra: add support for new clock framework features Peter De Schrijver
2012-01-02 15:18 ` [PATCH v1 2/3] arm/tegra: implement basic tegra30 clock framework Peter De Schrijver
2012-01-02 15:18 ` [PATCH v1 3/3] arm/tegra: enable " Peter De Schrijver
2012-01-03 23:03 ` [PATCH v1 0/3] Tegra30 clockframework Stephen Warren
2012-01-04 12:28 ` Peter De Schrijver
2012-01-06 21:13 ` Stephen Warren
2012-01-09 12:53 ` Peter De Schrijver
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=1325517486-22458-1-git-send-email-pdeschrijver@nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=swarren@nvidia.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®