From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>
Subject: [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw
Date: Wed, 21 Oct 2020 18:21:44 +0200 [thread overview]
Message-ID: <20201021162147.563655-1-jbrunet@baylibre.com> (raw)
This patchset a call in CCF to get "struct clk*" from "struct clk_hw*"
Changes since v1: [0]
* Add a con_id string to help keep track of the consumer
* Add devm variant:
- Following our discussion on V1, I choose to have the dev as
argument as most devm function do. However, as Stephen pointed out
we don't expect this to differ from the one linked to clk_hw. In
this case a warning is thrown.
* Add a first usage of this in the amlogic clock driver.
[0]: https://lore.kernel.org/r/20200519170440.294601-1-jbrunet@baylibre.com
Jerome Brunet (3):
clk: avoid devm_clk_release name clash
clk: add api to get clk consumer from clk_hw
clk: meson: g12: drop use of __clk_lookup()
drivers/clk/clk.c | 73 +++++++++++++++++++++++++++++++++---
drivers/clk/meson/g12a.c | 68 ++++++++++++++++-----------------
include/linux/clk-provider.h | 5 +++
3 files changed, 104 insertions(+), 42 deletions(-)
--
2.25.4
next reply other threads:[~2020-10-21 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 16:21 Jerome Brunet [this message]
2020-10-21 16:21 ` [PATCH v2 1/3] clk: avoid devm_clk_release name clash Jerome Brunet
2020-11-14 20:54 ` Stephen Boyd
2020-10-21 16:21 ` [PATCH v2 2/3] clk: add api to get clk consumer from clk_hw Jerome Brunet
2020-11-14 20:54 ` Stephen Boyd
2020-10-21 16:21 ` [PATCH v2 3/3] clk: meson: g12: drop use of __clk_lookup() Jerome Brunet
2020-11-14 20:54 ` Stephen Boyd
2020-10-26 16:11 ` [PATCH v2 0/3] clk: add api to get clk consumer from clk_hw Kevin Hilman
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=20201021162147.563655-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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