From: Samuel Ortiz <sameo@linux.intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] mfd: Add power control platform data to SDHI driver
Date: Fri, 27 Nov 2009 19:47:08 +0000 [thread overview]
Message-ID: <20091127194707.GB16866@sortiz.org> (raw)
In-Reply-To: <20091127043127.13567.23641.sendpatchset@rxone.opensource.se>
Hi Magnus,
On Fri, Nov 27, 2009 at 01:31:27PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> This patch adds platform data with a function for power
> control to the SDHI driver. The idea is that board specific
> code can provide their own functions so power can be enabled
> and disabled for the sd-cards.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Needed by the Ecovec board.
> Apply on top of the SDHI driver in the SuperH tree.
I wasnt cc'ed on that driver, right ? Just checking I didnt forget it...
Cheers,
Samuel.
> drivers/mfd/sh_mobile_sdhi.c | 11 +++++++++++
> include/linux/mfd/sh_mobile_sdhi.h | 8 ++++++++
> 2 files changed, 19 insertions(+)
>
> --- 0001/drivers/mfd/sh_mobile_sdhi.c
> +++ work/drivers/mfd/sh_mobile_sdhi.c 2009-11-27 13:14:24.000000000 +0900
> @@ -24,6 +24,7 @@
>
> #include <linux/mfd/core.h>
> #include <linux/mfd/tmio.h>
> +#include <linux/mfd/sh_mobile_sdhi.h>
>
> struct sh_mobile_sdhi {
> struct clk *clk;
> @@ -50,6 +51,15 @@ static struct mfd_cell sh_mobile_sdhi_ce
> .resources = sh_mobile_sdhi_resources,
> };
>
> +static void sh_mobile_sdhi_set_pwr(struct platform_device *tmio, int state)
> +{
> + struct platform_device *pdev = to_platform_device(tmio->dev.parent);
> + struct sh_mobile_sdhi_info *p = pdev->dev.platform_data;
> +
> + if (p && p->set_pwr)
> + p->set_pwr(pdev, state);
> +}
> +
> static int __init sh_mobile_sdhi_probe(struct platform_device *pdev)
> {
> struct sh_mobile_sdhi *priv;
> @@ -87,6 +97,7 @@ static int __init sh_mobile_sdhi_probe(s
>
> /* FIXME: silly const unsigned int hclk */
> *(unsigned int *)&priv->mmc_data.hclk = clk_get_rate(priv->clk);
> + priv->mmc_data.set_pwr = sh_mobile_sdhi_set_pwr;
>
> memcpy(&priv->cell_mmc, &sh_mobile_sdhi_cell, sizeof(priv->cell_mmc));
> priv->cell_mmc.driver_data = &priv->mmc_data;
> --- /dev/null
> +++ work/include/linux/mfd/sh_mobile_sdhi.h 2009-11-27 13:10:34.000000000 +0900
> @@ -0,0 +1,8 @@
> +#ifndef __SH_MOBILE_SDHI_H__
> +#define __SH_MOBILE_SDHI_H__
> +
> +struct sh_mobile_sdhi_info {
> + void (*set_pwr)(struct platform_device *pdev, int state);
> +};
> +
> +#endif /* __SH_MOBILE_SDHI_H__ */
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2009-11-27 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 9:28 [PATCH] sh: Improve kfr2r09 serial port setup code Magnus Damm
2009-11-27 7:38 ` [PATCH] sh: Break out SuperH PFC code Magnus Damm
2009-11-27 7:32 ` [PATCH] sh: Move KEYSC header file Magnus Damm
2009-11-27 5:16 ` [PATCH] sh: Add CPG save/restore code for sh7724 R-standby Magnus Damm
2009-11-27 4:36 ` [PATCH] sh: Add SDHI power control support to Ecovec Magnus Damm
2009-11-27 4:31 ` [PATCH] mfd: Add power control platform data to SDHI driver Magnus Damm
2009-11-27 19:47 ` Samuel Ortiz [this message]
2009-11-28 13:10 ` Magnus Damm
2009-11-29 23:56 ` Samuel Ortiz
2009-11-30 3:05 ` Paul Mundt
2009-11-28 1:43 ` [PATCH] sh: Move KEYSC header file Dmitry Torokhov
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=20091127194707.GB16866@sortiz.org \
--to=sameo@linux.intel.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).