From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 4/9] memory: tegra: Changes for v5.2-rc1
Date: Thu, 18 Apr 2019 17:07:15 +0200 [thread overview]
Message-ID: <20190418150721.8828-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190418150721.8828-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.2-memory
for you to fetch changes up to 67a8d5b0fadfd931f7e6a78e9ee7b2792a7114aa:
memory: tegra: Fix a typos for "fdcdwr2" mc client (2019-04-18 11:51:17 +0200)
Thanks,
Thierry
----------------------------------------------------------------
memory: tegra: Changes for v5.2-rc1
These are a set of fixes for various issues related to the Tegra memory
controller.
----------------------------------------------------------------
Dmitry Osipenko (4):
memory: tegra: Fix missed registers values latching
memory: tegra: Fix integer overflow on tick value calculation
memory: tegra: Replace readl-writel with mc_readl-mc_writel
Revert "ARM: tegra: Restore memory arbitration on resume from LP1 on Tegra30+"
Edward Cragg (1):
memory: tegra: Fix a typos for "fdcdwr2" mc client
Thierry Reding (1):
memory: tegra: Properly spell "tegra"
Yue Haibing (1):
memory: tegra: Make terga20_mc_reset_ops static
arch/arm/mach-tegra/iomap.h | 9 ---------
arch/arm/mach-tegra/sleep-tegra30.S | 21 ---------------------
drivers/memory/tegra/mc.c | 34 ++++++++++++++++++++--------------
drivers/memory/tegra/mc.h | 2 +-
drivers/memory/tegra/tegra114.c | 4 ++--
drivers/memory/tegra/tegra124.c | 4 ++--
drivers/memory/tegra/tegra20.c | 28 ++++++++++++++--------------
drivers/memory/tegra/tegra210.c | 2 +-
drivers/memory/tegra/tegra30.c | 4 ++--
9 files changed, 42 insertions(+), 66 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-18 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 15:07 [GIT PULL 1/9] bus/tegra: Changes for v5.2-rc1 Thierry Reding
2019-04-18 15:07 ` [GIT PULL 2/9] soc/tegra: " Thierry Reding
2019-04-29 6:34 ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 3/9] firmware: tegra: " Thierry Reding
2019-04-29 6:34 ` Olof Johansson
2019-04-18 15:07 ` Thierry Reding [this message]
2019-04-29 6:35 ` [GIT PULL 4/9] memory: " Olof Johansson
2019-04-18 15:07 ` [GIT PULL 5/9] ARM: tegra: Core changes " Thierry Reding
2019-04-29 6:35 ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 6/9] ARM: tegra: Device tree " Thierry Reding
2019-04-28 19:39 ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 7/9] ARM: tegra: Default configuration updates " Thierry Reding
2019-04-29 6:36 ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 8/9] arm64: tegra: Device tree changes " Thierry Reding
2019-04-28 19:40 ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 9/9] arm64: tegra: Default configuration updates " Thierry Reding
2019-04-29 6:37 ` Olof Johansson
2019-04-29 6:33 ` [GIT PULL 1/9] bus/tegra: Changes " Olof Johansson
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=20190418150721.8828-4-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.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).