linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Vikas Aggarwal" <va824363@albany.edu>
To: "Kim Phillips" <kim.phillips@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8248  SEC -- interrupt handler 'is' invoked
Date: Wed, 3 Aug 2005 14:33:26 -0400 (EDT)	[thread overview]
Message-ID: <30177.198.22.236.230.1123094006.squirrel@198.22.236.230> (raw)
In-Reply-To: <20050803114749.739ae51e.kim.phillips@freescale.com>

I will try the new BSP but meanwhile like to debug my ported driver.

Is there a way , like kernel level single-stepping to know why the
"interrupt status register"  gets a value of "0x0000000000000040" which
means TEA , transfer error acknowledge.

I changed and tested ur latest advice but same error in "interrupt status
register"

-vikas


> On Tue, 2 Aug 2005 11:45:15 -0400 (EDT)
> "Vikas Aggarwal" <va824363@albany.edu> wrote:
>
>>
>> This is how i write the address of RNG buffer(sec1_dpd.c.
>> DPDPTR->fld[i].ptr = virt_to_phys(*(unsigned int *) ((unsigned int)pReq
>> +
>> pDesc->fld[i].ptrOffset1st));
>>
>
> everything looks good except I'd try changing the above to something like:
>
> DPDPTR->fld[i].ptr = dma_map_single(NULL, ...ptrOffset1st,
> 		...lenOffset1st, DMA_TO_DEVICE);
>
> and change the DMA_BIDIRECTIONAL to DMA_TO_DEVICE in the DPD's address
> assignment.
>
> btw, a BSP upgrade (based on 2.6.11) for your platform should be available
> in a couple of weeks.  I'll let you know the status of the SEC driver for
> it.
>
> Kim
>

  reply	other threads:[~2005-08-03 18: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
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 [this message]
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=30177.198.22.236.230.1123094006.squirrel@198.22.236.230 \
    --to=va824363@albany.edu \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).