From: Jerome Brunet <jbrunet@baylibre.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-clk@vger.kernel.org
Subject: [PATCH RFC 0/5] clk: let clock claim resources
Date: Wed, 28 Aug 2019 12:20:07 +0200 [thread overview]
Message-ID: <20190828102012.4493-1-jbrunet@baylibre.com> (raw)
This patchset is a follow up on this pinky swear [0].
Its purpose is:
* Clarify the acceptable use of clk_ops init() callback
* Let the init() callback return an error code in case anything
fail.
* Add the terminate() counter part of of init() to release the
resources which may have been claimed in init()
* Add a per-clock placeholder for clock runtime data in the clock
core. This may be useful to init() and save/restore_context()
It was initially suggested to rename these callbacks register/deregister().
But, 'register' is reserved word of C ... :P
In the end, after discussing with Mike, I decided to keep the name "init".
It does not feel that important to change this. I really don't mind
changing this if you feel differently and have a suggestion.
The last patch in this series is just an example of how the above can be
used.
This is sent as an RFC to get the discussion going without bothering too
many people.
In the final series, Patch 2 and 3 will probably be squashed and series
sent to a wider audience.
[0]: https://lkml.kernel.org/r/CAEG3pNB-143Pr_xCTPj=tURhpiTiJqi61xfDGDVdU7zG5H-2tA@mail.gmail.com
Jerome Brunet (5):
clk: actually call the clock init before any other callback of the
clock
clk: let init callback return an error code
clk: add terminate callback to clk_ops
clk: add placeholder for clock internal data
clk: meson: sclk-div: use runtime data
drivers/clk/clk.c | 51 ++++++++++++++-----
drivers/clk/meson/clk-mpll.c | 4 +-
drivers/clk/meson/clk-phase.c | 4 +-
drivers/clk/meson/clk-pll.c | 4 +-
drivers/clk/meson/sclk-div.c | 72 +++++++++++++++++++--------
drivers/clk/meson/sclk-div.h | 2 -
drivers/clk/microchip/clk-core.c | 8 ++-
drivers/clk/mmp/clk-frac.c | 4 +-
drivers/clk/mmp/clk-mix.c | 4 +-
drivers/clk/qcom/clk-hfpll.c | 6 ++-
drivers/clk/rockchip/clk-pll.c | 28 +++++++----
drivers/clk/ti/clock.h | 2 +-
drivers/clk/ti/clockdomain.c | 8 +--
drivers/net/phy/mdio-mux-meson-g12a.c | 4 +-
include/linux/clk-provider.h | 15 ++++--
15 files changed, 154 insertions(+), 62 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-28 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 10:20 Jerome Brunet [this message]
2019-08-28 10:20 ` [PATCH RFC 1/5] clk: actually call the clock init before any other callback of the clock Jerome Brunet
2019-08-28 10:20 ` [PATCH RFC 2/5] clk: let init callback return an error code Jerome Brunet
2019-08-28 10:20 ` [PATCH RFC 3/5] clk: add terminate callback to clk_ops Jerome Brunet
2019-08-28 10:20 ` [PATCH RFC 4/5] clk: add placeholder for clock internal data Jerome Brunet
2019-08-28 22:15 ` Stephen Boyd
2019-08-29 7:20 ` Jerome Brunet
2019-08-29 17:17 ` Stephen Boyd
2019-08-30 14:06 ` Jerome Brunet
2019-09-04 22:52 ` Stephen Boyd
2019-08-28 10:20 ` [PATCH RFC 5/5] clk: meson: sclk-div: use runtime data Jerome Brunet
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=20190828102012.4493-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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).