From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] cpufreq: imx6q: Set max suspend_freq to avoid changes during suspend
Date: Tue, 11 Apr 2017 11:16:23 +0300 [thread overview]
Message-ID: <1491898583.26722.2.camel@nxp.com> (raw)
In-Reply-To: <20170411063738.GE3670@vireshk-i7>
On Tue, 2017-04-11 at 12:07 +0530, Viresh Kumar wrote:
> On 04-04-17, 20:04, Leonard Crestez wrote:
> > If the cpufreq driver tries to modify voltage/freq during suspend/resume
> > it might need to control an external PMIC via I2C or SPI but those
> > devices might be already suspended. This issue is likely to happen
> > whenever the LDOs have their vin-supply set.
> >
> > To avoid this scenario we just increase cpufreq to the maximum before
> > suspend.
> >
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > ---
> > drivers/cpufreq/imx6q-cpufreq.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> I have already Acked this earlier, why didn't you add it ?
Because v2 is different based on comments from Lucas. It didn't seem
appropriate to keep an old "Acked-by" in this case.
next prev parent reply other threads:[~2017-04-11 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:04 [PATCH v2 0/4] ARM: imx: Set LDO regulator supply Leonard Crestez
2017-04-04 17:04 ` [PATCH v2 1/4] cpufreq: imx6q: Fix handling EPROBE_DEFER from regulator Leonard Crestez
2017-04-04 17:04 ` [PATCH v2 2/4] cpufreq: imx6q: Set max suspend_freq to avoid changes during suspend Leonard Crestez
2017-04-05 8:03 ` Lucas Stach
2017-04-11 6:37 ` Viresh Kumar
2017-04-11 8:16 ` Leonard Crestez [this message]
2017-04-11 9:27 ` Viresh Kumar
2017-04-04 17:04 ` [PATCH v2 3/4] ARM: dts: imx6qdl-sabresd: Set LDO regulator supply Leonard Crestez
2017-04-07 12:20 ` Shawn Guo
2017-04-04 17:04 ` [PATCH v2 4/4] ARM: dts: imx6qp-sabresd: Set reg_arm " Leonard Crestez
2017-04-07 12:21 ` Shawn Guo
2017-04-19 9:28 ` [PATCH v2 0/4] ARM: imx: Set LDO " Leonard Crestez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1491898583.26722.2.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).