From: Scott Wood <scottwood@freescale.com>
To: biswa.nayak@wipro.com
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Wrong IRQ assigned on MPC8349EMDS board
Date: Thu, 28 Feb 2008 11:24:34 -0600 [thread overview]
Message-ID: <20080228172434.GA25737@ld0162-tx32.am.freescale.net> (raw)
In-Reply-To: <4F36B0A4CDAD6F46A61B2B32C33DC69C05C579C0@BLR-EC-MBX03.wipro.com>
On Thu, Feb 28, 2008 at 09:38:36PM +0530, biswa.nayak@wipro.com wrote:
> I found that the IRQ lines assigned to different peripherals are
> completely wrong.
> My serial ports are connected to pin 9 and 10, but in this kernel the
> IRQs assigned are 16 and 17.
These are virtual IRQ numbers, which have nothing to do with the IPIC IRQ
numbers.
> On a little investigation I found that the base address assigned to the
> IPIC chip is '0xFDDFB700'
That's a virtual address returned from ioremap(), not the physical
address of the IPIC.
> Does this wrong assignment is due to the wrong base address of the IPIC
> chip?
> With IRQs 16 and 17, how the serial console is working fine?
>
> When I tried hard coding the IPIC base value to '0xfe000700' then the
> system refuses to boot up.
That might be a hint that things aren't as wrong as you think. :-)
> I kept the IPIC base as 0xfddfb700 and hard coded the irq lines for
> serial ports as 9 and 10
> and in that case the 'request_irq' call fails with the error number as
> '-38',
> which translates to '-ENOSYS'.
Likewise.
-Scott
prev parent reply other threads:[~2008-02-28 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 16:08 Wrong IRQ assigned on MPC8349EMDS board biswa.nayak
2008-02-28 17:24 ` Scott Wood [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=20080228172434.GA25737@ld0162-tx32.am.freescale.net \
--to=scottwood@freescale.com \
--cc=biswa.nayak@wipro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@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