devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Stanimir Varbanov <svarbanov@mm-sol.com>
Cc: Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, Rob Landley <rob@landley.net>,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: DT: msm: Add Qualcomm's PRNG driver binding document
Date: Fri, 11 Oct 2013 13:46:40 -0700	[thread overview]
Message-ID: <20131011204640.GD13139@codeaurora.org> (raw)
In-Reply-To: <1381504601-23773-2-git-send-email-svarbanov@mm-sol.com>

On 10/11, Stanimir Varbanov wrote:
> This adds Qualcomm PRNG driver device tree binding documentation
> to use as an example in dts trees.
> 
> Signed-off-by: Stanimir Varbanov <svarbanov@mm-sol.com>
> ---
>  Documentation/devicetree/bindings/rng/qcom,prng.txt | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/rng/qcom,prng.txt
> 
> diff --git a/Documentation/devicetree/bindings/rng/qcom,prng.txt b/Documentation/devicetree/bindings/rng/qcom,prng.txt
> new file mode 100644
> index 000000000000..92be00085ab1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rng/qcom,prng.txt
> @@ -0,0 +1,17 @@
> +Qualcomm MSM pseudo random number generator.
> +
> +Required properties:
> +
> +- compatible  : should be "qcom,prng"
> +- reg         : specifies base physical address and size of the registers map
> +- clocks      : phandle to clock-controller plus clock-specifier pair
> +- clock-names : "prng" clocks all registers, FIFO and circuits in PRNG IP block

We're trying to keep to more generic names such as "core" for
clocks like this. We've had problems in the past where hardware
designers named the clock input after the name of the hardware
and then the name of the hardware changed in the next version of
the chip (although the hardware was mostly compatible with the
previous version) and so they renamed the clock input. This
leaked into the software drivers and we had horrible things like
platform data for clock names. Sticking to "core" indicates what
the clock does (i.e. it clocks the core PRNG hardware) while
staying generic enough to prevent problems in the future if the
block is renamed to something else. It might also help us in the
future should our bus layer become smart enough to manage clocks
for drivers without their knowing.

> +
> +Example:
> +
> +	rng {

It's good practice to add the unit address here, so rng@f9bff000.

> +		compatible = "qcom,prng";
> +		reg = <0xf9bff000 0x200>;
> +		clocks = <&clock GCC_PRNG_AHB_CLK>;
> +		clock-names = "prng";
> +	};

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-10-11 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 15:16 [PATCH v2 0/2] Add support for Qualcomm's PRNG Stanimir Varbanov
2013-10-11 15:16 ` [PATCH v2 1/2] ARM: DT: msm: Add Qualcomm's PRNG driver binding document Stanimir Varbanov
2013-10-11 20:46   ` Stephen Boyd [this message]
2013-10-14 15:01     ` Stanimir Varbanov
2013-10-11 15:16 ` [PATCH v2 2/2] hwrng: msm: Add PRNG support for MSM SoC's Stanimir Varbanov
2013-10-11 20:37   ` Stephen Boyd
2013-10-14 15:05     ` Stanimir Varbanov

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=20131011204640.GD13139@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mpm@selenic.com \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=svarbanov@mm-sol.com \
    --cc=swarren@wwwdotorg.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).