From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock: function clock and bus clock
Date: Thu, 20 Mar 2014 11:35:31 +0000 [thread overview]
Message-ID: <20140320113531.GP7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <532AB8B7.6060608@codethink.co.uk>
On Thu, Mar 20, 2014 at 10:45:27AM +0100, Ben Dooks wrote:
> On 11/03/14 03:06, Chao Xie wrote:
>> hi
>>
>> I can not find any examples for handling function clock and bus clock
>> in drivers/clk/.
>
> The convention is that clk_get(dev, NULL) will get the bus clock
> for the device and that any other clocks are appropriately named.
There is no such convention. clk_get(dev, NULL) with clkdev (the
reference) will find a clock in the table for the device also with
a NULL connection ID. That's the only "limitation".
There's no implication that NULL is some kind of bus clock.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
prev parent reply other threads:[~2014-03-20 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 2:06 Common clock: function clock and bus clock Chao Xie
2014-03-11 2:48 ` Haojian Zhuang
2014-03-12 2:30 ` Chao Xie
2014-03-12 10:14 ` Grygorii Strashko
2014-03-13 2:15 ` Chao Xie
2014-03-13 3:16 ` Emilio López
2014-03-13 11:30 ` Grygorii Strashko
[not found] ` <20140319210428.31449.19420@quantum>
[not found] ` <CAPDyKFqg230Ob5Wxu0tvXqia+B3WG5+YdKTdxTQ0ySbZokb+7Q@mail.gmail.com>
2014-03-20 10:30 ` Grygorii Strashko
2014-03-20 11:42 ` Russell King - ARM Linux
2014-03-20 9:45 ` Ben Dooks
2014-03-20 11:35 ` Russell King - ARM Linux [this message]
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=20140320113531.GP7528@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.