From: Victoria Milhoan <vicki.milhoan@freescale.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Ruchika Gupta <ruchika.gupta@freescale.com>,
Victoria Milhoan <Vicki.Milhoan@freescale.com>,
Russell King <linux@arm.linux.org.uk>,
"Jon Nettleton" <jon.nettleton@gmail.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@pengutronix.de>
Subject: Re: [PATCH] crypto: caam - fix non-64-bit write/read access
Date: Wed, 17 Jun 2015 07:30:53 -0700 [thread overview]
Message-ID: <20150617073053.c52be013e710e8a79363dd9d@freescale.com> (raw)
In-Reply-To: <1434452347-27177-1-git-send-email-s.trumtrar@pengutronix.de>
On Tue, 16 Jun 2015 12:59:07 +0200
Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote:
> The patch
>
> crypto: caam - Add definition of rd/wr_reg64 for little endian platform
>
> added support for little endian platforms to the CAAM driver. Namely a
> write and read function for 64 bit registers.
> The only user of this functions is the Job Ring driver (drivers/crypto/caam/jr.c).
> It uses the functions to set the DMA addresses for the input/output rings.
> However, at least in the default configuration, the least significant 32 bits are
> always in the base+0x0004 address; independent of the endianness of the bytes itself.
> That means the addresses do not change with the system endianness.
>
> DMA addresses are only 32 bits wide on non-64-bit systems, writing the upper 32 bits
> of this value to the register for the least significant bits results in the DMA address
> being set to 0.
>
> Fix this by always writing the registers in the same way.
>
> Suggested-by: Russell King <linux@arm.linux.org.uk>
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> ---
>
> This patch is only compile-tested for PowerPC and tested on ARM.
> According to the datasheets for i.MX6 and P1010 this should be correct, though.
I can confirm that this patch works on both QorIQ/PowerPC and ARM devices.
next prev parent reply other threads:[~2015-06-17 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 10:59 Steffen Trumtrar
2015-06-17 14:30 ` Victoria Milhoan [this message]
2015-06-18 6:49 ` Herbert Xu
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=20150617073053.c52be013e710e8a79363dd9d@freescale.com \
--to=vicki.milhoan@freescale.com \
--cc=herbert@gondor.apana.org.au \
--cc=jon.nettleton@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ruchika.gupta@freescale.com \
--cc=s.trumtrar@pengutronix.de \
/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
all inboxes | Powered by JetHome®