From: robherring2@gmail•com (Rob Herring)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] documentation: iommu: add description of ARM System MMU binding
Date: Fri, 05 Apr 2013 13:25:26 -0500 [thread overview]
Message-ID: <515F1716.70309@gmail.com> (raw)
In-Reply-To: <20130405165745.GB17151@mudshark.cambridge.arm.com>
On 04/05/2013 11:57 AM, Will Deacon wrote:
> Hi Rob,
>
> On Fri, Apr 05, 2013 at 05:43:06PM +0100, Rob Herring wrote:
[...]
>>> +- compatible : Should be one of "arm,smmu-v1" or "arm,smmu-v2"
>>> + depending on the version of the architecture
>>> + implemented.
>>
>> We can keep these, but we should have specific models like arm,smmu-400,
>> etc. as well.
>
> Ok, if distinctions need to be between MMU-400 and a v1 implementation, then
> we can add those strings later.
No, you want to have specific values in the dtb's up front. If there is
something needed later in the kernel, you don't want to require a dtb
update then. Adding future parts later is fine, but we already know what
blocks we have.
Rob
next prev parent reply other threads:[~2013-04-05 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:50 [PATCH] documentation: iommu: add description of ARM System MMU binding Will Deacon
2013-04-05 16:43 ` Rob Herring
2013-04-05 16:57 ` Will Deacon
2013-04-05 18:25 ` Rob Herring [this message]
2013-04-08 8:59 ` Will Deacon
2013-04-05 20:44 ` Olav Haugan
2013-04-08 9:25 ` Will Deacon
2013-04-08 17:03 ` Olav Haugan
2013-04-10 17:37 ` Will Deacon
2013-04-13 21:02 ` Olav Haugan
2013-04-15 13:13 ` Will Deacon
2013-04-16 18:18 ` Olav Haugan
2013-04-18 19:01 ` Will Deacon
2013-04-23 22:54 ` Olav Haugan
2013-04-24 9:55 ` Will Deacon
2013-05-07 20:26 ` Olav Haugan
2013-05-13 9:07 ` Andreas Herrmann
2013-05-13 10:04 ` Will Deacon
2013-07-08 16:20 ` Olav Haugan
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=515F1716.70309@gmail.com \
--to=robherring2@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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