From: Matthias Brugger <matthias.bgg@gmail.com>
To: matthias.bgg@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH] arm64: dts: Add uart for mt6797 EVB
Date: Thu, 29 Nov 2018 12:50:07 +0100 [thread overview]
Message-ID: <4a28375f-7487-f745-5d05-e2bc4c939369@gmail.com> (raw)
In-Reply-To: <20181116183040.18696-1-matthias.bgg@kernel.org>
On 16/11/2018 19:30, matthias.bgg@kernel.org wrote:
> From: Matthias Brugger <mbrugger@suse.com>
>
> This patch adds the pinctrl configuration for the mt6797 EVB.
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
> ---
> arch/arm64/boot/dts/mediatek/mt6797-evb.dts | 2 ++
> arch/arm64/boot/dts/mediatek/mt6797.dtsi | 7 +++++++
> 2 files changed, 9 insertions(+)
>
pushed to v4.20-next/dts64
> diff --git a/arch/arm64/boot/dts/mediatek/mt6797-evb.dts b/arch/arm64/boot/dts/mediatek/mt6797-evb.dts
> index c79109c65409..237e869a5fa1 100644
> --- a/arch/arm64/boot/dts/mediatek/mt6797-evb.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt6797-evb.dts
> @@ -33,4 +33,6 @@
>
> &uart0 {
> status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart0_pins_a>;
> };
> diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> index a64bb84bdec3..2b2a69c7567f 100644
> --- a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
> @@ -142,6 +142,13 @@
> gpio-controller;
> #gpio-cells = <2>;
>
> + uart0_pins_a: uart0 {
> + pins0 {
> + pinmux = <MT6797_GPIO234__FUNC_UTXD0>,
> + <MT6797_GPIO235__FUNC_URXD0>;
> + };
> + };
> +
> uart1_pins_a: uart1 {
> pins1 {
> pinmux = <MT6797_GPIO232__FUNC_URXD1>,
>
prev parent reply other threads:[~2018-11-29 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 18:30 [PATCH] arm64: dts: Add uart for mt6797 EVB matthias.bgg
2018-11-29 11:50 ` 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=4a28375f-7487-f745-5d05-e2bc4c939369@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=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=robh+dt@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).