On Tue, Dec 7, 2010 at 1:51 PM, Adrian Hunter <adrian.hunter@xxxxxxxxx> wrote: > On 07/12/10 20:21, ext Paul Walmsley wrote: >> >> Madhusudhan, >> >> On my OMAP35xx BeagleBoard here, HSMMC is non-functional after returning >> from dynamic off-mode. The MMC LED turns on and stays on, and the process >> hangs, although the rest of the system still seems to run. Looks like >> you're listed as the maintainer for this code. Do you know why this is, >> and what can be done to fix it? > > It is at least because omap_pm_get_dev_context_loss_count() is not > implemented. Tero Kristo was looking at that recently. > Yes. I agree that is the problem. In the .32 kernel I had hooked it to "get_last_off_on_transaction_id" which helped. But that functionality does not exist anymore. So something equivalent to tell the driver when the OFF was hit will make it work. Regards, Madhu >> >> This is using linux-omap master at commit >> a04fd22204b13ce34a3f8a8157f83c44d64f8da9, using omap2plus_defconfig with >> DSS configured in. My boot and root partitions are on MMC. Following are >> the commands I used to reproduce this problem. >> >> >> regards >> >> - Paul >> >> echo 1> /debug/pm_debug/sleep_while_idle >> echo 1> /debug/pm_debug/enable_off_mode >> echo 5> /sys/devices/platform/omap/omap-hsuart.0/sleep_timeout >> echo 5> /sys/devices/platform/omap/omap-hsuart.1/sleep_timeout >> echo 5> /sys/devices/platform/omap/omap-hsuart.2/sleep_timeout >> >> > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
