From: Mason <slash.tmp@free.fr>
To: linux-ide@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mans Rullgard <mans@mansr.com>,
Christian Lamparter <chunkeey@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
Kishon Vijay Abraham <kishon@ti.com>,
Sebastian Frias <sf84@laposte.net>
Subject: sata_dwc_460ex driver
Date: Fri, 27 May 2016 16:54:14 +0200 [thread overview]
Message-ID: <57485F96.8010001@free.fr> (raw)
Hello everyone,
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 = 971db06e09231
SATA_AHCI_PLATFORM = 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?)
Regards.
next reply other threads:[~2016-05-27 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:54 Mason [this message]
2016-05-27 16:20 ` sata_dwc_460ex driver Måns Rullgård
2016-05-27 16:56 ` Mason
2016-05-27 18:15 ` Andy Gross
2016-05-27 18:41 ` Mason
2016-05-27 18:46 ` Måns Rullgård
[not found] ` <CAAd0S9BQoLsz1226seRW697rzNC9=SJDRC=JR2s4242tyg1+4g@mail.gmail.com>
2016-05-27 17:33 ` Mason
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=57485F96.8010001@free.fr \
--to=slash.tmp@free.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=chunkeey@gmail.com \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=mans@mansr.com \
--cc=sf84@laposte.net \
--cc=srinivas.kandagatla@linaro.org \
--cc=tj@kernel.org \
/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