From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: dts: imx6ull: add operating points
Date: Tue, 3 Jul 2018 14:34:38 +0800 [thread overview]
Message-ID: <20180703063436.GI4348@dragon> (raw)
In-Reply-To: <20180702045205.fdh4dwwhwyfftptl@vireshk-i7>
On Mon, Jul 02, 2018 at 10:22:05AM +0530, Viresh Kumar wrote:
> On 29-06-18, 16:52, S?bastien Szymanski wrote:
> > i.MX6ULL has different operating ranges than i.MX6UL so add the
> > operating points for the i.MX6ULL and removed them form board device
>
> s/removed/remove/
> s/form/from/
I fixed them up and applied the patch.
Shawn
>
> > trees. A 25mV offset is added to the minimum allowed values like for the
> > i.MX6UL.
> > The valid frequencies are now selected by the cpufreq driver according
> > to ratings stored in fuses since commit 0aa9abd4c212 ("cpufreq: imx6q:
> > check speed grades for i.MX6ULL")
> >
> > Signed-off-by: S?bastien Szymanski <sebastien.szymanski@armadeus.com>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
linux-arm-kernel@lists.infradead.org,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/1] ARM: dts: imx6ull: add operating points
Date: Tue, 3 Jul 2018 14:34:38 +0800 [thread overview]
Message-ID: <20180703063436.GI4348@dragon> (raw)
In-Reply-To: <20180702045205.fdh4dwwhwyfftptl@vireshk-i7>
On Mon, Jul 02, 2018 at 10:22:05AM +0530, Viresh Kumar wrote:
> On 29-06-18, 16:52, Sébastien Szymanski wrote:
> > i.MX6ULL has different operating ranges than i.MX6UL so add the
> > operating points for the i.MX6ULL and removed them form board device
>
> s/removed/remove/
> s/form/from/
I fixed them up and applied the patch.
Shawn
>
> > trees. A 25mV offset is added to the minimum allowed values like for the
> > i.MX6UL.
> > The valid frequencies are now selected by the cpufreq driver according
> > to ratings stored in fuses since commit 0aa9abd4c212 ("cpufreq: imx6q:
> > check speed grades for i.MX6ULL")
> >
> > Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
next prev parent reply other threads:[~2018-07-03 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 14:52 [PATCH 1/1] ARM: dts: imx6ull: add operating points Sébastien Szymanski
2018-06-29 14:52 ` Sébastien Szymanski
2018-07-02 4:52 ` Viresh Kumar
2018-07-02 4:52 ` Viresh Kumar
2018-07-03 6:34 ` Shawn Guo [this message]
2018-07-03 6:34 ` Shawn Guo
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=20180703063436.GI4348@dragon \
--to=shawnguo@kernel.org \
--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 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.