• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: Can the PRU-ICSSG driver be safely disabled in Linux on TDA4VM?

Tiancheng Zhang
Prodigy 190 points
Part Number: TDA4VM

Hi TI Expert

According to TDA4VM datasheet, PRU_ICSSG is not available on TDA4VM.


We are using Linux SDK + RTOS SDK.
I found that PRU_ICSSG node is still defined in Linux dts and driver module loaded when Linux run:

dts: arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
icssg0: icssg@b000000 {
icssg1: icssg@b100000 {


Due to we need to customize Linux to speed up boot,
1.Can I safely disable the PRU_ICSSG driver in the Linux?
2.Is there anything needs to be modified in the RTOS SDK?

SDK version：
ti-processor-sdk-rtos-j721e-evm-08_04_00_06
ti-processor-sdk-linux-j7-evm-08_04_00_11
and
ti-processor-sdk-rtos-j721e-evm-08_06_00_12
ti-processor-sdk-linux-j7-evm-08_06_00_11

Thank you.
BRs

  • 0
    TI__Mastermind 38540 points

    Hi,

    Tiancheng Zhang said:
    .Can I safely disable the PRU_ICSSG driver in the Linux?

    Yes you can safely disable the all the PRU drivers in linux for J7 devices. You can make the change from config itself.

    Tiancheng Zhang said:
    Is there anything needs to be modified in the RTOS SDK?

    In standard linux boot flow, the PRU cores are supposed to be loaded by the remoteproc service running on linux. You can disable remoteproc for PRU. In this case, RTOS is not in the picture, hence RTOS modification not needed.

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    Prodigy 190 points

    Hi Tanmay
    Thank you for quick reply!

    Tanmay Patil said:
    In standard linux boot flow, the PRU cores are supposed to be loaded by the remoteproc service running on linux. You can disable remoteproc for PRU. In this case, RTOS is not in the picture, hence RTOS modification not needed.

    Our boot flow is:
    Boot Flow：tiboot3（SBL）-> can_boot_app_mcu_rtos(MCU1_0) -> lateapp1 (MCU2_0/MCU2_1)
                                                    -> lateapp2(MCU3_0/MCU3_1/C661/C662/C71)
                                                    -> atf_optee.appimage
                                                    -> tikernelimage_linux.appimage
                                                    -> tidtb_linux.appimage

    How about in this startup flow?
    (It seems that the RTOS SDK does not load PRU by default)


    BRs

  • +1 in reply to Tiancheng Zhang
    TI__Mastermind 38540 points

    Hi,

    Tiancheng Zhang said:
    How about in this startup flow?
    (It seems that the RTOS SDK does not load PRU by default)

    In your boot flow, the remoteproc driver of linux itself won't be used. Also RTOS is not loading the PRU. So removing all the PRU related configs from linux kernel / removing the device tree nodes would do the job for you.

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    Prodigy 190 points

    Hi Tanmay
    Thank you very much.