mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <mturquette@linaro.org>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] Override bits for PLLM
Date: Wed, 5 Jun 2013 17:08:25 +0300	[thread overview]
Message-ID: <1370441329-8619-1-git-send-email-pdeschrijver@nvidia.com> (raw)

PLLM has override bits on Tegra30 and Tegra114. This patchset implements
support for them for both Tegra30 and Tegra114.

Peter De Schrijver (4):
  CHROMIUM: clk: tegra: Add fields for override bits
  CHROMIUM: clk: tegra: override bits for Tegra114 PLLM
  CHROMIUM: clk: tegra: override bits for Tegra30 PLLM
  CHROMIUM: clk: tegra: Use override bits when needed

 drivers/clk/tegra/clk-pll.c      |   82 ++++++++++++++++++++++---------------
 drivers/clk/tegra/clk-tegra114.c |   15 +++++++
 drivers/clk/tegra/clk-tegra30.c  |   18 ++++++++
 drivers/clk/tegra/clk.h          |    8 ++++
 4 files changed, 90 insertions(+), 33 deletions(-)

-- 
1.7.7.rc0.72.g4b5ea.dirty


             reply	other threads:[~2013-06-05 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 14:08 Peter De Schrijver [this message]
2013-06-05 14:08 ` [PATCH 1/4] clk: tegra: Add fields for override bits Peter De Schrijver
2013-06-05 14:08 ` [PATCH 2/4] clk: tegra: override bits for Tegra114 PLLM Peter De Schrijver
2013-06-05 15:57   ` Stephen Warren
2013-06-06  8:15     ` Peter De Schrijver
2013-06-05 14:08 ` [PATCH 3/4] clk: tegra: override bits for Tegra30 PLLM Peter De Schrijver
2013-06-05 14:08 ` [PATCH 4/4] clk: tegra: Use override bits when needed Peter De Schrijver
2013-06-05 14:18 ` [PATCH 0/4] Override bits for PLLM Peter De Schrijver
2013-06-05 16:29 ` 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=1370441329-8619-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®