From: Cho KyongHo <pullip.cho@samsung.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Rob Herring <robherring2@gmail.com>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Hyunwoong Kim <khw0178.kim@samsung.com>,
Prathyush <prathyush.k@samsung.com>,
Grant Grundler <grundler@chromium.org>,
Joerg Roedel <joro@8bytes.org>,
Keyyoung Park <keyyoung.park@samsung.com>,
Subash Patel <supash.ramaswamy@linaro.org>,
Sachin Kamat <sachin.kamat@linaro.org>,
Antonios Motakis <a.motakis@virtualopensystems.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Rahul Sharma <rahul.sharma@samsung.com>
Subject: Re: [PATCH v8 06/12] ARM: dts: Add description of System MMU of Exynos SoCs
Date: Fri, 09 Aug 2013 11:24:36 +0900 [thread overview]
Message-ID: <20130809112436.8e44545cd503ca5a2b55a8cd@samsung.com> (raw)
In-Reply-To: <20130808214343.GA19383@mudshark.cambridge.arm.com>
On Thu, 08 Aug 2013 22:43:43 +0100, Will Deacon wrote:
> On Thu, Aug 08, 2013 at 10:38:10PM +0100, Tomasz Figa wrote:
> > On Thursday 08 of August 2013 08:09:49 Rob Herring wrote:
> > > On Thu, Aug 1, 2013 at 8:05 AM, Cho KyongHo <pullip.cho@samsung.com>
> > wrote:
> > > > Should this align with ARM System MMU bindings?
> > > > System MMU in Exynos SoC is different from ARM System MMU.
> > > > It does not follows the specifications of ARM System MMU.
> > >
> > > I'm not saying the h/w is the same or even the same spec, but how you
> > > describe a master to iommu connection needs to be done in the same
> > > way. This should be done in the same way for ALL iommu's. And if what
> > > is defined does not work for you, then we need to understand that and
> > > fix the binding now.
> >
> > +1
> >
> > All IOMMUs should use a generic IOMMU Device Tree bindings (and in
> > general, the same should be true for all Device Tree bindings).
> >
> > This means that if we already have some bindings for IOMMU, then they
> > should be reused if possible or extended if there is anything missing.
> >
> > Of course there might be things that such generic bindings can't specify.
> > In this case device-specific properties can be introduced, but this is
> > last resort.
>
> I'm also happy to discuss and/or review bindings in light of what we did for
> the ARM SMMU.
>
> Will
Rob, I now understood what you are talking about.
Do you mean the binding description is lack of details about connection
betwen System MMU and its master?
thanks.
KyongHo.
next prev parent reply other threads:[~2013-08-09 2:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 11:28 Cho KyongHo
2013-07-26 17:58 ` Grant Grundler
2013-07-27 9:29 ` Cho KyongHo
2013-07-27 13:54 ` Rob Herring
2013-08-01 13:05 ` Cho KyongHo
2013-08-08 13:09 ` Rob Herring
2013-08-08 21:38 ` Tomasz Figa
2013-08-08 21:43 ` Will Deacon
2013-08-09 2:24 ` Cho KyongHo [this message]
2013-07-29 6:37 ` Sachin Kamat
2013-07-29 7:20 ` Cho KyongHo
2013-07-29 7:57 ` Cho KyongHo
2013-07-29 8:05 ` Sachin Kamat
2013-08-01 13:12 ` Cho KyongHo
2013-08-02 17:14 ` Bartlomiej Zolnierkiewicz
2013-08-05 11:16 ` Cho KyongHo
2013-08-05 13:09 ` Bartlomiej Zolnierkiewicz
2013-08-05 13:34 ` Marek Szyprowski
2013-08-06 9:54 ` Cho KyongHo
2013-08-06 13:17 ` Marek Szyprowski
2013-08-06 16:07 ` Grant Grundler
2013-08-07 12:07 ` Cho KyongHo
2013-08-07 16:21 ` Grant Grundler
2013-08-08 2:19 ` Cho KyongHo
2013-10-07 13:44 ` Rob Herring
2013-10-08 4:38 ` Cho KyongHo
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=20130809112436.8e44545cd503ca5a2b55a8cd@samsung.com \
--to=pullip.cho@samsung.com \
--cc=a.motakis@virtualopensystems.com \
--cc=grundler@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=keyyoung.park@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=khw0178.kim@samsung.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prathyush.k@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=robherring2@gmail.com \
--cc=sachin.kamat@linaro.org \
--cc=supash.ramaswamy@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=will.deacon@arm.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®