From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org,
Mikhail Cherkashin <mcherkashin@ru.mvista.com>
Subject: Re: [PATCH 2/8] ide: add ide_set_irq() inline helper
Date: Mon, 7 Jul 2008 20:05:41 +0200 [thread overview]
Message-ID: <200807072005.42187.bzolnier@gmail.com> (raw)
In-Reply-To: <48724BB0.3080008@ru.mvista.com>
On Monday 07 July 2008, Sergei Shtylyov wrote:
> Hello, I wrote:
>
> >> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
>
> > We're getting "ide0: unexpected interrupt, status=0x58, count=1" with
> > palm_bk3710 driver when running hdparm with option -X. That interrupt
> > has beenidentidied to occur while ide_driveid_update() waits for non-BSY
> > status polling the alt. status reg. After looking at the code there, I
> > couldn't help wondering why I never saw that before with any other
> > controller since the code looked like it was bound to produce the
> > unexpected interrupts -- unless I'm missing something?..
>
> Ah, I know why: unexpected_intr() just is never called for PCI chips.
> Here's an related excerpt from ide_intr():
>
> #ifdef CONFIG_BLK_DEV_IDEPCI
> if (hwif->chipset != ide_pci)
> #endif /* CONFIG_BLK_DEV_IDEPCI */
> {
> /*
> * Probably not a shared PCI interrupt,
> * so we can safely try to do something about it:
> */
> unexpected_intr(irq, hwgroup);
> #ifdef CONFIG_BLK_DEV_IDEPCI
> } else {
> /*
> * Whack the status register, just in case
> * we have a leftover pending IRQ.
> */
> (void) hwif->INB(hwif->io_ports.status_addr);
> #endif /* CONFIG_BLK_DEV_IDEPCI */
Yes, we may consider removing #ifdef-s and always calling unexpected_intr()
(ide_driveid_update() needs fixing first though).
Thanks,
Bart
next prev parent reply other threads:[~2008-07-07 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 0:04 [PATCH 2/8] ide: add ide_set_irq() inline helper Bartlomiej Zolnierkiewicz
2008-07-07 15:47 ` Sergei Shtylyov
2008-07-07 17:00 ` Sergei Shtylyov
2008-07-07 18:05 ` Bartlomiej Zolnierkiewicz [this message]
2008-07-08 9:13 ` Sergei Shtylyov
2008-07-07 18:00 ` Bartlomiej Zolnierkiewicz
2008-07-08 9:10 ` Sergei Shtylyov
2008-07-11 21:20 ` Bartlomiej Zolnierkiewicz
2008-07-11 9:28 ` Sergei Shtylyov
2008-07-11 12:57 ` Sergei Shtylyov
2008-07-12 10:30 ` Bartlomiej Zolnierkiewicz
2008-07-10 12:11 ` Dubious IRQ masking in ide_config_drive_speed() Sergei Shtylyov
2008-07-11 19:39 ` Bartlomiej Zolnierkiewicz
2008-07-10 21:21 ` Sergei Shtylyov
2008-07-11 21:44 ` Bartlomiej Zolnierkiewicz
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=200807072005.42187.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mcherkashin@ru.mvista.com \
--cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).