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>,
linux-ide@vger.kernel.org (open list:LIBATA SUBSYSTEM (Serial
and Parallel ATA drivers)),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2 0/2] ata: ahci_brcm: Recover from failures to identify devices
Date: Thu, 11 Jan 2018 17:31:06 -0800 [thread overview]
Message-ID: <1515720668-4860-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.
This should likely go through Tejun's tree to make sure the SATA controller
and PHY changes are bundled together.
Thanks!
Changes in v2:
- avoid introducing an unnecessary port_recovery callback and instead
override read_id directly
Florian Fainelli (2):
phy: brcm-sata: Implement calibrate callback
ata: ahci_brcm: Recover from failures to identify devices
drivers/ata/ahci_brcm.c | 95 +++++++++++++++++++++++++++++++++---
drivers/phy/broadcom/phy-brcm-sata.c | 32 ++++++++++++
2 files changed, 119 insertions(+), 8 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-12 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 1:31 Florian Fainelli [this message]
2018-01-12 1:31 ` [PATCH v2 1/2] phy: brcm-sata: Implement calibrate callback Florian Fainelli
2018-01-17 5:19 ` Kishon Vijay Abraham I
2018-01-12 1:31 ` [PATCH v2 2/2] ata: ahci_brcm: Recover from failures to identify devices Florian Fainelli
2018-01-16 16:09 ` [PATCH v2 0/2] " Tejun Heo
2018-01-17 15:53 ` 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=1515720668-4860-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
all inboxes | Powered by JetHome®