From: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>
To: "Andrew Morton" <akpm@osdl.org>,
"Ronciak, John" <john.ronciak@intel.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"Jeremy Fitzhardinge" <jeremy@goop.org>
Subject: RE: [PATCH] Fix for spurious interrupts on e100 resume
Date: Thu, 30 Sep 2004 09:26:01 -0700 [thread overview]
Message-ID: <468F3FDA28AA87429AD807992E22D07E02B55EF6@orsmsx408> (raw)
Andrew:
I propose that we remove this patch from the -mm tree. We will work on a
clean solution and send a patch soon. Please see further discussion on
this under the subject "2.6.9-rc2-mm4 e100 enable_irq unbalanced from"
Ganesh.
-----Original Message-----
From: Jeremy Fitzhardinge [mailto:jeremy@goop.org]
Sent: Monday, September 13, 2004 3:53 PM
To: Ronciak, John
Cc: Venkatesan, Ganesh; Feldman, Scott; Andrew Morton; linux-kernel
Subject: Re: [PATCH] Fix for spurious interrupts on e100 resume
On Thu, 2004-09-09 at 15:36 -0700, Jeremy Fitzhardinge wrote:
> I've been having problems with spurious interrupts being raised when
the
> e100 driver resets the chip during a resume:
OK, that patch didn't really work terribly well - the interrupt still
happens. I've changed it to simply disable the interrupt during e100_up
(), which does seem to work properly.
J
On resume, the e100 chip seems to raise an interrupt during chip reset.
Since there's no IRQ handler registered yet, the kernel complains that
"nobody cared" about the interrupt. This change disables the IRQ during
e100_up(), while the hardware is being (re-)initialized.
drivers/net/e100.c | 6 ++++++
1 files changed, 6 insertions(+)
diff -puN drivers/net/e100.c~e100-restore-irq drivers/net/e100.c
--- local-2.6/drivers/net/e100.c~e100-restore-irq 2004-09-13
13:38:27.000000000 -0700
+++ local-2.6-jeremy/drivers/net/e100.c 2004-09-13 13:38:28.075416972
-0700
@@ -1678,6 +1678,9 @@ static int e100_up(struct nic *nic)
if((err = e100_rx_alloc_list(nic)))
return err;
+
+ disable_irq(nic->pdev->irq);
+
if((err = e100_alloc_cbs(nic)))
goto err_rx_clean_list;
if((err = e100_hw_init(nic)))
@@ -1689,6 +1692,7 @@ static int e100_up(struct nic *nic)
nic->netdev->name, nic->netdev)))
goto err_no_irq;
e100_enable_irq(nic);
+ enable_irq(nic->pdev->irq);
netif_wake_queue(nic->netdev);
return 0;
@@ -1698,6 +1702,8 @@ err_clean_cbs:
e100_clean_cbs(nic);
err_rx_clean_list:
e100_rx_clean_list(nic);
+
+ enable_irq(nic->pdev->irq);
return err;
}
_
Signed-off-by: Jeremy Fitzhardinge <jeremy@goop.org>
next reply other threads:[~2004-09-30 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 16:26 Venkatesan, Ganesh [this message]
2004-09-30 19:01 ` Jeremy Fitzhardinge
2004-09-30 19:36 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 22:36 Jeremy Fitzhardinge
2004-09-09 23:57 ` Nathan Bryant
2004-09-10 0:53 ` Jeremy Fitzhardinge
2004-09-13 22:53 ` Jeremy Fitzhardinge
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=468F3FDA28AA87429AD807992E22D07E02B55EF6@orsmsx408 \
--to=ganesh.venkatesan@intel.com \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/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
all inboxes | Powered by JetHome®