From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] documentation/iommu: update description of ARM System MMU binding
Date: Fri, 28 Feb 2014 16:21:14 +0000 [thread overview]
Message-ID: <20140228162114.GA30996@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAOZdJXUfAygZqw9s5qOECLjyo=B0VaD29iesbWzDeMbbyVTgqg@mail.gmail.com>
On Fri, Feb 28, 2014 at 04:17:43PM +0000, Timur Tabi wrote:
> On Fri, Feb 21, 2014 at 11:16 AM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > +- calxeda,smmu-secure-config-access : Enable proper handling of buggy
> > + implementations that always use secure access to
> > + SMMU configuration registers. In this case non-secure
> > + aliases of secure registers have to be used during
> > + SMMU configuration.
>
> I'm confused. Why does this property have a "calxeda" prefix? How is
> it a Calxeda-specific property?
Because they wired up their SMMU backwards. It's basically an
implementation-specific erratum workaround.
Will
next prev parent reply other threads:[~2014-02-28 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 17:16 [PATCH 0/5] iommu/arm-smmu: updates for 3.15 Will Deacon
2014-02-21 17:16 ` [PATCH 1/5] iommu/arm-smmu: set MAX_MASTER_STREAMIDS to MAX_PHANDLE_ARGS Will Deacon
2014-02-21 17:16 ` [PATCH 2/5] iommu/arm-smmu: support buggy implementations with secure cfg accesses Will Deacon
2014-02-21 17:16 ` [PATCH 3/5] documentation/iommu: update description of ARM System MMU binding Will Deacon
2014-02-21 18:57 ` Sergei Shtylyov
2014-02-28 16:17 ` Timur Tabi
2014-02-28 16:21 ` Will Deacon [this message]
2014-02-28 17:07 ` Timur Tabi
2014-03-04 10:08 ` Will Deacon
2014-03-04 13:20 ` Timur Tabi
2014-02-21 17:16 ` [PATCH 4/5] iommu/arm-smmu: clean up use of `flags' in page table handling code Will Deacon
2014-02-21 17:16 ` [PATCH 5/5] iommu/arm-smmu: provide option to dsb macro when publishing tables Will Deacon
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=20140228162114.GA30996@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).