* [PATCH 0/2] MMC Agressive clocking framework v2
@ 2009-06-02 12:35 Linus Walleij
0 siblings, 0 replies; only message in thread
From: Linus Walleij @ 2009-06-02 12:35 UTC (permalink / raw)
To: Pierre Ossman, linux-arm-kernel; +Cc: linux-embedded, Linus Walleij
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-06-02 12:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-02 12:35 [PATCH 0/2] MMC Agressive clocking framework v2 Linus Walleij
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).