From: Andy Lutomirski <luto@amacapital.net>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata: disable forced PORTS_IMPL for >= v3.0 controllers
Date: Thu, 14 Jan 2016 17:00:57 -0800 [thread overview]
Message-ID: <CALCETrVCfQjMQgnjpJh6YPsRF18X=XYRTb3Aoqbhe3f3ucam4w@mail.gmail.com> (raw)
In-Reply-To: <20160114223732.GG3520@mtj.duckdns.org>
On Thu, Jan 14, 2016 at 2:37 PM, Tejun Heo <tj@kernel.org> wrote:
> Some early controllers incorrectly reported zero ports in PORTS_IMPL
> register and the ahci driver fabricates PORTS_IMPL from the number of
> ports in those cases. This hasn't mattered but with the new nvme
> controllers there are cases where zero PORTS_IMPL is valid and should
> be honored.
>
> Disable the workaround for controllers >= v3.0.
I still see:
[ +0.001350] ahci 0000:00:17.0: version 3.0
[ +0.000034] ahci 0000:00:17.0: forcing PORTS_IMPL to 0xff
My "vers" is 0x10301.
--Andy
next prev parent reply other threads:[~2016-01-15 1:01 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
2016-01-14 22:37 ` [PATCH] libata: disable forced PORTS_IMPL for >= v3.0 controllers Tejun Heo
2016-01-15 1:00 ` Andy Lutomirski [this message]
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='CALCETrVCfQjMQgnjpJh6YPsRF18X=XYRTb3Aoqbhe3f3ucam4w@mail.gmail.com' \
--to=luto@amacapital.net \
--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;
as well as URLs for NNTP newsgroup(s).