From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, vladimir.barinov@cogentembedded.com
Subject: Re: [PATCH] sata_rcar: fix interrupt handling
Date: Sun, 02 Jun 2013 15:39:54 +0400 [thread overview]
Message-ID: <51AB2F0A.9030703@cogentembedded.com> (raw)
In-Reply-To: <20130602075821.GA8286@mtj.dyndns.org>
Hello.
On 02-06-2013 11:58, Tejun Heo wrote:
>>> The driver's interrupt handling code is too picky in deciding whether it should
>>> handle an interrupt or not which causes completely unneeded spurious interrupts.
>>> Thus make sata_rcar_{ata|serr}_interrupt() *void*; add ATA status register read
>>> to sata_rcar_ata_interrupt() to clear an unexpected ATA interrupt -- it doesn't
>>> get cleared by writing to the SATAINTSTAT register in the interrupt mode we use.
>>> Also, in sata_rcar_ata_interrupt() we should check SATAINTSTAT register only for
>>> enabled interrupts and we should clear only those interrupts that we have read
>>> as active first time around, because else we have a race and risk clearing an
>>> interrupt that can occur between read and write of the SATAINTSTAT register
>>> and never registering it...
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Darn, I forgot to Cc: stable@vger.kernel.org again.
> Applied to libata/for-3.10-fixes w/ stable cc'd. BTW, the driver
> generates the following compile warning.
> CC drivers/ata/sata_rcar.o
> drivers/ata/sata_rcar.c: In function ‘sata_rcar_thaw’:
> drivers/ata/sata_rcar.c:183:2: warning: large integer implicitly truncated to unsigned type [-Woverflow]
It compiles without warnings for me, IIRC. What version of gcc are
you using?
> Care to fix it?
I'll look into it...
> Thanks.
MBR, Sergei
next prev parent reply other threads:[~2013-06-02 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 22:38 [PATCH] sata_rcar: fix interrupt handling Sergei Shtylyov
2013-05-31 23:06 ` Sergei Shtylyov
2013-06-02 7:58 ` Tejun Heo
2013-06-02 11:39 ` Sergei Shtylyov [this message]
2013-06-02 17:00 ` Sergei Shtylyov
2013-06-03 3:49 ` Tejun Heo
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=51AB2F0A.9030703@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vladimir.barinov@cogentembedded.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