On Wed, Jun 29, 2011 at 12:11 AM, Paul Walmsley <paul@xxxxxxxxx> wrote: > On Tue, 28 Jun 2011, T Krishnamoorthy, Balaji wrote: > >> On Tue, Jun 28, 2011 at 10:52 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: >> > >> > On Wed, 22 Jun 2011, Balaji T K wrote: >> > >> >> Use runtime autosuspend APIs to enable auto suspend delay >> > >> > Does this really need to use runtime autosuspend? Seems to me that since >> > PM runtime is just controlling the MMC IP blocks and not the regulators in >> > this instance, this could simply use pm_runtime_put*() and just avoid the >> > extra power wastage and complexity involved in autosuspend. >> >> I have seen some instabilities if delay is very less, on some production boards. > > Could you be more specific? What type of instabilities did you see? There have been some experiments on our customer programs to reduce this value to a few ms and infrequent crashes were observed (stress testing for several hours) while trying to access the controller registers. > >> The previous implementation used 100ms delay before disabling the clocks. >> Is there any specific issue I should be aware of, for using _autosuspend ? > > > - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
