devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Hiroshi DOYU <hdoyu@nvidia.com>, Joerg Roedel <joerg.roedel@amd.com>
Cc: linux-tegra@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>, Ohad Ben-Cohen <ohad@wizery.com>,
	Tony Lindgren <tony@atomide.com>, Jiri Kosina <jkosina@suse.cz>,
	Thierry Reding <thierry.reding@avionic-design.de>,
	devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/tegra: smmu: Add device tree support for SMMU
Date: Thu, 10 May 2012 14:08:33 -0600	[thread overview]
Message-ID: <4FAC2041.7030405@wwwdotorg.org> (raw)
In-Reply-To: <1336636221-31575-2-git-send-email-hdoyu@nvidia.com>

On 05/10/2012 01:50 AM, Hiroshi DOYU wrote:
> The necessary info is expected to pass from DT.
> 
> For more precise resource reservation, there shouldn't be any
> overlapping of register range between SMMU and MC. SMMU register
> offset needs to be calculated correctly, based on its register bank.
> 
> Signed-off-by: Hiroshi DOYU <hdoyu@nvidia.com>

Acked-by: Stephen Warren <swarren@wwwdotorg.org>

I expect patch 1 will go through the IOMMU tree, and I'll take patch 2
through the Tegra tree.

  reply	other threads:[~2012-05-10 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1336636221-31575-1-git-send-email-hdoyu@nvidia.com>
2012-05-10  7:50 ` [PATCH 1/2] iommu/tegra: smmu: Add device tree support for SMMU Hiroshi DOYU
2012-05-10 20:08   ` Stephen Warren [this message]
     [not found]     ` <4FAC2041.7030405-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-10 22:38       ` Grant Likely
2012-05-11  9:46       ` Joerg Roedel
     [not found]         ` <20120511094625.GA11750-5C7GfCeVMHo@public.gmane.org>
2012-05-11 18:04           ` Stephen Warren
     [not found]   ` <1336636221-31575-2-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-14 17:41     ` Stephen Warren
     [not found]       ` <4FB143C4.6030502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-17 16:48         ` Stephen Warren
2012-05-18  5:50           ` Hiroshi Doyu
     [not found]             ` <20120518085051.4a0fca863c5ab37cf8d42cb1-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-18  6:43               ` [PATCH 1/1] iommu/tegra: smmu: Add DMA window parser Hiroshi DOYU
2012-05-18 15:15                 ` Stephen Warren
     [not found]                   ` <4FB66796.1030007-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-18 20:56                     ` Hiroshi Doyu
     [not found]                       ` <20120518.235619.175499431618565933.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-21 12:47                         ` joerg.roedel-5C7GfCeVMHo

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=4FAC2041.7030405@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hdoyu@nvidia.com \
    --cc=jkosina@suse.cz \
    --cc=joerg.roedel@amd.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=thierry.reding@avionic-design.de \
    --cc=tony@atomide.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).