public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Werner <andreas.werner@men.de>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-ide@vger.kernel.org>, <tj@kernel.org>
Subject: [v2 0/2] ata/libata-eh.c: introduce ATA_FLAG_NO_LOG_PAGE
Date: Fri, 4 Dec 2015 18:12:24 +0100	[thread overview]
Message-ID: <cover.1449248754.git.andreas.werner@men.de> (raw)

This patchset add a new ata port flag ATA_FLAG_NO_LOG_PAGE to be able
to blacklist ports/controller which e.g. locks up on a log page read.

This flag is added to the sata_fsl driver which is the first affected
one.

The lockup was detected on Freescale P1013/P1022, T4240 using a ATP
mSATA.
The device failed during initialisation if the SATA device includes the
devslp feature.

With this patchset, we blacklist the fsl sata controller and return
a error on any attempt to read a log page. This allows us to access
the mSATA.

Changes in v2:
	fixed the build issue detected by the kbuild test robot

Andreas Werner (2):
  libata-eh.c: Introduce new ata port flag for controller which lockup
    on read log page
  ata/sata_fsl.c: add ATA_FLAG_NO_LOG_PAGE to blacklist the controller
    for log page reads

 drivers/ata/libata-eh.c | 9 +++++++++
 drivers/ata/sata_fsl.c  | 3 ++-
 include/linux/libata.h  | 1 +
 3 files changed, 12 insertions(+), 1 deletion(-)

-- 
2.6.2


             reply	other threads:[~2015-12-04 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 17:12 Andreas Werner [this message]
2015-12-04 17:12 ` [v2 1/2] libata-eh.c: Introduce new ata port flag for controller which lockup on read log page Andreas Werner
2015-12-04 17:14 ` [v2 2/2] ata/sata_fsl.c: add ATA_FLAG_NO_LOG_PAGE to blacklist the controller for log page reads Andreas Werner
2015-12-07 15:26 ` [v2 0/2] ata/libata-eh.c: introduce ATA_FLAG_NO_LOG_PAGE Tejun Heo
2015-12-08  6:12   ` Andreas Werner

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=cover.1449248754.git.andreas.werner@men.de \
    --to=andreas.werner@men.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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