From: Kim Phillips <kim.phillips@freescale.com>
To: "Vikas Aggarwal" <va824363@albany.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8248 SEC -- interrupt handler not invoked
Date: Fri, 29 Jul 2005 15:33:23 -0500 [thread overview]
Message-ID: <20050729153323.3f2c62ad.kim.phillips@freescale.com> (raw)
In-Reply-To: <32704.198.22.236.230.1122651627.squirrel@198.22.236.230>
On Fri, 29 Jul 2005 11:40:27 -0400 (EDT)
"Vikas Aggarwal" <va824363@albany.edu> wrote:
> Hi All,
> Will appreciate if someone can guide me how to debug this inside SEC
> (security co-processor) core.
>
> The linux driver is writing descriptor into the FETCH-Register(0x2048)
> for Random Number generation execution unit(RNG-EU). The request came
> through a test program from user space. The RNG generation request never
> seems to complete as my ISR is not invoked.
> I checked the CCPSR(Crypto Channel Pointer Status register = 0x2010) and
> it has value=0:7(0-31 : 32-63 bits). 7 means "channel_error". But its
> always there even before I write the RNG descriptor to Fetch-register.
a value of 7 in bits 56-63 (PAIR_PTR) can suggest processing has not begun.
can you verify you are writing the upper bits of the FR (i.e. 0x204c)?
Kim
next prev parent reply other threads:[~2005-07-29 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 15:40 mpc8248 SEC -- interrupt handler not invoked Vikas Aggarwal
2005-07-29 20:33 ` Kim Phillips [this message]
2005-07-30 3:39 ` Vikas Aggarwal
2005-07-30 23:32 ` Kim Phillips
2005-08-01 0:48 ` mpc8248 SEC -- interrupt handler "is" invoked Vikas Aggarwal
2005-08-01 17:37 ` Kim Phillips
2005-08-01 18:50 ` mpc8248 SEC -- interrupt handler 'is' invoked Vikas Aggarwal
2005-08-02 15:45 ` Vikas Aggarwal
2005-08-03 16:47 ` Kim Phillips
2005-08-03 18:33 ` Vikas Aggarwal
2005-08-03 20:35 ` Kim Phillips
2005-08-09 13:38 ` Vikas Aggarwal
2005-08-09 15:13 ` Kim Phillips
2005-08-09 20:52 ` Vikas Aggarwal
2005-08-10 15:37 ` Kim Phillips
2005-08-11 18:48 ` Vikas Aggarwal
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=20050729153323.3f2c62ad.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=va824363@albany.edu \
/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).