This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C62D84.19AA9320
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi everyone, I am working with a pxa27x and I also have a fpga that =
doing background tasks that could raise an interrupt on a gpio pin of =
the pxa27x. I have implemented the functions for managing the interrupt =
requests. But I am experiencing this problem : my driver's thread =
doesn't get his event signaled when I return the associated sysintr =
with the event in the function BspIntrActiveIrq.

Here's what I do :
- In BspIntrInit I do a mapping of the sysintr with =
OALIntrStaticTranslate( sysintr, sysintr).
- In BspIntrEnableIrq I set the corresponding register of my fpga for =
enabling the interruption and return OAL_INTR_IRQ_UNDEFINED .
- In BspIntrDisableIrq about the same of BspIntrDisableIrq
- In BspIntrActiveIrq I read the the fpga status register to know which =
sysintr to return, clearing the status bit of the gpio and return the =
sysintr.

If you need more details so you can help me out, let me know.

Regards,
Keaven
------=_NextPart_000_0006_01C62D84.19AA9320
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DCourier size=3D1>Hi everyone, I am working with a =
pxa27x and I=20
also have a fpga that doing background tasks that could raise an =
interrupt on a=20
gpio pin of the pxa27x.&nbsp; I have implemented the functions for =
managing the=20
interrupt requests. But&nbsp;I am experiencing this problem : my =
driver's thread=20
doesn't get his event signaled when I return the associated =
sysintr&nbsp; with=20
the event in the function BspIntrActiveIrq.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Here's what I do :</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrInit I do a mapping of =
the sysintr=20
with OALIntrStaticTranslate( sysintr, sysintr).</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrEnableIrq I set the =
corresponding=20
register of my fpga for enabling the interruption and return=20
OAL_INTR_IRQ_UNDEFINED .</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrDisableIrq about the same =
of=20
BspIntrDisableIrq</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrActiveIrq I read the the =
fpga status=20
register to know which sysintr to return, clearing the status bit of the =
gpio=20
and return the sysintr.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>If you need more details so you can =
help me out,=20
let me know.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Regards,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>Keaven</FONT></DIV></BODY></HTML>

------=_NextPart_000_0006_01C62D84.19AA9320--

Re: Interrupt Handler by Tom

Tom
Thu Feb 09 14:37:28 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_00FA_01C62D8E.B5933FD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Have you verified that the interrupt is actually received and that =
BspIntrActiveIrq is called an returns the SYSINTR your driver's event is =
registered for? You don't mention programming the PXA gpio as an input, =
programming it's edge trigger for interrupt signalling, or enabling the =
gpio interrupt at the CPU's interrupt mask register anywhere, so I want =
to know if you're sure the interrupt is really firing. Also, have you =
verified that your driver is registering it's interrupt event with the =
correct SYSINTR number? =20

Tom Gensel (eMVP)

------=_NextPart_000_00FA_01C62D8E.B5933FD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Have you verified that the interrupt is =
actually=20
received and that BspIntrActiveIrq is called an returns the SYSINTR your =

driver's event&nbsp;is registered for?&nbsp; You don't mention =
programming the=20
PXA gpio as an input,&nbsp;programming it's edge trigger&nbsp; for =
interrupt=20
signalling, or enabling the gpio interrupt at the CPU's interrupt mask =
register=20
anywhere, so I want to know if you're sure the interrupt is really=20
firing.&nbsp;&nbsp;A</FONT><FONT face=3DArial size=3D2>lso, have =
you&nbsp;verified=20
that your driver is registering it's interrupt event with the correct =
SYSINTR=20
number?&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom Gensel (eMVP)</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00FA_01C62D8E.B5933FD0--


Re: Interrupt Handler by voidcoder

voidcoder
Thu Feb 09 14:56:57 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01C62DC3.BF3F30E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sounds right. How do you initialize interrupt in the driver? And why do =
you need=20
OALIntrStaticTranslate( sysintr, sysintr)?


"Keaven Pineau" <kpineau@labcal_antispam.com> wrote in message =
news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl...
Hi everyone, I am working with a pxa27x and I also have a fpga that =
doing background tasks that could raise an interrupt on a gpio pin of =
the pxa27x. I have implemented the functions for managing the interrupt =
requests. But I am experiencing this problem : my driver's thread =
doesn't get his event signaled when I return the associated sysintr =
with the event in the function BspIntrActiveIrq.

Here's what I do :
- In BspIntrInit I do a mapping of the sysintr with =
OALIntrStaticTranslate( sysintr, sysintr).
- In BspIntrEnableIrq I set the corresponding register of my fpga for =
enabling the interruption and return OAL_INTR_IRQ_UNDEFINED .
- In BspIntrDisableIrq about the same of BspIntrDisableIrq
- In BspIntrActiveIrq I read the the fpga status register to know =
which sysintr to return, clearing the status bit of the gpio and return =
the sysintr.

If you need more details so you can help me out, let me know.

Regards,
Keaven
------=_NextPart_000_0046_01C62DC3.BF3F30E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Sounds right. How do=20
you&nbsp;initialize&nbsp;interrupt in&nbsp;the driver?&nbsp;And why do =
you need=20
</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>OALIntrStaticTranslate( sysintr,=20
sysintr)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Keaven Pineau" &lt;<A=20
=
href=3D"mailto:kpineau@labcal_antispam.com">kpineau@labcal_antispam.com</=
A>&gt;=20
wrote in message <A=20
=
href=3D"news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl">news:OpXmD4aLGHA.500@T=
K2MSFTNGP15.phx.gbl</A>...</DIV>
<DIV><FONT face=3DCourier size=3D1>Hi everyone, I am working with a =
pxa27x and I=20
also have a fpga that doing background tasks that could raise an =
interrupt on=20
a gpio pin of the pxa27x.&nbsp; I have implemented the functions for =
managing=20
the interrupt requests. But&nbsp;I am experiencing this problem : my =
driver's=20
thread doesn't get his event signaled when I return the associated=20
sysintr&nbsp; with the event in the function =
BspIntrActiveIrq.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Here's what I do :</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrInit I do a mapping of =
the sysintr=20
with OALIntrStaticTranslate( sysintr, sysintr).</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrEnableIrq I set the =
corresponding=20
register of my fpga for enabling the interruption and return=20
OAL_INTR_IRQ_UNDEFINED .</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrDisableIrq about the =
same of=20
BspIntrDisableIrq</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrActiveIrq I read the =
the fpga=20
status register to know which sysintr to return, clearing the status =
bit of=20
the gpio and return the sysintr.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>If you need more details so you can =
help me=20
out, let me know.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Regards,</FONT></DIV>
<DIV><FONT face=3DCourier =
size=3D1>Keaven</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0046_01C62DC3.BF3F30E0--


Re: Interrupt Handler by Valter

Valter
Fri Feb 10 02:57:42 CST 2006

"Keaven Pineau" <kpineau@labcal_antispam.com> wrote in
news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl:

> Hi everyone, I am working with a pxa27x and I also have a fpga
> that doing background tasks that could raise an interrupt on a
> gpio pin of the pxa27x. I have implemented the functions for
> managing the interrupt requests. But I am experiencing this
> problem : my driver's thread doesn't get his event signaled when I
> return the associated sysintr with the event in the function
> BspIntrActiveIrq.
>
> Here's what I do :
> - In BspIntrInit I do a mapping of the sysintr with
> OALIntrStaticTranslate( sysintr, sysintr). - In BspIntrEnableIrq I
> set the corresponding register of my fpga for enabling the
> interruption and return OAL_INTR_IRQ_UNDEFINED . - In
> BspIntrDisableIrq about the same of BspIntrDisableIrq - In
> BspIntrActiveIrq I read the the fpga status register to know which
> sysintr to return, clearing the status bit of the gpio and return
> the sysintr.
>
> If you need more details so you can help me out, let me know.

BspIntrActiveIrq should not return a SYSINTR code.
It is called when an interrupt has been signaled on a GPIO pin and it
should return a sort of "virtual" interrupt code. The first 32
interrupt codes are defined as IRQ_* and mapped to the 32 bits of the
PXA interrupt pending register bits (the PXA has 2 irq pending
register, in the second one there's only one used bit, the LSB, that is
connected to the QCI, but the BSP provided with CE doesn't handle it
and you'll have to clone and change common code if you want to use that
peripheral device). External devices are mapped to values higher than
32 using constant values defined in intr.c.
You'll have to define a new IRQ_* value for your external device, map
it to the appropriate SYSINTR in BSPIntrInit, insert your
enable/disable code in the BSPIntr* functions (you need to enable the
IRQ on the FPGA but also on the PXA GPIO controller, configuring the
pin in the right way (alternate function set to 0, direction set to
input and rising/falling edge detect enabled).
In BSPIntrActiveIrq, if your FPGA is not connected to PIN 0/1 you've to
read the GPDR register, and then disable the rising/falling edge
detection on that pin (the system will call BSPIntrDoneIrq when your
IST calls InterruptDone) and clear the edge detect bit in GEDR register
by writing an 1 into the corrisponding bit.

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)

Re: Interrupt Handler by bluesphere

bluesphere
Fri Feb 10 15:57:17 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C62E95.57A7D720
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


It's not clear whether your FPGA acts like a

Secondary Interrupt Controller=20
[in this case Platform\MAINSTONEII shows the=20
example you need, as they all replied]

or like an

Application (background tasks)
[in this case you shouldn't put your hands on
the OAL, unless it doesn't manage the GPIO's
IRQ by default]




"Keaven Pineau" <kpineau@labcal_antispam.com> wrote in message =
news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl...
Hi everyone, I am working with a pxa27x and I also have a fpga that =
doing background tasks that could raise an interrupt on a gpio pin of =
the pxa27x. I have implemented the functions for managing the interrupt =
requests. But I am experiencing this problem : my driver's thread =
doesn't get his event signaled when I return the associated sysintr =
with the event in the function BspIntrActiveIrq.

Here's what I do :
- In BspIntrInit I do a mapping of the sysintr with =
OALIntrStaticTranslate( sysintr, sysintr).
- In BspIntrEnableIrq I set the corresponding register of my fpga for =
enabling the interruption and return OAL_INTR_IRQ_UNDEFINED .
- In BspIntrDisableIrq about the same of BspIntrDisableIrq
- In BspIntrActiveIrq I read the the fpga status register to know =
which sysintr to return, clearing the status bit of the gpio and return =
the sysintr.

If you need more details so you can help me out, let me know.

Regards,
Keaven
------=_NextPart_000_000B_01C62E95.57A7D720
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It's not clear whether your FPGA acts =
like=20
a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Secondary Interrupt Controller =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[in this case&nbsp;Platform\MAINSTONEII =
shows the=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>example </FONT><FONT face=3DArial =
size=3D2>you=20
need,&nbsp;as they all replied]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>or like an</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Application (background =
tasks)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[in this case you shouldn't put your =
hands=20
on</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the OAL, unless it doesn't manage the=20
GPIO's</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IRQ by default]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Keaven Pineau" &lt;<A=20
=
href=3D"mailto:kpineau@labcal_antispam.com">kpineau@labcal_antispam.com</=
A>&gt;=20
wrote in message <A=20
=
href=3D"news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl">news:OpXmD4aLGHA.500@T=
K2MSFTNGP15.phx.gbl</A>...</DIV>
<DIV><FONT face=3DCourier size=3D1>Hi everyone, I am working with a =
pxa27x and I=20
also have a fpga that doing background tasks that could raise an =
interrupt on=20
a gpio pin of the pxa27x.&nbsp; I have implemented the functions for =
managing=20
the interrupt requests. But&nbsp;I am experiencing this problem : my =
driver's=20
thread doesn't get his event signaled when I return the associated=20
sysintr&nbsp; with the event in the function =
BspIntrActiveIrq.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Here's what I do :</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrInit I do a mapping of =
the sysintr=20
with OALIntrStaticTranslate( sysintr, sysintr).</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrEnableIrq I set the =
corresponding=20
register of my fpga for enabling the interruption and return=20
OAL_INTR_IRQ_UNDEFINED .</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrDisableIrq about the =
same of=20
BspIntrDisableIrq</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrActiveIrq I read the =
the fpga=20
status register to know which sysintr to return, clearing the status =
bit of=20
the gpio and return the sysintr.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>If you need more details so you can =
help me=20
out, let me know.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Regards,</FONT></DIV>
<DIV><FONT face=3DCourier =
size=3D1>Keaven</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000B_01C62E95.57A7D720--


Re: Interrupt Handler by Keaven

Keaven
Wed Feb 15 08:43:33 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_001D_01C63214.48F6DAF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks all for your response. I found my problem, it was a pointer to a =
xllp_gpio structure that has not been initialize correctly. So when I =
passed it to XllpGpioGetEdgeDetectStatus it does an unwanted action.

Everything work well now :)

ps as an answer to bluesphere it was a secondary interrupt controller
"bluesphere" <ads_box@hotmail.com> wrote in message =
news:43ed0be7$0$12598$4fafbaef@reader3.news.tin.it...

It's not clear whether your FPGA acts like a

Secondary Interrupt Controller=20
[in this case Platform\MAINSTONEII shows the=20
example you need, as they all replied]

or like an

Application (background tasks)
[in this case you shouldn't put your hands on
the OAL, unless it doesn't manage the GPIO's
IRQ by default]




"Keaven Pineau" <kpineau@labcal_antispam.com> wrote in message =
news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl...
Hi everyone, I am working with a pxa27x and I also have a fpga that =
doing background tasks that could raise an interrupt on a gpio pin of =
the pxa27x. I have implemented the functions for managing the interrupt =
requests. But I am experiencing this problem : my driver's thread =
doesn't get his event signaled when I return the associated sysintr =
with the event in the function BspIntrActiveIrq.

Here's what I do :
- In BspIntrInit I do a mapping of the sysintr with =
OALIntrStaticTranslate( sysintr, sysintr).
- In BspIntrEnableIrq I set the corresponding register of my fpga =
for enabling the interruption and return OAL_INTR_IRQ_UNDEFINED .
- In BspIntrDisableIrq about the same of BspIntrDisableIrq
- In BspIntrActiveIrq I read the the fpga status register to know =
which sysintr to return, clearing the status bit of the gpio and return =
the sysintr.

If you need more details so you can help me out, let me know.

Regards,
Keaven
------=_NextPart_000_001D_01C63214.48F6DAF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks all for your response.&nbsp; I =
found my=20
problem, it&nbsp;was&nbsp;a pointer to a&nbsp;xllp_gpio structure =
that&nbsp;has=20
not been initialize correctly.&nbsp;&nbsp;So when I passed it to=20
XllpGpioGetEdgeDetectStatus it does an unwanted action.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Everything work well now =
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>ps as an answer to bluesphere it was a =
secondary=20
interrupt controller</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"bluesphere" &lt;<A=20
href=3D"mailto:ads_box@hotmail.com">ads_box@hotmail.com</A>&gt; wrote =
in message=20
<A=20
=
href=3D"news:43ed0be7$0$12598$4fafbaef@reader3.news.tin.it">news:43ed0be7=
$0$12598$4fafbaef@reader3.news.tin.it</A>...</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It's not clear whether your FPGA acts =
like=20
a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Secondary Interrupt Controller =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[in this =
case&nbsp;Platform\MAINSTONEII shows the=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>example </FONT><FONT face=3DArial =
size=3D2>you=20
need,&nbsp;as they all replied]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>or like an</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Application (background =
tasks)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[in this case you shouldn't put your =
hands=20
on</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the OAL, unless it doesn't manage the =

GPIO's</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IRQ by default]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Keaven Pineau" &lt;<A=20
=
href=3D"mailto:kpineau@labcal_antispam.com">kpineau@labcal_antispam.com</=
A>&gt;=20
wrote in message <A=20
=
href=3D"news:OpXmD4aLGHA.500@TK2MSFTNGP15.phx.gbl">news:OpXmD4aLGHA.500@T=
K2MSFTNGP15.phx.gbl</A>...</DIV>
<DIV><FONT face=3DCourier size=3D1>Hi everyone, I am working with a =
pxa27x and I=20
also have a fpga that doing background tasks that could raise an =
interrupt=20
on a gpio pin of the pxa27x.&nbsp; I have implemented the functions =
for=20
managing the interrupt requests. But&nbsp;I am experiencing this =
problem :=20
my driver's thread doesn't get his event signaled when I return the=20
associated sysintr&nbsp; with the event in the function=20
BspIntrActiveIrq.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Here's what I do :</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrInit I do a mapping =
of the=20
sysintr with OALIntrStaticTranslate( sysintr, sysintr).</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrEnableIrq I set the =
corresponding=20
register of my fpga for enabling the interruption and return=20
OAL_INTR_IRQ_UNDEFINED .</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrDisableIrq about the =
same of=20
BspIntrDisableIrq</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1>- In BspIntrActiveIrq I read the =
the fpga=20
status register to know which sysintr to return, clearing the status =
bit of=20
the gpio and return the sysintr.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>If you need more details so you =
can help me=20
out, let me know.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D1>Regards,</FONT></DIV>
<DIV><FONT face=3DCourier=20
size=3D1>Keaven</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_001D_01C63214.48F6DAF0--