From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.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>
Subject: pull request for Tegra clock fixes for 3.16
Date: Mon, 19 May 2014 16:40:49 +0300 [thread overview]
Message-ID: <20140519134049.GA20109@tbergstrom-lnx.Nvidia.com> (raw)
Hi Mike,
A number of fixes which are needed by the upcoming XHCI and SATA drivers.
Thanks,
Peter.
The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:
Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)
are available in the git repository at:
git://nv-tegra.nvidia.com/user/pdeschrijver/linux.git tegra-clk-v3.16
Andrew Bresticker (2):
clk: tegra: Fix xusb_hs_src clock hierarchy
clk: tegra: Initialize xusb clocks
Jim Lin (2):
clk: tegra: Enable hardware control of PLLE
clk: tegra: Fix xusb_fs_src mux
drivers/clk/tegra/clk-id.h | 1 +
drivers/clk/tegra/clk-pll.c | 33 +++++++++++++++++++++++++++++-
drivers/clk/tegra/clk-tegra-periph.c | 10 ++++++++-
drivers/clk/tegra/clk-tegra114.c | 22 ++++++++++----------
drivers/clk/tegra/clk-tegra124.c | 21 ++++++++++---------
include/dt-bindings/clock/tegra114-car.h | 3 +-
include/dt-bindings/clock/tegra124-car.h | 3 +-
7 files changed, 68 insertions(+), 25 deletions(-)
next reply other threads:[~2014-05-19 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 13:40 Peter De Schrijver [this message]
2014-05-21 10: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=20140519134049.GA20109@tbergstrom-lnx.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=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--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®