public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] dt-bindings: add document of mediatek efuse driver
Date: Fri, 20 Nov 2015 09:40:29 -0600	[thread overview]
Message-ID: <20151120154029.GA10692@rob-hp-laptop> (raw)
In-Reply-To: <1447930014-19579-2-git-send-email-andrew-ct.chen@mediatek.com>

On Thu, Nov 19, 2015 at 06:46:52PM +0800, Andrew-CT Chen wrote:
> Add Mediatek MT8173 EFUSE Devicetree binding file
> 
> Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com>

Acked-by: Rob Herring <robh@kernel.org>

> ---
>  .../devicetree/bindings/nvmem/mtk-efuse.txt        | 36 ++++++++++++++++++++++
>  1 file changed, 36 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> 
> diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> new file mode 100644
> index 0000000..74cf529
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> @@ -0,0 +1,36 @@
> += Mediatek MTK-EFUSE device tree bindings =
> +
> +This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs.
> +
> +Required properties:
> +- compatible: should be "mediatek,mt8173-efuse" or "mediatek,efuse"
> +- reg: Should contain registers location and length
> +
> += Data cells =
> +Are child nodes of MTK-EFUSE, bindings of which as described in
> +bindings/nvmem/nvmem.txt
> +
> +Example:
> +
> +	efuse: efuse at 10206000 {
> +		compatible = "mediatek,mt8173-efuse";
> +		reg	   = <0 0x10206000 0 0x1000>;
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +
> +		/* Data cells */
> +		thermal_calibration: calib at 528 {
> +			reg = <0x528 0xc>;
> +		};
> +	};
> +
> += Data consumers =
> +Are device nodes which consume nvmem data cells.
> +
> +For example:
> +
> +	thermal {
> +		...
> +		nvmem-cells = <&thermal_calibration>;
> +		nvmem-cell-names = "calibration";
> +	};
> -- 
> 1.9.1
> 

  reply	other threads:[~2015-11-20 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 10:46 [PATCH v2 0/3] Mediatek EFUSE Support Andrew-CT Chen
2015-11-19 10:46 ` [PATCH v2 1/3] dt-bindings: add document of mediatek efuse driver Andrew-CT Chen
2015-11-20 15:40   ` Rob Herring [this message]
2015-11-19 10:46 ` [PATCH v2 2/3] nvmem: mediatek: Add Mediatek EFUSE driver Andrew-CT Chen
2015-12-08  4:52   ` Nicolas Boichat
2015-11-19 10:46 ` [PATCH v2 3/3] dts: arm64: Add EFUSE device node Andrew-CT Chen
2016-02-10 17:48   ` Matthias Brugger
2015-12-14  4:27 ` [PATCH v2 0/3] Mediatek EFUSE Support Daniel Kurtz
2015-12-14 10:07   ` Srinivas Kandagatla
2016-01-21  9:33     ` Matthias Brugger
2016-01-21 14:32       ` Srinivas Kandagatla
2016-01-21 14:46         ` Matthias Brugger
2016-01-21 14:49           ` Srinivas Kandagatla
2016-02-01 10:23             ` Matthias Brugger

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=20151120154029.GA10692@rob-hp-laptop \
    --to=robh@kernel.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