
22 May
2024
22 May
'24
6:08 p.m.
On 5/22/24 1:36 AM, MD Danish Anwar wrote:
Add remoteproc-name property for PRU cores.
Signed-off-by: MD Danish Anwar danishanwar@ti.com
arch/arm/dts/k3-am642-evm-u-boot.dtsi | 44 +++++++++++++++++++++++++++ 1 file changed, 44 insertions(+)
diff --git a/arch/arm/dts/k3-am642-evm-u-boot.dtsi b/arch/arm/dts/k3-am642-evm-u-boot.dtsi index 705b3baa81..25ddace74e 100644 --- a/arch/arm/dts/k3-am642-evm-u-boot.dtsi +++ b/arch/arm/dts/k3-am642-evm-u-boot.dtsi @@ -11,6 +11,50 @@ }; };
+&pru0_0 {
- remoteproc-name = "pru0_0";
Why do we need all these? Looks like we fallback to using `dev->name` if these are not set, does that not work for us here?
Andrew
+};
+&rtu0_0 {
- remoteproc-name = "rtu0_0";
+};
+&tx_pru0_0 {
- remoteproc-name = "tx_pru0_0";
+};
+&pru0_1 {
- remoteproc-name = "pru0_1";
+};
+&rtu0_1 {
- remoteproc-name = "rtu0_1";
+};
+&tx_pru0_1 {
- remoteproc-name = "tx_pru0_1";
+};
+&pru1_0 {
- remoteproc-name = "pru1_0";
+};
+&rtu1_0 {
- remoteproc-name = "rtu1_0";
+};
+&tx_pru1_0 {
- remoteproc-name = "tx_pru1_0";
+};
+&pru1_1 {
- remoteproc-name = "pru1_1";
+};
+&rtu1_1 {
- remoteproc-name = "rtu1_1";
+};
- &main_timer0 { clock-frequency = <200000000>; };