From: Matthias Brugger <matthias.bgg@gmail.com>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Eddie Huang <eddie.huang@mediatek.com>,
Erin Lo <erin.lo@mediatek.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: mt8183-kukui: add scp node
Date: Thu, 10 Sep 2020 12:52:35 +0200 [thread overview]
Message-ID: <161d403a-2a3a-3365-1bb2-5067e8fb7cb8@gmail.com> (raw)
In-Reply-To: <20200909081422.2412795-1-pihsun@chromium.org>
On 09/09/2020 10:14, Pi-Hsun Shih wrote:
> Add scp node to mt8183-kukui
>
> Fixes: 0d5e41709f76 ("arm64: dts: mt8183: add scp node")
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
Applied to v5.9-next/dts64
I squashed this fix with the first patch to maintain bisectability.
Thanks!
> ---
>
> Change since v1:
> * Add Fixes tag.
>
> ---
> .../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi b/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi
> index f0a070535b34..85f7c33ba446 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi
> @@ -90,6 +90,18 @@ pp3300_alw: regulator6 {
> regulator-max-microvolt = <3300000>;
> };
>
> + reserved_memory: reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + scp_mem_reserved: scp_mem_region {
> + compatible = "shared-dma-pool";
> + reg = <0 0x50000000 0 0x2900000>;
> + no-map;
> + };
> + };
> +
> max98357a: codec0 {
> compatible = "maxim,max98357a";
> sdmode-gpios = <&pio 175 0>;
> @@ -524,6 +536,13 @@ pins_clk {
> };
> };
>
> + scp_pins: scp {
> + pins_scp_uart {
> + pinmux = <PINMUX_GPIO110__FUNC_TP_URXD1_AO>,
> + <PINMUX_GPIO112__FUNC_TP_UTXD1_AO>;
> + };
> + };
> +
> spi0_pins: spi0 {
> pins_spi{
> pinmux = <PINMUX_GPIO85__FUNC_SPI0_MI>,
> @@ -651,6 +670,17 @@ pins_wifi_wakeup {
> };
> };
>
> +&scp {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&scp_pins>;
> +
> + cros_ec {
> + compatible = "google,cros-ec-rpmsg";
> + mtk,rpmsg-name = "cros-ec-rpmsg";
> + };
> +};
> +
> &soc_data {
> status = "okay";
> };
>
prev parent reply other threads:[~2020-09-10 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:14 Pi-Hsun Shih
2020-09-09 8:57 ` Matthias Brugger
2020-09-10 5:33 ` Pi-Hsun Shih
2020-09-10 10:52 ` 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=161d403a-2a3a-3365-1bb2-5067e8fb7cb8@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=pihsun@chromium.org \
--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
all inboxes | Powered by JetHome®