From: Peng Fan <peng.fan@nxp.com> To: "sboyd@kernel.org" <sboyd@kernel.org>, "shawnguo@kernel.org" <shawnguo@kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "festevam@gmail.com" <festevam@gmail.com>, Abel Vesa <abel.vesa@nxp.com>, Leonard Crestez <leonard.crestez@nxp.com> Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>, dl-linux-imx <linux-imx@nxp.com>, Aisheng Dong <aisheng.dong@nxp.com>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Anson Huang <anson.huang@nxp.com>, Jacky Bai <ping.bai@nxp.com>, "l.stach@pengutronix.de" <l.stach@pengutronix.de>, Peng Fan <peng.fan@nxp.com> Subject: [PATCH V2 0/4] clk: imx: imx8m: fix a53 cpu clock Date: Tue, 14 Jan 2020 07:27:10 +0000 [thread overview] Message-ID: <1578986576-6168-1-git-send-email-peng.fan@nxp.com> (raw) From: Peng Fan <peng.fan@nxp.com> V2: Fix i.MX8MP build Update cover letter, i.MX7D not have this issue The A53 CCM clk root only accepts input up to 1GHz, CCM A53 root signoff timing is 1Ghz, however the A53 core which sources from CCM root could run above 1GHz which voilates the CCM. There is a CORE_SEL slice before A53 core, we need configure the CORE_SEL slice source from ARM PLL, not A53 CCM clk root. The A53 CCM clk root should only be used when need to change ARM PLL frequency. Peng Fan (4): clk: imx: imx8mq: fix a53 cpu clock clk: imx: imx8mm: fix a53 cpu clock clk: imx: imx8mn: fix a53 cpu clock clk: imx: imx8mp: fix a53 cpu clock drivers/clk/imx/clk-imx8mm.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mn.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mp.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mq.c | 16 ++++++++++++---- include/dt-bindings/clock/imx8mm-clock.h | 4 +++- include/dt-bindings/clock/imx8mn-clock.h | 4 +++- include/dt-bindings/clock/imx8mp-clock.h | 3 ++- include/dt-bindings/clock/imx8mq-clock.h | 4 +++- 8 files changed, 59 insertions(+), 20 deletions(-) -- 2.16.4
WARNING: multiple messages have this Message-ID (diff)
From: Peng Fan <peng.fan@nxp.com> To: "sboyd@kernel.org" <sboyd@kernel.org>, "shawnguo@kernel.org" <shawnguo@kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "festevam@gmail.com" <festevam@gmail.com>, Abel Vesa <abel.vesa@nxp.com>, Leonard Crestez <leonard.crestez@nxp.com> Cc: Aisheng Dong <aisheng.dong@nxp.com>, Peng Fan <peng.fan@nxp.com>, Jacky Bai <ping.bai@nxp.com>, Anson Huang <anson.huang@nxp.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "l.stach@pengutronix.de" <l.stach@pengutronix.de> Subject: [PATCH V2 0/4] clk: imx: imx8m: fix a53 cpu clock Date: Tue, 14 Jan 2020 07:27:10 +0000 [thread overview] Message-ID: <1578986576-6168-1-git-send-email-peng.fan@nxp.com> (raw) From: Peng Fan <peng.fan@nxp.com> V2: Fix i.MX8MP build Update cover letter, i.MX7D not have this issue The A53 CCM clk root only accepts input up to 1GHz, CCM A53 root signoff timing is 1Ghz, however the A53 core which sources from CCM root could run above 1GHz which voilates the CCM. There is a CORE_SEL slice before A53 core, we need configure the CORE_SEL slice source from ARM PLL, not A53 CCM clk root. The A53 CCM clk root should only be used when need to change ARM PLL frequency. Peng Fan (4): clk: imx: imx8mq: fix a53 cpu clock clk: imx: imx8mm: fix a53 cpu clock clk: imx: imx8mn: fix a53 cpu clock clk: imx: imx8mp: fix a53 cpu clock drivers/clk/imx/clk-imx8mm.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mn.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mp.c | 16 ++++++++++++---- drivers/clk/imx/clk-imx8mq.c | 16 ++++++++++++---- include/dt-bindings/clock/imx8mm-clock.h | 4 +++- include/dt-bindings/clock/imx8mn-clock.h | 4 +++- include/dt-bindings/clock/imx8mp-clock.h | 3 ++- include/dt-bindings/clock/imx8mq-clock.h | 4 +++- 8 files changed, 59 insertions(+), 20 deletions(-) -- 2.16.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:[~2020-01-14 7:27 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-14 7:27 Peng Fan [this message] 2020-01-14 7:27 ` [PATCH V2 0/4] clk: imx: imx8m: fix a53 cpu clock Peng Fan 2020-01-14 7:27 ` [PATCH V2 1/4] clk: imx: imx8mq: " Peng Fan 2020-01-14 7:27 ` Peng Fan 2020-02-12 13:43 ` Shawn Guo 2020-02-12 13:43 ` Shawn Guo 2020-02-12 13:47 ` Peng Fan 2020-02-12 13:47 ` Peng Fan 2020-01-14 7:27 ` [PATCH V2 2/4] clk: imx: imx8mm: " Peng Fan 2020-01-14 7:27 ` Peng Fan 2020-01-14 7:27 ` [PATCH V2 3/4] clk: imx: imx8mn: " Peng Fan 2020-01-14 7:27 ` Peng Fan 2020-01-14 7:27 ` [PATCH V2 4/4] clk: imx: imx8mp: " Peng Fan 2020-01-14 7:27 ` Peng Fan
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=1578986576-6168-1-git-send-email-peng.fan@nxp.com \ --to=peng.fan@nxp.com \ --cc=abel.vesa@nxp.com \ --cc=aisheng.dong@nxp.com \ --cc=anson.huang@nxp.com \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=l.stach@pengutronix.de \ --cc=leonard.crestez@nxp.com \ --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=ping.bai@nxp.com \ --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: linkBe 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.