public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Santini <luca.santini@spesonline.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] support for edosk7760 board
Date: Fri, 05 Sep 2008 10:16:24 +0000	[thread overview]
Message-ID: <48C106F8.6070101@spesonline.com> (raw)
In-Reply-To: <48B52DC8.1020208@spesonline.com>



Magnus Damm wrote:
> Hi again Luca!
> 
> On Fri, Sep 5, 2008 at 6:50 PM, Luca Santini
> <luca.santini@spesonline.com> wrote:
>> I think i'm misunderstanding something.....
>> if i try to setup eth on irq 2 (or 5 or 8 or 11...)
>> and set the platform like this
>>
>> static void __init sh_edosk7760_init_irq(void)
>> {
>> }
>>
>> static int __init init_edosk7760_devices(void)
>> {
>>        plat_irq_setup_pins(IRQ_MODE_IRQ);
>>
>>        return platform_add_devices(edosk7760_devices,
>> ARRAY_SIZE(edosk7760_devices));
>> }
>> __initcall(init_edosk7760_devices);
> 
> Ok, looking good!
> 
>> i have the well known
>>
>> ...
>> [    1.474095] eth0: SMC91C94 (rev 9) at a2000300 IRQ 2 [nowait]
>> ... (label:)
>> [    3.112795] irq 9, desc: 8c228978, depth: 1, count: 0, unhandled: 0
>> [    3.116471] ->handle_irq():  8c0361d8, handle_bad_irq+0x0/0x1ac
>> [    3.122343] ->chip(): 8c228740, no_irq_chip+0x0/0x40
>> [    3.127267] ->action(): 00000000
>> [    3.130464]   IRQ_DISABLED set
>> ... (goto label)
> 
> It still says "irq 9", is that a coding or copy-paste mistake?
> 

No, it's a fresh grab ! Very strange.....

Trying the IORESOURCE_IRQ_HIGHLEVEL flag and irq 2 the chip isn't 
detected (-19) so of course i have no nfs transfer and no irq problems;
i tried also IORESOURCE_IRQ_LOWLEVEL instead and i get the same

	[    6.893332] unexpected IRQ trap at vector 09
	[    6.897576] irq 9, desc: 8c228978, depth: 1, count: 0, unhandled: 0

etc..


> / magnus
> 
> 

  parent reply	other threads:[~2008-09-05 10:16 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
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 [this message]
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=48C106F8.6070101@spesonline.com \
    --to=luca.santini@spesonline.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