From: Abel Vesa <abel.vesa@nxp.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: sboyd@kernel.org, robh+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 0/3] clk: imx8m: remote sys pll1/2 clk gates
Date: Mon, 28 Feb 2022 14:23:34 +0200 [thread overview]
Message-ID: <Yhy+xjPXoCeZ8AhI@abelvesa> (raw)
In-Reply-To: <20220225081733.2294166-1-peng.fan@oss.nxp.com>
On 22-02-25 16:17:30, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Same to commit c586f53ae159c6c("clk: imx8mq: remove SYS PLL 1/2 clock gates"),
> This patchset is to remove the pll gate, but still keep the pll out gate
> following NXP vendor tree.
>
For the entire patchset:
Reviewed-by: Abel Vesa <abel.vesa@nxp.com>
> Peng Fan (3):
> clk: imx8mm: remove SYS PLL 1/2 clock gates
> clk: imx8mn: remove SYS PLL 1/2 clock gates
> clk: imx8mp: remove SYS PLL 1/2 clock gates
>
> drivers/clk/imx/clk-imx8mm.c | 49 ++++++++++++-----------------------
> drivers/clk/imx/clk-imx8mn.c | 50 ++++++++++++------------------------
> drivers/clk/imx/clk-imx8mp.c | 48 ++++++++++++----------------------
> 3 files changed, 48 insertions(+), 99 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-02-28 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 8:17 [PATCH 0/3] clk: imx8m: remote sys pll1/2 clk gates Peng Fan (OSS)
2022-02-25 8:17 ` [PATCH 1/3] clk: imx8mm: remove SYS PLL 1/2 clock gates Peng Fan (OSS)
2022-02-25 8:17 ` [PATCH 2/3] clk: imx8mn: " Peng Fan (OSS)
2022-02-25 8:17 ` [PATCH 3/3] clk: imx8mp: " Peng Fan (OSS)
2022-02-25 14:35 ` Abel Vesa
2022-02-28 0:39 ` Peng Fan
2022-02-28 12:23 ` Abel Vesa
2022-02-28 12:23 ` Abel Vesa [this message]
2022-03-04 8:50 ` [PATCH 0/3] clk: imx8m: remote sys pll1/2 clk gates Abel Vesa
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=Yhy+xjPXoCeZ8AhI@abelvesa \
--to=abel.vesa@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@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=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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