From: Kim Phillips <kim.phillips@freescale.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Steve Cornelius <sec@pobox.com>,
linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings
Date: Mon, 2 May 2011 18:27:27 -0500 [thread overview]
Message-ID: <20110502182727.366857bd.kim.phillips@freescale.com> (raw)
In-Reply-To: <20110415095049.GA2129@gondor.apana.org.au>
On Fri, 15 Apr 2011 17:50:49 +0800
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Mon, Apr 11, 2011 at 07:15:16PM -0500, Kim Phillips wrote:
> > - add IRQF_SHARED to request_irq flags to support parts such as
> > the p1023 that has one IRQ line per couple of rings.
> >
> > - resetting a job ring triggers an interrupt, so move request_irq
> > prior to jr_reset to avoid 'got IRQ but nobody cared' messages.
> >
> > - disable IRQs in h/w to avoid contention between reset and
> > interrupt status
> >
> > - delete invalid comment - if there were incomplete jobs,
> > module would be in use, preventing an unload.
> >
> > Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> > ---
> > this, and the remaining patches in this series, tested on p1023, p3041,
> > p4080, and 32- and 64-bit p5020.
>
> All four patches applied. Thanks Kim!
I don't see them in cryptodev-2.6 - did you forget to push them?
Thanks,
Kim
next prev parent reply other threads:[~2011-05-02 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 0:15 [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings Kim Phillips
2011-04-15 9:50 ` Herbert Xu
2011-05-02 23:27 ` Kim Phillips [this message]
2011-05-02 23:56 ` 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=20110502182727.366857bd.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sec@pobox.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).