From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
Date: Thu, 11 Aug 2016 10:14:03 +0200 [thread overview]
Message-ID: <21647624.nrv841C5QK@diego> (raw)
In-Reply-To: <1470878029-11878-2-git-send-email-finley.xiao@rock-chips.com>
Am Donnerstag, 11. August 2016, 09:13:46 schrieb Finlye Xiao:
> 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. The old binding is of course preserved,
> though deprecated.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2016-08-11 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 1:13 [PATCH v2 0/4] nvmem: rockchip-efuse: support more rockchip SoCs Finlye Xiao
2016-08-11 1:13 ` [PATCH v2 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse Finlye Xiao
2016-08-11 8:14 ` Heiko Stübner [this message]
2016-08-11 1:13 ` [PATCH v2 2/4] ARM: dts: rockchip: " Finlye Xiao
2016-08-11 8:18 ` Heiko Stübner
2016-08-11 1:13 ` [PATCH v2 3/4] arm64: dts: rockchip: add efuse0 device node for rk3399 Finlye Xiao
2016-08-11 8:19 ` Heiko Stübner
2016-09-01 17:57 ` Doug Anderson
2016-08-11 1:13 ` [PATCH v2 4/4] nvmem: rockchip-efuse: add rk3399-efuse support Finlye Xiao
2016-08-11 8:21 ` 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=21647624.nrv841C5QK@diego \
--to=heiko@sntech.de \
--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).