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: APM smmu implementation
Date: Mon, 9 Jan 2017 10:54:21 +0000	[thread overview]
Message-ID: <20170109105421.GA21398@arm.com> (raw)
In-Reply-To: <CAL85gmA_SSCwM80TKdkZqEe+S1beWzDEvdki1kpkmUTDRmSP7g@mail.gmail.com>

On Fri, Jan 06, 2017 at 03:21:34PM -0800, Feng Kan wrote:
> The APM IOMMU implementation is mostly just the ARM SMMU 500 variant.
> However, our internal bus is only 42 bits wide. Our IAS field is coded
> as 48 bits, which cause IPA to truncated to 42 bits on the physical
> bus. In order for our system to work with the arm-smmu.c, there needs
> to be a way to force the ipa_size to 42. The current internal solution
> is to use the cpuid, but that is quite ugly. I was thinking of using
> the model

Just so I understand, what are the UBS and OAS values on your part?

> as indication to right the ipa_size, but I am not too sure of the ACPI
> side. Would it be okay to add an APM MMU500 variant? I would also
> appreciated it if you guys have any alternate solutions.

For this sort of implementation erratum, I think using the model field
is the right thing to do. However, you'll need to get your model registered
with IORT, so I've added Charles to cc since he maintains that document.

Also, please add a device-tree property to override the IAS once you
start writing patches.

Will

  reply	other threads:[~2017-01-09 10:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 23:21 APM smmu implementation Feng Kan
2017-01-09 10:54 ` Will Deacon [this message]
2017-01-09 17:37   ` Feng Kan
2017-01-09 11:34 ` Robin Murphy
2017-01-09 12:03   ` Will Deacon
2017-01-09 17:49     ` Feng Kan
2017-01-09 17:55     ` Robin Murphy
2017-07-12 21:07       ` Feng Kan
2017-07-12 23:28         ` Al Stone
2017-07-12 23:31           ` Feng Kan
2017-07-13 10:03             ` Robin Murphy
2017-07-13 16:08               ` Feng Kan
2017-07-13 16:41                 ` Edward Gasiorowski
2017-07-13 16:52                 ` Lorenzo Pieralisi

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=20170109105421.GA21398@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).