Hi,
We run Linux on zynqmp SoC with Linux image loaded in SD card, and when we trying to bring up the SATA SSD, we encountered an issue that it is not detected. On vivado, we assigned the SATA lane 0 to GT lane #2 (Sata Lane #1 is not used or assigned), the GT lane ref clock is set to 150MHz for SATA. with the xsa file, we generated the device tree and build the peta-linux. here’s the device tree configuration for sata.
ahci@fd0c0000 {
power-domains = <0x0c 0x1c>;
ceva,p0-comwake-params = <0x614080e>;
ceva,p0-retry-params = <0x96a43ffc>;
ceva,p0-burst-params = <0x13084a06>;
interrupts = <0x00 0x85 0x04>;
clocks = <0x03 0x16>;
interrupt-parent = <0x04>;
xlnx,tz-nonsecure-sata0 = <0x00>;
ceva,p1-retry-params = <0x96a43ffc>;
ceva,p1-burst-params = <0x13084a06>;
ceva,p1-cominit-params = <0x18401828>;
compatible = “ceva,ahci-1v84”;
status = “okay”;
#stream-id-cells = <0x04>;
reg = <0x00 0xfd0c0000 0x00 0x2000>;
phandle = <0x61>;
ceva,p0-cominit-params = <0x18401828>;
xlnx,tz-nonsecure-sata1 = <0x00>;
ceva,p1-comwake-params = <0x614080e>;
};
However, the linux could not detect the SATA, here’s the log:
root@Xilinx2004:/mnt/boot# dmesg | grep -e ahci -e SATA
[ 4.488121] ahci-ceva fd0c0000.ahci: fd0c0000.ahci supply ahci not found, using dummy regulator
[ 4.496844] ahci-ceva fd0c0000.ahci: fd0c0000.ahci supply phy not found, using dummy regulator
[ 4.505481] ahci-ceva fd0c0000.ahci: fd0c0000.ahci supply target not found, using dummy regulator
[ 4.524504] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[ 4.533459] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst
[ 4.543689] scsi host0: ahci-ceva
[ 4.547218] scsi host1: ahci-ceva
[ 4.550630] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 39
[ 4.558539] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 39
[ 4.880665] ata1: SATA link down (SStatus 0 SControl 330)
[ 4.886072] ata2: SATA link down (SStatus 0 SControl 330)
Is this device tree problem or peta-linux configuration? Does anyone know the possible cause?
Thanks,
Adam