From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-clk@vger.kernel.org
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Michael Grzeschik" <m.grzeschik@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Aisheng Dong" <aisheng.dong@nxp.com>
Subject: [PATCH v2 0/2] clk: imx5: Fix i.MX50 clock registers
Date: Tue, 26 Mar 2019 19:22:56 +0100 [thread overview]
Message-ID: <20190326182258.21945-1-j.neuschaefer@gmx.net> (raw)
There are a few differences between the i.MX50 clock tree and those of
i.MX51 and i.MX53 that are not yet handled in clk-imx51-imx53.c. This
series handles two of them.
Jonathan Neuschäfer (2):
clk: imx5: Fix i.MX50 mainbus clock registers
clk: imx5: Fix i.MX50 ESDHC clock registers
v2:
- Split into two patches, as suggested by Aisheng Dong
v1:
https://lore.kernel.org/lkml/20190318231737.8459-1-j.neuschaefer@gmx.net/
drivers/clk/imx/clk-imx51-imx53.c | 59 +++++++++++++++++++++++--------
1 file changed, 45 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-26 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 18:22 Jonathan Neuschäfer [this message]
2019-03-26 18:22 ` [PATCH v2 1/2] clk: imx5: Fix i.MX50 mainbus clock registers Jonathan Neuschäfer
2019-03-26 18:22 ` [PATCH v2 2/2] clk: imx5: Fix i.MX50 ESDHC " Jonathan Neuschäfer
2019-04-03 9:14 ` [PATCH v2 0/2] clk: imx5: Fix i.MX50 " 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=20190326182258.21945-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.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=m.grzeschik@pengutronix.de \
--cc=mturquette@baylibre.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: 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).