From: "Heiko Stübner" <heiko@sntech.de>
To: Finlye Xiao <finley.xiao@rock-chips.com>
Cc: srinivas.kandagatla@linaro.org, maxime.ripard@free-electrons.com,
robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
catalin.marinas@arm.com, will.deacon@arm.com,
dianders@chromium.org, wbriannorris@chromium.org,
wxt@rock-chips.com, jay.xu@rock-chips.com,
huangtao@rock-chips.com, cl@rock-chips.com,
tony.xie@rock-chips.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
Date: Wed, 10 Aug 2016 10:21:46 +0200 [thread overview]
Message-ID: <18634361.lkZvz8cT7b@diego> (raw)
In-Reply-To: <1470811843-42668-2-git-send-email-finley.xiao@rock-chips.com>
Hi Finley,
Am Mittwoch, 10. August 2016, 14:50:40 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.
>
> 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"
you cannot drop the old compatible that way. Please add a new section
Deprecated properties:
- compatible: "rockchip,rockchip-efuse"
Old efuse compatible value compatible to rk3066a, rk3188 and rk3288 efuses
and move the old compatible there.
Thanks
Heiko
next parent reply other threads:[~2016-08-10 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1470811843-42668-1-git-send-email-finley.xiao@rock-chips.com>
[not found] ` <1470811843-42668-2-git-send-email-finley.xiao@rock-chips.com>
2016-08-10 8:21 ` Heiko Stübner [this message]
[not found] ` <1470811843-42668-5-git-send-email-finley.xiao@rock-chips.com>
2016-08-10 8:30 ` [PATCH v1 4/4] nvmem: rockchip-efuse: add rk3399-efuse support 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=18634361.lkZvz8cT7b@diego \
--to=heiko@sntech.de \
--cc=catalin.marinas@arm.com \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=finley.xiao@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tony.xie@rock-chips.com \
--cc=wbriannorris@chromium.org \
--cc=will.deacon@arm.com \
--cc=wxt@rock-chips.com \
/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
all inboxes | Powered by JetHome®