From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/8] ARM: tegra: RAM code access for v4.2-rc1
Date: Wed, 13 May 2015 15:49:35 +0200 [thread overview]
Message-ID: <1431524980-13599-4-git-send-email-thierry.reding@gmail.com> (raw)
In-Reply-To: <1431524980-13599-1-git-send-email-thierry.reding@gmail.com>
Hi ARM SoC maintainers, Mike, Stephen,
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.2-ramcode
for you to fetch changes up to 6ea2609ab386f6bfeebc39e1418b7497a9deb55c:
soc/tegra: fuse: Add RAM code reader helper (2015-05-04 14:21:21 +0200)
Note that this is a shared dependency for the tegra-for-4.2-clk and the
tegra-for-4.2-emc pull requests and they are already based on this, so
it's sufficient if you pull those in individually.
Thanks,
Thierry
----------------------------------------------------------------
ARM: tegra: RAM code access for v4.2-rc1
The RAM code is used by the memory and external memory controllers to
determine which set of timings to use for memory frequency scaling.
----------------------------------------------------------------
Mikko Perttunen (1):
soc/tegra: fuse: Add RAM code reader helper
Tomeu Vizoso (1):
of: Document long-ram-code property in nvidia,tegra20-apbmisc
.../bindings/misc/nvidia,tegra20-apbmisc.txt | 2 ++
drivers/soc/tegra/fuse/tegra-apbmisc.c | 21 +++++++++++++++++++++
include/soc/tegra/fuse.h | 1 +
3 files changed, 24 insertions(+)
next prev parent reply other threads:[~2015-05-13 13:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 13:49 [GIT PULL 0/8] ARM: tegra: Changes for v4.2-rc1 Thierry Reding
2015-05-13 13:49 ` [GIT PULL 1/8] ARM: tegra: Cleanup patches " Thierry Reding
2015-05-13 15:54 ` Arnd Bergmann
2015-05-13 13:49 ` [GIT PULL 2/8] ARM: tegra: Memory controller updates " Thierry Reding
2015-05-13 15:55 ` Arnd Bergmann
2015-05-13 13:49 ` Thierry Reding [this message]
2015-05-13 15:58 ` [GIT PULL 3/8] ARM: tegra: RAM code access " Arnd Bergmann
2015-05-13 13:49 ` [GIT PULL 4/8] clk: tegra: Changes " Thierry Reding
2015-05-20 19:54 ` Stephen Boyd
2015-05-21 6:25 ` Mikko Perttunen
2015-05-27 14:59 ` Mikko Perttunen
2015-05-27 19:50 ` Stephen Boyd
2015-05-28 7:03 ` Mikko Perttunen
2015-06-18 23:41 ` Michael Turquette
2015-06-20 20:41 ` Michael Turquette
2015-06-22 6:59 ` Mikko Perttunen
2015-06-22 7:03 ` Mikko Perttunen
2015-06-29 8:54 ` Thierry Reding
2015-05-28 10:13 ` Peter De Schrijver
2015-05-13 13:49 ` [GIT PULL 5/8] ARM: tegra: Add EMC driver " Thierry Reding
2015-05-13 16:00 ` Arnd Bergmann
2015-05-13 13:49 ` [GIT PULL 6/8] ARM: tegra: Core SoC changes " Thierry Reding
2015-05-13 16:02 ` Arnd Bergmann
2015-05-13 13:49 ` [GIT PULL 7/8] ARM: tegra: Devicetree " Thierry Reding
2015-05-13 16:09 ` Arnd Bergmann
2015-05-15 10:43 ` Thierry Reding
2015-05-15 11:06 ` Arnd Bergmann
2015-05-13 13:49 ` [GIT PULL 8/8] ARM: tegra: Default configuration updates " Thierry Reding
2015-05-13 16:12 ` Arnd Bergmann
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=1431524980-13599-4-git-send-email-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--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).