From: mcuelenaere@gmail.com (Maurus Cuelenaere)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/8] s3c6410: sdhci: Adding additional data in sdhci platform data structure.
Date: Sat, 12 Sep 2009 18:04:55 +0200 [thread overview]
Message-ID: <4AABC6A7.6050707@gmail.com> (raw)
Hi,
this breaks hsmmc1 (and hsmmc2).
Attached patch fixes hsmmc1.
Regards,
Maurus Cuelenaere
From a743b9c3b7a6b63e2c0ccf22a45a06952920dff4 Mon Sep 17 00:00:00 2001
From: Maurus Cuelenaere <mcuelenaere@gmail.com>
Date: Sat, 12 Sep 2009 17:40:33 +0200
This patch adds additional information about the parent clock
name, sdhci clock name and desired sdhci operating frequency
for hsmmc1 (based on e52782df345ec3e826701438ef42d2a8425bb973).
Signed-off-by: Maurus Cuelenaere <mcuelenaere@gmail.com>
---
arch/arm/plat-s3c/dev-hsmmc1.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/plat-s3c/dev-hsmmc1.c b/arch/arm/plat-s3c/dev-hsmmc1.c
index e49bc4c..d8c8f61 100644
--- a/arch/arm/plat-s3c/dev-hsmmc1.c
+++ b/arch/arm/plat-s3c/dev-hsmmc1.c
@@ -41,6 +41,9 @@ struct s3c_sdhci_platdata s3c_hsmmc1_def_platdata = {
.max_width = 4,
.host_caps = (MMC_CAP_4_BIT_DATA |
MMC_CAP_MMC_HIGHSPEED | MMC_CAP_SD_HIGHSPEED),
+ .clk_parent_name = "dout_mpll",
+ .clk_source_name = "mmc_bus",
+ .clk_speed = 50*MHZ,
};
struct platform_device s3c_device_hsmmc1 = {
--
1.6.3.3
next reply other threads:[~2009-09-12 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 16:04 Maurus Cuelenaere [this message]
2009-09-14 13:29 ` [PATCH 2/8] s3c6410: sdhci: Adding additional data in sdhci platform data structure Thomas P. Abraham
2009-09-14 13:33 ` Maurus Cuelenaere
2009-09-16 0:33 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 6:47 thomas.ab at samsung.com
2009-09-16 0:43 ` Ben Dooks
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=4AABC6A7.6050707@gmail.com \
--to=mcuelenaere@gmail.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).