From: Apurva Nandan <a-nandan@ti.com> To: Aswath Govindraju <a-govindraju@ti.com> Cc: Marc Kleine-Budde <mkl@pengutronix.de>, Kishon Vijay Abraham I <kishon@ti.com>, Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v5 2/6] arm64: dts: ti: am654-base-board/am65-iot2050-common: Disable mcan nodes Date: Tue, 7 Dec 2021 18:49:50 +0530 [thread overview] Message-ID: <f5e66abb-5c84-eccd-dc7f-333b525fafae@ti.com> (raw) In-Reply-To: <20211122134159.29936-3-a-govindraju@ti.com> On 22/11/21 7:11 pm, Aswath Govindraju wrote: > AM654 base board and iot platforms do not have mcan instances pinned out. > Therefore, disable all the mcan instances. > > Signed-off-by: Aswath Govindraju <a-govindraju@ti.com> Reviewed-by: Apurva Nandan <a-nandan@ti.com> > --- > arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 8 ++++++++ > arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 8 ++++++++ > 2 files changed, 16 insertions(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > index 65da226847f4..1e0112b90d9f 100644 > --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > @@ -646,6 +646,14 @@ > reset-gpios = <&wkup_gpio0 27 GPIO_ACTIVE_HIGH>; > }; > > +&m_can0 { > + status = "disabled"; > +}; > + > +&m_can1 { > + status = "disabled"; > +}; > + > &pcie1_ep { > status = "disabled"; > }; > diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > index cfbcebfa37c1..9043f91c9bec 100644 > --- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > +++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > @@ -416,6 +416,14 @@ > status = "disabled"; > }; > > +&m_can0 { > + status = "disabled"; > +}; > + > +&m_can1 { > + status = "disabled"; > +}; > + > &mailbox0_cluster0 { > interrupts = <436>; >
WARNING: multiple messages have this Message-ID (diff)
From: Apurva Nandan <a-nandan@ti.com> To: Aswath Govindraju <a-govindraju@ti.com> Cc: Marc Kleine-Budde <mkl@pengutronix.de>, Kishon Vijay Abraham I <kishon@ti.com>, Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v5 2/6] arm64: dts: ti: am654-base-board/am65-iot2050-common: Disable mcan nodes Date: Tue, 7 Dec 2021 18:49:50 +0530 [thread overview] Message-ID: <f5e66abb-5c84-eccd-dc7f-333b525fafae@ti.com> (raw) In-Reply-To: <20211122134159.29936-3-a-govindraju@ti.com> On 22/11/21 7:11 pm, Aswath Govindraju wrote: > AM654 base board and iot platforms do not have mcan instances pinned out. > Therefore, disable all the mcan instances. > > Signed-off-by: Aswath Govindraju <a-govindraju@ti.com> Reviewed-by: Apurva Nandan <a-nandan@ti.com> > --- > arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 8 ++++++++ > arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 8 ++++++++ > 2 files changed, 16 insertions(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > index 65da226847f4..1e0112b90d9f 100644 > --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi > @@ -646,6 +646,14 @@ > reset-gpios = <&wkup_gpio0 27 GPIO_ACTIVE_HIGH>; > }; > > +&m_can0 { > + status = "disabled"; > +}; > + > +&m_can1 { > + status = "disabled"; > +}; > + > &pcie1_ep { > status = "disabled"; > }; > diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > index cfbcebfa37c1..9043f91c9bec 100644 > --- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > +++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts > @@ -416,6 +416,14 @@ > status = "disabled"; > }; > > +&m_can0 { > + status = "disabled"; > +}; > + > +&m_can1 { > + status = "disabled"; > +}; > + > &mailbox0_cluster0 { > interrupts = <436>; > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-07 13:20 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 13:41 [PATCH v5 0/6] CAN: Add support for CAN in AM65,J721e and AM64 Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-11-22 13:41 ` [PATCH v5 1/6] arm64: dts: ti: k3-am65-mcu: Add Support for MCAN Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 11:37 ` Apurva Nandan 2021-12-07 11:37 ` Apurva Nandan 2021-11-22 13:41 ` [PATCH v5 2/6] arm64: dts: ti: am654-base-board/am65-iot2050-common: Disable mcan nodes Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 13:19 ` Apurva Nandan [this message] 2021-12-07 13:19 ` Apurva Nandan 2021-11-22 13:41 ` [PATCH v5 3/6] arm64: dts: ti: k3-j721e: Add support for MCAN nodes Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 13:20 ` Apurva Nandan 2021-12-07 13:20 ` Apurva Nandan 2021-11-22 13:41 ` [PATCH v5 4/6] arm64: dts: ti: k3-j721e-common-proc-board: Add support for mcu and main mcan nodes Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 13:20 ` Apurva Nandan 2021-12-07 13:20 ` Apurva Nandan 2021-11-22 13:41 ` [PATCH v5 5/6] arm64: dts: ti: k3-am64-main: Add support for MCAN Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 13:21 ` Apurva Nandan 2021-12-07 13:21 ` Apurva Nandan 2021-11-22 13:41 ` [PATCH v5 6/6] arm64: dts: ti: k3-am642-evm/sk: Add support for main domain mcan nodes in EVM and disable them on SK Aswath Govindraju 2021-11-22 13:41 ` Aswath Govindraju 2021-12-07 13:21 ` Apurva Nandan 2021-12-07 13:21 ` Apurva Nandan 2021-12-15 7:13 ` [PATCH v5 0/6] CAN: Add support for CAN in AM65,J721e and AM64 Vignesh Raghavendra 2021-12-15 7:13 ` Vignesh Raghavendra
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=f5e66abb-5c84-eccd-dc7f-333b525fafae@ti.com \ --to=a-nandan@ti.com \ --cc=a-govindraju@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=kishon@ti.com \ --cc=kristo@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mkl@pengutronix.de \ --cc=nm@ti.com \ --cc=robh+dt@kernel.org \ --cc=vigneshr@ti.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: linkBe 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.