From: mturquette@ti.com (Turquette, Mike)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] HACK: omap: convert 44xx data to common struct clk
Date: Tue, 13 Dec 2011 20:44:53 -0800 [thread overview]
Message-ID: <CAJOA=zM8hP=1BxcpDu-XMvt0KefRPwhP3m-+yC7Uta+Aozz8Xw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112132125200.12046@utopia.booyaka.com>
On Tue, Dec 13, 2011 at 8:27 PM, Paul Walmsley <paul@pwsan.com> wrote:
> Hi
>
> On Tue, 13 Dec 2011, Mike Turquette wrote:
>
>> omap_clk_get_by_name must die.
>
> You do realize that it exists for a reason? ?That hardware clock names
> don't have anything to do with the Linux device model?
We have a tree structure of clks in the new common clk code, and a
list of clks in clkdev (which admittedly is meant to be a subset, but
in reality we register every OMAP clk with it), and then the omap clk
list which is only really used by omap_get_clk_by_name for hwmod and
some initialization stuff. What I'd really like to do is get rid of
the OMAP clk code keeping track of it's clks in a separate list, which
seems quite wasteful.
Regards,
Mike
next prev parent reply other threads:[~2011-12-14 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 4:11 [PATCH 0/7] RFC: convert OMAP to common struct clk Mike Turquette
2011-12-14 4:11 ` [PATCH 1/7] OMAP: Kconfig: select GENERIC_CLK Mike Turquette
2011-12-14 4:11 ` [PATCH 2/7] HACK: omap4: clk: convert to common struct clk Mike Turquette
2011-12-14 4:11 ` [PATCH 4/7] omap: hwmod: convert to use " Mike Turquette
2011-12-14 4:11 ` [PATCH 5/7] omap: panda: use clk_prepare in ehci init Mike Turquette
2011-12-14 4:11 ` [PATCH 6/7] omap: dss: use clk_prepare in dss reset Mike Turquette
2011-12-14 4:11 ` [PATCH 7/7] HACK: comment WARN_ON in _clkdm_clk_hwmod_disable Mike Turquette
[not found] ` <1323835918-2371-4-git-send-email-mturquette@ti.com>
2011-12-14 4:27 ` [PATCH 3/7] HACK: omap: convert 44xx data to common struct clk Paul Walmsley
2011-12-14 4:44 ` Turquette, Mike [this message]
2011-12-14 5:29 ` Paul Walmsley
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='CAJOA=zM8hP=1BxcpDu-XMvt0KefRPwhP3m-+yC7Uta+Aozz8Xw@mail.gmail.com' \
--to=mturquette@ti.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).