From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/7] Tegra124 clock support
Date: Thu, 17 Oct 2013 16:12:44 +0300 [thread overview]
Message-ID: <1382015565-20139-1-git-send-email-pdeschrijver@nvidia.com> (raw)
This series introduces support for the Tegra124 CAR clocks.
Based on '[PATCH v4 00/15] Introduce common infra for tegra clocks'
changes since v1:
+ suspend/resume for LP1 (Joseph Lo)
+ fixed some comments
+ account for changes to the common infra code
changes since v2:
+ simplified PLLSS support
+ added binding document
+ minor fixes
Joseph Lo (2):
clk: tegra124: add wait_for_reset and disable_clock for
tegra_cpu_car_ops
clk: tegra124: add suspend/resume function for tegra_cpu_car_ops
Peter De Schrijver (5):
clk: tegra: Add support for PLLSS
clk: tegra: Add periph regs bank X
clk: tegra124: Add common clk IDs to clk-id.h
clk: tegra124: Add new peripheral clocks
clk: tegra124: Add support for Tegra124 clocks
.../bindings/clock/nvidia,tegra124-car.txt | 59 +
drivers/clk/tegra/Makefile | 1 +
drivers/clk/tegra/clk-id.h | 20 +
drivers/clk/tegra/clk-pll.c | 124 ++
drivers/clk/tegra/clk-tegra-periph.c | 54 +
drivers/clk/tegra/clk-tegra124.c | 1428 ++++++++++++++++++++
drivers/clk/tegra/clk.c | 10 +
drivers/clk/tegra/clk.h | 5 +
include/dt-bindings/clock/tegra124-car.h | 340 +++++
9 files changed, 2041 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-car.txt
create mode 100644 drivers/clk/tegra/clk-tegra124.c
create mode 100644 include/dt-bindings/clock/tegra124-car.h
--
1.7.7.rc0.72.g4b5ea.dirty
reply other threads:[~2013-10-17 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1382015565-20139-1-git-send-email-pdeschrijver@nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pgaikwad@nvidia.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®