From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] Documentation: dt-bindings: Add option to workaround STE.VALID in Broadcom Vulcan
Date: Thu, 17 Dec 2015 11:51:03 +0000 [thread overview]
Message-ID: <20151217115102.GC11456@arm.com> (raw)
In-Reply-To: <1450346376-30920-2-git-send-email-pmallapp@broadcom.com>
[adding devicetree since I'd like an Ack from them if possible]
On Thu, Dec 17, 2015 at 03:29:36PM +0530, Prem Mallappa wrote:
> Signed-off-by: Prem Mallappa <pmallapp@broadcom.com>
Please can you add a commit message for this?
> ---
> Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt
> index 947863a..9c1218e 100644
> --- a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt
> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt
> @@ -43,6 +43,11 @@ the PCIe specification.
> - hisilicon,broken-prefetch-cmd
> : Avoid sending CMD_PREFETCH_* commands to the SMMU.
>
> +- broadcom,broken-ste-valid-check
> + : Broadcom specific, h/w peeks into more than just
> + STE.VALID bit in "Bypass" mode. Enabling this,
> + populates needed bits.
This should really describe more about what happens, I think. For example,
"Enable ATS and Stage-2 AArch64 translation in bypass STEs, since some
hardware requires this in order for an STE to be treated as valid."
Will
next prev parent reply other threads:[~2015-12-17 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:59 [PATCH v2 1/2] IOMMU: arm-smmu-v3: Fix broken STE.VALID check in Broadcom Vulcan Prem Mallappa
2015-12-17 9:59 ` [PATCH v2 2/2] Documentation: dt-bindings: Add option to workaround STE.VALID " Prem Mallappa
2015-12-17 11:51 ` Will Deacon [this message]
2015-12-17 12:00 ` Mark Rutland
2015-12-17 11:42 ` [PATCH v2 1/2] IOMMU: arm-smmu-v3: Fix broken STE.VALID check " Will Deacon
2015-12-19 4:47 ` Prem (Premachandra) Mallappa
2015-12-21 9:55 ` 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=20151217115102.GC11456@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).