From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Tejun Heo <tj@kernel.org>, Kishon Vijay Abraham I <kishon@ti.com>,
Heiko Stuebner <heiko@sntech.de>,
Srinath Mannam <srinath.mannam@broadcom.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
"open list:LIBATA SUBSYSTEM Serial and Parallel ATA drivers"
<linux-ide@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] ata: ahci_brcm: Recover from failures to identify devices
Date: Tue, 9 Jan 2018 15:04:54 -0800 [thread overview]
Message-ID: <1515539097-26742-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi Tejun, Kishon,
This patch series implement a recovery mechanism to work around a HW bug
on Broadcom AHCI SATA controller subject to noise triggering a failure to
identify hard drives.
I would like to make this this is okay with you as an approach on how to solve
this.
Thanks!
Florian Fainelli (3):
ata: Allow having a port recovery callback
phy: brcm-sata: Implementation calibrate callback
ata: ahci_brcm: Recover from failures to identify devices
drivers/ata/ahci_brcm.c | 83 ++++++++++++++++++++++++++++++++----
drivers/ata/libata-core.c | 2 +
drivers/phy/broadcom/phy-brcm-sata.c | 32 ++++++++++++++
include/linux/libata.h | 1 +
4 files changed, 110 insertions(+), 8 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-09 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 23:04 Florian Fainelli [this message]
2018-01-09 23:04 ` [PATCH 1/3] ata: Allow having a port recovery callback Florian Fainelli
2018-01-10 14:25 ` Tejun Heo
2018-01-10 17:53 ` Florian Fainelli
2018-01-10 16:02 ` Sergei Shtylyov
2018-01-09 23:04 ` [PATCH 2/3] phy: brcm-sata: Implementation calibrate callback Florian Fainelli
2018-01-09 23:04 ` [PATCH 3/3] ata: ahci_brcm: Recover from failures to identify devices Florian Fainelli
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=1515539097-26742-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinath.mannam@broadcom.com \
--cc=tj@kernel.org \
--cc=vivek.gautam@codeaurora.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;
as well as URLs for NNTP newsgroup(s).