All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
	robh+dt@kernel.org, mark.rutland@arm.com
Cc: argus.lin@mediatek.com, sean.wang@mediatek.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mediatek@lists.infradead.org, chenglin.xu@mediatek.com,
	chen.zhong@mediatek.com, srv_heupstream@mediatek.com
Subject: Re: [PATCH 4/4] arm64: dts: mediatek: add pwrap device node for mt8183
Date: Sat, 29 Sep 2018 15:30:54 +0200	[thread overview]
Message-ID: <f1cc2f58-ad3c-2f88-8e86-b80848e17cc5@gmail.com> (raw)
In-Reply-To: <1537341961-20736-5-git-send-email-hsin-hsiung.wang@mediatek.com>



On 19/09/2018 09:26, Hsin-Hsiung Wang wrote:
> add pwrap device node for mt8183.
> 
> Signed-off-by: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>
> ---
>  arch/arm64/boot/dts/mediatek/mt8183.dtsi | 10 ++++++++++
>  1 file changed, 10 insertions(+)

The basic support for mt8183 is not ready to be merged.
I'll also try to not forget about this patch.
If you re-submit after basic mt8183 support got accepted, that will help me. :)

Thanks,
Matthias

> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> index c22a2dc..fa67d781 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> @@ -170,6 +170,16 @@
>  		#clock-cells = <1>;
>  	};
>  
> +	pwrap: pwrap@1000d000 {
> +		compatible = "mediatek,mt8183-pwrap";
> +		reg = <0 0x1000d000 0 0x1000>;
> +		reg-names = "pwrap";
> +		interrupts = <GIC_SPI 209 IRQ_TYPE_LEVEL_HIGH>;
> +		clocks = <&topckgen CLK_TOP_MUX_PMICSPI>,
> +			 <&infracfg CLK_INFRA_PMIC_AP>;
> +		clock-names = "spi", "wrap";
> +	};
> +
>  	uart0: serial@11002000 {
>  		compatible = "mediatek,mt8183-uart",
>  			     "mediatek,mt6577-uart";
> 

      reply	other threads:[~2018-09-29 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  7:25 [PATCH 0/4] Add PMIC wrapper support for Mediatek MT8183 SoC IC Hsin-Hsiung Wang
2018-09-19  7:25 ` Hsin-Hsiung Wang
2018-09-19  7:25 ` [PATCH 1/4] dt-bindings: mediatek: add compatible for mt8183 pwrap Hsin-Hsiung Wang
2018-09-19  7:25   ` Hsin-Hsiung Wang
     [not found]   ` <1537341961-20736-2-git-send-email-hsin-hsiung.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-09-25 11:24     ` Rob Herring
2018-09-25 13:52   ` Matthias Brugger
2018-09-19  7:25 ` [PATCH 2/4] soc: mediatek: use group of bits for pwrap capability Hsin-Hsiung Wang
2018-09-19  7:25   ` Hsin-Hsiung Wang
2018-09-25 13:53   ` Matthias Brugger
2018-09-19  7:26 ` [PATCH 3/4] soc: mediatek: add mt8183 pwrap support Hsin-Hsiung Wang
2018-09-19  7:26   ` Hsin-Hsiung Wang
2018-09-25 13:52   ` Matthias Brugger
2018-09-19  7:26 ` [PATCH 4/4] arm64: dts: mediatek: add pwrap device node for mt8183 Hsin-Hsiung Wang
2018-09-19  7:26   ` Hsin-Hsiung Wang
2018-09-29 13:30   ` Matthias Brugger [this message]

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=f1cc2f58-ad3c-2f88-8e86-b80848e17cc5@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=argus.lin@mediatek.com \
    --cc=chen.zhong@mediatek.com \
    --cc=chenglin.xu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsin-hsiung.wang@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.wang@mediatek.com \
    --cc=srv_heupstream@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.