linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Interrupts on xilinx ml403
Date: Tue, 24 Jul 2007 21:44:55 -0700 (PDT)	[thread overview]
Message-ID: <11776097.post@talk.nabble.com> (raw)
In-Reply-To: <11765540.post@talk.nabble.com>


hi ...

Well you are always welcome to contact me . Just look at the configuration
of registers are proper or not and you have followed Bigendian format or
not. more than 90 % of the problem comes when you dont configure the
controler registers properly.

----Misbah

Mirek23 wrote:
> 
> I will try to go further with that after trying Grant's suggestion. When I
> still have a problem I will contact you.
> 
> Best Regards
> 
> Mirek
> 
> Misbah khan wrote:
>> 
>> hi ..
>> 
>> If you could send me the code and the config related doc . I could then
>> be able to suggest you something. As per the understanding of the problem
>> i guess you are not congiguring the interrupt controller properly. you
>> have to use correct IRQ no for  that ports then other configuration such
>> as interrupt type, and whenever you service the interrupt you have to
>> clear the interrupt etc are to be taken care ....Please see the interrupt
>> controller register and do your settings correctly . If the same persists
>> then you please send me the code and the documents then only i could give
>> the exact explaination on this 
>> 
>> ----misbah
>> 
>> Mirek23 wrote:
>>> 
>>> Dear All,
>>> 
>>>       I use linux kernel 2.6 on ppc405 of my Avnet (xilinx like ml403)
>>> evaluation board.
>>> 
>>> I have setup the virtex-4 FPGA to deal with Themac and Serial
>>> interfaces. As input/output devices I have chosen 8 LEDs and DIP
>>> Switches.
>>> 
>>> With such a configuration I am able to control from Linux user
>>> applications via GPIO driver the LEDs and DIP Switches.
>>> 
>>> Right now I just wanted to make use of the interrupts. I have configured
>>> the Dip switches to use interrupt. The interrupt accoures when the DIP
>>> Switches state has changed.
>>> 
>>> In the BSP generated by EDK 9.1 I see that macro :   
>>> 
>>> #define XPAR_DIP_SWITCHES_8BIT_INTERRUPT_PRESENT 1
>>> 
>>> has changed from zero to one.
>>> The macro XPAR_INTC_MAX_NUM_INTR_INPUTS is set to 1 as it was before.
>>> This is due to the fact that 
>>> TEMAC uses one interrupt line.
>>> 
>>> Does it mean that DIP Switches do not use INTC interrupt controller?
>>> How to handle the DIP Switches interrupt?
>>> Does the Interrupt handler routine have to acknowledge the interrupt
>>> from Dip Switches?
>>> 
>>> Many thanks in advance for any hint on that.
>>> 
>>> Best Regards
>>> 
>>> Mirek
>>> 
>>> 
>>> 
>>> 
>>>  
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Interrupts-on-xilinx-ml403-tf4117226.html#a11776097
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

      reply	other threads:[~2007-07-25  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 13:52 Interrupts on xilinx ml403 Mirek23
2007-07-20 15:12 ` Grant Likely
2007-07-24 15:19   ` Mirek23
2007-07-24  7:31 ` Misbah khan
2007-07-24 15:22   ` Mirek23
2007-07-25  4:44     ` Misbah khan [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=11776097.post@talk.nabble.com \
    --to=misbah_khan@engineer.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).