linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Pierre Ossman <pierre@ossman.eu>,
	linux-arm-kernel@lists.arm.linux.org.uk
Cc: linux-embedded@vger.kernel.org,
	Linus Walleij <linus.walleij@stericsson.com>
Subject: [PATCH 0/2] MMC Agressive clocking framework v2
Date: Tue, 2 Jun 2009 14:35:00 +0200	[thread overview]
Message-ID: <63386a3d0906020535j723e5b92y4f5a122db06553f0@mail.gmail.com> (raw)

ChangeLog v1->v2:

* Switch the gating mechanism from using an additional callback
  to setting the "clock" field in the ios structure to 0 and
  storing away the current value to ungate the clock later on.

* Remove the mmc_clk_enable/disable around the ios() operations
  as a result, if you use clock gating you have to take the
  gating into account in your set_ios() code.

* Keep the nesting code (use count) this is used so that quick
  bursts of requests can be handled properly while the disable
  work is idling in the background and appears quite solid.
  Tried my best to clarify why this code look as it does.

* Removed unnecessary depend on MMC!=n in the Kconfig, explicit
  (EXPERIMENTAL) in option description.

* Updates MMCI reference implementation to reflect the new use
  of the clock field.

* Remove unnecessary #include <clk.h>

* Added a debugfs file appearing in /mmcN/clk_delay that can
  be used to trim the delay cycle count to test what happens
  with different values.

* Works fine on my system.

Yours,
Linus Walleij

                 reply	other threads:[~2009-06-02 12:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=63386a3d0906020535j723e5b92y4f5a122db06553f0@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=pierre@ossman.eu \
    /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).