From: Tejun Heo <tj@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-ide@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Andy Gross <andy.gross@linaro.org>,
Hans de Goede <hdegoede@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jmaggard10@gmail.com
Subject: Re: [PATCH v3 0/3] ahci: add ports-implemented dt bindings
Date: Fri, 1 Apr 2016 10:44:06 -0400 [thread overview]
Message-ID: <20160401144406.GS7822@mtj.duckdns.org> (raw)
In-Reply-To: <1459497178-31090-1-git-send-email-srinivas.kandagatla@linaro.org>
On Fri, Apr 01, 2016 at 08:52:55AM +0100, Srinivas Kandagatla wrote:
> On some SOCs PORTS_IMPL register value is never programmed by the BIOS
> and left at zero value. Which means that no sata ports are available for
> software. AHCI driver used to cope up with this by fabricating the
> port_map if the PORTS_IMPL register is read zero, but recent patch [1]
> broke this workaround as zero value was valid for nvme disks.
>
> This patch adds ports-implemented dt bindings as workaround for this issue
> in a way that DT can dictate the port_map incase where the SOCs does not
> program it already.
Applied all three patches to libata/for-4.6-fixes w/ stable cc'd.
Thanks.
--
tejun
prev parent reply other threads:[~2016-04-01 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 7:52 [PATCH v3 0/3] ahci: add ports-implemented dt bindings Srinivas Kandagatla
[not found] ` <1459497178-31090-1-git-send-email-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-01 7:52 ` [PATCH v3 1/3] libahci: save port map for forced port map Srinivas Kandagatla
2016-04-01 7:52 ` [PATCH v3 2/3] ata: ahci-platform: Add ports-implemented DT bindings Srinivas Kandagatla
2016-04-04 5:15 ` Rob Herring
2016-04-01 7:52 ` [PATCH v3 3/3] ARM: dts: apq8064: add ahci ports-implemented mask Srinivas Kandagatla
2016-04-01 14:44 ` 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=20160401144406.GS7822@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=jmaggard10@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).