Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: allen-kh.cheng <allen-kh.cheng@mediatek.com>
To: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Ryder Lee <ryder.lee@kernel.org>, <hsinyi@chromium.org>
Subject: Re: [PATCH v8 2/2] arm64: dts: Add MediaTek SoC MT8186 dts and evaluation board and Makefile
Date: Thu, 5 May 2022 21:10:36 +0800	[thread overview]
Message-ID: <2e9a4f5446c99e5e573168bfbdc1786ba73734b4.camel@mediatek.com> (raw)
In-Reply-To: <c60bf00a-340d-e1de-cabc-87535470c472@collabora.com>

Hi Angelo,

On Thu, 2022-04-28 at 15:32 +0200, AngeloGioacchino Del Regno wrote:
> Il 28/04/22 08:17, Allen-KH Cheng ha scritto:
> > Add basic chip support for MediaTek MT8186.
> > 
> > Signed-off-by: Allen-KH Cheng <Allen-KH.Cheng@mediatek.com>
> > ---
> >   arch/arm64/boot/dts/mediatek/Makefile       |   1 +
> >   arch/arm64/boot/dts/mediatek/mt8186-evb.dts | 232 +++++
> >   arch/arm64/boot/dts/mediatek/mt8186.dtsi    | 949
> > ++++++++++++++++++++
> >   3 files changed, 1182 insertions(+)
> >   create mode 100644 arch/arm64/boot/dts/mediatek/mt8186-evb.dts
> >   create mode 100644 arch/arm64/boot/dts/mediatek/mt8186.dtsi
> > 
> > diff --git a/arch/arm64/boot/dts/mediatek/Makefile
> > b/arch/arm64/boot/dts/mediatek/Makefile
> > index c7d4636a2cb7..50a2c58c5f56 100644
> > --- a/arch/arm64/boot/dts/mediatek/Makefile
> > +++ b/arch/arm64/boot/dts/mediatek/Makefile
> > @@ -37,6 +37,7 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-kukui-
> > kodama-sku32.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-kukui-krane-sku0.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-kukui-krane-sku176.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-pumpkin.dtb
> > +dtb-$(CONFIG_ARCH_MEDIATEK) += mt8186-evb.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8192-evb.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8195-demo.dtb
> >   dtb-$(CONFIG_ARCH_MEDIATEK) += mt8195-evb.dtb
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8186-evb.dts
> > b/arch/arm64/boot/dts/mediatek/mt8186-evb.dts
> > new file mode 100644
> > index 000000000000..6bf5b81e3e6b
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt8186-evb.dts
> > @@ -0,0 +1,232 @@
> 
> ..snip..
> 
> > +
> > +&pio {
> > +	i2c0_pins: i2c0{
> > +		pins_bus {
> 
> No underscores please!
> 
> Either name this "pins-bus" or, more appropriately, I would give it a
> more
> descriptive name, like "pins-sda-scl".

ok, pins-sda-scl is great, I will change name.

> 
> > +			pinmux = <PINMUX_GPIO128__FUNC_SDA0>,
> > +				 <PINMUX_GPIO127__FUNC_SCL0>;
> > +			bias-disable;
> > +			mediatek,drive-strength-adv =<0>;
> > +			drive-strength = <MTK_DRIVE_4mA>;
> > +			input-enable;
> > +		};
> > +	};
> 
> ..snip..
> 
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> > b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> > new file mode 100644
> > index 000000000000..9e3d45f3e5de
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> > @@ -0,0 +1,949 @@
> > +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +/*
> > + * Copyright (C) 2022 MediaTek Inc.
> > + * Author: Allen-KH Cheng <allenn-kh.cheng@mediatek.com>
> 
> Uhm, you typoed your email address! :-)
> 

will correct.

> > + */
> > +/dts-v1/;
> > +#include <dt-bindings/clock/mt8186-clk.h>
> > +#include <dt-bindings/interrupt-controller/arm-gic.h>
> > +#include <dt-bindings/interrupt-controller/irq.h>
> > +#include <dt-bindings/pinctrl/mt8186-pinfunc.h>
> > +#include <dt-bindings/power/mt8186-power.h>
> > +#include <dt-bindings/phy/phy.h>
> > +#include <dt-bindings/reset/mt8186-resets.h>
> > +
> > +/ {
> > +	compatible = "mediatek,mt8186";
> > +	interrupt-parent = <&gic>;
> > +	#address-cells = <2>;
> > +	#size-cells = <2>;
> > +
> > +	cpus {
> > +		#address-cells = <1>;
> > +		#size-cells = <0>;
> > +
> > +		cpu0: cpu@0 {
> > +			device_type = "cpu";
> > +			compatible = "arm,cortex-a55";
> > +			reg = <0x000>;
> > +			enable-method = "psci";
> > +			clock-frequency = <2000000000>;
> 
> No capacity-dmips-mhz for the CPUs?!
> 

oh I will add this.

> > +			cpu-idle-states = <&cpu_off_l &cluster_off_l>;
> > +			next-level-cache = <&l2_0>;
> > +		};
> 
> ..snip..
> 
> > +	soc { 
> > +		#address-cells = <2>;
> > +		#size-cells = <2>;
> > +		compatible = "simple-bus";
> > +		ranges;
> > +
> > +		gic: interrupt-controller@c000000 {
> > +			compatible = "arm,gic-v3";
> > +			#interrupt-cells = <3>;
> > +			#address-cells = <2>;
> > +			#size-cells = <2>;
> > +			#redistributor-regions = <1>;
> > +			interrupt-parent = <&gic>;
> > +			interrupt-controller;
> > +			reg = <0 0x0c000000 0 0x40000>,
> > +			      <0 0x0c040000 0 0x200000>;
> > +			interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
> 
> Are there no ppi-partitions for this interrupt controller?
> 

I will check this and update in next version.

> > +		};
> > +
> 
> ..snip..
> 
> > +
> > +		scpsys: syscon@10006000 {
> > +			compatible = "syscon", "simple-mfd";
> > +			reg = <0 0x10006000 0 0x1000>;
> > +			#power-domain-cells = <1>;
> > +
> > +			/* System Power Manager */
> > +			spm: power-controller {
> > +				compatible = "mediatek,mt8186-power-
> > controller";
> > +				#address-cells = <1>;
> > +				#size-cells = <0>;
> > +				#power-domain-cells = <1>;
> > +
> > +				/* power domain of the SoC */
> > +				mfg0: mfg0@MT8186_POWER_DOMAIN_MFG0 {
> 
> This should be, for consistency with other mtk devicetrees:
>      mfg0: power-domain@MT8186_POWER_DOMAIN_MFG0 {
> 

ok

> > +					reg =
> > <MT8186_POWER_DOMAIN_MFG0>;
> > +					clocks = <&topckgen
> > CLK_TOP_MFG>;
> > +					clock-names= "mfg00";
> > +					#address-cells = <1>;
> > +					#size-cells = <0>;
> > +					#power-domain-cells = <1>;
> > +
> > +					mfg1@MT8186_POWER_DOMAIN_MFG1 {
> 
> power-domain@MT8186_POWER_DOMAIN_MFG1
> 
> ....and the same for all of the other occurrences.
> 

ok

> > +						reg =
> > <MT8186_POWER_DOMAIN_MFG1>;
> > +						mediatek,infracfg =
> > <&infracfg_ao>;
> > +						#address-cells = <1>;
> > +						#size-cells = <0>;
> > +						#power-domain-cells =
> > <1>;
> 
> ..snip..
> 
> > +
> > +		scp: scp@10500000 {
> > +			compatible = "mediatek,mt8186-scp";
> > +			reg = <0 0x10500000 0 0x40000>,
> > +			      <0 0x105c0000 0 0x19080>;
> > +			reg-names = "sram", "cfg";
> > +			interrupts = <GIC_SPI 205 IRQ_TYPE_LEVEL_HIGH>;
> > +			status = "okay";
> 
> `status = "okay"` can be omitted here: all the nodes are enabled by
> default.
> 

will remove

thanks,
Allen

> > +		};
> > +
> 
> Cheers,
> Angelo


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2022-05-05 13:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:17 [PATCH v8 0/2] Add basic node support for MediaTek MT8186 SoC Allen-KH Cheng
2022-04-28  6:17 ` [PATCH v8 1/2] dt-bindings: arm: Add compatible for MediaTek MT8186 Allen-KH Cheng
2022-04-28 13:34   ` AngeloGioacchino Del Regno
2022-04-29 22:31   ` Rob Herring
2022-04-28  6:17 ` [PATCH v8 2/2] arm64: dts: Add MediaTek SoC MT8186 dts and evaluation board and Makefile Allen-KH Cheng
2022-04-28 13:32   ` AngeloGioacchino Del Regno
2022-05-05 13:10     ` allen-kh.cheng [this message]
2022-04-28 17:27   ` Nícolas F. R. A. Prado
2022-04-29 21:39     ` Nícolas F. R. A. Prado
2022-05-05 12:21       ` allen-kh.cheng

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=2e9a4f5446c99e5e573168bfbdc1786ba73734b4.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsinyi@chromium.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=ryder.lee@kernel.org \
    --cc=wenst@chromium.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