From: Ben Dooks <ben.dooks@codethink.co.uk>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
sebastian.hesselbarth@gmail.com, chris@printf.net,
anton@enomsg.org
Cc: alexandre.belloni@free-electrons.com, zmxu@marvell.com,
jszhang@marvell.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] mmc: sdhci: add a driver for Berlin SoCs
Date: Fri, 09 May 2014 16:55:36 +0100 [thread overview]
Message-ID: <536CFA78.9050609@codethink.co.uk> (raw)
In-Reply-To: <1397652011-21284-2-git-send-email-antoine.tenart@free-electrons.com>
On 16/04/14 13:40, Antoine Ténart wrote:
> Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> This controller supports 3 sockets.
[snip]
> +
> +static struct sdhci_ops sdhci_berlin_ops = {
> + .get_max_clock = sdhci_pltfm_clk_get_max_clock,
> +};
> +
> +static struct sdhci_pltfm_data sdhci_berlin2_pdata = {
> + .quirks = SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN |
> + SDHCI_QUIRK_BROKEN_ADMA |
> + SDHCI_QUIRK_BROKEN_TIMEOUT_VAL,
> + .ops = &sdhci_berlin_ops,
> +};
> +
> +static struct sdhci_pltfm_data sdhci_berlin2q_pdata = {
> + .quirks = SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN |
> + SDHCI_QUIRK_INVERTED_WRITE_PROTECT |
> + SDHCI_QUIRK_BROKEN_TIMEOUT_VAL,
> + .ops = &sdhci_berlin_ops,
> +};
> +
> +static const struct of_device_id sdhci_berlin_of_match_table[] = {
> + {
> + .compatible = "marvell,berlin2-sdhci",
> + .data = &sdhci_berlin2_pdata,
> + },
> + {
> + .compatible = "marvell,berlin2cd-sdhci",
> + .data = &sdhci_berlin2_pdata,
> + },
> + {
> + .compatible = "marvell,berlin2q-sdhci",
> + .data = &sdhci_berlin2q_pdata,
> + },
> + {}
I think the hardware names should be used instead of the
quirks the hardware has (broken wp / broken adma)
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-05-09 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 12:40 [PATCH 0/4] ARM: berlin: add SDHCI support Antoine Ténart
2014-04-16 12:40 ` [PATCH 1/4] mmc: sdhci: add a driver for Berlin SoCs Antoine Ténart
2014-04-16 12:56 ` Joe Perches
2014-04-16 13:09 ` Antoine Ténart
2014-04-16 14:26 ` Sebastian Hesselbarth
2014-04-17 13:33 ` Antoine Ténart
2014-04-18 6:06 ` Jisheng Zhang
2014-04-18 7:20 ` Antoine Ténart
2014-05-09 15:55 ` Ben Dooks [this message]
[not found] ` <1397652011-21284-1-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-16 12:40 ` [PATCH 2/4] Documentation: bindings: add the sdhci-berlin Antoine Ténart
2014-04-16 12:40 ` [PATCH 3/4] ARM: dts: berlin: add the SDHCI nodes for the BG2Q Antoine Ténart
[not found] ` <1397652011-21284-4-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-16 13:09 ` Andrew Lunn
[not found] ` <20140416130915.GC11310-g2DYL2Zd6BY@public.gmane.org>
2014-04-16 13:23 ` Antoine Ténart
2014-04-17 3:33 ` Jisheng Zhang
2014-04-17 6:54 ` Sebastian Hesselbarth
2014-04-16 12:40 ` [PATCH 4/4] ARM: dts: berlin: enable SD card reader and eMMC for 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=536CFA78.9050609@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=anton@enomsg.org \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.com \
/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).