From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 00/15] Memory controller hot reset
Date: Tue, 20 Feb 2018 19:25:13 +0300 [thread overview]
Message-ID: <cover.1519141896.git.digetx@gmail.com> (raw)
Tegra's memory controller has a "memory hot reset" functionality that
blocks all memory transactions for the memory client, which is required
for a proper HW resetting. HW could perform DMA while being reset and this
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 (on
Tegra20 especially), like GPU or video decoder, as it is quite easy to get
in a trouble without a proper HW reset.
Changelog:
V3:
Addressed review comments to V2 from Thierry Reding. MC now
uses generic reset controller API instead of a custom one,
hence DT changes are now involved and so Rob Herring is CC'd
for a review.
Added couple minor cleanup/correction patches.
V2:
Basically a re-send of V1 with some minor changes.
Dmitry Osipenko (14):
dt-bindings: arm: tegra: Remove duplicated Tegra30+ MC binding
dt-bindings: memory: tegra: Document #reset-cells property of the
Tegra30 MC
dt-bindings: arm: tegra: Document #reset-cells property of the Tegra20
MC
dt-bindings: memory: tegra: Add hot resets definitions
memory: tegra: Do not handle spurious interrupts
memory: tegra: Setup interrupts mask before requesting IRQ
memory: tegra: Apply interrupts mask per SoC
memory: tegra: Remove unused headers inclusions
memory: tegra: Squash tegra20-mc into common tegra-mc driver
memory: tegra: Introduce memory client hot reset
memory: tegra: Add Tegra124 memory controller hot resets
memory: tegra: Add Tegra114 memory controller hot resets
memory: tegra: Add Tegra30 memory controller hot resets
memory: tegra: Add Tegra20 memory controller hot resets
Thierry Reding (1):
memory: tegra: Add Tegra210 memory controller hot resets
.../bindings/arm/tegra/nvidia,tegra20-mc.txt | 12 +-
.../bindings/arm/tegra/nvidia,tegra30-mc.txt | 18 --
.../memory-controllers/nvidia,tegra30-mc.txt | 5 +
drivers/memory/Kconfig | 10 -
drivers/memory/Makefile | 1 -
drivers/memory/tegra/Makefile | 1 +
drivers/memory/tegra/mc.c | 358 +++++++++++++++++++--
drivers/memory/tegra/mc.h | 22 ++
drivers/memory/tegra/tegra114.c | 35 ++
drivers/memory/tegra/tegra124.c | 48 +++
drivers/memory/tegra/tegra20.c | 296 +++++++++++++++++
drivers/memory/tegra/tegra210.c | 53 ++-
drivers/memory/tegra/tegra30.c | 35 ++
drivers/memory/tegra20-mc.c | 254 ---------------
include/dt-bindings/memory/tegra114-mc.h | 19 ++
include/dt-bindings/memory/tegra124-mc.h | 25 ++
include/dt-bindings/memory/tegra20-mc.h | 21 ++
include/dt-bindings/memory/tegra210-mc.h | 31 ++
include/dt-bindings/memory/tegra30-mc.h | 19 ++
include/soc/tegra/mc.h | 37 ++-
20 files changed, 978 insertions(+), 322 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt
create mode 100644 drivers/memory/tegra/tegra20.c
delete mode 100644 drivers/memory/tegra20-mc.c
create mode 100644 include/dt-bindings/memory/tegra20-mc.h
--
2.16.1
next reply other threads:[~2018-02-20 16:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 16:25 Dmitry Osipenko [this message]
2018-02-20 16:25 ` [PATCH v3 01/15] dt-bindings: arm: tegra: Remove duplicated Tegra30+ MC binding Dmitry Osipenko
2018-03-01 21:53 ` Rob Herring
2018-02-20 16:25 ` [PATCH v3 02/15] dt-bindings: memory: tegra: Document #reset-cells property of the Tegra30 MC Dmitry Osipenko
2018-03-01 21:54 ` Rob Herring
2018-02-20 16:25 ` [PATCH v3 03/15] dt-bindings: arm: tegra: Document #reset-cells property of the Tegra20 MC Dmitry Osipenko
2018-03-01 21:55 ` Rob Herring
2018-02-20 16:25 ` [PATCH v3 04/15] dt-bindings: memory: tegra: Add hot resets definitions Dmitry Osipenko
2018-03-01 21:56 ` Rob Herring
2018-02-20 16:25 ` [PATCH v3 05/15] memory: tegra: Do not handle spurious interrupts Dmitry Osipenko
2018-02-20 16:25 ` [PATCH v3 06/15] memory: tegra: Setup interrupts mask before requesting IRQ Dmitry Osipenko
2018-02-20 16:25 ` [PATCH v3 07/15] memory: tegra: Apply interrupts mask per SoC Dmitry Osipenko
2018-02-20 16:25 ` [PATCH v3 08/15] memory: tegra: Remove unused headers inclusions Dmitry Osipenko
2018-02-20 16:25 ` [PATCH v3 09/15] memory: tegra: Squash tegra20-mc into common tegra-mc driver Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 10/15] memory: tegra: Introduce memory client hot reset Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 11/15] memory: tegra: Add Tegra210 memory controller hot resets Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 12/15] memory: tegra: Add Tegra124 " Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 13/15] memory: tegra: Add Tegra114 " Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 14/15] memory: tegra: Add Tegra30 " Dmitry Osipenko
2018-02-20 16:36 ` [PATCH v3 15/15] memory: tegra: Add Tegra20 " 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.1519141896.git.digetx@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).