Hi, just realized that I need these patches patches as well: https://github.com/dgerlach/linux-pm/commits/pm-v4.1-rc4-amx3-suspend I tried to merge that branch into current v4.2-rc2, but I made quite a mess out of it. I'll try probably try cherry-picking next or will just wait for an update so ignore my previous mail, :-) 2015-07-15 11:23 GMT+02:00 Andreas Fenkart <afenkart@xxxxxxxxx>: > cat /sys/power/state is empty, should be 'mem' > > I applied these patches: > https://lkml.org/lkml/2015/4/1/542 > > here suspend support in kernel-config (shall I append the full .config?) > # > # Power management options > # > CONFIG_SUSPEND=y > CONFIG_SUSPEND_FREEZER=y > # CONFIG_HIBERNATION is not set > CONFIG_PM_SLEEP=y > # CONFIG_PM_AUTOSLEEP is not set > # CONFIG_PM_WAKELOCKS is not set > CONFIG_PM=y > CONFIG_PM_DEBUG=y > # CONFIG_PM_ADVANCED_DEBUG is not set > # CONFIG_PM_TEST_SUSPEND is not set > CONFIG_PM_SLEEP_DEBUG=y > # CONFIG_APM_EMULATION is not set > CONFIG_PM_OPP=y > CONFIG_PM_CLK=y > # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set > CONFIG_CPU_PM=y > CONFIG_ARCH_SUSPEND_POSSIBLE=y > CONFIG_ARM_CPU_SUSPEND=y > CONFIG_ARCH_HIBERNATION_POSSIBLE=y > CONFIG_NET=y > > > [ 1.642524] remoteproc0: wkup_m3 is available > [ 1.647570] remoteproc0: Note: remoteproc is still under > development and considered experimental. > [ 1.657068] remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, > and backward compatibility isn't yet guaranteed. > [ 1.668418] remoteproc0: unsupported resource 4 > [ 1.673275] remoteproc0: unsupported resource 4 > [ 1.685122] usbcore: registered new interface driver snd-usb-audio > [ 1.691835] remoteproc0: unsupported resource 4 > [ 1.696777] remoteproc0: unsupported resource 4 > > tip of m3 firmware > git://arago-project.org/git/projects/am33x-cm3.git > Sun Mar 9 23:52:27 2014 -0700 32cf44e CM3: AM43XX: Add Tamper swakeup settings > > Do I need to update my m3 firmware? > > kind regards, > Andreas Fenkart -- 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
