All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanks Chen <hanks.chen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Sean Wang <sean.wang@kernel.org>,
	Andy Teng <andy.teng@mediatek.com>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>,
	<devicetree@vger.kernel.org>, CC Hwang <cc.hwang@mediatek.com>
Subject: Re: [PATCH v5 6/6] arm64: dts: add dts nodes for MT6779
Date: Mon, 22 Jun 2020 20:09:26 +0800	[thread overview]
Message-ID: <1592827766.10773.33.camel@mtkswgap22> (raw)
In-Reply-To: <247c07c2-4488-a112-5874-4bd7c9d98292@gmail.com>

On Mon, 2020-06-22 at 13:25 +0200, Matthias Brugger wrote:
> 
> On 16/06/2020 15:34, Hanks Chen wrote:
> > On Wed, 2020-03-25 at 17:39 +0100, Matthias Brugger wrote:
> >>
> >> On 25/03/2020 10:31, Hanks Chen wrote:
> >>> this adds initial MT6779 dts settings fo board support,
> >>
> >> "for board support"
> >>
> >>> including cpu, gic, timer, ccf, pinctrl, uart...etc.
> >>
> >> The etc is PMU and PSCI and sysirq, correct? Let's list at least sysirq as this
> >> is something MediaTek specific.
> >>
> >>>
> >>> Signed-off-by: Hanks Chen <hanks.chen@mediatek.com>
> >>> ---
> >>>  arch/arm64/boot/dts/mediatek/Makefile       |    1 +
> >>>  arch/arm64/boot/dts/mediatek/mt6779-evb.dts |   31 ++++
> >>>  arch/arm64/boot/dts/mediatek/mt6779.dtsi    |  265 +++++++++++++++++++++++++++
> >>>  3 files changed, 297 insertions(+)
> >>>  create mode 100644 arch/arm64/boot/dts/mediatek/mt6779-evb.dts
> >>>  create mode 100644 arch/arm64/boot/dts/mediatek/mt6779.dtsi
> >>>
> >>> diff --git a/arch/arm64/boot/dts/mediatek/Makefile b/arch/arm64/boot/dts/mediatek/Makefile
> >>> index 458bbc4..53f1c61 100644
> >>> --- a/arch/arm64/boot/dts/mediatek/Makefile
> >>> +++ b/arch/arm64/boot/dts/mediatek/Makefile
> >>> @@ -1,6 +1,7 @@
> >>>  # SPDX-License-Identifier: GPL-2.0
> >>>  dtb-$(CONFIG_ARCH_MEDIATEK) += mt2712-evb.dtb
> >>>  dtb-$(CONFIG_ARCH_MEDIATEK) += mt6755-evb.dtb
> >>> +dtb-$(CONFIG_ARCH_MEDIATEK) += mt6779-evb.dtb
> >>>  dtb-$(CONFIG_ARCH_MEDIATEK) += mt6795-evb.dtb
> >>>  dtb-$(CONFIG_ARCH_MEDIATEK) += mt6797-evb.dtb
> >>>  dtb-$(CONFIG_ARCH_MEDIATEK) += mt6797-x20-dev.dtb
> >>> diff --git a/arch/arm64/boot/dts/mediatek/mt6779-evb.dts b/arch/arm64/boot/dts/mediatek/mt6779-evb.dts
> >>> new file mode 100644
> >>> index 0000000..164f5cb
> >>> --- /dev/null
> >>> +++ b/arch/arm64/boot/dts/mediatek/mt6779-evb.dts
> >>> @@ -0,0 +1,31 @@
> >>> +// SPDX-License-Identifier: GPL-2.0+
> >>> +/*
> >>> + * Copyright (c) 2019 MediaTek Inc.
> >>> + * Author: Mars.C <mars.cheng@mediatek.com>
> >>> + *
> >>> + */
> >>> +
> >>> +/dts-v1/;
> >>> +#include "mt6779.dtsi"
> >>> +
> >>> +/ {
> >>> +	model = "MediaTek MT6779 EVB";
> >>> +	compatible = "mediatek,mt6779-evb", "mediatek,mt6779";
> >>> +
> >>> +	aliases {
> >>> +		serial0 = &uart0;
> >>> +	};
> >>> +
> >>> +	memory@40000000 {
> >>> +		device_type = "memory";
> >>> +		reg = <0 0x40000000 0 0x1e800000>;
> >>> +	};
> >>> +
> >>> +	chosen {
> >>> +		stdout-path = "serial0:921600n8";
> >>> +	};
> >>> +};
> >>> +
> >>> +&uart0 {
> >>> +	status = "okay";
> >>> +};
> >>> diff --git a/arch/arm64/boot/dts/mediatek/mt6779.dtsi b/arch/arm64/boot/dts/mediatek/mt6779.dtsi
> >>> new file mode 100644
> >>> index 0000000..422ff5f
> >>> --- /dev/null
> >>> +++ b/arch/arm64/boot/dts/mediatek/mt6779.dtsi
> >>> @@ -0,0 +1,265 @@
> >> [...]
> >>> +
> >>> +	uart_clk: dummy26m {
> >>> +		compatible = "fixed-clock";
> >>> +		clock-frequency = <26000000>;
> >>> +		#clock-cells = <0>;
> >>> +	};
> >>
> >> No real clocks for uart? What about CLK_INFRA_UARTx?
> > 
> > sorry, I miss the clocks for uart
> > I'll add "baud" and "bus" in next version.
> > 
> > clocks = <&clk26m>, <&infracfg_ao CLK_INFRA_UART0>;
> > clock-names = "baud", "bus";
> > 
> > 
> >>
> >>> +
> >>> +	timer {
> >>> +		compatible = "arm,armv8-timer";
> >>> +		interrupt-parent = <&gic>;
> >>> +		interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW 0>,
> >>> +			     <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW 0>,
> >>> +			     <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW 0>,
> >>> +			     <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW 0>;
> >>> +	};
> >>> +
> >>> +	soc {
> >>> +		#address-cells = <2>;
> >>> +		#size-cells = <2>;
> >>> +		compatible = "simple-bus";
> >>> +		ranges;
> >>> +
> >> [...]
> >>> +
> >>> +		uart0: serial@11002000 {
> >>> +			compatible = "mediatek,mt6779-uart",
> >>> +				     "mediatek,mt6577-uart";
> >>> +			reg = <0 0x11002000 0 0x400>;
> >>> +			interrupts = <GIC_SPI 115 IRQ_TYPE_LEVEL_LOW>;
> >>> +			clocks = <&uart_clk>;
> >>> +			status = "disabled";
> >>> +		};
> >>> +
> >>> +		uart1: serial@11003000 {
> >>> +			compatible = "mediatek,mt6779-uart",
> >>> +				     "mediatek,mt6577-uart";
> >>> +			reg = <0 0x11003000 0 0x400>;
> >>> +			interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_LOW>;
> >>> +			clocks = <&uart_clk>;
> >>> +			status = "disabled";
> >>> +		};
> >>
> >> SoC has only two UARTs but clock driver has three, how comes?
> >>
> > 
> > In mt6779 SoC, we have four UARTs.
> > but we only use UART0 and UART1 as standard serial ports for APMCU.The
> > others for modem side.
> > so we add two UARTs in dts.
> > 
> 
> Sorry for the late reply.
> 
> DTS describes the HW, so we should add all four to the mt6779.dtsi but only
> enable the one that can be used.
> BTW I thought modem works through user space application, so why don't you want
> to expose them?
> 
> Regards,
> Matthias
> 

Thank you for your comment.

In MT6779 platform, MDMCUs control UART2 and UART3 directly, it doesn't
need any support from apmcu.

but I'll add all four to the mt6779 dtsi to share the info in next
version.(v7)


Thanks
Hanks

> >>> +
> >>> +		audio: clock-controller@11210000 {
> >>> +			compatible = "mediatek,mt6779-audio", "syscon";
> >>> +			reg = <0 0x11210000 0 0x1000>;
> >>> +			#clock-cells = <1>;
> >>> +		};
> >>> +
> >>> +		mfgcfg: clock-controller@13fbf000 {
> >>> +			compatible = "mediatek,mt6779-mfgcfg", "syscon";
> >>> +			reg = <0 0x13fbf000 0 0x1000>;
> >>> +			#clock-cells = <1>;
> >>> +		};
> >>> +
> >>> +		mmsys: clock-controller@14000000 {
> >>> +			compatible = "mediatek,mt6779-mmsys", "syscon";
> >>> +			reg = <0 0x14000000 0 0x1000>;
> >>> +			#clock-cells = <1>;
> >>> +		};
> >>
> >> Please beware that we are refactoring the mmsys right now. Please use this new
> >> approach as this will go upstream soon.
> >>
> >> https://patchwork.kernel.org/project/linux-mediatek/list/?series=254897
> >>
> > Got it, I'll update new approach in next version.
> > Thanks!
> > 
> >> Regards,
> >> Matthias
> >>
> >> _______________________________________________
> >> Linux-mediatek mailing list
> >> Linux-mediatek@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-mediatek
> > 


      reply	other threads:[~2020-06-22 12:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  9:31 [PATCH v5 0/6] Add basic SoC Support for Mediatek MT6779 SoC Hanks Chen
2020-03-25  9:31 ` Hanks Chen
2020-03-25  9:31 ` [PATCH v5 1/6] dt-bindings: pinctrl: add bindings for MediaTek " Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-03-26 16:28   ` Rob Herring
2020-03-26 16:28     ` Rob Herring
2020-03-26 17:43   ` Rob Herring
2020-03-26 17:43     ` Rob Herring
2020-05-28 11:51     ` Hanks Chen
2020-05-28 11:51       ` Hanks Chen
2020-03-25  9:31 ` [PATCH v5 2/6] pinctrl: mediatek: update pinmux definitions for mt6779 Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-04-02 21:54   ` Sean Wang
2020-04-02 21:54     ` Sean Wang
2020-05-28 11:59     ` Hanks Chen
2020-05-28 11:59       ` Hanks Chen
2020-03-25  9:31 ` [PATCH v5 3/6] pinctrl: mediatek: avoid virtual gpio trying to set reg Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-04-02 21:33   ` Sean Wang
2020-04-02 21:33     ` Sean Wang
2020-03-25  9:31 ` [PATCH v5 4/6] pinctrl: mediatek: add pinctrl support for MT6779 SoC Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-03-25 15:05   ` Randy Dunlap
2020-03-25 15:05     ` Randy Dunlap
2020-04-02 21:46   ` Sean Wang
2020-04-02 21:46     ` Sean Wang
2020-05-28 12:34     ` Hanks Chen
2020-05-28 12:34       ` Hanks Chen
2020-03-25  9:31 ` [PATCH v5 5/6] pinctrl: mediatek: add mt6779 eint support Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-03-25  9:31 ` [PATCH v5 6/6] arm64: dts: add dts nodes for MT6779 Hanks Chen
2020-03-25  9:31   ` Hanks Chen
2020-03-25 16:39   ` Matthias Brugger
2020-03-25 16:39     ` Matthias Brugger
2020-06-16 13:34     ` Hanks Chen
2020-06-16 13:34       ` Hanks Chen
2020-06-22 11:25       ` Matthias Brugger
2020-06-22 12:09         ` Hanks Chen [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=1592827766.10773.33.camel@mtkswgap22 \
    --to=hanks.chen@mediatek.com \
    --cc=andy.teng@mediatek.com \
    --cc=cc.hwang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.wang@kernel.org \
    --cc=wsd_upstream@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.