From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [RFC] ata/core: don't enable the interrupt while activating the host
Date: Tue, 06 Apr 2010 14:00:33 +0400 [thread overview]
Message-ID: <4BBB0641.3040500@ru.mvista.com> (raw)
In-Reply-To: <20100406094535.GA30917@Chamillionaire.breakpoint.cc>
Hello.
Sebastian Andrzej Siewior wrote:
>> On 03/26/2010 07:04 AM, Sebastian Andrzej Siewior wrote:
>>
>>>> Can you please play with ata_sff_freeze() and find out why it's not
>>>> working?
>>>>
>>> I've been there. I've moved the functions around and nothing changed.
>>> After removing the ATA_NIEN bit it started working. So it looks like
>>> ->sff_check_status() & ->sff_irq_clear() are not clearing the interrupt
>>> for what reason ever.
>>>
>> What happens if you remove everything else from the function and just
>> set ATA_NIEN?
>>
>
> removing everything from ata_sff_freeze() makes the interrupt storm go
> away.
> Leaving
> - ap->ctl |= ATA_NIEN;
> => seems to work
> - the upper and "ap->last_ctl = ap->ctl;"
> => seems to work
> - the upper and "iowrite8(ap->ctl, ioaddr->ctl_addr);"
> => irq storm on request irq.
>
> ata_sff_check_status() does not report ATA_DRQ set so I don't know why
> the interrupt is comming.
>
Perhaps the drive incorrectly triggers interrupt on setting the nIEN
bit -- some drives are known to do this; there is a blacklist of such
drives in the IDE core so that it avoids setting nIEN bit for them.
WBR, Sergei
next prev parent reply other threads:[~2010-04-06 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 22:04 [RFC] ata/core: don't enable the interrupt while activating the host Sebastian Andrzej Siewior
2010-03-25 0:30 ` Tejun Heo
2010-03-25 22:04 ` Sebastian Andrzej Siewior
2010-03-25 23:54 ` Tejun Heo
2010-04-06 9:45 ` Sebastian Andrzej Siewior
2010-04-06 10:00 ` Sergei Shtylyov [this message]
2010-04-06 21:56 ` Tejun Heo
2010-04-07 7:52 ` Sebastian Andrzej Siewior
2010-04-13 14:38 ` Sebastian Andrzej Siewior
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=4BBB0641.3040500@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-ide@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
--cc=tj@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