linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Mark Zhang <markz@nvidia.com>
Cc: gnurou@gmail.com, hdoyu@nvidia.com, joro@8bytes.org,
	swarren@wwwdotorg.org, olof@lixom.net,
	iommu@lists.linux-foundation.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memory: Add NVIDIA SMMU suspend/resume support
Date: Fri, 9 Jan 2015 12:57:07 +0100	[thread overview]
Message-ID: <20150109115706.GH16465@ulmo> (raw)
In-Reply-To: <1419383441-18242-1-git-send-email-markz@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

On Wed, Dec 24, 2014 at 09:10:41AM +0800, Mark Zhang wrote:
> This patch adds suspend/resume support for NVIDIA SMMU.
> 
> Signed-off-by: Mark Zhang <markz@nvidia.com>
> ---
> Hi Alex/Olof/Thierry/Hiroshi,
> 
> This patch is created on top of Thierry Reding's patch set:
> "[PATCH v7 00/12] NVIDIA Tegra memory controller and IOMMU support"
> 
> Changes since v1:
> - Remove the list which saves "tegra_smmu_swgroup_asid" instances
> - Save all ASID registers when suspend then restore them when resume
> 
>  drivers/iommu/tegra-smmu.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++
>  drivers/memory/tegra/mc.c  | 24 ++++++++++++++++
>  drivers/memory/tegra/mc.h  |  8 ++++++
>  3 files changed, 103 insertions(+)

We only need this for LP0, right? As such I'm reluctant to apply this
since we can't test it upstream.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-01-09 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  1:10 [PATCH v2] memory: Add NVIDIA SMMU suspend/resume support Mark Zhang
2015-01-09 11:57 ` Thierry Reding [this message]

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=20150109115706.GH16465@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=hdoyu@nvidia.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=markz@nvidia.com \
    --cc=olof@lixom.net \
    --cc=swarren@wwwdotorg.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).