From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] iommu/arm-smmu-v2: ThunderX mis-extends 64bit registers
Date: Tue, 18 Aug 2015 13:44:48 +0100 [thread overview]
Message-ID: <20150818124448.GA13507@arm.com> (raw)
In-Reply-To: <1439853235-12162-1-git-send-email-tchalamarla@caviumnetworks.com>
Hi Tirumalesh,
On Tue, Aug 18, 2015 at 12:13:55AM +0100, tchalamarla at caviumnetworks.com wrote:
> From: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
>
> The SMMU architecture defines two different behaviors when 64-bit
> registers are written with 32-bit writes. The first behavior causes
> zero extension into the upper 32-bits. The second behavior splits a
> 64-bit register into "normal" 32-bit register pairs.
>
> On some buggy implementations, registers incorrectly zero extended
> when they should instead behave as normal 32-bit register pairs.
>
> Signed-off-by: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
>
> Changes from V2:
> - removed unused definitions
>
> Changes from V1:
> - Introduced smmu_writeq
> ---
> drivers/iommu/arm-smmu.c | 57 +++++++++++++++++++++++++-----------------------
> 1 file changed, 30 insertions(+), 27 deletions(-)
I'm happy with this, but it doesn't apply against mainline or my tree.
Please can you rebase it onto something more recent, preferably my
iommu/devel branch?
Thanks,
Will
prev parent reply other threads:[~2015-08-18 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 23:13 [PATCH V3] iommu/arm-smmu-v2: ThunderX mis-extends 64bit registers tchalamarla at caviumnetworks.com
2015-08-18 12:44 ` Will Deacon [this message]
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=20150818124448.GA13507@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).