public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH PM-0 v2] ARM: OMAP3: HSMMC: Ensure HSMMC is fully reset on boot
Date: Fri, 19 Sep 2008 09:41:16 +0300	[thread overview]
Message-ID: <87y71o3aer.fsf@deeprootsystems.com> (raw)
In-Reply-To: <023001c91a0b$936f09e0$LocalHost@wipultra1303> (Madhusudhan Chikkature's message of "Fri\, 19 Sep 2008 09\:25\:35 +0530")

"Madhusudhan Chikkature" <madhu.cr@ti.com> writes:

>> This ensures that each HSMMC block is reset so it will not interfere
>> with retention or OFF-mode.
>> 
>> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>

[...]

> This might not be the right place to reset the controllers. You can
> avoid all the clk stuff if you do the reset in the driver probe
> function after the clocks are enabled.

The point is that this needs to be done even when the MMC driver is
NOT built into the kernel, or in the case of a module, before the MMC
driver is loaded.

> BTW, What is the issue you are facing if you dont reset the
> controllers? 

See mail from Jouni where he described it well.

> I have seen that on L-o that suspend/resume works with this driver
> enabled.

Without this patch, suspend/resume may work, but you may not hit
retention or OFF.  As Jouni also described, some boards work without
this patch, and others do not.

Kevin



  reply	other threads:[~2008-09-19  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 15:54 [PATCH PM-0 v2] ARM: OMAP3: HSMMC: Ensure HSMMC is fully reset on boot Kevin Hilman
2008-09-19  3:55 ` Madhusudhan Chikkature
2008-09-19  6:41   ` Kevin Hilman [this message]
2008-09-19 11:33 ` 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=87y71o3aer.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.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