From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] dt-bindings: configuration of parent clocks and clock frequency
Date: Fri, 31 Jan 2014 19:06:14 -0800 [thread overview]
Message-ID: <20140201030614.9977.80501@quantum> (raw)
In-Reply-To: <52DE6CAB.10008@samsung.com>
Quoting Sylwester Nawrocki (2014-01-21 04:48:43)
> 5. Similarly to the regulator bindings the clock names could be appended
> to name of a DT property:
>
> [clk_name]-assigned-clock-parent = <...>;
> [clk_name]-assigned-clock-rate = <...>;
I have always been partial to the way that the reg framework does its
[reg_name]-supply. We could shorten it to something like:
[clk-name]-asn-parent = ....
[clk-name]-asn-rate = ...
This is actually the format that was discussed at the ARM kernel summit
IIRC.
Regards,
Mike
next prev parent reply other threads:[~2014-02-01 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 12:48 [RFC] dt-bindings: configuration of parent clocks and clock frequency Sylwester Nawrocki
2014-02-01 3:06 ` Mike Turquette [this message]
2014-02-04 12:16 ` Marek Szyprowski
2014-02-06 16:43 ` Mike Turquette
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=20140201030614.9977.80501@quantum \
--to=mturquette@linaro.org \
--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).