linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
	linuxppc-dev@ozlabs.org, mr.scada@gmail.com,
	linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
Date: Fri, 30 May 2008 15:35:05 -0500	[thread overview]
Message-ID: <20080530153505.21eb1ec4.kim.phillips@freescale.com> (raw)
In-Reply-To: <4840615F.4070103@freescale.com>

On Fri, 30 May 2008 15:19:43 -0500
Scott Wood <scottwood@freescale.com> wrote:

> Kim Phillips wrote:
> > On Fri, 30 May 2008 14:41:17 -0500
> > Scott Wood <scottwood@freescale.com> wrote:
> > 
> >> Kim Phillips wrote:
> >>> On Fri, 30 May 2008 22:09:04 +0400
> >>> Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> >>>> Don't you want to protect against simultaneous access to register space
> >>>> from different CPUs? Or it is single processor board only?
> >>> Doesn't linux mask the IRQ line for the interrupt currently being
> >>> serviced, and on all processors?
> >> Yes.  Could there be interference from non-interrupt driver code on 
> >> another cpu (or interrupted code), though?
> > 
> > not that I can see - the fetch fifo register writes are protected with
> > per-channel spinlocks.
> 
> But you don't take the spinlocks from the interrupt handler.

why can't fetch fifo registers be written the same time the ISR is
being accessed?

Kim

  reply	other threads:[~2008-05-30 20:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 19:12 [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver Kim Phillips
2008-05-30 18:09 ` Evgeniy Polyakov
2008-05-30 19:36   ` Kim Phillips
2008-05-30 19:41     ` Scott Wood
2008-05-30 20:13       ` Evgeniy Polyakov
2008-05-30 20:16       ` Kim Phillips
2008-05-30 20:19         ` Scott Wood
2008-05-30 20:35           ` Kim Phillips [this message]
2008-05-30 20:36             ` Scott Wood
2008-05-30 20:48               ` Kim Phillips
2008-05-30 21:12                 ` Evgeniy Polyakov
2008-05-30 22:19                   ` Kim Phillips
2008-05-31  9:59                     ` Evgeniy Polyakov
2008-06-02 14:27                       ` Kim Phillips
2008-06-02 16:00                         ` Evgeniy Polyakov
2008-06-02 16:50                           ` Kim Phillips
2008-06-02 17:57                             ` Evgeniy Polyakov
2008-06-02 19:06                               ` Kim Phillips
2008-06-03  1:24                                 ` 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=20080530153505.21eb1ec4.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mr.scada@gmail.com \
    --cc=scottwood@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).