From: Marek Vasut <marex@denx.de>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: "Gupta Ruchika-R66431" <ruchika.gupta@freescale.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] crypto:caam - Modify width of few read only registers
Date: Sat, 24 May 2014 14:34:46 +0200 [thread overview]
Message-ID: <201405241434.46807.marex@denx.de> (raw)
In-Reply-To: <20140507185442.02b5ec3c4e40baf6ef8d13b4@freescale.com>
On Thursday, May 08, 2014 at 01:54:42 AM, Kim Phillips wrote:
[...]
> > In the first version of guide they were defined as 64 bit. They were
> > later changed to 32 bit once issue was reported while testing on
> > emulator. Latest guide of LS2100 has them modified. A register width
> > column has also been added in the memory map now.
>
> I love how they try to cover up h/w bugs by amending the
> documentation...
Typical, yes :-(
[...]
> > Since these are 32 bit registers by nature, shouldn't we just treat them
> > as 32 bit instead of enabling the swapping option .
>
> depends on the definition of 'treat': I'd rather still use the
> superior 64-bit accessors on all possible arches, if we can get them
> to work.
Was there any resolution for this problem ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-05-24 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 10:04 [PATCH] crypto:caam - Modify width of few read only registers Ruchika Gupta
2014-05-01 20:45 ` Kim Phillips
2014-05-06 10:11 ` Ruchika Gupta
2014-05-06 20:32 ` Kim Phillips
2014-05-07 4:09 ` Ruchika Gupta
2014-05-07 23:54 ` Kim Phillips
2014-05-24 12:34 ` Marek Vasut [this message]
2014-06-11 4:36 ` Ruchika Gupta
2014-06-11 22:53 ` Kim Phillips
2014-06-12 9:56 ` Ruchika Gupta
2014-06-12 23:14 ` Kim Phillips
[not found] <herbert@gondor.apana.org.au, kim.phillips@freescale.com>
2014-04-29 10:02 ` Ruchika Gupta
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=201405241434.46807.marex@denx.de \
--to=marex@denx.de \
--cc=herbert@gondor.apana.org.au \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=ruchika.gupta@freescale.com \
/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).