Dear Thierry-san, Thank for your feedback!
This has been discussed before, but this really shouldn't be done in the PWM driver. Consumers should really be reconfiguring the PWM upon resume as appropriate. This is the only way to ensure that everything is resumed in the proper order. Most, if not all, consumers already implement suspend/resume that way. sysfs is the only one that I'm aware of that doesn't. Since you've been using sysfs to test this, things are slightly more complicated (i.e. we don't have a consumer driver in the conventional way). However, you should be able to solve this by implementing dev_pm_ops for the pwm_class. Do you think you could give that a try?
I understood the problem. Really this is difficult with me. Therefore, I will just stop here. Thank you, Dong
Thierry
