Tomasz, On Thu, May 16, 2013 at 3:56 PM, Tomasz Figa <tomasz.figa@xxxxxxxxx> wrote: > Seems like I need some sleep, as I'm already starting to overlook large > blobs of code. > > Originally, GPIO suspend/resume handlers have been configured in > drivers/gpio/gpio-samsung.c, by setting pm field of samsung_gpio_chip > struct to point to appropriate samsung_gpio_pm struct, which contains > pointers to save and resume callbacks. > > In result, samsung_gpio_pm_2bit_* or samsung_gpio_pm_4bit_* have been > used, depending on bank type, on all SoCs. > > Now since the documentation states that wake-up reset doesn't reset GPIO > registers (at least on S3C2440 and S3C2416), I wonder what is the correct > way of handling them. If state of these registers isn't lost on those SoCs then running the save/restore shouldn't _hurt_ though, right? If you can run the old GPIO code on one of those systems and do a suspend/resume you could check... -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |