From: <Yuantian.Tang@freescale.com>
To: hdegoede@redhat.com
Cc: tj@kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Tang Yuantian <Yuantian.Tang@freescale.com>
Subject: [PATCH 1/3] Revert "ahci: added support for Freescale AHCI sata"
Date: Mon, 7 Sep 2015 16:23:14 +0800 [thread overview]
Message-ID: <1441614196-4284-1-git-send-email-Yuantian.Tang@freescale.com> (raw)
From: Tang Yuantian <Yuantian.Tang@freescale.com>
This reverts commit 5163fb62541e
("ahci: added support for Freescale AHCI sata")
The reverted patch added Freescale QorIQ AHCI sata support to
ahci_platform driver though, but it left SoC specific settings to uboot.
It leads to QorIQ sata heavily depending on uboot. In order to removing
the dependency we first revert the old patch and then will add a new driver
for QorIQ SATA.
Since there are no LS* platforms that have been upstreamed, So
the revert would not break anything exists.
Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 2 --
drivers/ata/ahci_platform.c | 1 -
2 files changed, 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/ata/ahci-platform.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
index a232181..c2340ee 100644
--- a/Documentation/devicetree/bindings/ata/ahci-platform.txt
+++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
@@ -16,8 +16,6 @@ Required properties:
- "snps,dwc-ahci"
- "snps,exynos5440-ahci"
- "snps,spear-ahci"
- - "fsl,qoriq-ahci" : for qoriq series socs which include ls1021, ls2085, etc.
- - "fsl,<chip>-ahci" : chip could be ls1021, ls2085 etc.
- "generic-ahci"
- interrupts : <interrupt mapping for SATA IRQ>
- reg : <registers mapping>
diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
index 1befb11..04975b8 100644
--- a/drivers/ata/ahci_platform.c
+++ b/drivers/ata/ahci_platform.c
@@ -76,7 +76,6 @@ static const struct of_device_id ahci_of_match[] = {
{ .compatible = "ibm,476gtr-ahci", },
{ .compatible = "snps,dwc-ahci", },
{ .compatible = "hisilicon,hisi-ahci", },
- { .compatible = "fsl,qoriq-ahci", },
{},
};
MODULE_DEVICE_TABLE(of, ahci_of_match);
--
2.1.0.27.g96db324
next reply other threads:[~2015-09-07 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 8:23 Yuantian.Tang [this message]
2015-09-07 8:23 ` [PATCH 2/3] devicetree:bindings: add devicetree bindings for Freescale AHCI Yuantian.Tang
2015-09-09 23:19 ` Li Yang
[not found] ` <CADRPPNSSzWKY1P0DwyPLuTKk31YhnLxExoJX3GG+EpyWYdqSbQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-10 1:23 ` Yuantian Tang
2015-09-07 8:23 ` [PATCH 3/3 v2] ahci: added a new driver for supporting Freescale AHCI sata Yuantian.Tang
[not found] ` <1441614196-4284-1-git-send-email-Yuantian.Tang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-09-07 8:52 ` [PATCH 1/3] Revert "ahci: added support for Freescale AHCI sata" Hans de Goede
2015-09-08 16:31 ` 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=1441614196-4284-1-git-send-email-Yuantian.Tang@freescale.com \
--to=yuantian.tang@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--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).