From: Suman Anna <s-anna@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Bao Cheng Su <baocheng.su@siemens.com>,
Chao Zeng <chao.zeng@siemens.com>,
Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH v4 2/6] arm64: dts: ti: iot2050: Disable SR2.0-only PRUs
Date: Tue, 21 Sep 2021 10:06:19 -0500 [thread overview]
Message-ID: <29a9389f-c27a-9b88-37b8-2de3bf54c37a@ti.com> (raw)
In-Reply-To: <c18b46fcf205074db2bdd6d0f7694f07216fc241.1631708830.git.jan.kiszka@siemens.com>
On 9/15/21 7:27 AM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> The IOT2050 devices described so far are using SR1.0 silicon, thus do
> not have the additional PRUs of the ICSSG of the SR2.0. Disable them.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Acked-by: Aswath Govindraju <a-govindraju@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
> ---
> .../boot/dts/ti/k3-am65-iot2050-common.dtsi | 24 +++++++++++++++++++
> 1 file changed, 24 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 6261ca8ee2d8..58c8e64d5885 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> @@ -716,3 +716,27 @@ &icssg1_mdio {
> &icssg2_mdio {
> status = "disabled";
> };
> +
> +&tx_pru0_0 {
> + status = "disabled";
> +};
> +
> +&tx_pru0_1 {
> + status = "disabled";
> +};
> +
> +&tx_pru1_0 {
> + status = "disabled";
> +};
> +
> +&tx_pru1_1 {
> + status = "disabled";
> +};
> +
> +&tx_pru2_0 {
> + status = "disabled";
> +};
> +
> +&tx_pru2_1 {
> + status = "disabled";
> +};
>
next prev parent reply other threads:[~2021-09-21 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:27 [PATCH v4 0/6] arm64: dts: Update IOT2050 boards Jan Kiszka
2021-09-15 12:27 ` [PATCH v4 1/6] arm64: dts: ti: iot2050: Flip mmc device ordering on Advanced devices Jan Kiszka
2021-09-15 12:27 ` [PATCH v4 2/6] arm64: dts: ti: iot2050: Disable SR2.0-only PRUs Jan Kiszka
2021-09-21 15:06 ` Suman Anna [this message]
2021-09-15 12:27 ` [PATCH v4 3/6] arm64: dts: ti: iot2050: Add/enabled mailboxes and carve-outs for R5F cores Jan Kiszka
2021-09-21 15:11 ` Suman Anna
2021-09-15 12:27 ` [PATCH v4 4/6] dt-bindings: arm: ti: Add bindings for Siemens IOT2050 PG2 boards Jan Kiszka
2021-09-21 21:35 ` Rob Herring
2021-09-15 12:27 ` [PATCH v4 5/6] arm64: dts: ti: iot2050: Prepare for adding 2nd-generation boards Jan Kiszka
2021-09-15 12:27 ` [PATCH v4 6/6] arm64: dts: ti: iot2050: Add support for product generation 2 boards Jan Kiszka
2021-09-22 15:58 ` Nishanth Menon
2021-09-26 11:57 ` Jan Kiszka
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=29a9389f-c27a-9b88-37b8-2de3bf54c37a@ti.com \
--to=s-anna@ti.com \
--cc=a-govindraju@ti.com \
--cc=baocheng.su@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.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).