From: Abel Vesa <abel.vesa@nxp.com>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>,
Angus Ainslie <angus.ainslie@puri.sm>,
Rob Herring <robh@kernel.org>
Cc: Abel Vesa <abel.vesa@nxp.com>, Anson Huang <anson.huang@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 0/3] Necessary i.MX8MQ clock updates in order to support cpufreq
Date: Fri, 15 Feb 2019 17:48:42 +0000 [thread overview]
Message-ID: <1550252913-24532-1-git-send-email-abel.vesa@nxp.com> (raw)
This is basically the v2 for the proposed clock changes in the
following RFC:
https://lkml.org/lkml/2019/2/13/1111
No changes here (other than adding the Reviewed-by tags).
Just a resent as a separate patchset.
Abel Vesa (3):
clk: imx: imx8mq: Fix the rate propagation for arm pll
dt-bindings: imx8mq-clock: Add the missing ARM clock
clk: imx8mq: Add the missing ARM clock
drivers/clk/imx/clk-imx8mq.c | 8 +++++++-
include/dt-bindings/clock/imx8mq-clock.h | 4 +++-
2 files changed, 10 insertions(+), 2 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-15 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 17:48 Abel Vesa [this message]
2019-02-15 17:48 ` [PATCH v2 1/3] clk: imx: imx8mq: Fix the rate propagation for arm pll Abel Vesa
2019-02-21 20:44 ` Stephen Boyd
2019-02-15 17:48 ` [PATCH v2 2/3] dt-bindings: imx8mq-clock: Add the missing ARM clock Abel Vesa
2019-02-21 20:40 ` Stephen Boyd
2019-02-15 17:48 ` [PATCH v2 3/3] clk: imx8mq: " Abel Vesa
2019-02-21 20:44 ` Stephen Boyd
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=1550252913-24532-1-git-send-email-abel.vesa@nxp.com \
--to=abel.vesa@nxp.com \
--cc=angus.ainslie@puri.sm \
--cc=anson.huang@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.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).