From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <me@felipebalbi.com>
Cc: linux-omap@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>
Subject: Re: [PATCH] omap: mmc: make mmc build again for omap1
Date: Tue, 11 Nov 2008 16:30:59 -0800 [thread overview]
Message-ID: <20081112003058.GT3984@atomide.com> (raw)
In-Reply-To: <1226444744-22617-1-git-send-email-me@felipebalbi.com>
* Felipe Balbi <me@felipebalbi.com> [081111 15:08]:
> From: Felipe Balbi <felipe.balbi@nokia.com>
>
> Trivial fix making mmc build for omap1 boards.
Thanks, looks like I missed pushing some changes to the series I made
earlier.. Pushing today.
Tony
> Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
> ---
> arch/arm/mach-omap1/board-innovator.c | 2 +-
> arch/arm/mach-omap1/devices.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-omap1/board-innovator.c b/arch/arm/mach-omap1/board-innovator.c
> index 7a97f6b..feaf616 100644
> --- a/arch/arm/mach-omap1/board-innovator.c
> +++ b/arch/arm/mach-omap1/board-innovator.c
> @@ -385,7 +385,7 @@ static struct omap_mmc_platform_data mmc1_data = {
> .nr_slots = 1,
> .slots[0] = {
> .set_power = mmc_set_power,
> - .wire4 = 1,
> + .wires = 4,
> .name = "mmcblk",
> },
> };
> diff --git a/arch/arm/mach-omap1/devices.c b/arch/arm/mach-omap1/devices.c
> index 45712a5..e8ff6b5 100644
> --- a/arch/arm/mach-omap1/devices.c
> +++ b/arch/arm/mach-omap1/devices.c
> @@ -116,7 +116,7 @@ static inline void omap1_mmc_mux(struct omap_mmc_platform_data *mmc_controller,
> omap_cfg_reg(P19_1710_MMC_CMDDIR);
> omap_cfg_reg(P20_1710_MMC_DATDIR0);
> }
> - if (mmc_controller->slots[0].wire4) {
> + if (mmc_controller->slots[0].wires == 4) {
> omap_cfg_reg(MMC_DAT1);
> /* NOTE: DAT2 can be on W10 (here) or M15 */
> if (!mmc_controller->slots[0].nomux)
> @@ -132,7 +132,7 @@ static inline void omap1_mmc_mux(struct omap_mmc_platform_data *mmc_controller,
> omap_cfg_reg(Y10_1610_MMC2_CLK);
> omap_cfg_reg(R18_1610_MMC2_CLKIN);
> omap_cfg_reg(W8_1610_MMC2_DAT0);
> - if (mmc_controller->slots[1].wire4) {
> + if (mmc_controller->slots[1].wires == 4) {
> omap_cfg_reg(V8_1610_MMC2_DAT1);
> omap_cfg_reg(W15_1610_MMC2_DAT2);
> omap_cfg_reg(R10_1610_MMC2_DAT3);
> --
> 1.6.0.2.307.gc427
>
prev parent reply other threads:[~2008-11-12 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 23:05 [PATCH] omap: mmc: make mmc build again for omap1 Felipe Balbi
2008-11-12 0:30 ` Tony Lindgren [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=20081112003058.GT3984@atomide.com \
--to=tony@atomide.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.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