From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot
Date: Fri, 5 Dec 2008 16:27:47 -0800 [thread overview]
Message-ID: <20081206002747.GQ9714@atomide.com> (raw)
In-Reply-To: <1228148566-9358-2-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [081201 08:23]:
> The bootloader may leave the MMC in a state which prevents hitting
> retention. Even when MMC is not compiled in, each MMC module needs to
> be forced into reset.
Pushing to l-o tree, and adding omap mmc queue for mainline.
Tony
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> arch/arm/mach-omap2/devices.c | 85 +++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 85 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 241e418..423647e 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -14,6 +14,7 @@
> #include <linux/init.h>
> #include <linux/platform_device.h>
> #include <linux/io.h>
> +#include <linux/clk.h>
>
> #include <mach/hardware.h>
> #include <asm/mach-types.h>
> @@ -358,6 +359,89 @@ static inline void omap_init_sha1_md5(void) { }
>
> /*-------------------------------------------------------------------------*/
>
> +#ifdef CONFIG_ARCH_OMAP3
> +
> +#define MMCHS_SYSCONFIG 0x0010
> +#define MMCHS_SYSCONFIG_SWRESET (1 << 1)
> +#define MMCHS_SYSSTATUS 0x0014
> +#define MMCHS_SYSSTATUS_RESETDONE (1 << 0)
> +
> +static struct platform_device dummy_pdev = {
> + .dev = {
> + .bus = &platform_bus_type,
> + },
> +};
> +
> +/**
> + * omap_hsmmc_reset() - Full reset of each HS-MMC controller
> + *
> + * Ensure that each MMC controller is fully reset. Controllers
> + * left in an unknown state (by bootloader) may prevent retention
> + * or OFF-mode. This is especially important in cases where the
> + * MMC driver is not enabled, _or_ built as a module.
> + *
> + * In order for reset to work, interface, functional and debounce
> + * clocks must be enabled. The debounce clock comes from func_32k_clk
> + * and is not under SW control, so we only enable i- and f-clocks.
> + **/
> +static void __init omap_hsmmc_reset(void)
> +{
> + u32 i, nr_controllers = cpu_is_omap34xx() ? OMAP34XX_NR_MMC :
> + OMAP24XX_NR_MMC;
> +
> + for (i = 0; i < nr_controllers; i++) {
> + u32 v, base = 0;
> + struct clk *iclk, *fclk;
> + struct device *dev = &dummy_pdev.dev;
> +
> + switch (i) {
> + case 0:
> + base = OMAP2_MMC1_BASE;
> + break;
> + case 1:
> + base = OMAP2_MMC2_BASE;
> + break;
> + case 2:
> + base = OMAP3_MMC3_BASE;
> + break;
> + }
> +
> + dummy_pdev.id = i;
> + iclk = clk_get(dev, "mmchs_ick");
> + if (iclk && clk_enable(iclk))
> + iclk = NULL;
> +
> + fclk = clk_get(dev, "mmchs_fck");
> + if (fclk && clk_enable(fclk))
> + fclk = NULL;
> +
> + if (!iclk || !fclk) {
> + printk(KERN_WARNING
> + "%s: Unable to enable clocks for MMC%d, "
> + "cannot reset.\n", __func__, i);
> + break;
> + }
> +
> + omap_writel(MMCHS_SYSCONFIG_SWRESET, base + MMCHS_SYSCONFIG);
> + v = omap_readl(base + MMCHS_SYSSTATUS);
> + while (!(omap_readl(base + MMCHS_SYSSTATUS) &
> + MMCHS_SYSSTATUS_RESETDONE))
> + cpu_relax();
> +
> + if (fclk) {
> + clk_disable(fclk);
> + clk_put(fclk);
> + }
> + if (iclk) {
> + clk_disable(iclk);
> + clk_put(iclk);
> + }
> + }
> +}
> +#else
> +static inline void omap_hsmmc_reset(void) {}
> +#endif
> +
> #if defined(CONFIG_MMC_OMAP) || defined(CONFIG_MMC_OMAP_MODULE) || \
> defined(CONFIG_MMC_OMAP_HS) || defined(CONFIG_MMC_OMAP_HS_MODULE)
>
> @@ -477,6 +561,7 @@ static int __init omap2_init_devices(void)
> /* please keep these calls, and their implementations above,
> * in alphabetical order so they're easier to sort through.
> */
> + omap_hsmmc_reset();
> omap_init_camera();
> omap_init_mbox();
> omap_init_mcspi();
> --
> 1.6.0.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-06 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 16:22 [PATCH v2 0/5] extra module resets to ensure full-chip idle Kevin Hilman
2008-12-01 16:22 ` [PATCH v2 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot Kevin Hilman
2008-12-01 16:22 ` [PATCH v2 2/5] OMAP3: PM: Force IVA2 into idle during bootup Kevin Hilman
2008-12-01 16:22 ` [PATCH v2 3/5] OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init Kevin Hilman
2008-12-01 16:22 ` [PATCH v2 4/5] OMAP3: PM: D2D clockdomain supports SW supervised transitions Kevin Hilman
2008-12-01 16:22 ` [PATCH v2 5/5] OMAP3: PM: Ensure modem is reset during PRCM init Kevin Hilman
2008-12-06 6:38 ` [PATCH v2 4/5] OMAP3: PM: D2D clockdomain supports SW supervised transitions Paul Walmsley
2008-12-06 6:37 ` [PATCH v2 3/5] OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init Paul Walmsley
2008-12-06 6:23 ` [PATCH v2 2/5] OMAP3: PM: Force IVA2 into idle during bootup Paul Walmsley
2008-12-06 0:27 ` Tony Lindgren [this message]
2008-12-06 6:28 ` [PATCH v2 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot Paul Walmsley
2008-12-01 16:36 ` [PATCH v2 0/5] extra module resets to ensure full-chip idle Kevin Hilman
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=20081206002747.GQ9714@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@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