On 30 September 2012 15:48, Tanya Brokhman <tlinder@xxxxxxxxxxxxxx> wrote: > Hi Ulf, > >> >> Hi Tanya, >> >> Thanks a lot for helping out!!! > > NP. >> >> Testing suspend to ram, and then resuming back again is the key use case > to >> test. > > > Is there a special scenario to trigger suspend or just leaving the system > idle? I did that. Added prints in the code to verify that the PON was sent > to the card.... It feels a bit superficial to me that's why I'm asking if > there is a specific scenario I can try. > Other than that, as I already mentioned we ran our test suit that includes > various user-use cases such as playing a game, reading a web page, email > etc. And of course I tried lmdd both ways. from command prompt you can suspend by forcing the string mem to state variable as given below echo mem > sys/power/state If sysfs is not mounted mount it(mount -t sysfs sys /sys) before running the above command. If your board is configured for an external interrupt as a wakeup source (on my board it is the keypad) press the key for resume. If no External interrupt wakeup source is availabe, and if the SOc has a RTC, it can be used for resume purpose as below echo 0 > /sys/class/rtc/rtcN/wakealarm (reset old value) echo 10 > /sys/class/rtc/rtcN/wakealarm (set new value) After the specified above seconds the system will resume > >> >> Kind regards >> Ulf Hansson >> > > > Thanks, > Tanya Brokhman > --- > QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member > of Code Aurora Forum, hosted by The Linux Foundation > > -- 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
