From: Tejun Heo <tj@kernel.org>
To: Sui Chen <suichen6@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH Resend] ahci: Acer SA5-271 SSD Not Detected Fix
Date: Tue, 9 May 2017 10:20:23 -0400 [thread overview]
Message-ID: <20170509142023.GB8609@htj.duckdns.org> (raw)
In-Reply-To: <086b549a-e2ec-58c4-42af-c5b5e23f67a7@gmail.com>
Hello, Sui.
On Tue, May 09, 2017 at 07:47:22AM -0500, Sui Chen wrote:
> (Correction in this resend: fixed function name acer_sa5_271_workaround; fixed
> the always-true condition in the function; fixed description.)
>
> On the Acer Switch Alpha 12 (model number: SA5-271), the internal SSD may not
> get detected because the port_map and CAP.nr_ports combination causes the driver
> to skip the port that is actually connected to the SSD. More specifically,
> either all SATA ports are identified as DUMMY, or all ports get ``link down''
> and never get up again.
>
> This problem occurs occasionally. When this problem occurs, CAP may hold a
> value of 0xC734FF00 or 0xC734FF01 and port_map may hold a value of 0x00 or 0x01.
> When this problem does not occur, CAP holds a value of 0xC734FF02 and port_map
> may hold a value of 0x07. Overriding the CAP value to 0xC734FF02 and port_map to
> 0x7 significantly reduces the occurrence of this problem.
>
> Link: https://bugzilla.kernel.org/attachment.cgi?id=253091
> Signed-off-by: Sui Chen <suichen6@gmail.com>
> Tested-by: Damian Ivanov <damianatorrpm@gmail.com>
Applied to libata/for-4.12-fixes w/ stable cc'd and a couple trivial
changes.
> @@ -1636,6 +1669,10 @@ static int ahci_init_one(struct pci_dev *pdev, const struct
> pci_device_id *ent)
The patch was new line damaged here. You probably wanna make sure
that your mail client isn't breaking long lines automatically.
Thanks!
--
tejun
prev parent reply other threads:[~2017-05-09 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:47 [PATCH Resend] ahci: Acer SA5-271 SSD Not Detected Fix Sui Chen
2017-05-09 14:20 ` Tejun Heo [this message]
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=20170509142023.GB8609@htj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=suichen6@gmail.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