From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Override bits for PLLM
Date: Tue, 11 Jun 2013 18:01:24 -0700 [thread overview]
Message-ID: <20130612010124.8816.81006@quantum> (raw)
In-Reply-To: <1370515677-6807-1-git-send-email-pdeschrijver@nvidia.com>
Quoting Peter De Schrijver (2013-06-06 03:47:27)
> PLLM has override bits on Tegra30 and Tegra114. This patchset implements
> support for them for both Tegra30 and Tegra114.
>
> Changes since v1:
> * Remove some stray lines from 'clk: tegra: override bits for Tegra114 PLLM'
Pulled into clk-next.
Regards,
Mike
>
> Peter De Schrijver (4):
> clk: tegra: Add fields for override bits
> clk: tegra: override bits for Tegra114 PLLM
> clk: tegra: override bits for Tegra30 PLLM
> clk: tegra: Use override bits when needed
>
> drivers/clk/tegra/clk-pll.c | 82 ++++++++++++++++++++++---------------
> drivers/clk/tegra/clk-tegra114.c | 9 ++++
> drivers/clk/tegra/clk-tegra30.c | 18 ++++++++
> drivers/clk/tegra/clk.h | 8 ++++
> 4 files changed, 84 insertions(+), 33 deletions(-)
>
> --
> 1.7.7.rc0.72.g4b5ea.dirty
prev parent reply other threads:[~2013-06-12 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 10:47 [PATCH v2 0/4] Override bits for PLLM Peter De Schrijver
2013-06-06 10:47 ` [PATCH v2 1/4] clk: tegra: Add fields for override bits Peter De Schrijver
2013-06-06 10:47 ` [PATCH v2 2/4] clk: tegra: override bits for Tegra114 PLLM Peter De Schrijver
2013-06-06 10:47 ` [PATCH v2 3/4] clk: tegra: override bits for Tegra30 PLLM Peter De Schrijver
2013-06-06 10:47 ` [PATCH v2 4/4] clk: tegra: Use override bits when needed Peter De Schrijver
2013-06-06 16:05 ` [PATCH v2 0/4] Override bits for PLLM Stephen Warren
2013-06-12 1:01 ` Mike Turquette [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=20130612010124.8816.81006@quantum \
--to=mturquette@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).