From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clk: Document .is_enabled op
Date: Wed, 3 Oct 2012 23:38:53 -0700 [thread overview]
Message-ID: <1349332735-20096-2-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1349332735-20096-1-git-send-email-sboyd@codeaurora.org>
Add the missing kernel-doc for this op.
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
include/linux/clk-provider.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
index 710c6cb..5a548e3 100644
--- a/include/linux/clk-provider.h
+++ b/include/linux/clk-provider.h
@@ -53,6 +53,10 @@ struct clk_hw;
* @disable: Disable the clock atomically. Called with enable_lock held.
* This function must not sleep.
*
+ * @is_enabled: Queries the hardware to determine if the clock is enabled.
+ * This function must not sleep. Optional, if this op is not
+ * set then the enable count will be used.
+ *
* @recalc_rate Recalculate the rate of this clock, by quering hardware. The
* parent rate is an input parameter. It is up to the caller to
* insure that the prepare_mutex is held across this call.
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-10-04 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 6:38 [PATCH 0/3] Minor fixes for generic clock framework Stephen Boyd
2012-10-04 6:38 ` Stephen Boyd [this message]
2012-10-04 6:38 ` [PATCH 2/3] clk: Fix documentation typos Stephen Boyd
2012-10-04 6:38 ` [PATCH 3/3] clk: Don't return negative numbers for unsigned values with !clk Stephen Boyd
2012-10-29 18:12 ` [PATCH 0/3] Minor fixes for generic clock framework Stephen Boyd
2012-10-29 18:16 ` Mike Turquette
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=1349332735-20096-2-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).