From: prathika <prathika@deeopl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Interrupt handlers in u-boot
Date: Thu, 09 Apr 2009 13:52:53 +0530 [thread overview]
Message-ID: <49DDB05D.2090109@deeopl.com> (raw)
In-Reply-To: <200904090906.18720.sr@denx.de>
i am using PPC 440 EP. i used mtdcr definitions available in uboot. i
understand the UIC dcr registers are directly accessable.
I have configured IRQ0 as interrupt by writing to the following registers=>
GPIO1_TCR[8]=0
GPIO1_TSRL[16:17]=00
GPIO1_ISR1L[16:17]=01
And when thought it could a hardware issue on my board as the IRQ0 is
connected to the CPLD, i tried configuring IRQ1. the state of IRQ1 is low.
when i enable UIC0_ER register for IRQ1, there is no interrupt
generated.but when i enable UIC0_PR for IRQ1 to be detected in positive
polarity, an interrupt is generated with a bogus interrupt message. Did
i understand the UIC0_PR register functionality wrong?
Thank & Regards,
Prathika R
Stefan Roese wrote:
> On Thursday 09 April 2009, prathika wrote:
>> i got the interrupt handler working for SPI Receive in PPC 440 using
>> install_hdlr().
>> Now i am trying to enable the External IRQ0 in my stand alone
>> application. I am trying to detect the positive of the interrupt pulse,
>> so i wrote corresponding bit to the UIC0_PR and UIC0_EN register and
>> also calling the install_hdlr().
>> but still it detects the zero state at the IRQ0 pin and always executes
>> the interrupt handler.
>> when i read back the DCRs UIC0 enable and polarity registers using my
>> application, the control word is fine.
>> but when i read using uboot commands getdcr in command window, the
>> status of both enable and polarity registers are not enabled for IRQ0.
>> when i try to set the corresponding bit for IRQ0 using setdcr, it gives
>> me message, "Masking bogus interrupt for 0x17"
>> where am i going wrong.Some one please help.
>> Thanks in advance.
>
> So which PPC440 variant are you using? And how did you configure the UIC
> registers exactly? And is IRQ0 perhaps multiplexed with another multifunction
> pin (see GPIO chapter)?
>
> Best regards,
> Stefan
>
> =====================================================================
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
> =====================================================================
prev parent reply other threads:[~2009-04-09 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 11:02 [U-Boot] Interrupt handlers in u-boot prathika
2009-04-08 12:42 ` Stefan Roese
2009-04-09 4:44 ` prathika
2009-04-09 6:22 ` prathika
2009-04-09 7:06 ` Stefan Roese
2009-04-09 8:22 ` prathika [this message]
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=49DDB05D.2090109@deeopl.com \
--to=prathika@deeopl.com \
--cc=u-boot@lists.denx.de \
/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