From: Matthias Brugger <matthias.bgg@gmail.com>
To: Fabien Parent <fparent@baylibre.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, srinivas.kandagatla@linaro.org
Subject: Re: [PATCH 2/2] arm64: dts: mediatek: mt8516: add efuse node
Date: Fri, 27 Nov 2020 09:34:09 +0100 [thread overview]
Message-ID: <34955ee3-3505-9445-709e-34d95ea37dbb@gmail.com> (raw)
In-Reply-To: <20201016171837.3261310-2-fparent@baylibre.com>
On 16/10/2020 19:18, Fabien Parent wrote:
> Add node to support e-fuses on MT8516
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8516.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Applied to v5.10-next/dts64
Thanks!
> diff --git a/arch/arm64/boot/dts/mediatek/mt8516.dtsi b/arch/arm64/boot/dts/mediatek/mt8516.dtsi
> index 89af661e7f63..18ddea519be2 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8516.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8516.dtsi
> @@ -237,6 +237,13 @@ pio: pinctrl@1000b000 {
> interrupts = <GIC_SPI 134 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> + efuse: efuse@10009000 {
> + compatible = "mediatek,mt8516-efuse", "mediatek,efuse";
> + reg = <0 0x10009000 0 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + };
> +
> pwrap: pwrap@1000f000 {
> compatible = "mediatek,mt8516-pwrap";
> reg = <0 0x1000f000 0 0x1000>;
>
next prev parent reply other threads:[~2020-11-27 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 17:18 [PATCH 1/2] dt-bindings: nvmem: mtk-efuse: add documentation for MT8516 SoC Fabien Parent
2020-10-16 17:18 ` [PATCH 2/2] arm64: dts: mediatek: mt8516: add efuse node Fabien Parent
2020-11-27 8:34 ` Matthias Brugger [this message]
2020-10-26 13:13 ` [PATCH 1/2] dt-bindings: nvmem: mtk-efuse: add documentation for MT8516 SoC Rob Herring
2020-11-24 10:54 ` Srinivas Kandagatla
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=34955ee3-3505-9445-709e-34d95ea37dbb@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).