public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: Nishanth Menon <nm@ti.com>, Garrett Giordano <ggiordano@phytec.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<r-gunasekaran@ti.com>, <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<upstream@lists.phytec.de>
Subject: Re: [PATCH] arm64: dts: ti: phycore-am64: Add R5F DMA Region and Mailboxes
Date: Fri, 3 Nov 2023 10:00:11 +0100	[thread overview]
Message-ID: <5effa700-480b-4030-8335-304ebc4444b7@phytec.de> (raw)
In-Reply-To: <20231103001707.2ktwfgtqegpfiijy@subpanel>

Hi Nishanth,

Am 03.11.23 um 01:17 schrieb Nishanth Menon:
> On 13:12-20231102, Garrett Giordano wrote:
>> Communication between the R5F subsystem and Linux takes place using DMA
>> memory regions and mailboxes. Here we add DT nodes for the memory
>> regions and mailboxes to facilitate communication between the R5
>> clusters and Linux as remoteproc will fail to start if no memory
>> regions or mailboxes are provided.
>>
>> Fixes: c48ac0efe6d7 ("arm64: dts: ti: Add support for phyBOARD-Electra-AM642")
> is this fixes? Sounds more or less like rproc support is added in?

I would say it is also a fix, as the R5 cores are enabled by default at 
the SoC level devicetree and also require mboxes & memory regions to be 
configured. The docs mention both as mandatory.

Otherwise, we will encounter errors such as

   platform 78000000.r5f: device does not have reserved memory regions, 
ret = -22

Regards,
Wadim

>
>> Signed-off-by: Garrett Giordano <ggiordano@phytec.com>
>> ---
>>   .../boot/dts/ti/k3-am64-phycore-som.dtsi      | 102 +++++++++++++++++-
>>   1 file changed, 101 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi b/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> index 1c2c8f0daca9..37a33006c1fc 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> @@ -29,7 +29,7 @@ memory@80000000 {
>>   		reg = <0x00000000 0x80000000 0x00000000 0x80000000>;
>>   	};
>>   
>> -	reserved-memory {
>> +	reserved_memory: reserved-memory {
>>   		#address-cells = <2>;
>>   		#size-cells = <2>;
>>   		ranges;
>> @@ -39,6 +39,54 @@ secure_ddr: optee@9e800000 {
>>   			alignment = <0x1000>;
>>   			no-map;
>>   		};
>> +
>> +		main_r5fss0_core0_dma_memory_region: r5f-dma-memory@a0000000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa0000000 0x00 0x100000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss0_core0_memory_region: r5f-memory@a0100000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa0100000 0x00 0xf00000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss0_core1_dma_memory_region: r5f-dma-memory@a1000000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa1000000 0x00 0x100000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss0_core1_memory_region: r5f-memory@a1100000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa1100000 0x00 0xf00000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss1_core0_dma_memory_region: r5f-dma-memory@a2000000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa2000000 0x00 0x100000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss1_core0_memory_region: r5f-memory@a2100000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa2100000 0x00 0xf00000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss1_core1_dma_memory_region: r5f-dma-memory@a3000000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa3000000 0x00 0x100000>;
>> +			no-map;
>> +		};
>> +
>> +		main_r5fss1_core1_memory_region: r5f-memory@a3100000 {
>> +			compatible = "shared-dma-pool";
>> +			reg = <0x00 0xa3100000 0x00 0xf00000>;
>> +			no-map;
>> +		};
>>   	};
>>   
>>   	leds {
>> @@ -160,6 +208,34 @@ &cpsw_port2 {
>>   	status = "disabled";
>>   };
>>   
>> +&mailbox0_cluster2 {
>> +	status = "okay";
>> +
>> +	mbox_main_r5fss0_core0: mbox-main-r5fss0-core0 {
>> +		ti,mbox-rx = <0 0 2>;
>> +		ti,mbox-tx = <1 0 2>;
>> +	};
>> +
>> +	mbox_main_r5fss0_core1: mbox-main-r5fss0-core1 {
>> +		ti,mbox-rx = <2 0 2>;
>> +		ti,mbox-tx = <3 0 2>;
>> +	};
>> +};
>> +
>> +&mailbox0_cluster4 {
>> +	status = "okay";
>> +
>> +	mbox_main_r5fss1_core0: mbox-main-r5fss1-core0 {
>> +		ti,mbox-rx = <0 0 2>;
>> +		ti,mbox-tx = <1 0 2>;
>> +	};
>> +
>> +	mbox_main_r5fss1_core1: mbox-main-r5fss1-core1 {
>> +		ti,mbox-rx = <2 0 2>;
>> +		ti,mbox-tx = <3 0 2>;
>> +	};
>> +};
>> +
>>   &main_i2c0 {
>>   	status = "okay";
>>   	pinctrl-names = "default";
>> @@ -180,6 +256,30 @@ i2c_som_rtc: rtc@52 {
>>   	};
>>   };
>>   
>> +&main_r5fss0_core0 {
>> +	mboxes = <&mailbox0_cluster2 &mbox_main_r5fss0_core0>;
>> +	memory-region = <&main_r5fss0_core0_dma_memory_region>,
>> +			<&main_r5fss0_core0_memory_region>;
>> +};
>> +
>> +&main_r5fss0_core1 {
>> +	mboxes = <&mailbox0_cluster2 &mbox_main_r5fss0_core1>;
>> +	memory-region = <&main_r5fss0_core1_dma_memory_region>,
>> +			<&main_r5fss0_core1_memory_region>;
>> +};
>> +
>> +&main_r5fss1_core0 {
>> +	mboxes = <&mailbox0_cluster4 &mbox_main_r5fss1_core0>;
>> +	memory-region = <&main_r5fss1_core0_dma_memory_region>,
>> +			<&main_r5fss1_core0_memory_region>;
>> +};
>> +
>> +&main_r5fss1_core1 {
>> +	mboxes = <&mailbox0_cluster4 &mbox_main_r5fss1_core1>;
>> +	memory-region = <&main_r5fss1_core1_dma_memory_region>,
>> +			<&main_r5fss1_core1_memory_region>;
>> +};
>> +
>>   &ospi0 {
>>   	status = "okay";
>>   	pinctrl-names = "default";
>> -- 
>> 2.25.1
>>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-11-03  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231102201216.3771589-1-ggiordano@phytec.com>
2023-11-03  0:17 ` [PATCH] arm64: dts: ti: phycore-am64: Add R5F DMA Region and Mailboxes Nishanth Menon
2023-11-03  9:00   ` Wadim Egorov [this message]
2023-12-04 13:44     ` Nishanth Menon
2023-12-04 21:23 Garrett Giordano
2023-12-05 17:26 ` Wadim Egorov
2023-12-06 16:02 ` Nishanth Menon

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=5effa700-480b-4030-8335-304ebc4444b7@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ggiordano@phytec.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=r-gunasekaran@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=upstream@lists.phytec.de \
    --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: 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