Re: [PATCH] PM / devfreq: Do not change the frequency of a suspended device

[Arun Iyengar]

Please don't apply this version. The Sashiko review found bugs in it:

- A limit change on a suspended passive device stores 0 in
  pending_freq, so devfreq_resume_device() can then fail with -EINVAL.
- After a deferred update, resume asks the governor instead of
  restoring resume_freq, so a userspace governor without set_freq
  stays at the suspend OPP.
- Two error paths leave the device marked suspended or skip
  DEVFREQ_GOV_RESUME.
- The passive question in the cover: exynos-bus children need to
  follow their parent to its suspend OPP, also at shutdown.

v2 will fix these.

Arun