From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mason Subject: Re: sata_dwc_460ex driver Date: Fri, 27 May 2016 18:56:19 +0200 Message-ID: <57487C33.4020306@free.fr> References: <57485F96.8010001@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from smtp4-g21.free.fr ([212.27.42.4]:59622 "EHLO smtp4-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755996AbcE0Q4r (ORCPT ); Fri, 27 May 2016 12:56:47 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mans Rullgard Cc: linux-ide@vger.kernel.org, Tejun Heo , Hans de Goede , Andy Shevchenko , Christian Lamparter , Srinivas Kandagatla , Andy Gross , Kishon Vijay Abraham , Sebastian Frias On 27/05/2016 18:20, M=E5ns Rullg=E5rd wrote: > Mason wrote: >=20 >> I'm working on a SoC which embeds an IP block from Synopsys labeled >> Synopsys DesignWare Cores Serial ATA AHCI Core, aka DWC_ahsata >> (DWC SATA AHCI Host 6Gb/s AXI Interface). >> >> Would the sata_dwc_460ex driver support this DWC_ahsata hardware? >> >> I suppose I would also need to enable AHCI support, right? >> >> What is the difference between SATA_AHCI and SATA_AHCI_PLATFORM ? >> >> SATA_AHCI =3D 971db06e09231 >> SATA_AHCI_PLATFORM =3D 1c2a49f61785e >> >> If I understand correctly, SATA_AHCI is for platforms with a PCI bus= , >> while SATA_AHCI_PLATFORM is for other platforms. I probably want the >> latter then? >> >> On the analog side, the SATA PHY is also made by Synopsys. >> Do I need to enable a specific driver? >> I didn't see anything relevant in drivers/phy >> >> (The documentation mentions 11 registers for tweaking the controller= , >> but maybe it's the boot-loader's job to set this up correctly?) >=20 > The sata_dwc_460ex driver can be made to work with the tango3/4 chips= =2E I'm talking about tango5. It's not the same controller as tango3/4. (They use different Synopsys DesignWare controllers.) > You need a dmaengine driver (I've written one for tango3, needs sligh= t > tweaking for tango4) and some additions to the SATA driver to handle = the > DMA glue logic (I have unpublished code for this as well). There are= a > bunch of fixes for the SATA driver currently in linux-next, and I was > planning to take another look at supporting tango3/4 once these hit > mainline (4.7-rc1 most likely). =46WIW, it seems like tango4 is low-priority internally ATM. > A driver for the PHY is probably a good idea, even if the boot loader > does some configuration, since this allows it to be powered down when > not in use. How come there are so few phy drivers in drivers/phy if most devices would typically require one? Regards.