From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] ARM: omap: clk: add clk_prepare and clk_unprepare
Date: Tue, 31 Jul 2012 00:02:33 +0100 [thread overview]
Message-ID: <20120730230233.GA12574@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAJOA=zPmfq+WsAF-7nAkMGghPLYHpd+fCkrsv=3JSWLGMb-zkg@mail.gmail.com>
On Mon, Jul 30, 2012 at 03:42:13PM -0700, Turquette, Mike wrote:
> On Mon, Jul 30, 2012 at 3:31 PM, Paul Walmsley <paul@pwsan.com> wrote:
> > So if we make a change like this one, it seems like we would basically
> > expect it to break once we start doing anything meaningful with
> > clk_prepare(), like using clk_prepare() for voltage scaling or something
> > that requires I2C? We'd also probably want to mark this with some kind of
> > "HACK" comment.
>
> Hi Paul,
>
> Did you have anything in mind to start using clk_prepare? I still
> hope to get rid of it some day and replace that call with a
> combination of clk_enable and a check like clk_enable_can_sleep.
Don't you dare.
We arrived at the clk_prepare()/clk_enable() split after lots of
discussion between different platform maintainers and their
requirements.
Shoving crap like "clk_enable_can_sleep()" down into drivers is
totally and utterly idiotic. We've had the situation *already*
where some drivers can be used on some platforms but not on others
because of differences in clk_enable() expectations.
Don't go back there. clk_prepare() and clk_enable() are separate
calls for a very good reason. One is sleepable, the other can be
called from any atomic contexts.
next prev parent reply other threads:[~2012-07-30 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 10:24 [PATCH v3 0/3] Prepare for OMAP2+ movement to Common Clk Rajendra Nayak
2012-07-02 10:24 ` [PATCH v3 1/3] ARM: omap: clk: add clk_prepare and clk_unprepare Rajendra Nayak
2012-07-30 22:31 ` Paul Walmsley
2012-07-30 22:42 ` Turquette, Mike
2012-07-30 23:02 ` Russell King - ARM Linux [this message]
2012-07-31 0:31 ` Turquette, Mike
2012-07-31 8:21 ` Saravana Kannan
2012-07-31 9:27 ` Russell King - ARM Linux
2012-07-31 9:23 ` Russell King - ARM Linux
2012-07-31 18:00 ` Paul Walmsley
2012-07-02 10:24 ` [PATCH v3 2/3] ARM: omap: hwmod: get rid of all omap_clk_get_by_name usage Rajendra Nayak
2012-07-02 10:24 ` [PATCH v3 3/3] ARM: omap: clk: Remove all direct dereferencing of struct clk Rajendra Nayak
2012-07-30 7:12 ` Paul Walmsley
2012-07-30 7:36 ` Rajendra Nayak
2012-07-30 18:56 ` Paul Walmsley
2012-07-31 6:05 ` Rajendra Nayak
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=20120730230233.GA12574@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).