From: "Magnus Damm" <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] support for edosk7760 board
Date: Fri, 05 Sep 2008 08:14:34 +0000 [thread overview]
Message-ID: <aec7e5c30809050114je2ff5e9y3c19455dde169260@mail.gmail.com> (raw)
In-Reply-To: <48B52DC8.1020208@spesonline.com>
On Mon, Sep 1, 2008 at 5:11 PM, Luca Santini
<luca.santini@spesonline.com> wrote:
> thanks for reply Magnus,
> in 2.6.26 everything works fine with irq 9;
I see that you install imask handlers for the flash and the ethernet:
+static int __init init_edosk7760_devices(void){
+ int ret = -1;
+
+ /* This is the Ethernet interrupt */
+ make_imask_irq(ETHERNET_IRQ);
+
+ /* This is the IntelStrata Flash interrupt */
+ make_imask_irq(0x0A);
Is the flash interrupt tested?
I suspect that the chips are connected straight to the IRL pins of the
processor. Using "individual interrupt mode" would make sense then. Do
you have access to schematics?
I recommend you to enable "individual interrupt mode" calling
plat_irq_setup_pins(IRQ_MODE_IRQ) from your board code. Try using
interrupt number 2 for IRL0 pin, 5 for IRL1, 8 for IRL2 and 11 for
IRL3. These values are calculated from vectors_irq[] in
setup-sh7760.c.
> trying to debug a little kernel/irq/manage.c i found that
> in 2.6.26 in function setup_irq()
>
> compat_irq_chip_set_default_handler(desc);
>
> is called;
>
> otherwise in 2.6.27-rc4 :
>
> __irq_set_trigger()
>
> is called with
> chip->set_type = NULL
>
>
> i tried (for debug) to force in smc91x.h
> #define SMC_IRQ_FLAGS 0
> to force using compat_irq_chip_set_default_handler(desc);
> but what i get is a loop of
>
> "Unable to handle kernel NULL pointer dereference..."
This may be because the imask interrupt controller code doesn't
support interrupt type or something. I'm not sure.
/ magnus
next prev parent reply other threads:[~2008-09-05 8:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 10:34 [PATCH] support for edosk7760 board Luca Santini
2008-08-27 11:12 ` Manuel Lauss
2008-08-27 14:55 ` Paul Mundt
2008-08-28 3:00 ` Paul Mundt
2008-08-28 11:50 ` Magnus Damm
2008-08-29 8:35 ` Luca Santini
2008-09-01 1:24 ` Magnus Damm
2008-09-01 8:11 ` Luca Santini
2008-09-05 8:14 ` Magnus Damm [this message]
2008-09-05 8:14 ` Luca Santini
2008-09-05 8:17 ` Magnus Damm
2008-09-05 8:30 ` Magnus Damm
2008-09-05 8:33 ` Manuel Lauss
2008-09-05 8:46 ` Magnus Damm
2008-09-05 8:48 ` Paul Mundt
2008-09-05 9:01 ` Manuel Lauss
2008-09-05 10:16 ` Luca Santini
2008-09-05 14:14 ` Luca Santini
2008-09-08 2:26 ` Magnus Damm
2008-09-08 2:30 ` Paul Mundt
2008-09-08 2:52 ` Paul Mundt
2008-09-08 5:41 ` Manuel Lauss
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=aec7e5c30809050114je2ff5e9y3c19455dde169260@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.kernel.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