public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: finley.xiao@rock-chips.com (Finlye Xiao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
Date: Wed, 10 Aug 2016 14:50:40 +0800	[thread overview]
Message-ID: <1470811843-42668-2-git-send-email-finley.xiao@rock-chips.com> (raw)
In-Reply-To: <1470811843-42668-1-git-send-email-finley.xiao@rock-chips.com>

From: Finley Xiao <finley.xiao@rock-chips.com>

Rk3399-efuse is organized as 32bits by 32 one-time programmable
electrical fuses. The efuse of earlier SoCs are organized as
32bits by 8 one-time programmable electrical fuses with random
access interface.

Add different device tree compatible string for different SoCs
to be able to differentiate between the two.

Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
---
 Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt b/Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt
index 8f86ab3..8ec1b80 100644
--- a/Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt
+++ b/Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt
@@ -1,7 +1,11 @@
 = Rockchip eFuse device tree bindings =
 
 Required properties:
-- compatible: Should be "rockchip,rockchip-efuse"
+- compatible: Should be one of the following.
+	"rockchip,rk3066a-efuse" - for RK3066a SoCs.
+	"rockchip,rk3188-efuse" - for RK3188 SoCs.
+	"rockchip,rk3288-efuse" - for RK3288 SoCs.
+	"rockchip,rk3399-efuse" - for RK3399 SoCs.
 - reg: Should contain the registers location and exact eFuse size
 - clocks: Should be the clock id of eFuse
 - clock-names: Should be "pclk_efuse"
@@ -13,7 +17,7 @@ bindings/nvmem/nvmem.txt
 Example:
 
 	efuse: efuse at ffb40000 {
-		compatible = "rockchip,rockchip-efuse";
+		compatible = "rockchip,rk3288-efuse";
 		reg = <0xffb40000 0x20>;
 		#address-cells = <1>;
 		#size-cells = <1>;
-- 
1.9.1

  reply	other threads:[~2016-08-10  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  6:50 [PATCH v1 0/4] nvmem: rockchip-efuse: support more rockchip SoCs Finlye Xiao
2016-08-10  6:50 ` Finlye Xiao [this message]
2016-08-10  8:21   ` [PATCH v1 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse Heiko Stübner
2016-08-10  6:50 ` [PATCH v1 2/4] ARM: dts: rockchip: " Finlye Xiao
2016-08-10  6:50 ` [PATCH v1 3/4] arm64: dts: rockchip: add efuse0 device node for rk3399 Finlye Xiao
2016-08-10  6:50 ` [PATCH v1 4/4] nvmem: rockchip-efuse: add rk3399-efuse support Finlye Xiao
2016-08-10  8:30   ` Heiko Stübner

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=1470811843-42668-2-git-send-email-finley.xiao@rock-chips.com \
    --to=finley.xiao@rock-chips.com \
    --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