From: Lubomir Rintel <lkundrak@v3.sk>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] MMP2 CLK Update
Date: Wed, 19 Feb 2020 08:33:43 +0100 [thread overview]
Message-ID: <20200219073353.184336-1-lkundrak@v3.sk> (raw)
Hi,
please consider applying this patch series. Its goal is to ultimately
provide accurate clock sources from PLLs configured by firmware on MMP2 and
MMP3. Currently they are hardcoded to more or less wrong values, which
causes bad timings when they are use (e.g. to generate display clock).
It starts off with a handful of cleanups:
[PATCH 01/10] clk: mmp2: Remove a unused prototype
[PATCH 02/10] clk: mmp2: Constify some strings
[PATCH 03/10] dt-bindings: clock: Convert marvell,mmp2-clock to
The next patch adds the logic for calculating the rate of clock signals
coming from the PLLs dynamically, while not actually switching the
driver over to using it.
[PATCH 04/10] clk: mmp2: Add support for PLL clock sources
Then MMP2 is switched over:
[PATCH 05/10] clk: mmp2: Stop pretending PLL outputs are constant
Switching MMP3 requires some more work, because until now, the driver
has been the same for both versions of the SoC:
[PATCH 06/10] dt-bindings: clock: Add MMP3 compatible string
[PATCH 07/10] clk: mmp2: Check for MMP3
[PATCH 08/10] dt-bindings: marvell,mmp2: Add clock ids for MMP3 PLLs
[PATCH 09/10] clk: mmp2: Add PLLs that are available on MMP3
[PATCH 10/10] ARM: dts: mmp3: Use the MMP3 compatible string for
The hardware vendor doesn't supply documentation, so this is best-effort
work based on the code dump from Marvell.
Tested on MMP2 and MMP3 based hardware I have; details in relevant
commit messages.
Thank you,
Lubo
next reply other threads:[~2020-02-19 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 7:33 Lubomir Rintel [this message]
2020-02-19 7:33 ` [PATCH 01/10] clk: mmp2: Remove a unused prototype Lubomir Rintel
2020-02-19 7:33 ` [PATCH 02/10] clk: mmp2: Constify some strings Lubomir Rintel
2020-02-19 7:33 ` [PATCH 03/10] dt-bindings: clock: Convert marvell,mmp2-clock to json-schema Lubomir Rintel
2020-02-26 15:28 ` Rob Herring
2020-02-19 7:33 ` [PATCH 04/10] clk: mmp2: Add support for PLL clock sources Lubomir Rintel
2020-02-19 7:33 ` [PATCH 05/10] clk: mmp2: Stop pretending PLL outputs are constant Lubomir Rintel
2020-02-19 7:33 ` [PATCH 06/10] dt-bindings: clock: Add MMP3 compatible string Lubomir Rintel
2020-02-26 15:28 ` Rob Herring
2020-02-19 7:33 ` [PATCH 07/10] clk: mmp2: Check for MMP3 Lubomir Rintel
2020-02-19 7:33 ` [PATCH 08/10] dt-bindings: marvell,mmp2: Add clock ids for MMP3 PLLs Lubomir Rintel
2020-02-26 15:29 ` Rob Herring
2020-02-19 7:33 ` [PATCH 09/10] clk: mmp2: Add PLLs that are available on MMP3 Lubomir Rintel
2020-02-19 7:33 ` [PATCH 10/10] ARM: dts: mmp3: Use the MMP3 compatible string for /clocks Lubomir Rintel
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=20200219073353.184336-1-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).