From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
Date: Mon, 12 Sep 2016 10:35:08 -0500 [thread overview]
Message-ID: <20160912153508.GA25555@rob-hp-laptop> (raw)
In-Reply-To: <1472786217-52214-2-git-send-email-finley.xiao@rock-chips.com>
On Thu, Sep 01, 2016 at 08:16:54PM -0700, Finley Xiao wrote:
> 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>
> ---
> Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-09-12 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 3:16 [PATCH v5 0/4] nvmem: rockchip-efuse: support more rockchip SoCs Finley Xiao
2016-09-02 3:16 ` [PATCH v5 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse Finley Xiao
2016-09-02 3:54 ` Doug Anderson
2016-09-12 15:35 ` Rob Herring [this message]
2016-09-02 3:16 ` [PATCH v5 2/4] ARM: dts: rockchip: " Finley Xiao
2016-09-02 3:54 ` Doug Anderson
2016-09-02 15:48 ` Heiko Stübner
2016-09-02 3:16 ` [PATCH v5 3/4] arm64: dts: rockchip: add efuse0 device node for rk3399 Finley Xiao
2016-09-02 3:53 ` Doug Anderson
2016-09-02 15:45 ` Heiko Stübner
2016-09-02 3:16 ` [PATCH v5 4/4] nvmem: rockchip-efuse: add rk3399-efuse support Finley Xiao
2016-09-02 3:54 ` Doug Anderson
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=20160912153508.GA25555@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