From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Memory controller hot reset
Date: Mon, 12 Feb 2018 20:06:29 +0300 [thread overview]
Message-ID: <cover.1518452709.git.digetx@gmail.com> (raw)
Hello,
Tegra's memory controller has a "memory hot reset" functionality that
blocks all memory transactions for the memory client. During reset of HW,
it could perform DMA and resetting HW during DMA could lead to a system
hang or memory corruption, so here comes the memory hot reset that blocks
all interactions of HW with memory so that it could be reset safely. Memory
hot reset is urgently required for multimedia, like GPU or video decoder,
as it is quite easy to get into trouble without a proper HW reset.
The short series introduces a custom Tegra-specific memory hot reset API.
Since first revision of this patchset haven't got any comment, I'm trying
again with a V2 that has one minor correction compared to V1, I've added
terga_mc_hotreset_assert()/deassert() functions as in V1 there was only
tegra_mc_hot_reset() and turned out it is not enough.
Please review, thanks.
Dmitry Osipenko (2):
memory: tegra: Squash tegra20-mc into common tegra-mc driver
memory: tegra: Introduce memory client hot reset API
drivers/memory/Kconfig | 10 -
drivers/memory/Makefile | 1 -
drivers/memory/tegra/Makefile | 1 +
drivers/memory/tegra/mc.c | 433 ++++++++++++++++++++++++++++++++++------
drivers/memory/tegra/mc.h | 10 +
drivers/memory/tegra/tegra114.c | 25 +++
drivers/memory/tegra/tegra124.c | 32 +++
drivers/memory/tegra/tegra20.c | 95 +++++++++
drivers/memory/tegra/tegra210.c | 27 +++
drivers/memory/tegra/tegra30.c | 25 +++
drivers/memory/tegra20-mc.c | 254 -----------------------
include/soc/tegra/mc.h | 81 +++++++-
12 files changed, 669 insertions(+), 325 deletions(-)
create mode 100644 drivers/memory/tegra/tegra20.c
delete mode 100644 drivers/memory/tegra20-mc.c
--
2.15.1
next reply other threads:[~2018-02-12 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 17:06 Dmitry Osipenko [this message]
2018-02-12 17:06 ` [PATCH v2 1/2] memory: tegra: Squash tegra20-mc into common tegra-mc driver Dmitry Osipenko
2018-02-13 10:30 ` Thierry Reding
2018-02-14 11:15 ` Peter De Schrijver
2018-02-14 15:42 ` Dmitry Osipenko
2018-02-19 2:04 ` Dmitry Osipenko
2018-02-19 2:16 ` Dmitry Osipenko
2018-02-12 17:06 ` [PATCH v2 2/2] memory: tegra: Introduce memory client hot reset API Dmitry Osipenko
2018-02-13 11:24 ` Thierry Reding
2018-02-19 12:35 ` Dmitry Osipenko
2018-02-19 12:44 ` Dmitry Osipenko
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=cover.1518452709.git.digetx@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).