[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Thomas Petazzoni]

Hello,

The Marvell Armada 38x ARM processors use an AHCI compatible interface
for SATA (in replacement of the Marvell-specific SATA interface,
handled by the sata_mv driver). However, like all DMA-capable Marvell
interfaces, some specific MBus window configuration must be done, so a
small specific glue layer is needed, which relies on the recently
introduced libahci_platform.c.

Changes since v1:

 * Rebased on top of v3.15-rc1

 * Added a preliminary patch that orders alphabetically the list of
   compatible strings in the DT binding document
   ahci-platform.txt. Suggested by Andrew Lunn.

 * Made the availability of MBus DRAM window informations
   mandatory. Suggested by Andrew Lunn.

 * Fixed the module alias name. Suggested by Bartlomiej
   Zolnierkiewicz.

Details of the patches:

 * The first patch is a DT binding documentation cleanup. I believe it
   should be taken by the ATA maintainer, because the second patch
   (driver patch) depends on it.

 * The second patch of this series contains the driver itself, which
   is fairly straight-forward. It should be taken by Tejun Heo as the
   ATA maintainer.

 * The last three patches add the Device Tree and defconfig
   changes. They should be taken by the respective ARM maintainers
   (mvebu maintainers for the DT and mvebu_v7_defconfig, and arm-soc
   maintainers for the multi_v7_defconfig change).

Thanks!

Thomas

Thomas Petazzoni (5):
  Documentation: dt-bindings: reformat and order list of ahci-platform
    compatibles
  ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces
  ARM: mvebu: add Device Tree description of AHCI interfaces on Armada
    38x
  ARM: configs: add ahci_mvebu to mvebu_v7_defconfig
  ARM: configs: add ahci_mvebu to multi_v7_defconfig

 .../devicetree/bindings/ata/ahci-platform.txt      |  13 ++-
 arch/arm/boot/dts/armada-385-db.dts                |   8 ++
 arch/arm/boot/dts/armada-38x.dtsi                  |  16 +++
 arch/arm/configs/multi_v7_defconfig                |   1 +
 arch/arm/configs/mvebu_v7_defconfig                |   1 +
 drivers/ata/Kconfig                                |   9 ++
 drivers/ata/Makefile                               |   1 +
 drivers/ata/ahci_mvebu.c                           | 107 +++++++++++++++++++++
 8 files changed, 152 insertions(+), 4 deletions(-)
 create mode 100644 drivers/ata/ahci_mvebu.c

-- 
1.8.3.2

[PATCH v2 1/5] Documentation: dt-bindings: reformat and order list of ahci-platform compatibles

[Thomas Petazzoni]

The ahci-platform.txt Device Tree binding documentation is gaining a
growing number of compatible strings, and it will gain one more with
the addition of the Marvell Armada 380 AHCI support. It is therefore
time to reformat this list into a proper bullet list, and more
importantly order it alphabetically;

Suggested-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 Documentation/devicetree/bindings/ata/ahci-platform.txt | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/Documentation/devicetree/bindings/ata/ahci-platform.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
index 48b285f..5598862 100644
--- a/Documentation/devicetree/bindings/ata/ahci-platform.txt
+++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
@@ -4,10 +4,14 @@ SATA nodes are defined to describe on-chip Serial ATA controllers.
 Each SATA controller should have its own node.
 
 Required properties:
-- compatible        : compatible list, one of "snps,spear-ahci",
-                      "snps,exynos5440-ahci", "ibm,476gtr-ahci",
-                      "allwinner,sun4i-a10-ahci", "fsl,imx53-ahci"
-                      "fsl,imx6q-ahci" or "snps,dwc-ahci"
+- compatible        : compatible string, one of:
+  - "allwinner,sun4i-a10-ahci"
+  - "fsl,imx53-ahci"
+  - "fsl,imx6q-ahci"
+  - "ibm,476gtr-ahci"
+  - "snps,dwc-ahci"
+  - "snps,exynos5440-ahci"
+  - "snps,spear-ahci"
 - interrupts        : <interrupt mapping for SATA IRQ>
 - reg               : <registers mapping>
 
-- 
1.8.3.2

[PATCH v2 1/5] Documentation: dt-bindings: reformat and order list of ahci-platform compatibles

[Andrew Lunn]

On Mon, Apr 14, 2014 at 04:34:11PM +0200, Thomas Petazzoni wrote:
> The ahci-platform.txt Device Tree binding documentation is gaining a
> growing number of compatible strings, and it will gain one more with
> the addition of the Marvell Armada 380 AHCI support. It is therefore
> time to reformat this list into a proper bullet list, and more
> importantly order it alphabetically;
> 
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Acked-by: Andrew Lunn <andrew@lunn.ch>

Thanks Thomas

       Andrew

> ---
>  Documentation/devicetree/bindings/ata/ahci-platform.txt | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/ata/ahci-platform.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
> index 48b285f..5598862 100644
> --- a/Documentation/devicetree/bindings/ata/ahci-platform.txt
> +++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
> @@ -4,10 +4,14 @@ SATA nodes are defined to describe on-chip Serial ATA controllers.
>  Each SATA controller should have its own node.
>  
>  Required properties:
> -- compatible        : compatible list, one of "snps,spear-ahci",
> -                      "snps,exynos5440-ahci", "ibm,476gtr-ahci",
> -                      "allwinner,sun4i-a10-ahci", "fsl,imx53-ahci"
> -                      "fsl,imx6q-ahci" or "snps,dwc-ahci"
> +- compatible        : compatible string, one of:
> +  - "allwinner,sun4i-a10-ahci"
> +  - "fsl,imx53-ahci"
> +  - "fsl,imx6q-ahci"
> +  - "ibm,476gtr-ahci"
> +  - "snps,dwc-ahci"
> +  - "snps,exynos5440-ahci"
> +  - "snps,spear-ahci"
>  - interrupts        : <interrupt mapping for SATA IRQ>
>  - reg               : <registers mapping>
>  
> -- 
> 1.8.3.2
> 

[PATCH v2 2/5] ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces

[Thomas Petazzoni]

The Marvell Armada 380 SoC includes two AHCI compatible
interfaces. However, like all DMA-capable Marvell interface, they
require special handling to configure MBus windows. Therefore, this
commit adds a new ahci_mvebu driver, which relies on the
libahci_platform.c code recently introduced.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 .../devicetree/bindings/ata/ahci-platform.txt      |   1 +
 drivers/ata/Kconfig                                |   9 ++
 drivers/ata/Makefile                               |   1 +
 drivers/ata/ahci_mvebu.c                           | 107 +++++++++++++++++++++
 4 files changed, 118 insertions(+)
 create mode 100644 drivers/ata/ahci_mvebu.c

diff --git a/Documentation/devicetree/bindings/ata/ahci-platform.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
index 5598862..d6b07e8 100644
--- a/Documentation/devicetree/bindings/ata/ahci-platform.txt
+++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
@@ -9,6 +9,7 @@ Required properties:
   - "fsl,imx53-ahci"
   - "fsl,imx6q-ahci"
   - "ibm,476gtr-ahci"
+  - "marvell,armada-380-ahci"
   - "snps,dwc-ahci"
   - "snps,exynos5440-ahci"
   - "snps,spear-ahci"
diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
index 20e03a7..58d04cb 100644
--- a/drivers/ata/Kconfig
+++ b/drivers/ata/Kconfig
@@ -123,6 +123,15 @@ config AHCI_IMX
 
 	  If unsure, say N.
 
+config AHCI_MVEBU
+	tristate "Marvell EBU AHCI SATA support"
+	depends on ARCH_MVEBU
+	help
+	  This option enables support for the Marvebu EBU SoC's
+	  onboard AHCI SATA.
+
+	  If unsure, say N.
+
 config AHCI_SUNXI
 	tristate "Allwinner sunxi AHCI SATA support"
 	depends on ARCH_SUNXI
diff --git a/drivers/ata/Makefile b/drivers/ata/Makefile
index 44c8016..5a02aee 100644
--- a/drivers/ata/Makefile
+++ b/drivers/ata/Makefile
@@ -12,6 +12,7 @@ obj-$(CONFIG_SATA_DWC)		+= sata_dwc_460ex.o
 obj-$(CONFIG_SATA_HIGHBANK)	+= sata_highbank.o libahci.o
 obj-$(CONFIG_AHCI_DA850)	+= ahci_da850.o libahci.o libahci_platform.o
 obj-$(CONFIG_AHCI_IMX)		+= ahci_imx.o libahci.o libahci_platform.o
+obj-$(CONFIG_AHCI_MVEBU)	+= ahci_mvebu.o libahci.o libahci_platform.o
 obj-$(CONFIG_AHCI_SUNXI)	+= ahci_sunxi.o libahci.o libahci_platform.o
 obj-$(CONFIG_AHCI_ST)		+= ahci_st.o libahci.o libahci_platform.o
 obj-$(CONFIG_AHCI_XGENE)	+= ahci_xgene.o libahci.o libahci_platform.o
diff --git a/drivers/ata/ahci_mvebu.c b/drivers/ata/ahci_mvebu.c
new file mode 100644
index 0000000..2a1973b
--- /dev/null
+++ b/drivers/ata/ahci_mvebu.c
@@ -0,0 +1,107 @@
+/*
+ * AHCI glue platform driver for Marvell EBU SOCs
+ *
+ * Copyright (C) 2014 Marvell
+ *
+ * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
+ * Marcin Wojtas <mw@semihalf.com>
+ *
+ * This file is licensed under the terms of the GNU General Public
+ * License version 2.  This program is licensed "as is" without any
+ * warranty of any kind, whether express or implied.
+ */
+
+#include <linux/ahci_platform.h>
+#include <linux/kernel.h>
+#include <linux/mbus.h>
+#include <linux/module.h>
+#include <linux/of_device.h>
+#include <linux/platform_device.h>
+#include "ahci.h"
+
+#define AHCI_WINDOW_CTRL(win)	(0x60 + ((win) << 4))
+#define AHCI_WINDOW_BASE(win)	(0x64 + ((win) << 4))
+#define AHCI_WINDOW_SIZE(win)	(0x68 + ((win) << 4))
+
+static void ahci_mvebu_mbus_config(struct ahci_host_priv *hpriv,
+				   const struct mbus_dram_target_info *dram)
+{
+	int i;
+
+	for (i = 0; i < 4; i++) {
+		writel(0, hpriv->mmio + AHCI_WINDOW_CTRL(i));
+		writel(0, hpriv->mmio + AHCI_WINDOW_BASE(i));
+		writel(0, hpriv->mmio + AHCI_WINDOW_SIZE(i));
+	}
+
+	for (i = 0; i < dram->num_cs; i++) {
+		const struct mbus_dram_window *cs = dram->cs + i;
+
+		writel((cs->mbus_attr << 8) |
+		       (dram->mbus_dram_target_id << 4) | 1,
+		       hpriv->mmio + AHCI_WINDOW_CTRL(i));
+		writel(cs->base, hpriv->mmio + AHCI_WINDOW_BASE(i));
+		writel(((cs->size - 1) & 0xffff0000),
+		       hpriv->mmio + AHCI_WINDOW_SIZE(i));
+	}
+}
+
+static const struct ata_port_info ahci_mvebu_port_info = {
+	.flags	   = AHCI_FLAG_COMMON,
+	.pio_mask  = ATA_PIO4,
+	.udma_mask = ATA_UDMA6,
+	.port_ops  = &ahci_platform_ops,
+};
+
+static int ahci_mvebu_probe(struct platform_device *pdev)
+{
+	struct ahci_host_priv *hpriv;
+	const struct mbus_dram_target_info *dram;
+	int rc;
+
+	hpriv = ahci_platform_get_resources(pdev);
+	if (IS_ERR(hpriv))
+		return PTR_ERR(hpriv);
+
+	rc = ahci_platform_enable_resources(hpriv);
+	if (rc)
+		return rc;
+
+	dram = mv_mbus_dram_info();
+	if (!dram)
+		return -ENODEV;
+
+	ahci_mvebu_mbus_config(hpriv, dram);
+
+	rc = ahci_platform_init_host(pdev, hpriv, &ahci_mvebu_port_info, 0, 0);
+	if (rc)
+		goto disable_resources;
+
+	return 0;
+
+disable_resources:
+	ahci_platform_disable_resources(hpriv);
+	return rc;
+}
+
+static const struct of_device_id ahci_mvebu_of_match[] = {
+	{ .compatible = "marvell,armada-380-ahci", },
+	{ },
+};
+MODULE_DEVICE_TABLE(of, ahci_mvebu_of_match);
+
+static struct platform_driver ahci_mvebu_driver = {
+	.probe = ahci_mvebu_probe,
+	.remove = ata_platform_remove_one,
+	.driver = {
+		.name = "ahci-mvebu",
+		.owner = THIS_MODULE,
+		.of_match_table = ahci_mvebu_of_match,
+	},
+};
+module_platform_driver(ahci_mvebu_driver);
+
+MODULE_DESCRIPTION("Marvell EBU AHCI SATA driver");
+MODULE_AUTHOR("Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Marcin Wojtas <mw@semihalf.com>");
+MODULE_LICENSE("GPL");
+MODULE_ALIAS("platform:ahci_mvebu");
-- 
1.8.3.2

[PATCH v2 3/5] ARM: mvebu: add Device Tree description of AHCI interfaces on Armada 38x

[Thomas Petazzoni]

The Marvell Armada 38x processors contain two AHCI compatible
interfaces. This commit adds the Device Tree description of those
interfaces at the SoC level, and also enables them on the Armada 385
DB platform, which allows access to both interfaces through SATA
ports.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 arch/arm/boot/dts/armada-385-db.dts |  8 ++++++++
 arch/arm/boot/dts/armada-38x.dtsi   | 16 ++++++++++++++++
 2 files changed, 24 insertions(+)

diff --git a/arch/arm/boot/dts/armada-385-db.dts b/arch/arm/boot/dts/armada-385-db.dts
index 6828d77..bdde8ff 100644
--- a/arch/arm/boot/dts/armada-385-db.dts
+++ b/arch/arm/boot/dts/armada-385-db.dts
@@ -81,6 +81,14 @@
 				};
 			};
 
+			sata at a8000 {
+				status = "okay";
+			};
+
+			sata at e0000 {
+				status = "okay";
+			};
+
 			flash at d0000 {
 				status = "okay";
 				num-cs = <1>;
diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi
index a064f59..634a020 100644
--- a/arch/arm/boot/dts/armada-38x.dtsi
+++ b/arch/arm/boot/dts/armada-38x.dtsi
@@ -338,6 +338,22 @@
 				reg = <0x72004 0x4>;
 			};
 
+			sata at a8000 {
+				compatible = "marvell,armada-380-ahci";
+				reg = <0xa8000 0x2000>;
+				interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
+				clocks = <&gateclk 15>;
+				status = "disabled";
+			};
+
+			sata at e0000 {
+				compatible = "marvell,armada-380-ahci";
+				reg = <0xe0000 0x2000>;
+				interrupts = <GIC_SPI 28 IRQ_TYPE_LEVEL_HIGH>;
+				clocks = <&gateclk 30>;
+				status = "disabled";
+			};
+
 			coredivclk: clock at e4250 {
 				compatible = "marvell,armada-380-corediv-clock";
 				reg = <0xe4250 0xc>;
-- 
1.8.3.2

[PATCH v2 4/5] ARM: configs: add ahci_mvebu to mvebu_v7_defconfig

[Thomas Petazzoni]

The Marvell Armada 38x platform needs the ahci_mvebu driver enabled
for the AHCI interfaces, so this commit enables the corresponding
Kconfig option in mvebu_v7_defconfig.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 arch/arm/configs/mvebu_v7_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/configs/mvebu_v7_defconfig b/arch/arm/configs/mvebu_v7_defconfig
index a34713d..aaa625a 100644
--- a/arch/arm/configs/mvebu_v7_defconfig
+++ b/arch/arm/configs/mvebu_v7_defconfig
@@ -36,6 +36,7 @@ CONFIG_CFG80211=y
 CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
 CONFIG_BLK_DEV_SD=y
 CONFIG_ATA=y
+CONFIG_AHCI_MVEBU=y
 CONFIG_SATA_MV=y
 CONFIG_NETDEVICES=y
 CONFIG_MVNETA=y
-- 
1.8.3.2

[PATCH v2 5/5] ARM: configs: add ahci_mvebu to multi_v7_defconfig

[Thomas Petazzoni]

The Marvell Armada 38x platform needs the ahci_mvebu driver enabled
for the AHCI interfaces, so this commit enables the corresponding
Kconfig option in multi_v7_defconfig.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 arch/arm/configs/multi_v7_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index d4e8a47..59f7ede 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -116,6 +116,7 @@ CONFIG_BLK_DEV_SD=y
 CONFIG_BLK_DEV_SR=y
 CONFIG_SCSI_MULTI_LUN=y
 CONFIG_ATA=y
+CONFIG_AHCI_MVEBU=y
 CONFIG_SATA_AHCI_PLATFORM=y
 CONFIG_SATA_HIGHBANK=y
 CONFIG_SATA_MV=y
-- 
1.8.3.2

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Andrew Lunn]

On Mon, Apr 14, 2014 at 04:34:10PM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> The Marvell Armada 38x ARM processors use an AHCI compatible interface
> for SATA (in replacement of the Marvell-specific SATA interface,
> handled by the sata_mv driver). However, like all DMA-capable Marvell
> interfaces, some specific MBus window configuration must be done, so a
> small specific glue layer is needed, which relies on the recently
> introduced libahci_platform.c.
> 
> Changes since v1:
> 
>  * Rebased on top of v3.15-rc1
> 
>  * Added a preliminary patch that orders alphabetically the list of
>    compatible strings in the DT binding document
>    ahci-platform.txt. Suggested by Andrew Lunn.
> 
>  * Made the availability of MBus DRAM window informations
>    mandatory. Suggested by Andrew Lunn.
> 
>  * Fixed the module alias name. Suggested by Bartlomiej
>    Zolnierkiewicz.

Acked-by: Andrew Lunn <andrew@lunn.ch>

	  Andrew


> 
> Details of the patches:
> 
>  * The first patch is a DT binding documentation cleanup. I believe it
>    should be taken by the ATA maintainer, because the second patch
>    (driver patch) depends on it.
> 
>  * The second patch of this series contains the driver itself, which
>    is fairly straight-forward. It should be taken by Tejun Heo as the
>    ATA maintainer.
> 
>  * The last three patches add the Device Tree and defconfig
>    changes. They should be taken by the respective ARM maintainers
>    (mvebu maintainers for the DT and mvebu_v7_defconfig, and arm-soc
>    maintainers for the multi_v7_defconfig change).
> 
> Thanks!
> 
> Thomas
> 
> Thomas Petazzoni (5):
>   Documentation: dt-bindings: reformat and order list of ahci-platform
>     compatibles
>   ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces
>   ARM: mvebu: add Device Tree description of AHCI interfaces on Armada
>     38x
>   ARM: configs: add ahci_mvebu to mvebu_v7_defconfig
>   ARM: configs: add ahci_mvebu to multi_v7_defconfig
> 
>  .../devicetree/bindings/ata/ahci-platform.txt      |  13 ++-
>  arch/arm/boot/dts/armada-385-db.dts                |   8 ++
>  arch/arm/boot/dts/armada-38x.dtsi                  |  16 +++
>  arch/arm/configs/multi_v7_defconfig                |   1 +
>  arch/arm/configs/mvebu_v7_defconfig                |   1 +
>  drivers/ata/Kconfig                                |   9 ++
>  drivers/ata/Makefile                               |   1 +
>  drivers/ata/ahci_mvebu.c                           | 107 +++++++++++++++++++++
>  8 files changed, 152 insertions(+), 4 deletions(-)
>  create mode 100644 drivers/ata/ahci_mvebu.c
> 
> -- 
> 1.8.3.2
> 

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Bartlomiej Zolnierkiewicz]

Hi,

On Monday, April 14, 2014 04:34:10 PM Thomas Petazzoni wrote:
> Hello,
> 
> The Marvell Armada 38x ARM processors use an AHCI compatible interface
> for SATA (in replacement of the Marvell-specific SATA interface,
> handled by the sata_mv driver). However, like all DMA-capable Marvell
> interfaces, some specific MBus window configuration must be done, so a
> small specific glue layer is needed, which relies on the recently
> introduced libahci_platform.c.
> 
> Changes since v1:
> 
>  * Rebased on top of v3.15-rc1
> 
>  * Added a preliminary patch that orders alphabetically the list of
>    compatible strings in the DT binding document
>    ahci-platform.txt. Suggested by Andrew Lunn.
> 
>  * Made the availability of MBus DRAM window informations
>    mandatory. Suggested by Andrew Lunn.
> 
>  * Fixed the module alias name. Suggested by Bartlomiej
>    Zolnierkiewicz.

Well, you could have also added a comment explaining the lack of
the Power Management support..

> Details of the patches:
> 
>  * The first patch is a DT binding documentation cleanup. I believe it
>    should be taken by the ATA maintainer, because the second patch
>    (driver patch) depends on it.
> 
>  * The second patch of this series contains the driver itself, which
>    is fairly straight-forward. It should be taken by Tejun Heo as the
>    ATA maintainer.
> 
>  * The last three patches add the Device Tree and defconfig
>    changes. They should be taken by the respective ARM maintainers
>    (mvebu maintainers for the DT and mvebu_v7_defconfig, and arm-soc
>    maintainers for the multi_v7_defconfig change).

Anyway, all patches look OK to me.

Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

> Thanks!
> 
> Thomas
> 
> Thomas Petazzoni (5):
>   Documentation: dt-bindings: reformat and order list of ahci-platform
>     compatibles
>   ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces
>   ARM: mvebu: add Device Tree description of AHCI interfaces on Armada
>     38x
>   ARM: configs: add ahci_mvebu to mvebu_v7_defconfig
>   ARM: configs: add ahci_mvebu to multi_v7_defconfig
> 
>  .../devicetree/bindings/ata/ahci-platform.txt      |  13 ++-
>  arch/arm/boot/dts/armada-385-db.dts                |   8 ++
>  arch/arm/boot/dts/armada-38x.dtsi                  |  16 +++
>  arch/arm/configs/multi_v7_defconfig                |   1 +
>  arch/arm/configs/mvebu_v7_defconfig                |   1 +
>  drivers/ata/Kconfig                                |   9 ++
>  drivers/ata/Makefile                               |   1 +
>  drivers/ata/ahci_mvebu.c                           | 107 +++++++++++++++++++++
>  8 files changed, 152 insertions(+), 4 deletions(-)
>  create mode 100644 drivers/ata/ahci_mvebu.c

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Thomas Petazzoni]

Dear Bartlomiej Zolnierkiewicz,

On Mon, 14 Apr 2014 17:53:37 +0200, Bartlomiej Zolnierkiewicz wrote:

> >  * Fixed the module alias name. Suggested by Bartlomiej
> >    Zolnierkiewicz.
> 
> Well, you could have also added a comment explaining the lack of
> the Power Management support..

True, sorry for this. Should I resend a new version of the patch series
with an indication about this in the commit log? Or is this OK as it is?

Note that working on power management support is part of our mid-term
TODO list for this platform, so it will not remain unimplemented
forever.

> Anyway, all patches look OK to me.
> 
> Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Bartlomiej Zolnierkiewicz]

On Monday, April 14, 2014 06:01:42 PM Thomas Petazzoni wrote:
> Dear Bartlomiej Zolnierkiewicz,
> 
> On Mon, 14 Apr 2014 17:53:37 +0200, Bartlomiej Zolnierkiewicz wrote:
> 
> > >  * Fixed the module alias name. Suggested by Bartlomiej
> > >    Zolnierkiewicz.
> > 
> > Well, you could have also added a comment explaining the lack of
> > the Power Management support..
> 
> True, sorry for this. Should I resend a new version of the patch series
> with an indication about this in the commit log? Or is this OK as it is?

Please include the comment in the next revision if this is not too much
trouble (I assume that you would like to do another re-spin just to add
Acked-by/Reviewed-by tags anyway).

> Note that working on power management support is part of our mid-term
> TODO list for this platform, so it will not remain unimplemented
> forever.

OK, good to hear that.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Thomas Petazzoni]

Dear Bartlomiej Zolnierkiewicz,

On Mon, 14 Apr 2014 18:13:07 +0200, Bartlomiej Zolnierkiewicz wrote:
> On Monday, April 14, 2014 06:01:42 PM Thomas Petazzoni wrote:
> > Dear Bartlomiej Zolnierkiewicz,
> > 
> > On Mon, 14 Apr 2014 17:53:37 +0200, Bartlomiej Zolnierkiewicz wrote:
> > 
> > > >  * Fixed the module alias name. Suggested by Bartlomiej
> > > >    Zolnierkiewicz.
> > > 
> > > Well, you could have also added a comment explaining the lack of
> > > the Power Management support..
> > 
> > True, sorry for this. Should I resend a new version of the patch series
> > with an indication about this in the commit log? Or is this OK as it is?
> 
> Please include the comment in the next revision if this is not too much
> trouble (I assume that you would like to do another re-spin just to add
> Acked-by/Reviewed-by tags anyway).

Well, I wasn't planning on re-spinning just to add Acked-by/Reviewed-by
tags, as those are generally added by the subsystem maintainers when
applying the patches. Though if Tejun says otherwise, I can definitely
re-spin without any problem.

Tejun, just let me know what you prefer.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Tejun Heo]

On Mon, Apr 14, 2014 at 06:19:20PM +0200, Thomas Petazzoni wrote:
> Dear Bartlomiej Zolnierkiewicz,
> 
> On Mon, 14 Apr 2014 18:13:07 +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Monday, April 14, 2014 06:01:42 PM Thomas Petazzoni wrote:
> > > Dear Bartlomiej Zolnierkiewicz,
> > > 
> > > On Mon, 14 Apr 2014 17:53:37 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > 
> > > > >  * Fixed the module alias name. Suggested by Bartlomiej
> > > > >    Zolnierkiewicz.
> > > > 
> > > > Well, you could have also added a comment explaining the lack of
> > > > the Power Management support..
> > > 
> > > True, sorry for this. Should I resend a new version of the patch series
> > > with an indication about this in the commit log? Or is this OK as it is?
> > 
> > Please include the comment in the next revision if this is not too much
> > trouble (I assume that you would like to do another re-spin just to add
> > Acked-by/Reviewed-by tags anyway).
> 
> Well, I wasn't planning on re-spinning just to add Acked-by/Reviewed-by
> tags, as those are generally added by the subsystem maintainers when
> applying the patches. Though if Tejun says otherwise, I can definitely
> re-spin without any problem.
> 
> Tejun, just let me know what you prefer.

I can collect the -by's but better patch description is always nice.
Maybe just update the patch description and post that one as reply to
the patch posted in this thread?  Also, how do you want the patches to
be routed?  Can all go through libata?

-- 
tejun

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Thomas Petazzoni]

Dear Tejun Heo,

On Mon, 14 Apr 2014 13:46:06 -0400, Tejun Heo wrote:

> > Well, I wasn't planning on re-spinning just to add Acked-by/Reviewed-by
> > tags, as those are generally added by the subsystem maintainers when
> > applying the patches. Though if Tejun says otherwise, I can definitely
> > re-spin without any problem.
> > 
> > Tejun, just let me know what you prefer.
> 
> I can collect the -by's but better patch description is always nice.
> Maybe just update the patch description and post that one as reply to
> the patch posted in this thread?

Actually, Bartlomiej wanted the comment about the power management
features to be made in the code itself, rather than in the commit log,
so I guess I'll just respin the patch series. Expect a v3 tomorrow with
this change.

> Also, how do you want the patches to be routed?  Can all go through libata?

As written in the cover letter, I'd expect patches 1 and 2 to go
through libata, and then patches 3, 4 and 5 to go through arm-soc. The
reason is that patches 3, 4 and 5 modifies the Device Tree files and
the ARM defconfigs, which are likely to also be changed by other
commits in the same cycle. However, the DT binding documentation change
and the driver change are independent, so they can go through libata.

I guess Jason Cooper, who handles the patch merging for mvebu
platforms, can confirm (or not?) this proposal.

Thanks a lot for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[PATCH v2 0/5] Support for Marvell AHCI interface on Armada 38x

[Jason Cooper]

On Mon, Apr 14, 2014 at 08:44:55PM +0200, Thomas Petazzoni wrote:
> On Mon, 14 Apr 2014 13:46:06 -0400, Tejun Heo wrote:
> > Also, how do you want the patches to be routed?  Can all go through libata?
> 
> As written in the cover letter, I'd expect patches 1 and 2 to go
> through libata, and then patches 3, 4 and 5 to go through arm-soc. The
> reason is that patches 3, 4 and 5 modifies the Device Tree files and
> the ARM defconfigs, which are likely to also be changed by other
> commits in the same cycle. However, the DT binding documentation change
> and the driver change are independent, so they can go through libata.
> 
> I guess Jason Cooper, who handles the patch merging for mvebu
> platforms, can confirm (or not?) this proposal.

Yep, this is how we do it.  The only caveat is if there are going to be
changes during this window that depend on the driver changes in this
series.  Then we would ask to set up a topic branch.

That happens a little more frequently now that we have boards in the
boot farm testing linux-next and other trees.  It means we also care
about boot-time dependencies as well as build deps.

I'll take a closer look at this series in the next few days and let you
know.

thx,

Jason.