netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Remy Bohmer <linux@bohmer.net>
Cc: netdev@vger.kernel.org
Subject: Re: DM9000_IRQ_FLAGS
Date: Wed, 12 Dec 2007 14:41:53 +0100	[thread overview]
Message-ID: <20071212134153.GA21510@buzzloop.caiaq.de> (raw)
In-Reply-To: <3efb10970712111231r29f9fba1l3528d805d1009c52@mail.gmail.com>

Hi Remy,

On Tue, Dec 11, 2007 at 09:31:03PM +0100, Remy Bohmer wrote:
> This controller is also used on many other boards, like the e.g. Atmel
> AT91sam9261-ek board. On that board on both the rising _and_ falling
> edge an interrupt is generated.

However, request_irq() is called with IRQF_SHARED only, so neither
IRQT_RISING nor IRQT_FALLING is set and the value defaults to
IRQT_NOEDGE. How can you get IRQs?

> I can test tomorrow if this patch leaves this board in tact, but
> should the board-specific code not add this flag if it is required ?
> By modifying this driver you will interfere the behavior of other
> boards, and I do not know if there any level triggered types used.

Actually, the best way to go is to let the platform resources flags 
decide about that with something like

	resource->flags = IORESOURCE_IRQ | IRQT_RISING;

but the dm9000 does not care about them at all. Changing that would also
imply modifications to all board support code.

Regards,
Daniel


  reply	other threads:[~2007-12-12 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 19:18 DM9000_IRQ_FLAGS Daniel Mack
2007-12-11 20:31 ` DM9000_IRQ_FLAGS Remy Bohmer
2007-12-12 13:41   ` Daniel Mack [this message]
2007-12-12 14:46     ` DM9000_IRQ_FLAGS Remy Bohmer
2007-12-12 15:01       ` DM9000_IRQ_FLAGS Daniel Mack
2007-12-20  9:46     ` DM9000_IRQ_FLAGS Ben Dooks
2007-12-20  9:54       ` DM9000_IRQ_FLAGS Remy Bohmer
2008-01-15 11:42         ` DM9000_IRQ_FLAGS Daniel Mack
2007-12-20  9:45 ` DM9000_IRQ_FLAGS Ben Dooks

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=20071212134153.GA21510@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=linux@bohmer.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).