From: antoine.tenart@free-electrons.com (Antoine Ténart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/7] ata: ahci_platform: add the Marvell Berlin AHCI compatible
Date: Tue, 20 May 2014 11:23:07 +0200 [thread overview]
Message-ID: <20140520092307.GA26491@kwain> (raw)
In-Reply-To: <537B1DD3.2040104@gmail.com>
On Tue, May 20, 2014 at 11:18:11AM +0200, Sebastian Hesselbarth wrote:
> On 05/20/2014 11:04 AM, Antoine T?nart wrote:
> >The Marvell Berlin AHCI has all his specific in the PHY driver. It then
> >only need to use the libahci functions to work properly.
>
> If it is that generic, ..
>
> >Add its compatible into the libahci_platform driver.
> >
> >Signed-off-by: Antoine T?nart <antoine.tenart@free-electrons.com>
> >---
> > drivers/ata/ahci_platform.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> >diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
> >index ef67e79944f9..bc050aabf206 100644
> >--- a/drivers/ata/ahci_platform.c
> >+++ b/drivers/ata/ahci_platform.c
> >@@ -76,6 +76,7 @@ static const struct of_device_id ahci_of_match[] = {
> > { .compatible = "snps,exynos5440-ahci", },
> > { .compatible = "ibm,476gtr-ahci", },
> > { .compatible = "snps,dwc-ahci", },
> >+ { .compatible = "marvell,berlin-ahci", },
>
> .. why have a Marvell-specific compatible?
Well, the 3 other compatibles seemed as generic as the marvell one. Just
following what was done before here.
> How about "generic-ahci" instead, like we have for other fooHCIs
> already?
That would avoid an endless list of compatibles :)
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-20 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 9:04 [PATCH v4 0/7] ARM: berlin: add AHCI support Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 1/7] phy: add a driver for the Berlin SATA PHY Antoine Ténart
2014-05-20 9:11 ` Sebastian Hesselbarth
2014-05-20 9:15 ` Antoine Ténart
2014-05-20 12:34 ` Bartlomiej Zolnierkiewicz
2014-05-20 13:49 ` Andrew Lunn
2014-05-20 14:03 ` Antoine Ténart
2014-05-20 14:06 ` Andrew Lunn
2014-05-20 14:40 ` Antoine Ténart
2014-05-20 14:06 ` Antoine Ténart
2014-05-20 14:40 ` Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 2/7] Documentation: bindings: add " Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 3/7] ata: libahci: allow to use multiple PHYs Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 4/7] ata: ahci_platform: add the Marvell Berlin AHCI compatible Antoine Ténart
2014-05-20 9:18 ` Sebastian Hesselbarth
2014-05-20 9:23 ` Antoine Ténart [this message]
2014-05-20 9:04 ` [PATCH v4 5/7] Documentation: bindings: document the sub-nodes AHCI bindings Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 6/7] ARM: berlin: add the AHCI node for the BG2Q Antoine Ténart
2014-05-20 9:04 ` [PATCH v4 7/7] ARM: berlin: enable the eSATA interface on the BG2Q DMP Antoine Ténart
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=20140520092307.GA26491@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).