From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ata: ahci-platform: Add ports-implemented DT bindings.
Date: Mon, 4 Apr 2016 00:15:56 -0500 [thread overview]
Message-ID: <20160404051556.GH17806@rob-hp-laptop> (raw)
In-Reply-To: <1459497178-31090-3-git-send-email-srinivas.kandagatla@linaro.org>
On Fri, Apr 01, 2016 at 08:52:57AM +0100, Srinivas Kandagatla wrote:
> On some SOCs PORTS_IMPL register value is never programmed by the
> firmware 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 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 can override the PORTS_IMPL register in cases where
> the firmware did not program it already.
>
> Fixes: 566d1827df2e ("libata: disable forced PORTS_IMPL for >= AHCI 1.3)
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Acked-by: Tejun Heo <tj@kernel.org>
> Reviewed-by: Andy Gross <andy.gross@linaro.org>
> ---
> Documentation/devicetree/bindings/ata/ahci-platform.txt | 4 ++++
> drivers/ata/ahci_platform.c | 3 +++
> 2 files changed, 7 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-04-04 5:15 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
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 [this message]
2016-04-01 7:52 ` [PATCH v3 3/3] ARM: dts: apq8064: add ahci ports-implemented mask Srinivas Kandagatla
2016-04-01 14:44 ` [PATCH v3 0/3] ahci: add ports-implemented dt bindings 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=20160404051556.GH17806@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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