linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-André Hébert" <hebert.marcandre@gmail.com>
To: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Stopping mmc clock between transfers
Date: Tue, 24 May 2011 14:42:32 -0400	[thread overview]
Message-ID: <BANLkTikbm_OjtwB4fhwj1Mc0HAsNPH3CVg@mail.gmail.com> (raw)

Hello,

We are using a OMAPL108 with 2.6.33 and noticed that the mmc clock
signal stays active when idle. This doesn't seem very power efficient
and we wondered if there was a reason for this. Before trying to fix
this on our side I had a few questions regarding this:
-Is this behavior the same in more recent versions?
-Was this designed to be this way?
-Would stopping the clock be a responsibility of the core (set_ios) or
the host controller (between requests)?

Regards
Marc

             reply	other threads:[~2011-05-24 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 18:42 Marc-André Hébert [this message]
2011-05-25 15:54 ` Stopping mmc clock between transfers Chris Ball

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=BANLkTikbm_OjtwB4fhwj1Mc0HAsNPH3CVg@mail.gmail.com \
    --to=hebert.marcandre@gmail.com \
    --cc=linux-mmc@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).