From: Stephen Warren <swarren@wwwdotorg.org>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Hiroshi DOYU <hdoyu@nvidia.com>,
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: Fri, 11 May 2012 12:04:57 -0600 [thread overview]
Message-ID: <4FAD54C9.6040904@wwwdotorg.org> (raw)
In-Reply-To: <20120511094625.GA11750@amd.com>
On 05/11/2012 03:46 AM, Joerg Roedel wrote:
> On Thu, May 10, 2012 at 02:08:33PM -0600, Stephen Warren wrote:
>> 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.
>
> Any reason for splitting it up? The patches touch mostly drivers/iommu.
> So to avoid conflicts its probably the best to apply them together.
Patch 1 is the driver that touches drivers/iommu and related
documentation, whereas patch 2 touches the device tree file in
arch/arm/boot/dts. Either of the patches would get conflicts if they
were merged into the "other" tree.
next prev parent reply other threads:[~2012-05-11 18:05 UTC|newest]
Thread overview: 19+ 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
2012-05-10 22:38 ` Grant Likely
2012-05-11 9:46 ` Joerg Roedel
2012-05-11 18:04 ` Stephen Warren [this message]
2012-05-14 17:41 ` Stephen Warren
2012-05-17 16:48 ` Stephen Warren
2012-05-18 5:50 ` Hiroshi Doyu
2012-05-18 6:43 ` [PATCH 1/1] iommu/tegra: smmu: Add DMA window parser Hiroshi DOYU
2012-05-18 15:15 ` Stephen Warren
2012-05-18 20:56 ` Hiroshi Doyu
2012-05-21 12:47 ` joerg.roedel
[not found] ` <1340176620-13012-1-git-send-email-hdoyu@nvidia.com>
[not found] ` <4FE20457.8090307@wwwdotorg.org>
2012-06-21 6:46 ` [PATCH 1/5] iommu/tegra: smmu: Add DMA window parser, of_get_dma_window() Hiroshi Doyu
2012-06-21 6:57 ` Stephen Warren
2012-06-21 8:30 ` [v2 1/5] iommu: " Hiroshi Doyu
2012-06-21 16:18 ` Stephen Warren
2012-06-25 5:15 ` Hiroshi Doyu
2012-06-25 10:42 ` joerg.roedel
2012-05-10 7:50 ` [PATCH 2/2] ARM: dt: tegra30.dtsi: Add SMMU node Hiroshi DOYU
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=4FAD54C9.6040904@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).