Skip to contentSkip to conversation

TI dspbridge rebase against latest l-o

FYI Rick Bronson 2 participants 2 messages Nov 8, 2008

lore
Share & tools
lore
#0 lore raw

Hi Hiroshi,

I just tried this on my beagleboard and I'm not sure if it worked.
First, did you forget to add that you need "mem=122m" in the bootargs? Also do you need to add in the addresses like:

sudo modprobe bridgedriver phys_mempool_base=0x87a00000 phys_mempool_size=0x600000 base_img=/home/rick/dspbridge_binaries/ddspbase_tiomap3430.dof64P

Anyway, when I followed the instructions (except for above) I get:

Quoted 1 line

sudo modprobe bridgedriver phys_mempool_base=0x87a00000 phys_mempool_size=0x60

0000 base_img=/home/rick/dspbridge_binaries/ddspbase_tiomap3430.dof64P

Quoted 1 line

lsmod

Module Size Used by
bridgedriver 356488 0

Quoted 1 line

cat /proc/interrupts | grep Dsp

 26:          3        INTC  DspBridge                                          
 28:          0        INTC  DspBridge                                          
Quoted 3 lines

/home/rick/dspbridge_binaries/ping.out

cat /proc/interrupts | grep Dsp

 26:          4        INTC  DspBridge                                          
 28:          0        INTC  DspBridge                                          

After this, no matter how many times I run ping, I get the same
number of interrupts. How do I know ping is really working?

Thanks,

Rick

#1 lore raw

Hi Rick, thank you for comments.

From: "ext Rick Bronson" <[email protected]>
Subject: Re: [FYI] TI dspbridge rebase against latest l-o
Date: Fri, 07 Nov 2008 19:15:44 -0800

Quoted 5 lines

Hi Hiroshi,

I just tried this on my beagleboard and I'm not sure if it worked.
First, did you forget to add that you need "mem=122m" in the bootargs? Also do you need to add in the addresses like:

I don't think that it's mandatory. Without phys_* parameters, just dynamic allocation from non-reserved area would be used. This may sometimes suffer from memory allocation, especially in the case that the target board has small amount of memory(RAM).

Quoted 12 lines

sudo modprobe bridgedriver phys_mempool_base=0x87a00000 phys_mempool_size=0x600000 base_img=/home/rick/dspbridge_binaries/ddspbase_tiomap3430.dof64P

Anyway, when I followed the instructions (except for above) I get:

Quoted 1 line

sudo modprobe bridgedriver phys_mempool_base=0x87a00000 phys_mempool_size=0x60

0000 base_img=/home/rick/dspbridge_binaries/ddspbase_tiomap3430.dof64P

Quoted 1 line

lsmod

Module Size Used by
bridgedriver 356488 0

Quoted 1 line

cat /proc/interrupts | grep Dsp

 26:          3        INTC  DspBridge                                          
 28:          0        INTC  DspBridge                                          
Quoted 8 lines
Quoted 3 lines

/home/rick/dspbridge_binaries/ping.out

cat /proc/interrupts | grep Dsp

 26:          4        INTC  DspBridge                                          
 28:          0        INTC  DspBridge                                          

After this, no matter how many times I run ping, I get the same
number of interrupts. How do I know ping is really working?

The above is a bit different from mine as below, where the count of mailbox interrupt are incremented reasonably.

bridge:~$ modprobe bridgedriver base_img=ddspbase_tiomap3430.dof64P 
bridge:~$ grep DspBridge /proc/interrupts 
 26:          3        INTC  DspBridge  mailbox
 28:          0        INTC  DspBridge  iommu fault
bridge:~$ ./ping.out > /dev/null
bridge:~$ grep DspBridge /proc/interrupts 
 26:        169        INTC  DspBridge  mailbox
 28:          0        INTC  DspBridge  iommu fault
bridge:~$ ./ping.out > /dev/null
bridge:~$ grep DspBridge /proc/interrupts 
 26:        334        INTC  DspBridge  mailbox
 28:          0        INTC  DspBridge  iommu fault
bridge:~$ 

You can see how it's working by appending GT_str="**=01234567" on module parameter to investigate further.

Hiroshi DOYU

Quoted 1 line

From f9331a0c1b04cf812624b0e1d96ce491ddb0d7d1 Mon Sep 17 00:00:00 2001

From: Hiroshi DOYU <[email protected]>
Date: Sat, 8 Nov 2008 06:17:08 +0200
Subject: [PATCH 1/1] BRIDGE: use more detail name for interrupt claiming device

---
 drivers/dsp/bridge/wmd/io_sm.c  |    2 +-
 drivers/dsp/bridge/wmd/ue_deh.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
drivers/dsp/bridge/wmd/io_sm.c +1 -1
index 08bc4d3..6843a42 100644
@@ -341,7 +341,7 @@ DSP_STATUS WMD_IO_Create(OUT struct IO_MGR **phIOMgr,
 		if (devType == DSP_UNIT) {
 			/* Plug the channel ISR:. */
                        if ((request_irq(INT_MAIL_MPU_IRQ, IO_ISR, 0,
-                                           "DspBridge", (void *)pIOMgr)) == 0)
+                                           "DspBridge\tmailbox", (void *)pIOMgr)) == 0)
                                status = DSP_SOK;
                        else
                                status = DSP_EFAIL;
drivers/dsp/bridge/wmd/ue_deh.c +1 -1
index 7e450b3..2110353 100644
@@ -121,7 +121,7 @@ DSP_STATUS WMD_DEH_Create(OUT struct DEH_MGR **phDehMgr,
 			pDehMgr->errInfo.dwVal3 = 0L;
 			/* Install ISR function for DSP MMU fault */
                        if ((request_irq(INT_DSP_MMU_IRQ, MMU_FaultIsr, 0,
-                                           "DspBridge", (void *)pDehMgr)) == 0)
+                                           "DspBridge\tiommu fault", (void *)pDehMgr)) == 0)
                                status = DSP_SOK;
                        else
                                status = DSP_EFAIL;
Signature · 1 line
1.5.5.1.357.g1af8b