From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "David F." <df7729@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch fix for intel sdd s3500 series on Sil3512 controller
Date: Mon, 24 Mar 2014 14:15:58 +0000 [thread overview]
Message-ID: <20140324141558.31c169cf@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <CAGRSmLtifL=hFBP1AUHB_va6ZvNfqXo8Bu=6XciH--jOEYVJjQ@mail.gmail.com>
On Sat, 22 Mar 2014 16:32:54 -0700
"David F." <df7729@gmail.com> wrote:
> Hi,
>
> It appears if nIEN is set all polling type IO fails. After an
> attempt, future non-polled communications also fails. This patch
> allows it to work. Not sure if any spin lock protection would be
> needed or the system already handles the device existence for the
> generated irq with polling enabled. handler already ignored irq if
> queued command was polling type.
Does it behave plugged into a different controller without the hacks ?
Alan
next prev parent reply other threads:[~2014-03-24 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 23:32 patch fix for intel sdd s3500 series on Sil3512 controller David F.
2014-03-24 14:15 ` One Thousand Gnomes [this message]
2014-03-24 15:27 ` Bartlomiej Zolnierkiewicz
2014-03-27 0:11 ` David F.
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=20140324141558.31c169cf@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=df7729@gmail.com \
--cc=linux-kernel@vger.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