Skip to content

Commit

Permalink
DM9000: Remove DEFAULT_TRIGGER for request_irq() flags.
Browse files Browse the repository at this point in the history
Currently all but one user (AT91SAM9261EK) of the dm9000
driver passes their IRQ flags through the resources attached
to the platform device. This means we can remove the use
of DEFAULT_TRIGGER as the blackfin machines all seem to
have their triggers set properly.

Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
  • Loading branch information
Ben Dooks authored and Jeff Garzik committed Jun 25, 2008
1 parent 485ca22 commit 6ff4ff0
Showing 1 changed file with 2 additions and 7 deletions.
9 changes: 2 additions & 7 deletions drivers/net/dm9000.c
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,6 @@
#define writesb outsb
#define writesw outsw
#define writesl outsl
#define DEFAULT_TRIGGER IRQF_TRIGGER_HIGH
#else
#define DEFAULT_TRIGGER (0)
#endif

/*
Expand Down Expand Up @@ -1014,11 +1011,9 @@ dm9000_open(struct net_device *dev)
/* If there is no IRQ type specified, default to something that
* may work, and tell the user that this is a problem */

if (irqflags == IRQF_TRIGGER_NONE) {
if (irqflags == IRQF_TRIGGER_NONE)
dev_warn(db->dev, "WARNING: no IRQ resource flags set.\n");
irqflags = DEFAULT_TRIGGER;
}


irqflags |= IRQF_SHARED;

if (request_irq(dev->irq, &dm9000_interrupt, irqflags, dev->name, dev))
Expand Down

0 comments on commit 6ff4ff0

Please sign in to comment.