From: Matthias Brugger <matthias.bgg@gmail.com>
To: Yong Liang <yong.liang@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] amr64: dts: modify mt8183.dtsi
Date: Wed, 8 Jan 2020 15:05:01 +0100 [thread overview]
Message-ID: <675aa211-eba5-e44c-0931-32c1b6d5ca8b@gmail.com> (raw)
In-Reply-To: <20191226093930.22413-2-yong.liang@mediatek.com>
On 26/12/2019 10:39, Yong Liang wrote:
> From: "yong.liang" <yong.liang@mediatek.com>
>
> Include mt8183-reset.h and add reset-cells in infracfg
> in dtsi file
>
> Signed-off-by: yong.liang <yong.liang@mediatek.com>
applied with fixed subject line to v5.5-next/dts64
Thanks
> ---
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> index 10b32471bc7b..76bfcbdf097a 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> @@ -8,6 +8,7 @@
> #include <dt-bindings/clock/mt8183-clk.h>
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> #include <dt-bindings/interrupt-controller/irq.h>
> +#include <dt-bindings/reset-controller/mt8183-resets.h>
> #include "mt8183-pinfunc.h"
>
> / {
> @@ -227,6 +228,7 @@
> compatible = "mediatek,mt8183-infracfg", "syscon";
> reg = <0 0x10001000 0 0x1000>;
> #clock-cells = <1>;
> + #reset-cells = <1>;
> };
>
> pio: pinctrl@10005000 {
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-01-08 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 9:39 [PATCH v1 0/1] add reset-cells in infracfg Yong Liang
2019-12-26 9:39 ` [PATCH v1 1/1] amr64: dts: modify mt8183.dtsi Yong Liang
2020-01-08 14:05 ` Matthias Brugger [this message]
2020-01-13 4:52 ` Nicolas Boichat
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=675aa211-eba5-e44c-0931-32c1b6d5ca8b@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=yong.liang@mediatek.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;
as well as URLs for NNTP newsgroup(s).