linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 06/12] ARM: dts: Add description of System MMU of Exynos SoCs
Date: Thu, 8 Aug 2013 22:43:43 +0100	[thread overview]
Message-ID: <20130808214343.GA19383@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <5354557.DijgoUKjW2@flatron>

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

  reply	other threads:[~2013-08-08 21:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 11:28 [PATCH v8 06/12] ARM: dts: Add description of System MMU of Exynos SoCs 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 [this message]
2013-08-09  2:24           ` Cho KyongHo
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=20130808214343.GA19383@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).