Skip to contentSkip to conversation

ata: Add APM X-Gene SoC SATA host controller support

PATCH Superseded Loc Ho 3 participants 13 messages Jan 15, 2014 – Jan 16, 2014

Subsystems (3)

v9 of 15 Superseded Latest is v15 →

lore
Share & tools
lore

Loc Ho

author
#0 lore raw

v9 cover ata: Add APM X-Gene SoC SATA host controller support

This patch adds support for the APM X-Gene SoC SATA host controller. In order for the host controller to work, the corresponding PHY driver musts also be available.

v9:
* Remove ACPI/EFI include files
* Remove the IO flush support, interrupt routine, and DTS resources
* Remove function xgene_rd, xgene_wr, and xgene_wr_flush
* Remove PMP support (function xgene_ahci_qc_issue, xgene_ahci_qc_prep, xgene_ahci_qc_fill_rtf, xgene_ahci_softreset, and xgene_ahci_do_softreset)
* Rename function xgene_ahci_enable_phy to xgene_ahci_force_phy_rdy
* Clean up hardreset functions
* Require v7 of the PHY driver

v8:
* Remove _ADDR from defines
* Remove define MSTAWAUX_COHERENT_BYPASS_SET and STARAUX_COHERENT_BYPASS_SET and use direct coding
* Remove the un-necessary check for DTS boot with built in ACPI table
* Switch to use dma_set_mask_and_coherent for setting DMA mask
* Remove ACPI table matching code
* Update clock-names for sata01clk, sata23clk, and sata45clk

v7:
* Update the clock code by toggle the clock
* Update the DTS clock mask values due to the clock spilt between host and v5 of the PHY drivers

v6:
* Update binding documentation
* Change select PHY_XGENE_SATA to PHY_XGENE
* Add ULL to constants
* Change indentation and comments
* Clean up the probe functions a bit more
* Remove xgene_ahci_remove function
* Add the flush register to DTS
* Remove the interrupt-parent from DTS

v5:
* Sync up to v3 of the PHY driver
* Remove MSLIM wrapper functions
* Change the memory shutdown loop to use usleep_range
* Use devm_ioremap_resource instead devm_ioremap
* Remove suspend/resume functions as not needed

v4:
* Remove the ID property in DT
* Remove the temporary PHY direct function call and use PHY function
* Change printk to pr_debug
* Move the IOB flush addresses into the DT
* Remove the parameters retrieval function as no longer needed
* Remove the header file as no longer needed
* Require v2 patch of the SATA PHY driver. Require slightly modification in the Kconfig as it is moved to folder driver/phy and use Kconfig PHY_XGENE_SATA instead SATA_XGENE_PHY.

v3:
* Move out the SATA PHY to another driver
* Remove the clock-cells entry from DTS
* Remove debug wrapper
* Remove delay functions wrapper
* Clean up resource and IRQ query
* Remove query clock name
* Switch to use dma_set_mask/dma_coherent_mask
* Remove un-necessary devm_kfree
* Update GPL license header to v2
* Spilt up function xgene_ahci_hardreset
* Spilt up function xgene_ahci_probe
* Remove all reference of CONFIG_ARCH_MSLIM
* Clean up chip revision code

v2:
* Clean up file sata_xgene.c with Lindent and etc
* Clean up file sata_xgene_serdes.c with Lindent and etc
* Add description to each patch

v1:
* inital version

---
Loc Ho (4):
ata: Export required functions by APM X-Gene SATA driver
Documentation: Add documentation for APM X-Gene SoC SATA host
controller DTS binding
ata: Add APM X-Gene SoC SATA host controller driver
arm64: Add APM X-Gene SoC SATA host controller DTS entries

 .../devicetree/bindings/ata/apm-xgene.txt          |   68 +++
 arch/arm64/boot/dts/apm-storm.dtsi                 |   75 +++
 drivers/ata/Kconfig                                |    8 +
 drivers/ata/Makefile                               |    1 +
 drivers/ata/ahci.h                                 |    9 +
 drivers/ata/libahci.c                              |   16 +-
 drivers/ata/sata_xgene.c                           |  630 ++++++++++++++++++++
 7 files changed, 801 insertions(+), 6 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/ata/apm-xgene.txt
 create mode 100644 drivers/ata/sata_xgene.c
author
#1 lore raw

PATCH v9 1/4 ata: Export required functions by APM X-Gene SATA driver

This patch exports functions required by APM X-Gene SoC SATA host controller driver to avoid duplication of code.

---
 drivers/ata/ahci.h    |    9 +++++++++
 drivers/ata/libahci.c |   16 ++++++++++------
 2 files changed, 19 insertions(+), 6 deletions(-)
drivers/ata/ahci.h +9 -0
index 2289efd..8163b59 100644
@@ -370,6 +370,15 @@ irqreturn_t ahci_thread_fn(int irq, void *dev_instance);
 void ahci_print_info(struct ata_host *host, const char *scc_s);
 int ahci_host_activate(struct ata_host *host, int irq, unsigned int n_msis);
 void ahci_error_handler(struct ata_port *ap);
+void ahci_sw_activity(struct ata_link *link);
+int ahci_scr_write(struct ata_link *link, unsigned int sc_reg, u32 val);
+void ahci_error_intr(struct ata_port *ap, u32 irq_stat);
+int ahci_exec_polled_cmd(struct ata_port *ap, int pmp,
+			 struct ata_taskfile *tf, int is_cmd, u16 flags,
+			 unsigned long timeout_msec);
+void ahci_fill_cmd_slot(struct ahci_port_priv *pp, unsigned int tag,
+                        u32 opts);
+unsigned int ahci_fill_sg(struct ata_queued_cmd *qc, void *cmd_tbl);
 
 static inline void __iomem *__ahci_port_base(struct ata_host *host,
 					     unsigned int port_no)
drivers/ata/libahci.c +10 -6
index c482f8c..1d24bf5 100644
@@ -68,7 +68,6 @@ static ssize_t ahci_transmit_led_message(struct ata_port *ap, u32 state,
 
 
 static int ahci_scr_read(struct ata_link *link, unsigned int sc_reg, u32 *val);
-static int ahci_scr_write(struct ata_link *link, unsigned int sc_reg, u32 val);
 static unsigned int ahci_qc_issue(struct ata_queued_cmd *qc);
 static bool ahci_qc_fill_rtf(struct ata_queued_cmd *qc);
 static int ahci_port_start(struct ata_port *ap);
@@ -553,7 +552,7 @@ static int ahci_scr_read(struct ata_link *link, unsigned int sc_reg, u32 *val)
 	return -EINVAL;
 }
 
-static int ahci_scr_write(struct ata_link *link, unsigned int sc_reg, u32 val)
+int ahci_scr_write(struct ata_link *link, unsigned int sc_reg, u32 val)
 {
 	void __iomem *port_mmio = ahci_port_base(link->ap);
 	int offset = ahci_scr_offset(link->ap, sc_reg);
@@ -564,6 +563,7 @@ static int ahci_scr_write(struct ata_link *link, unsigned int sc_reg, u32 val)
 	}
 	return -EINVAL;
 }
+EXPORT_SYMBOL_GPL(ahci_scr_write);
 
 void ahci_start_engine(struct ata_port *ap)
 {
@@ -869,7 +869,7 @@ int ahci_reset_controller(struct ata_host *host)
 }
 EXPORT_SYMBOL_GPL(ahci_reset_controller);
 
-static void ahci_sw_activity(struct ata_link *link)
+void ahci_sw_activity(struct ata_link *link)
 {
 	struct ata_port *ap = link->ap;
 	struct ahci_port_priv *pp = ap->private_data;
@@ -882,6 +882,7 @@ static void ahci_sw_activity(struct ata_link *link)
 	if (!timer_pending(&emp->timer))
 		mod_timer(&emp->timer, jiffies + msecs_to_jiffies(10));
 }
+EXPORT_SYMBOL_GPL(ahci_sw_activity);
 
 static void ahci_sw_activity_blink(unsigned long arg)
 {
@@ -1239,7 +1240,7 @@ int ahci_kick_engine(struct ata_port *ap)
 }
 EXPORT_SYMBOL_GPL(ahci_kick_engine);
 
-static int ahci_exec_polled_cmd(struct ata_port *ap, int pmp,
+int ahci_exec_polled_cmd(struct ata_port *ap, int pmp,
 				struct ata_taskfile *tf, int is_cmd, u16 flags,
 				unsigned long timeout_msec)
 {
@@ -1268,6 +1269,7 @@ static int ahci_exec_polled_cmd(struct ata_port *ap, int pmp,
 
 	return 0;
 }
+EXPORT_SYMBOL_GPL(ahci_exec_polled_cmd);
 
 int ahci_do_softreset(struct ata_link *link, unsigned int *class,
 		      int pmp, unsigned long deadline,
@@ -1472,7 +1474,7 @@ static void ahci_postreset(struct ata_link *link, unsigned int *class)
 	}
 }
 
-static unsigned int ahci_fill_sg(struct ata_queued_cmd *qc, void *cmd_tbl)
+unsigned int ahci_fill_sg(struct ata_queued_cmd *qc, void *cmd_tbl)
 {
 	struct scatterlist *sg;
 	struct ahci_sg *ahci_sg = cmd_tbl + AHCI_CMD_TBL_HDR_SZ;
@@ -1494,6 +1496,7 @@ static unsigned int ahci_fill_sg(struct ata_queued_cmd *qc, void *cmd_tbl)
 
 	return si;
 }
+EXPORT_SYMBOL_GPL(ahci_fill_sg);
 
 static int ahci_pmp_qc_defer(struct ata_queued_cmd *qc)
 {
@@ -1568,7 +1571,7 @@ static void ahci_fbs_dec_intr(struct ata_port *ap)
 		dev_err(ap->host->dev, "failed to clear device error\n");
 }
 
-static void ahci_error_intr(struct ata_port *ap, u32 irq_stat)
+void ahci_error_intr(struct ata_port *ap, u32 irq_stat)
 {
 	struct ahci_host_priv *hpriv = ap->host->private_data;
 	struct ahci_port_priv *pp = ap->private_data;
@@ -1678,6 +1681,7 @@ static void ahci_error_intr(struct ata_port *ap, u32 irq_stat)
 	} else
 		ata_port_abort(ap);
 }
+EXPORT_SYMBOL_GPL(ahci_error_intr);
 
 static void ahci_handle_port_interrupt(struct ata_port *ap,
 				       void __iomem *port_mmio, u32 status)
Signature · 1 line
1.5.5
author
#2 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

---
 .../devicetree/bindings/ata/apm-xgene.txt          |   68 ++++++++++++++++++++
 1 files changed, 68 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/ata/apm-xgene.txt
Documentation/devicetree/bindings/ata/apm-xgene.txt new file +68 -0
new file mode 100644
index 0000000..3d1421a
@@ -0,0 +1,68 @@
+* APM X-Gene 6.0 Gb/s SATA host controller nodes
+
+SATA host controller nodes are defined to describe on-chip Serial ATA
+controllers. Each SATA controller (pair of ports) have its own node.
+
+Required properties:
+- compatible		: Shall be "apm,xgene-ahci-sgmii" if mux'ed with SGMII
+			  or "apm,xgene-ahci-pcie" if mux'ed with PCIe.
+- reg			: First memory resource shall be the AHCI memory
+			  resource.
+			  Second memory resource shall be the host controller
+			  memory resource.
+- interrupts		: Interrupt mapping for SATA host controller IRQ.
+- clocks		: Reference to the clock entry.
+- phys			: PHY reference with parameter 0.
+- phy-names		: Name of the PHY. Shall be "sata-6g".
+
+Optional properties:
+- status		: Shall be "ok" if enabled or "disabled" if disabled.
+			  Default is "ok".
+- interrupt-parent	: Interrupt controller.
+
+Example:
+		sataclk: sataclk {
+			compatible = "fixed-clock";
+			#clock-cells = <1>;
+			clock-frequency = <100000000>;
+			clock-output-names = "sataclk";
+		};
+
+		phy2: phy at 1f22a000 {
+			compatible = "apm,xgene-phy";
+			reg = <0x0 0x1f22a000 0x0 0x100>,
+			      <0x0 0x1f22c000 0x0 0x100>;
+			#phy-cells = <1>;
+		};
+
+		phy3: phy at 1f23a000 {
+			compatible = "apm,xgene-phy-ext";
+			reg = <0x0 0x1f23a000 0x0 0x100>,
+			      <0x0 0x1f23c000 0x0 0x100>,
+			      <0x0 0x1f2d0000 0x0 0x100>;
+			#phy-cells = <1>;
+		};
+
+		sata2: sata at 1a400000 {
+			compatible = "apm,xgene-ahci-sgmii";
+			reg = <0x0 0x1a400000 0x0 0x1000>,
+			      <0x0 0x1f220000 0x0 0x10000>;
+			interrupt-parent = <&gic>;
+			interrupts = <0x0 0x87 0x4>;
+			status = "ok";
+			clocks = <&sataclk 0>;
+			phys = <&phy2 0>;
+			phy-names = "sata-6g";
+		};
+
+		sata3: sata at 1a800000 {
+			compatible = "apm,xgene-ahci-pcie";
+			reg = <0x0 0x1a800000 0x0 0x1000>,
+			      <0x0 0x1f230000 0x0 0x10000>;
+			interrupt-parent = <&gic>;
+			interrupts = <0x0 0x88 0x4>;
+			status = "ok";
+			clocks = <&sataclk 0>;
+			phys = <&phy3 0>;
+			phy-names = "sata-6g";
+		};
Signature · 1 line
1.5.5
author
#3 lore raw

PATCH v9 3/4 ata: Add APM X-Gene SoC SATA host controller driver

This patch adds support for the APM X-Gene SoC SATA host controller driver. It requires the corresponding APM X-Gene SoC PHY driver.

---
 drivers/ata/Kconfig      |    8 +
 drivers/ata/Makefile     |    1 +
 drivers/ata/sata_xgene.c |  630 ++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 639 insertions(+), 0 deletions(-)
 create mode 100644 drivers/ata/sata_xgene.c
drivers/ata/Kconfig +8 -0
index 4e73772..cd1bc3c 100644
@@ -106,6 +106,14 @@ config AHCI_IMX
 
 	  If unsure, say N.
 
+config SATA_XGENE
+	tristate "APM X-Gene 6.0Gbps SATA host controller support"
+	depends on ARM64 || COMPILE_TEST
+	select SATA_AHCI_PLATFORM
+	select PHY_XGENE
+	help
+	  This option enables support for APM X-Gene SoC SATA host controller.
+
 config SATA_FSL
 	tristate "Freescale 3.0Gbps SATA support"
 	depends on FSL_SOC
drivers/ata/Makefile +1 -0
index 46518c6..1c0fabe 100644
@@ -11,6 +11,7 @@ obj-$(CONFIG_SATA_SIL24)	+= sata_sil24.o
 obj-$(CONFIG_SATA_DWC)		+= sata_dwc_460ex.o
 obj-$(CONFIG_SATA_HIGHBANK)	+= sata_highbank.o libahci.o
 obj-$(CONFIG_AHCI_IMX)		+= ahci_imx.o
+obj-$(CONFIG_SATA_XGENE)	+= sata_xgene.o
 
 # SFF w/ custom DMA
 obj-$(CONFIG_PDC_ADMA)		+= pdc_adma.o
drivers/ata/sata_xgene.c new file +630 -0

630 lines not on this page · raw message

Signature · 1 line
1.5.5
author
#4 lore raw

PATCH v9 4/4 arm64: Add APM X-Gene SoC SATA host controller DTS entries

---
 arch/arm64/boot/dts/apm-storm.dtsi |   75 ++++++++++++++++++++++++++++++++++++
 1 files changed, 75 insertions(+), 0 deletions(-)
arch/arm64/boot/dts/apm-storm.dtsi +75 -0
index a1f475d..34900d2 100644
@@ -221,6 +221,48 @@
 				enable-offset = <0x0>;
 				enable-mask = <0x06>;
 			};
+
+			sata01clk: sata01clk at 1f21c000 {
+				compatible = "apm,xgene-device-clock";
+				#clock-cells = <1>;
+				clocks = <&socplldiv2 0>;
+				clock-names = "socplldiv2";
+				reg = <0x0 0x1f21c000 0x0 0x1000>;
+				reg-names = "csr-reg";
+				clock-output-names = "sata01clk";
+				csr-offset = <0x4>;
+				csr-mask = <0x05>;
+				enable-offset = <0x0>;
+				enable-mask = <0x39>;
+			};
+
+			sata23clk: sata23clk at 1f22c000 {
+				compatible = "apm,xgene-device-clock";
+				#clock-cells = <1>;
+				clocks = <&socplldiv2 0>;
+				clock-names = "socplldiv2";
+				reg = <0x0 0x1f22c000 0x0 0x1000>;
+				reg-names = "csr-reg";
+				clock-output-names = "sata23clk";
+				csr-offset = <0x4>;
+				csr-mask = <0x05>;
+				enable-offset = <0x0>;
+				enable-mask = <0x39>;
+			};
+
+			sata45clk: sata45clk at 1f23c000 {
+				compatible = "apm,xgene-device-clock";
+				#clock-cells = <1>;
+				clocks = <&socplldiv2 0>;
+				clock-names = "socplldiv2";
+				reg = <0x0 0x1f23c000 0x0 0x1000>;
+				reg-names = "csr-reg";
+				clock-output-names = "sata45clk";
+				csr-offset = <0x4>;
+				csr-mask = <0x05>;
+				enable-offset = <0x0>;
+				enable-mask = <0x39>;
+			};
 		};
 
 		serial0: serial at 1c020000 {
@@ -269,5 +311,38 @@
 			apm,tx-boost-gain = <31 31 31 31 31 31>;
 			apm,tx-eye-tuning = <2 10 10 2 10 10>;
 		};
+
+		sata1: sata at 1a000000 {
+			compatible = "apm,xgene-ahci-sgmii";
+			reg = <0x0 0x1a000000 0x0 0x1000>,
+			      <0x0 0x1f210000 0x0 0x10000>;
+			interrupts = <0x0 0x86 0x4>;
+			status = "disabled";
+			clocks = <&sata01clk 0>;
+			phys = <&phy1 0>;
+			phy-names = "sata-6g";
+		};
+
+		sata2: sata at 1a400000 {
+			compatible = "apm,xgene-ahci-sgmii";
+			reg = <0x0 0x1a400000 0x0 0x1000>,
+			      <0x0 0x1f220000 0x0 0x10000>;
+			interrupts = <0x0 0x87 0x4>;
+			status = "ok";
+			clocks = <&sata23clk 0>;
+			phys = <&phy2 0>;
+			phy-names = "sata-6g";
+		};
+
+		sata3: sata at 1a800000 {
+			compatible = "apm,xgene-ahci-pcie";
+			reg = <0x0 0x1a800000 0x0 0x1000>,
+			      <0x0 0x1f230000 0x0 0x10000>;
+			interrupts = <0x0 0x88 0x4>;
+			status = "ok";
+			clocks = <&sata45clk 0>;
+			phys = <&phy3 0>;
+			phy-names = "sata-6g";
+		};
 	};
 };
Signature · 1 line
1.5.5
#5 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

In reply to Loc Ho
Quoted 17 lines · Loc Ho
---
 .../devicetree/bindings/ata/apm-xgene.txt          |   68 ++++++++++++++++++++
 1 files changed, 68 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/ata/apm-xgene.txt
Documentation/devicetree/bindings/ata/apm-xgene.txt new file +3 -0
new file mode 100644
index 0000000..3d1421a
@@ -0,0 +1,68 @@
+* APM X-Gene 6.0 Gb/s SATA host controller nodes
+
+SATA host controller nodes are defined to describe on-chip Serial ATA

Documentation/devicetree/bindings/ata/apm-xgene.txt line 13

Quoted 10 lines
Documentation/devicetree/bindings/ata/apm-xgene.txt new file +10 -0
+controllers. Each SATA controller (pair of ports) have its own node.
+
+Required properties:
+- compatible		: Shall be "apm,xgene-ahci-sgmii" if mux'ed with SGMII
+			  or "apm,xgene-ahci-pcie" if mux'ed with PCIe.
+- reg			: First memory resource shall be the AHCI memory
+			  resource.
+			  Second memory resource shall be the host controller
+			  memory resource.
+- interrupts		: Interrupt mapping for SATA host controller IRQ.

s/Interrupt-mapping/interrupt-specifier/

Documentation/devicetree/bindings/ata/apm-xgene.txt line 15

Quoted 2 lines
Documentation/devicetree/bindings/ata/apm-xgene.txt new file +2 -0
+- clocks		: Reference to the clock entry.
+- phys			: PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

Documentation/devicetree/bindings/ata/apm-xgene.txt line 16

Quoted 1 line
Documentation/devicetree/bindings/ata/apm-xgene.txt new file +1 -0
+- phy-names		: Name of the PHY. Shall be "sata-6g".

Could you define phys in terms of phy-names please? It makes the relationship clearer:

- phys: a list of phandles + phy-sciefiers, one for each entry in phy-names

- phy-names: Should contain:
* "sata-6g" for the SATA PHY <notes about requirements go here>

Cheers,
Mark.

author
#6 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Hi,

Quoted 5 lines
Quoted 2 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

-Loc

#7 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Quoted 10 lines · On Wednesday 15 January 2014 12:04:02 Loc Ho wrote:
Quoted 6 lines
Quoted 3 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

The SATA device should not care what the argument for the PHY device is. You could connect the same device to another PHY that has a different set of arguments, which is the whole point of abstracting it.

Arnd

author
#8 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Hi,

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
Quoted 3 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

Quoted 9 lines
Quoted 3 lines

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

The SATA device should not care what the argument for the PHY device is. You could connect the same device to another PHY that has a different set of arguments, which is the whole point of abstracting it.

I understand what you wrote here. We should not have an argument from the host controller. Then my question is how should the PHY node indicates that it needs to be configured itself as an SATA PHY?

-Loc

#9 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Quoted 16 lines · On Wednesday 15 January 2014 13:08:47 Loc Ho wrote:
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

Quoted 9 lines
Quoted 3 lines

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

The SATA device should not care what the argument for the PHY device is. You could connect the same device to another PHY that has a different set of arguments, which is the whole point of abstracting it.

Quoted 3 lines

I understand what you wrote here. We should not have an argument from the host controller. Then my question is how should the PHY node indicates that it needs to be configured itself as an SATA PHY?

The "phys" property should specify whatever the configuration of the phy device is supposed to be. It's just not the business of the sata driver or the sata binding to know what that configuration is.

Arnd

author
#10 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Hi,

Quoted 16 lines
Quoted 16 lines
Quoted 15 lines
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

The SATA device should not care what the argument for the PHY device is. You could connect the same device to another PHY that has a different set of arguments, which is the whole point of abstracting it.

Quoted 9 lines
Quoted 3 lines

I understand what you wrote here. We should not have an argument from the host controller. Then my question is how should the PHY node indicates that it needs to be configured itself as an SATA PHY?

The "phys" property should specify whatever the configuration of the phy device is supposed to be. It's just not the business of the sata driver or the sata binding to know what that configuration is.

Here is what I have and I am trying to piece this together:

phy1 {
#phy-cells = <0>; /* No parameter as suggest by Mark */
};

sata1 {
    :::
    phys = <&phy1>;
};

What I don't get is how does one specify the mode (SATA/USB/SGMII/etc)? As another parameter in the phy1 node?

-Loc

author
#11 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Hi,

Quoted 32 lines
Quoted 16 lines
Quoted 16 lines
Quoted 15 lines
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
+- clocks             : Reference to the clock entry.
+- phys                       : PHY reference with parameter 0.

The specific value of the phy-specifier shouldn't matter to this binding. What should matter is what it logically corresponds to.

I not quite following this. Are you suggest that I drop the value 0. In the binding, one needs to specify the mode of operation - 0 is for SATA. Can you explain more?

The SATA device should not care what the argument for the PHY device is. You could connect the same device to another PHY that has a different set of arguments, which is the whole point of abstracting it.

Quoted 9 lines
Quoted 3 lines

I understand what you wrote here. We should not have an argument from the host controller. Then my question is how should the PHY node indicates that it needs to be configured itself as an SATA PHY?

The "phys" property should specify whatever the configuration of the phy device is supposed to be. It's just not the business of the sata driver or the sata binding to know what that configuration is.

Here is what I have and I am trying to piece this together:

phy1 {
#phy-cells = <0>; /* No parameter as suggest by Mark */
};

Quoted 8 lines
sata1 {
    :::
    phys = <&phy1>;
};

What I don't get is how does one specify the mode (SATA/USB/SGMII/etc)? As another parameter in the phy1 node?

May be I misread what Mark mentioned. The binding documentation should not specify the requirement of 0. And the binding of the dts should be as is:

phy1 {
#phy-cells = <1>;
};

sata1 {
:::
phys = <&phy1 0>; where 0 indicates the mode of operation?
};

-Loc

#12 lore raw

PATCH v9 2/4 Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding

Quoted 5 lines · On Wednesday 15 January 2014 15:59:27 Loc Ho wrote:

May be I misread what Mark mentioned. The binding documentation should not specify the requirement of 0. And the binding of the dts should be as is:

Quoted 10 lines
phy1 {
   #phy-cells = <1>;
};

sata1 {
:::
phys = <&phy1 0>; where 0 indicates the mode of operation?
};

Yes, that is right. You can keep the zero in the example, but the binding text must not require a specific phy to be used.

Arnd