From: Hiroshi Doyu <hdoyu@nvidia.com>
To: Joerg Roedel <joerg.roedel@amd.com>,
Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux-tegra@vger.kernel.org" <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"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] iommu/tegra: smmu: Add device tree support for SMMU
Date: Fri, 18 May 2012 08:50:51 +0300 [thread overview]
Message-ID: <20120518085051.4a0fca863c5ab37cf8d42cb1@nvidia.com> (raw)
In-Reply-To: <4FB52BE7.8080908@wwwdotorg.org>
Hi Stephen and Joerg,
On Thu, 17 May 2012 18:48:39 +0200
Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 05/14/2012 11:41 AM, 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>
> >> ---
> >> This patch requires the following ones, sent earlier:
> >>
> >> DMA window:
> >> http://article.gmane.org/gmane.linux.ports.tegra/4603
> >
> > This patch has been merged even though the patch above isn't present in
> > the kernel anywhere, let alone in the history of the iommu tree. This
> > breaks compilation in linux-next.
> >
> >> AHB:
> >> http://article.gmane.org/gmane.linux.ports.tegra/4657
> >
> > This patch is in linux-next, but also is not in the history of the iommu
> > tree, so will break bisection of the iommu tree for Tegra.
>
> Joerg,
>
> Can this patch please be dropped or reverted? It's still breaking
> tegra_defconfig in next-20120517 since the dependencies I mentioned
> above aren't satisfied. At this stage, it seems unlikely that the DMA
> window parsing change is going to make it into 3.5, so this isn't just a
> temporary issue.
I can move of_get_dma_window() function into tegra-smmu.c as a static
function. I just want SMMU available with DT for the furthuer
development. Then, it's also possible to promote that function global
later as is in the origianl patch.
I'm posting that patch follows this email. Please take it if this
proposal is acceptable.
next prev parent reply other threads:[~2012-05-18 5:51 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 ` 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
2012-05-14 17:41 ` Stephen Warren
2012-05-17 16:48 ` Stephen Warren
2012-05-18 5:50 ` Hiroshi Doyu [this message]
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=20120518085051.4a0fca863c5ab37cf8d42cb1@nvidia.com \
--to=hdoyu@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--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=swarren@wwwdotorg.org \
--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
all inboxes | Powered by JetHome®