From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 09/12] ARM: shmobile: bockw: add MMCIF support
Date: Thu, 16 May 2013 15:22:05 +0000 [thread overview]
Message-ID: <5194F99D.4070708@cogentembedded.com> (raw)
In-Reply-To: <8761yjwg26.wl%kuninori.morimoto.gx@renesas.com>
On 16-05-2013 11:16, Kuninori Morimoto wrote:
> Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> arch/arm/mach-shmobile/board-bockw.c | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> diff --git a/arch/arm/mach-shmobile/board-bockw.c b/arch/arm/mach-shmobile/board-bockw.c
> index 769069e..2f51e8b 100644
> --- a/arch/arm/mach-shmobile/board-bockw.c
> +++ b/arch/arm/mach-shmobile/board-bockw.c
[...]
> @@ -100,10 +117,24 @@ static struct spi_board_info spi_board_info[] __initdata = {
> },
> };
>
> +/* MMC */
> +static struct sh_mmcif_plat_data sh_mmcif_plat = {
You can annotate this as '__initdata' as it will be kmemdup()'ed
when registering the device.
> + .sup_pclk = 0,
> + .ocr = MMC_VDD_165_195 | MMC_VDD_32_33 | MMC_VDD_33_34,
> + .caps = MMC_CAP_4_BIT_DATA |
> + MMC_CAP_8_BIT_DATA |
> + MMC_CAP_NEEDS_POLL,
> +};
> +
[...]
> @@ -133,6 +164,7 @@ static void __init bockw_init(void)
> r8a7778_add_standard_devices();
> r8a7778_add_i2c_device(0);
> r8a7778_add_hspi_device(0);
> + r8a7778_add_mmc_device(&sh_mmcif_plat);
>
> i2c_register_board_info(0, i2c0_devices,
> ARRAY_SIZE(i2c0_devices));
WBR, Sergei
prev parent reply other threads:[~2013-05-16 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 7:16 [PATCH 09/12] ARM: shmobile: bockw: add MMCIF support Kuninori Morimoto
2013-05-16 15:22 ` Sergei Shtylyov [this message]
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=5194F99D.4070708@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).