From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] ARM: DTS: tegra: add the DFLL IP block to the T114 SoC file
Date: Thu, 19 Dec 2013 17:05:33 -0700 [thread overview]
Message-ID: <52B389CD.8010004@wwwdotorg.org> (raw)
In-Reply-To: <20131219123719.3226.44864.stgit@tamien>
On 12/19/2013 05:49 AM, Paul Walmsley wrote:
> Add basic DT bindings for the DFLL IP block for the NVIDIA Tegra114 SoC.
> diff --git a/Documentation/devicetree/bindings/clock/nvidia,tegra114-dfll.txt b/Documentation/devicetree/bindings/clock/nvidia,tegra114-dfll.txt
> +- clocks : Must contain an array of two-cell arrays, one per clock.
> + DFLL source clocks. At minimum this should include the
> + reference clock source and the IP block's main clock
> + source. Also it should contain the DFLL's I2C controller
> + clock source. The format is <&clock-provider-phandle
> + clock-id>.
Entries in "clocks" aren't two cells, they're a phandle plus as many
cells as the node referenced by the phandle specifies.
> +
> +- clock-names : Must contain an array of strings, one per 'clocks'
> + two-cell array. The position in the array of these
clock-names defines the set of entries in clocks, not the other way around.
> + strings must correspond to the position in the 'clocks'
> + array (see above). The DFLL driver currently requires
> + the "soc", "ref", and "i2c" clock names to be populated.
The standard wording used by all the Tegra clock client bindings is now:
- clocks : Must contain an entry for each entry in clock-names.
See clock-bindings.txt for details.
- clock-names : Must include the following entries:
- soc
- ref
- i2c
For consistency, it'd be nice to adopt the same style here.
> +Optional properties:
> +
> +- status : device availability -- managed by the DT integration code, not
> + the DFLL driver. Should be set to "disabled" in the SoC
> + DTS file.
That's such a core property that it's not worth documenting in every
single binding.
> +
Blank line at EOF.
next prev parent reply other threads:[~2013-12-20 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 12:36 [PATCH 0/6] clk: tegra: add basic support for the DFLL clocksource Paul Walmsley
2013-12-19 12:36 ` [PATCH 1/6] ARM: tegra: fuse: add functions to read speedo ID and process ID Paul Walmsley
2013-12-19 23:09 ` Stephen Warren
2013-12-19 12:36 ` [PATCH 2/6] ARM: tegra114: fuse: add DFLL FCPU minimum voltage override test function Paul Walmsley
2013-12-19 23:12 ` Stephen Warren
2013-12-19 12:37 ` [PATCH 3/6] clk: tegra: add library for the DFLL clocksource (open-loop mode) Paul Walmsley
2013-12-19 23:57 ` Stephen Warren
2013-12-19 12:49 ` [PATCH 4/6] ARM: DTS: tegra: add the DFLL IP block to the T114 SoC file Paul Walmsley
2013-12-20 0:05 ` Stephen Warren [this message]
2014-01-14 6:27 ` Paul Walmsley
2014-01-14 6:32 ` Paul Walmsley
2014-01-15 19:50 ` Gerhard Sittig
2014-01-15 20:09 ` Paul Walmsley
[not found] ` <52D4D314.3000208@nvidia.com>
2014-01-14 17:43 ` Stephen Warren
2013-12-19 12:49 ` [PATCH 5/6] ARM: DTS: tegra: add DFLL integration to the Dalmore DTS file Paul Walmsley
2013-12-20 0:10 ` Stephen Warren
2014-01-14 6:36 ` Paul Walmsley
2013-12-19 12:49 ` [PATCH 6/6] clk: tegra: add Tegra114 FCPU DFLL clocksource platform driver Paul Walmsley
2013-12-20 0:18 ` Stephen Warren
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=52B389CD.8010004@wwwdotorg.org \
--to=swarren@wwwdotorg.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).