linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/11] clk: Prototype and document clk_register()
Date: Wed, 24 Aug 2011 14:15:53 +0100	[thread overview]
Message-ID: <1314191759-16941-5-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1314191759-16941-1-git-send-email-broonie@opensource.wolfsonmicro.com>

This allows the compiler to ensure drivers are using the correct prototype.

Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
---
 include/linux/clk.h |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/include/linux/clk.h b/include/linux/clk.h
index 7c26135..2ca4f66 100644
--- a/include/linux/clk.h
+++ b/include/linux/clk.h
@@ -136,6 +136,18 @@ extern struct clk_hw_ops clk_gate_ops;
 
 #endif /* CONFIG_GENERIC_CLK_GATE */
 
+/**
+ * clk_register - register and initialize a new clock
+ *
+ * @ops: ops for the new clock
+ * @hw: struct clk_hw to be passed to the ops of the new clock
+ * @name: name to use for the new clock
+ *
+ * Register a new clock with the clk subsytem.  Returns either a
+ * struct clk for the new clock or a NULL pointer.
+ */
+struct clk *clk_register(struct clk_hw_ops *ops, struct clk_hw *hw,
+			 const char *name);
 
 #else /* !CONFIG_GENERIC_CLK */
 
-- 
1.7.5.4

  parent reply	other threads:[~2011-08-24 13:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 13:13 [PATCH 0/11] generic struct clk patches Mark Brown
2011-08-24 13:15 ` [PATCH 01/11] clk: Add a generic clock infrastructure Mark Brown
2011-08-24 13:15   ` [PATCH 02/11] clk: Implement clk_set_rate Mark Brown
2011-08-26  8:53     ` Sascha Hauer
2011-08-26  8:55       ` Mark Brown
2011-08-26  8:58         ` Sascha Hauer
2011-08-26  9:01           ` Mark Brown
2011-08-26 23:45     ` Turquette, Mike
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` [PATCH 03/11] clk: Add fixed-rate clock Mark Brown
2011-08-24 13:15   ` [PATCH 04/11] clk: Add simple gated clock Mark Brown
2011-08-25 13:17     ` Jamie Iles
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` Mark Brown [this message]
2011-09-13 19:03     ` [PATCH 05/11] clk: Prototype and document clk_register() Stephen Boyd
2011-08-24 13:15   ` [PATCH 06/11] clk: Provide a dummy clk_unregister() Mark Brown
2011-08-25 11:12     ` Jamie Iles
2011-08-24 13:15   ` [PATCH 07/11] clk: Constify struct clk_hw_ops Mark Brown
2011-08-24 13:15   ` [PATCH 08/11] clk: Avoid clock name collisions Mark Brown
2011-09-13 19:03     ` Stephen Boyd
2011-08-24 13:15   ` [PATCH 09/11] clk: Add Kconfig option to build all generic clk drivers Mark Brown
2011-08-24 13:15   ` [PATCH 10/11] clk: Add initial WM831x clock driver Mark Brown
2011-08-24 13:15   ` [PATCH 11/11] x86: Enable generic clk API on x86 Mark Brown
2011-09-13 19:03   ` [PATCH 01/11] clk: Add a generic clock infrastructure Stephen Boyd
     [not found]   ` <1314191759-16941-1-git-send-email-broonie@opensource.wolfsonmicro.com >
2011-09-14  2:22     ` Saravana Kannan
2011-09-14  9:41       ` Mark Brown

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=1314191759-16941-5-git-send-email-broonie@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).