From: Leonard Crestez <leonard.crestez@nxp.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>,
Mark Brown <broonie@kernel.org>, Robin Gong <yibin.gong@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Irina Tirdea <irina.tirdea@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Octavian Purdila <octavian.purdila@nxp.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] ARM: imx: Set LDO regulator supply
Date: Wed, 19 Apr 2017 12:28:01 +0300 [thread overview]
Message-ID: <1492594081.15137.0.camel@nxp.com> (raw)
In-Reply-To: <cover.1491324640.git.leonard.crestez@nxp.com>
On Tue, 2017-04-04 at 20:04 +0300, Leonard Crestez wrote:
> Setting the LDO regulator parent is optional but beneficial. It will cause
> the PMIC output voltage to be dynamically set to the minimum input for the
> LDOs, this should be more efficient.
>
> This propagation was introduced by:
> commit fc42112c0eaa ("regulator: core: Propagate voltage changes to supply
> regulators")
>
> Changes since v1:
> * Drop patch 1 since it only avoids logging a warning and the gpc driver
> is going through more changes.
> * Initialize cpufreq->suspend_freq based on policy->max instead.
> * Remove reference to ldo-bypass from suspend_freq patch message.
Hello,
This is a gentle reminder that this was sent ~2 weeks ago and patches 1
and 2 are still waiting (with no objections). Patches 3/4 were applied.
--
Regards,
Leonard
WARNING: multiple messages have this Message-ID (diff)
From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: imx: Set LDO regulator supply
Date: Wed, 19 Apr 2017 12:28:01 +0300 [thread overview]
Message-ID: <1492594081.15137.0.camel@nxp.com> (raw)
In-Reply-To: <cover.1491324640.git.leonard.crestez@nxp.com>
On Tue, 2017-04-04 at 20:04 +0300, Leonard Crestez wrote:
> Setting the LDO regulator parent is optional but beneficial. It will cause
> the PMIC output voltage to be dynamically set to the minimum input for the
> LDOs, this should be more efficient.
>
> This propagation was introduced by:
> commit fc42112c0eaa ("regulator: core: Propagate voltage changes to supply
> regulators")
>
> Changes since v1:
> * Drop patch 1 since it only avoids logging a warning and the gpc driver
> is going through more changes.
> * Initialize cpufreq->suspend_freq based on policy->max instead.
> * Remove reference to ldo-bypass from suspend_freq patch message.
Hello,
This is a gentle reminder that this was sent ~2 weeks ago and patches 1
and 2 are still waiting (with no objections). Patches 3/4 were applied.
--
Regards,
Leonard
WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>,
Mark Brown <broonie@kernel.org>, Robin Gong <yibin.gong@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
"Irina Tirdea" <irina.tirdea@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Octavian Purdila <octavian.purdila@nxp.com>,
Liam Girdwood <lgirdwood@gmail.com>, <linux-pm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] ARM: imx: Set LDO regulator supply
Date: Wed, 19 Apr 2017 12:28:01 +0300 [thread overview]
Message-ID: <1492594081.15137.0.camel@nxp.com> (raw)
In-Reply-To: <cover.1491324640.git.leonard.crestez@nxp.com>
On Tue, 2017-04-04 at 20:04 +0300, Leonard Crestez wrote:
> Setting the LDO regulator parent is optional but beneficial. It will cause
> the PMIC output voltage to be dynamically set to the minimum input for the
> LDOs, this should be more efficient.
>
> This propagation was introduced by:
> commit fc42112c0eaa ("regulator: core: Propagate voltage changes to supply
> regulators")
>
> Changes since v1:
> * Drop patch 1 since it only avoids logging a warning and the gpc driver
> is going through more changes.
> * Initialize cpufreq->suspend_freq based on policy->max instead.
> * Remove reference to ldo-bypass from suspend_freq patch message.
Hello,
This is a gentle reminder that this was sent ~2 weeks ago and patches 1
and 2 are still waiting (with no objections). Patches 3/4 were applied.
--
Regards,
Leonard
next prev parent reply other threads:[~2017-04-19 9:28 UTC|newest]
Thread overview: 31+ 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 ` Leonard Crestez
2017-04-04 17:04 ` 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 ` Leonard Crestez
2017-04-04 17:04 ` 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-04 17:04 ` Leonard Crestez
2017-04-04 17:04 ` Leonard Crestez
2017-04-05 8:03 ` Lucas Stach
2017-04-05 8:03 ` Lucas Stach
2017-04-11 6:37 ` Viresh Kumar
2017-04-11 6:37 ` Viresh Kumar
2017-04-11 8:16 ` Leonard Crestez
2017-04-11 8:16 ` Leonard Crestez
2017-04-11 8:16 ` Leonard Crestez
2017-04-11 9:27 ` Viresh Kumar
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-04 17:04 ` Leonard Crestez
2017-04-04 17:04 ` Leonard Crestez
2017-04-07 12:20 ` Shawn Guo
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-04 17:04 ` Leonard Crestez
2017-04-04 17:04 ` Leonard Crestez
2017-04-07 12:21 ` Shawn Guo
2017-04-07 12:21 ` Shawn Guo
2017-04-19 9:28 ` Leonard Crestez [this message]
2017-04-19 9:28 ` [PATCH v2 0/4] ARM: imx: Set LDO " Leonard Crestez
2017-04-19 9:28 ` 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=1492594081.15137.0.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=irina.tirdea@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=octavian.purdila@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yibin.gong@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.