From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Allocate and add clock lookups from clk_register()
Date: Fri, 13 Apr 2012 12:01:33 +0200 [thread overview]
Message-ID: <20120413100133.GI3852@pengutronix.de> (raw)
In-Reply-To: <9fa570d09d94cdc4892b4e413ef3a0edc6f9dcef.1334298848.git.viresh.kumar@st.com>
On Fri, Apr 13, 2012 at 12:04:57PM +0530, Viresh Kumar wrote:
> clock lookups are required for few clocks for which we do clk_get() or
> clk_get_sys(). Adding clock lookups for them with new clock framework, would
> mean a lot of code for each platform. Simplify this by doing this allocation and
> addition to global list in clk_register() only.
>
> This is done on request by the caller, i.e. only if user passes valid pointers
> in "dev_id" OR "con_id" fields.
>
> A lot of changes at other places/files/comments are also required, that i would
> do separately. This is the initial version to get initial feedback.
>
> Pointer to original discussion:
> http://www.spinics.net/lists/arm-kernel/msg169133.html
For reasons mentioned in this thread (long argument list, line wraps in
clk_register calls, only leaf nodes need lookups) I don't think this is
a good idea.
> */
> struct clk *clk_register(struct device *dev, const char *name,
> const struct clk_ops *ops, struct clk_hw *hw,
> - const char **parent_names, u8 num_parents, unsigned long flags)
> + const char **parent_names, u8 num_parents, unsigned long flags,
> + struct clk_lookup **cl, const char *dev_id, const char *con_id)
> {
Also this doesn't handle the case when multiple lookups are associated
with a single clock (which is quite a common case on some SoCs). Yes,
we could still use the returned clk to register the additional lookups,
but that would make the advantage of this patch even smaller.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-04-13 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 6:34 [PATCH] clk: Allocate and add clock lookups from clk_register() Viresh Kumar
2012-04-13 8:56 ` Richard Zhao
2012-04-13 9:25 ` Viresh Kumar
2012-04-13 10:01 ` Sascha Hauer [this message]
2012-04-13 10:10 ` Viresh Kumar
2012-04-13 10:30 ` Russell King - ARM Linux
2012-04-13 11:16 ` Domenico Andreoli
2012-04-16 3:48 ` Viresh Kumar
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=20120413100133.GI3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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