From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Martin Schiller <mschiller@tdt.de>,
info-linux@geode.amd.com, linux-crypto@vger.kernel.org
Subject: Re: Testing the geode-aes driver with the tcrypt module completely freezes the machine
Date: Fri, 27 Apr 2007 13:53:11 +0400 [thread overview]
Message-ID: <20070427095311.GC29804@2ka.mipt.ru> (raw)
In-Reply-To: <20070427095033.GB29804@2ka.mipt.ru>
On Fri, Apr 27, 2007 at 01:50:37PM +0400, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> On Fri, Apr 27, 2007 at 06:10:51PM +1000, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> > > Has anyone else tried to test the geode-aes driver with the tcrypt module?
> > >
> > > I am also not able to use the geode-aes driver with openswan-2.4.7 on kernel
> > > 2.6.19 (with patched-in geode driver).
> >
> > Jordan, do you have any ideas why this is happening?
>
> Could it be compiler problem and broken hardware?
> Martin, can you test attached patch?
Or better this one:
diff --git a/drivers/crypto/geode-aes.c b/drivers/crypto/geode-aes.c
index 6d3840e..724169b 100644
--- a/drivers/crypto/geode-aes.c
+++ b/drivers/crypto/geode-aes.c
@@ -78,7 +78,7 @@ static int
do_crypt(void *src, void *dst, int len, u32 flags)
{
u32 status;
- u32 counter = AES_OP_TIMEOUT;
+ int counter = 0x1000;
iowrite32(virt_to_phys(src), _iobase + AES_SOURCEA_REG);
iowrite32(virt_to_phys(dst), _iobase + AES_DSTA_REG);
@@ -89,7 +89,9 @@ do_crypt(void *src, void *dst, int len, u32 flags)
do
status = ioread32(_iobase + AES_INTR_REG);
- while(!(status & AES_INTRA_PENDING) && --counter);
+ while(--counter > 0 && !(status & AES_INTRA_PENDING));
+
+ WARN_ON(!counter);
/* Clear the event */
iowrite32((status & 0xFF) | AES_INTRA_PENDING, _iobase + AES_INTR_REG);
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-04-27 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 9:04 Testing the geode-aes driver with the tcrypt module completely freezes the machine Martin Schiller
2007-04-26 11:05 ` Sebastian Siewior
2007-04-26 11:27 ` Martin Schiller
2007-04-27 8:10 ` Herbert Xu
2007-04-27 9:50 ` Evgeniy Polyakov
2007-04-27 9:53 ` Evgeniy Polyakov [this message]
2007-05-03 6:19 ` Martin Schiller
2007-05-03 7:57 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 13:12 Martin Schiller
2007-05-03 13:23 ` Evgeniy Polyakov
2007-05-03 13:49 ` Herbert Xu
2007-05-03 14:47 ` Jordan Crouse
2007-05-03 16:53 ` Evgeniy Polyakov
2007-05-03 14:08 ` Martin Schiller
2007-05-03 14:47 ` Evgeniy Polyakov
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=20070427095311.GC29804@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=herbert@gondor.apana.org.au \
--cc=info-linux@geode.amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mschiller@tdt.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