From: Leonard Crestez <leonard.crestez@nxp.com>
To: Jacky Bai <ping.bai@nxp.com>, Abel Vesa <abel.vesa@nxp.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Cc: Anson Huang <Anson.Huang@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-clk@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] clk: imx8m: Fix incorrect parents
Date: Tue, 13 Aug 2019 20:05:27 +0300 [thread overview]
Message-ID: <cover.1565715590.git.leonard.crestez@nxp.com> (raw)
No checks are made to ensure the parents in the _sels arrays actually
exist and it turns out that several are incorrect.
I found the errors using a hack to clk core, is there a better way?
Link: https://github.com/cdleonard/linux/commit/da32c2e76eb373e8a03aec905af2eef28a7997a7
Also add imx8mn GIC clock while we're at it because otherwise parent
could get disabled and lock the system.
Leonard Crestez (4):
clk: imx8mq: Fix sys3 pll references
clk: imx8mm: Fix incorrect parents
clk: imx8mn: Fix incorrect parents
clk: imx8mn: Add GIC clock
drivers/clk/imx/clk-imx8mm.c | 8 +-
drivers/clk/imx/clk-imx8mn.c | 19 ++--
drivers/clk/imx/clk-imx8mq.c | 112 +++++++++++------------
include/dt-bindings/clock/imx8mn-clock.h | 3 +-
4 files changed, 74 insertions(+), 68 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Jacky Bai <ping.bai@nxp.com>, Abel Vesa <abel.vesa@nxp.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] clk: imx8m: Fix incorrect parents
Date: Tue, 13 Aug 2019 20:05:27 +0300 [thread overview]
Message-ID: <cover.1565715590.git.leonard.crestez@nxp.com> (raw)
No checks are made to ensure the parents in the _sels arrays actually
exist and it turns out that several are incorrect.
I found the errors using a hack to clk core, is there a better way?
Link: https://github.com/cdleonard/linux/commit/da32c2e76eb373e8a03aec905af2eef28a7997a7
Also add imx8mn GIC clock while we're at it because otherwise parent
could get disabled and lock the system.
Leonard Crestez (4):
clk: imx8mq: Fix sys3 pll references
clk: imx8mm: Fix incorrect parents
clk: imx8mn: Fix incorrect parents
clk: imx8mn: Add GIC clock
drivers/clk/imx/clk-imx8mm.c | 8 +-
drivers/clk/imx/clk-imx8mn.c | 19 ++--
drivers/clk/imx/clk-imx8mq.c | 112 +++++++++++------------
include/dt-bindings/clock/imx8mn-clock.h | 3 +-
4 files changed, 74 insertions(+), 68 deletions(-)
--
2.17.1
_______________________________________________
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-08-13 17:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 17:05 Leonard Crestez [this message]
2019-08-13 17:05 ` [PATCH 0/4] clk: imx8m: Fix incorrect parents Leonard Crestez
2019-08-13 17:05 ` [PATCH 1/4] clk: imx8mq: Fix sys3 pll references Leonard Crestez
2019-08-13 17:05 ` Leonard Crestez
2019-08-13 17:05 ` [PATCH 2/4] clk: imx8mm: Fix incorrect parents Leonard Crestez
2019-08-13 17:05 ` Leonard Crestez
2019-08-13 17:05 ` [PATCH 3/4] clk: imx8mn: " Leonard Crestez
2019-08-13 17:05 ` Leonard Crestez
2019-08-13 17:05 ` [PATCH 4/4] clk: imx8mn: Add GIC clock Leonard Crestez
2019-08-13 17:05 ` Leonard Crestez
2019-08-15 19:36 ` [PATCH 0/4] clk: imx8m: Fix incorrect parents Stephen Boyd
2019-08-15 19:36 ` Stephen Boyd
2019-08-19 11:55 ` Shawn Guo
2019-08-19 11:55 ` 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=cover.1565715590.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--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 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.