[Gta04-owner] Suspend / Resume on 3.12

Dr. H. Nikolaus Schaller hns at goldelico.com
Sat Nov 16 13:23:04 CET 2013


Am 14.11.2013 um 22:21 schrieb Benjamin Deering:

> On 11/14/2013 12:36 PM, Dr. H. Nikolaus Schaller wrote:
>> 
>> Ok, I have reverted this in the 3.12.0 kernel. Maybe it conflicts with the
>> 3.12 kernel?
>> 
>> But I still have a problem with mmc1 (WiFi):
>> 
>> echo mem>  /sys/power/state
>> 
>> [  462.113830] PM: Syncing filesystems ... done.
>> [  462.190917] Freezing user space processes ... (elapsed 0.001 seconds) done.
>> [  462.201293] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
>> [  462.210693] Suspending console(s) (use no_console_suspend to debug)
>> [  462.218627] dpm_run_callback(): mmc_bus_suspend+0x0/0x44 returns -38
>> [  462.218750] PM: Device mmc1:0001 failed to suspend: error -38
>> [  462.218780] PM: Some devices failed to suspend, or early wake event detected
>> [  462.219146] PM: resume of devices complete after 0.335 msecs
>> [  462.246551] Restarting tasks ... done.
>> 
>> BTW: a description about OMAP3 power management can be found here:
>> 
>> http://elinux.org/OMAP_Power_Management
>> 
>> The only thing to note is that some /sys nodes have moved and changed.
>> 
>> BR,
>> Nikolaus
>> 
>> _______________________________________________
>> Gta04-owner mailing list
>> Gta04-owner at goldelico.com
>> http://lists.goldelico.com/mailman/listinfo/gta04-owner
>> 
> I applied this hack: http://git.neil.brown.name/?p=gta04.git;a=commit;h=da9b70a32f5b7ca53d89840ace01c2471c76ef69 to my build a while ago to make it suspend.  It look like it just ignores an error condition.  I haven't looked at why there is an error condition.

Thanks!

That looks like what I was looking for. I don't know if it is correct, but if it works...

This brings up one observation that I have made several times and it is about
the way we, the GTA04 community. are really working together.

It appears to me that we have to reinvent the wheel over and over and think about
solutions others have already found...

The problem is that nobody can monitor many trees to keep the official kernel
at the tip of development.

What will happen if we do not try to? The official kernel will rapidly been seen as
"outdated" and people start to use the private kernels (which are good for experimenting
and testing issues) again. So it will prove that the official kernel is outdated, unless
we establish a flow of patches from private experiments to the "official" kernel.

And I think we definitively need one kernel that is robust, feature complete, mature
*and* permanently maintained. One that can be flashed into production devices to
give the best initial experience. And one different OS distros can rely on. This is
what the "official GTA04" kernel [1] is for.

Well, I can only repeat to invite people to submit (i.e. actively notify) patches against
the official GTA04 kernel (and not only make them in their private trees hoping that
someone sees them and then tries to merge).


BR,
Nikolaus

[1]: http://git.goldelico.com/?p=gta04-kernel.git;a=shortlog;h=refs/heads/master



More information about the Gta04-owner mailing list