From: Tejun Heo <tj@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-ide@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Unhappy ahci controller on Dell XPS 13 9350
Date: Thu, 14 Jan 2016 17:16:30 -0500 [thread overview]
Message-ID: <20160114221630.GF3520@mtj.duckdns.org> (raw)
In-Reply-To: <CALCETrU7yMvXEDhjAUShoHEhDwifJGapdw--BKxsP0jmjKGmRw@mail.gmail.com>
Hello, Andy.
On Tue, Jan 12, 2016 at 10:51:15PM -0800, Andy Lutomirski wrote:
> Hi-
>
> My XPS 13 9350 laptop has an nvme drive. It has on-chip ahci
> capability, but the M.2 port isn't using it due to the aforementioned
> nvme drive using the same signal pins.
>
> It is very unhappy:
>
> [ 0.230455] libata version 3.00 loaded.
> [ 1.039360] ahci 0000:00:17.0: version 3.0
> [ 1.039386] ahci 0000:00:17.0: forcing PORTS_IMPL to 0xff
...
> It has Alpine Ridge, but I don't think there's such thing as SATA over
> USB Type C. I'd guess that that what's going on is that the ahci
> controller genuinely has zero ports enabled and the workaround for
> port_map == 0 is firing incorrectly.
Yeah, that's a workaround for very early ahci controllers. I'll think
of a way to disable it for newer controllers. Filtering on ahci
controller version should work.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-01-14 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 6:51 Unhappy ahci controller on Dell XPS 13 9350 Andy Lutomirski
2016-01-14 22:16 ` Tejun Heo [this message]
2016-01-14 22:37 ` [PATCH] libata: disable forced PORTS_IMPL for >= v3.0 controllers Tejun Heo
2016-01-15 1:00 ` Andy Lutomirski
2016-01-15 19:48 ` Tejun Heo
2016-01-15 20:13 ` [PATCH v2] libata: disable forced PORTS_IMPL for >= AHCI 1.3 Tejun Heo
2016-01-15 22:49 ` Andy Lutomirski
2016-01-16 10:09 ` Sergei Shtylyov
2016-01-19 17:22 ` Tejun Heo
2016-01-19 17:23 ` Sergei Shtylyov
2016-01-25 20:46 ` [PATCH v3] " 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=20160114221630.GF3520@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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).