From: Matthias Brugger <matthias.bgg@gmail.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
sean.wang@kernel.org, linus.walleij@linaro.org,
robh+dt@kernel.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, amit.kucheria@linaro.org
Subject: Re: [PATCH v3 3/4] arm64: dts: mediatek: x20: Add pinmux support for UART1
Date: Thu, 29 Nov 2018 12:49:37 +0100 [thread overview]
Message-ID: <12508cbf-0718-a09f-4061-24a485fd5dc0@gmail.com> (raw)
In-Reply-To: <20181107174844.5381-4-manivannan.sadhasivam@linaro.org>
On 07/11/2018 18:48, Manivannan Sadhasivam wrote:
> Add pinmux support for UART1 on MediatekX20 Development board based
> on Mediatek MT6797 SoC.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts | 2 ++
> arch/arm64/boot/dts/mediatek/mt6797.dtsi | 7 +++++++
> 2 files changed, 9 insertions(+)
>
pushed to v4.20-next/dts64
Thanks!
> diff --git a/arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts b/arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts
> index 742938a1a548..13939d55b85b 100644
> --- a/arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts
> @@ -30,4 +30,6 @@
>
> &uart1 {
> status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart1_pins_a>;
> };
> diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> index 231230d32d09..a64bb84bdec3 100644
> --- a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> @@ -141,6 +141,13 @@
> "iocfgr", "iocfgt";
> gpio-controller;
> #gpio-cells = <2>;
> +
> + uart1_pins_a: uart1 {
> + pins1 {
> + pinmux = <MT6797_GPIO232__FUNC_URXD1>,
> + <MT6797_GPIO233__FUNC_UTXD1>;
> + };
> + };
> };
>
> scpsys: scpsys@10006000 {
>
next prev parent reply other threads:[~2018-11-29 11:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:48 [PATCH v3 0/4] Add initial pinctrl support for MT6797 SoC Manivannan Sadhasivam
2018-11-07 17:48 ` [PATCH v3 1/4] dt-bindings: pinctrl: Add devicetree bindings for MT6797 SoC Pinctrl Manivannan Sadhasivam
2018-11-08 2:11 ` Yingjoe Chen
2018-11-08 4:05 ` Manivannan Sadhasivam
2018-11-15 10:04 ` Linus Walleij
2018-12-03 1:08 ` Matthias Brugger
2018-12-05 12:00 ` Linus Walleij
2018-12-07 18:41 ` Olof Johansson
2018-12-07 21:42 ` Sean Wang
2018-12-11 15:41 ` Olof Johansson
2018-11-07 17:48 ` [PATCH v3 2/4] arm64: dts: mediatek: mt6797: Add pinctrl support Manivannan Sadhasivam
2018-11-15 10:06 ` Linus Walleij
2018-11-29 11:49 ` Matthias Brugger
2018-11-07 17:48 ` [PATCH v3 3/4] arm64: dts: mediatek: x20: Add pinmux support for UART1 Manivannan Sadhasivam
2018-11-15 10:07 ` Linus Walleij
2018-11-29 11:49 ` Matthias Brugger [this message]
2018-11-07 17:48 ` [PATCH v3 4/4] pinctrl: mediatek: Add initial pinctrl driver for MT6797 SoC Manivannan Sadhasivam
2018-11-15 10:06 ` Linus Walleij
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=12508cbf-0718-a09f-4061-24a485fd5dc0@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=amit.kucheria@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.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).