From: pdeschrijver@nvidia.com (Peter De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: define and export __clk_get_debug for providers
Date: Wed, 25 Jun 2014 18:20:55 +0300 [thread overview]
Message-ID: <1403709655-6220-1-git-send-email-pdeschrijver@nvidia.com> (raw)
Define and export a new function __clk_get_debug which returns the debugfs
directory entry pointer. This can be used by clock providers to add debugfs
entries which are not related to a specific clock type. Examples include the
ability to measure the rate of a clock. It can also be used by modules to
create new debugfs entries. This is useful if you want to expose features
for testing which can potentially cause system instability such as allowing
to change a clock's rate from userspace.
Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
---
drivers/clk/clk.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 8b73ede..5fe7942 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -652,6 +652,15 @@ unsigned long __clk_get_flags(struct clk *clk)
}
EXPORT_SYMBOL_GPL(__clk_get_flags);
+struct dentry *__clk_get_dentry(struct clk *clk)
+{
+ if (!clk)
+ return NULL;
+
+ return clk->dentry;
+}
+EXPORT_SYMBOL_GPL(__clk_get_dentry);
+
bool __clk_is_prepared(struct clk *clk)
{
int ret;
--
1.7.7.rc0.72.g4b5ea.dirty
next reply other threads:[~2014-06-25 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 15:20 Peter De Schrijver [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-25 16:26 [PATCH] clk: define and export __clk_get_debug for providers Peter De Schrijver
2014-06-25 18:07 ` Arnd Bergmann
2014-06-25 18:23 ` Mike Turquette
2014-06-26 7:37 ` Tomeu Vizoso
2014-06-26 22:11 ` Mike Turquette
2014-06-26 10:32 ` Peter De Schrijver
2014-06-26 10:49 ` Peter De Schrijver
2014-06-26 13:22 Peter De Schrijver
2014-06-26 15:00 ` Peter De Schrijver
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=1403709655-6220-1-git-send-email-pdeschrijver@nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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