From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/8] s3c6410: sdhci: Adding additional data in sdhci platform data structure.
Date: Wed, 16 Sep 2009 01:43:59 +0100 [thread overview]
Message-ID: <20090916004359.GP13508@trinity.fluff.org> (raw)
In-Reply-To: <1252392458-23921-1-git-send-email-thomas.ab@samsung.com>
On Tue, Sep 08, 2009 at 03:47:38PM +0900, thomas.ab at samsung.com wrote:
> From: Thomas Abraham <thomas.ab@samsung.com>
>
> This patch adds additional information about the parent clock
> name, sdhci clock name and desired sdhci operating frequency
> in the sdhci platform data structure.
This would have been better off being a series of adding the max field
and the clock fields seperately, and fixing up their platform data at
the same time.
The addiiton of the clock information is not necessary due to the
following:
1) There are four clock choices here, not just one.
2) The mmc_bus is a fixed clock name, it should not be up to the
driver to change it, it is registered by the clock core code for
the relevant architecture.
3) struct s3c_sdhci_platdata already has a `char **` pointer to an
array of clock names for (1). Setup by functions such as the
s3c_sdhci0_set_platdata. It does however seem to be missing a
documentation point in the data.
I'd apply the max-frequency change, but not the clock change.
> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
> ---
> arch/arm/plat-s3c/dev-hsmmc.c | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/plat-s3c/dev-hsmmc.c b/arch/arm/plat-s3c/dev-hsmmc.c
> index 4c05b39..357ec60 100644
> --- a/arch/arm/plat-s3c/dev-hsmmc.c
> +++ b/arch/arm/plat-s3c/dev-hsmmc.c
> @@ -38,9 +38,12 @@ static struct resource s3c_hsmmc_resource[] = {
> static u64 s3c_device_hsmmc_dmamask = 0xffffffffUL;
>
> struct s3c_sdhci_platdata s3c_hsmmc0_def_platdata = {
> - .max_width = 4,
> - .host_caps = (MMC_CAP_4_BIT_DATA |
> - MMC_CAP_MMC_HIGHSPEED | MMC_CAP_SD_HIGHSPEED),
> + .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_hsmmc0 = {
> --
> 1.5.3.4
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-09-16 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 6:47 [PATCH 2/8] s3c6410: sdhci: Adding additional data in sdhci platform data structure thomas.ab at samsung.com
2009-09-16 0:43 ` Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-12 16:04 Maurus Cuelenaere
2009-09-14 13:29 ` Thomas P. Abraham
2009-09-14 13:33 ` Maurus Cuelenaere
2009-09-16 0:33 ` 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=20090916004359.GP13508@trinity.fluff.org \
--to=ben-linux@fluff.org \
--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).