From: Viresh Kumar <viresh.linux@gmail.com>
To: jgarzik@redhat.com
Cc: spear-devel@list.st.com, viresh.linux@gmail.com,
linux-ide@vger.kernel.org, sshtylyov@mvista.com,
Viresh Kumar <viresh.kumar@st.com>,
Rob Herring <rob.herring@calxeda.com>
Subject: [PATCH V2 4/5] ata: ahci_platform: Add synopsys ahci controller in DT's compatible list
Date: Sat, 21 Apr 2012 17:40:12 +0530 [thread overview]
Message-ID: <aad8dce41013d16075a4ea479fd21a67ca548715.1335009632.git.viresh.kumar@st.com> (raw)
In-Reply-To: <cover.1335009631.git.viresh.kumar@st.com>
In-Reply-To: <cover.1335009631.git.viresh.kumar@st.com>
SPEAr13xx series of SoCs contain Synopsys AHCI SATA Controller which shares
ahci_platform driver with other controller versions.
This patch updates DT compatible list for ahci_platform. It also updates and
renames binding documentation to more generic name.
Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
Cc: Rob Herring <rob.herring@calxeda.com>
---
.../ata/{calxeda-sata.txt => ahci-platform.txt} | 5 ++---
drivers/ata/ahci_platform.c | 1 +
2 files changed, 3 insertions(+), 3 deletions(-)
rename Documentation/devicetree/bindings/ata/{calxeda-sata.txt => ahci-platform.txt} (90%)
diff --git a/Documentation/devicetree/bindings/ata/calxeda-sata.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
similarity index 90%
rename from Documentation/devicetree/bindings/ata/calxeda-sata.txt
rename to Documentation/devicetree/bindings/ata/ahci-platform.txt
index 79caa56..8bb8a76 100644
--- a/Documentation/devicetree/bindings/ata/calxeda-sata.txt
+++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
@@ -1,10 +1,10 @@
-* Calxeda SATA Controller
+* AHCI SATA Controller
SATA nodes are defined to describe on-chip Serial ATA controllers.
Each SATA controller should have its own node.
Required properties:
-- compatible : compatible list, contains "calxeda,hb-ahci"
+- compatible : compatible list, contains "calxeda,hb-ahci" or "snps,spear-ahci"
- interrupts : <interrupt mapping for SATA IRQ>
- reg : <registers mapping>
@@ -14,4 +14,3 @@ Example:
reg = <0xffe08000 0x1000>;
interrupts = <115>;
};
-
diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
index 0c86c77..9e419e1 100644
--- a/drivers/ata/ahci_platform.c
+++ b/drivers/ata/ahci_platform.c
@@ -280,6 +280,7 @@ static struct dev_pm_ops ahci_pm_ops = {
static const struct of_device_id ahci_of_match[] = {
{ .compatible = "calxeda,hb-ahci", },
+ { .compatible = "snps,spear-ahci", },
{},
};
MODULE_DEVICE_TABLE(of, ahci_of_match);
--
1.7.9
next prev parent reply other threads:[~2012-04-21 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 12:10 [PATCH V2 0/5] ata: pata_arasan and ahci_platform updates Viresh Kumar
2012-04-21 12:10 ` [PATCH V2 1/5] ata/pata_arasan_cf: Move arasan_cf_pm_ops out of #ifdef, #endif macros Viresh Kumar
2012-04-21 12:10 ` [PATCH V2 2/5] ata: pata_arasan: Add clk_{un}prepare() support Viresh Kumar
2012-04-21 12:10 ` [PATCH V2 3/5] ata: pata_arasan: add Device Tree probing capability Viresh Kumar
2012-04-21 12:10 ` Viresh Kumar [this message]
2012-04-21 12:10 ` [PATCH V2 5/5] ata/ahci_platform: Add clock framework support Viresh Kumar
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=aad8dce41013d16075a4ea479fd21a67ca548715.1335009632.git.viresh.kumar@st.com \
--to=viresh.linux@gmail.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=spear-devel@list.st.com \
--cc=sshtylyov@mvista.com \
--cc=viresh.kumar@st.com \
/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).