[Prism54-devel] No interrupt afterisl38xx_w32_flush(ISL38XX_DEV_INT_UPDATE...)?

[Barret,Lee]

Hi Kevin,
    I think it base on you host chip. You need check PCI setup on your host cpu(PCI configuration register Type0 WORD0 bit1).
BR,
Barret,Lee
  ----- Original Message ----- 
  From: waveon 
  To: prism54-devel at prism54.org 
  Sent: Wednesday, December 15, 2004 12:14 AM
  Subject: [Prism54-devel] No interrupt afterisl38xx_w32_flush(ISL38XX_DEV_INT_UPDATE...)? 


  Hi all,

  I try to port the prism54 driver to MIPS platform ( in little endian mode ) ,
  everything looks ok , but I can't get interrupt after I issue isl38xx_w32_flush(ISL38XX_DEV_INT_UPDATE) command.
  I observe that the mini-PCI signal REQ# , GNT# , FRAME# , IRDY# are already asserted , but DEVSEL# and TRDY# are still in de-asserted state.

  But if I try to trigger another interrupt such as ISL38XX_DEV_INT_SLEEP , I can get that interrupt immediately.
  Is this DMA problem ?

  I find there is someone encounter the same problem before ,but there is no response.
  Please reference the following link.   
  http://prism54.org/pipermail/prism54-devel/2004-May/001241.html

  Thanks for any help.

  Kevin


------------------------------------------------------------------------------


  _______________________________________________
  Prism54-devel mailing list
  Prism54-devel at prism54.org
  http://prism54.org/mailman/listinfo/prism54-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://prism54.org/pipermail/prism54-devel/attachments/20041215/1495ddc7/attachment.html