• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 192 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: QSPI probed failed during system bootup on v8.6 of vh

angel angel
Prodigy 50 points
Part Number: TDA4VM
Other Parts Discussed in Thread: TDA4VH

Hi,

We have found below error during system bootup, it seems like the cadence-qspi device have probed failed.And this error have not found on v8.5.

Could you provide patch for this error ?

[    1.222918] cadence-qspi 47040000.spi: error -ENODEV: No Rx DMA available

the bootup log showed as below:

[    1.211550] printk: bootconsole [ns16550a0] disabled
[    1.222786] cadence-qspi 47040000.spi: error -ENODEV: No Rx DMA available
[    1.230277] spi-nor spi1.0: Software reset done, line 3405
[    1.235783] NOR: name:s25sl032p read_id ok
[    1.240327] spi-nor spi1.0: s28hs512t (65536 Kbytes)
[    1.245292] 7 cmdlinepart partitions found on MTD device 47040000.spi.0
[    1.251891] Creating 7 MTD partitions on "47040000.spi.0":
[    1.257364] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[    1.263442] 0x000000080000-0x000000280000 : "ospi.tispl"
[    1.269232] 0x000000280000-0x000000680000 : "ospi.u-boot"
[    1.275115] 0x000000680000-0x0000006c0000 : "ospi.env"
[    1.280726] 0x0000006c0000-0x000000700000 : "ospi.env.backup"
[    1.286932] 0x000000800000-0x000003fc0000 : "ospi.rootfs"
[    1.292804] 0x000003fc0000-0x000004000000 : "ospi.phypattern"
[    1.299010] NOR: spi_nor_probe done
[    1.404906] mmc0: CQHCI version 5.10
[    1.408640] mmc1: CQHCI version 5.10
[    1.412043] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fca100
[    1.419020] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fca100
[    1.425822] omap-mailbox 31f82000.mailbox: omap mailbox rev 0x66fca100
[    1.432623] omap-mailbox 31f83000.mailbox: omap mailbox rev 0x66fca100
[    1.439422] omap-mailbox 31f84000.mailbox: omap mailbox rev 0x66fca100
[    1.446221] omap-mailbox 31f85000.mailbox: omap mailbox rev 0x66fca100
[    1.449430] mmc0: SDHCI controller on 4f80000.mmc [4f80000.mmc] using ADMA 64-bit
[    1.453036] mmc1: SDHCI controller on 4fb0000.mmc [4fb0000.mmc] using ADMA 64-bit
[    1.499712] mmc1: new SDHC card at address aaaa
[    1.504549] mmcblk1: mmc1:aaaa SD32G 29.7 GiB
[    1.510519]  mmcblk1: p1 p2
[    1.534288] mmc0: mmc_select_hs200 failed, error -110
[    1.539336] mmc0: error -110 whilst initialising MMC card
[    1.667862] mmc0: mmc_select_hs200 failed, error -110
[    1.672903] mmc0: error -110 whilst initialising MMC card
[    1.815223] mmc0: mmc_select_hs200 failed, error -110
[    1.820267] mmc0: error -110 whilst initialising MMC card
[    2.004794] mmc0: mmc_select_hs200 failed, error -110
[    2.009835] mmc0: error -110 whilst initialising MMC card

  • 0
    TI__Guru**** 155970 points
    angel angel said:

    We have found below error during system bootup, it seems like the cadence-qspi device have probed failed.And this error have not found on v8.5.

    Could you provide patch for this error ?

    [    1.222918] cadence-qspi 47040000.spi: error -ENODEV: No Rx DMA available

    Hi,

    Are you using the TI TDA4VH EVM or a custom board?
    Can you confirm that this error was not happening on 8.5 SDK & this started on 8.6?

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 50 points

    >>Are you using the TI TDA4VH EVM or a custom board?
    We're using a custom board with reference design.

    >>Can you confirm that this error was not happening on 8.5 SDK & this started on 8.6?

    We could confirm that this error have not found on 8.2 and 8.5 SDK, have found this error on 8.6 only.

    And we have replaced the drivers/dma/ti folder with 8.5 version, then this error was not found again.

  • 0 in reply to angel angel
    TI__Guru**** 155970 points

    Thanks for all the details. We will investigate this internally and get back early next week.

    Regards,

    Keerthy

  • 0 in reply to Keerthy J
    TI__Guru**** 155970 points

    Hi,

    I have reproduced the issue on 8.6 and as per your observations I confirm that once i replace the drivers/dma/ti folder from 8.5 SDK this error goes away.
    I have created an internal ticket. I will keep you posted once I have updates.

    - Keerthy

  • 0 in reply to Keerthy J
    TI__Guru**** 155970 points

    Hi,

    Can you try the below diff:

    diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
index 3f64275a3140..2138bd28bd6d 100644
--- a/drivers/spi/spi-cadence-quadspi.c
+++ b/drivers/spi/spi-cadence-quadspi.c
@@ -2219,6 +2219,8 @@ static int cqspi_request_mmap_dma(struct cqspi_st *cqspi)
        if (IS_ERR(cqspi->rx_chan)) {
                int ret = PTR_ERR(cqspi->rx_chan);
                cqspi->rx_chan = NULL;
+               if (ret == -ENODEV)
+                       ret = -EPROBE_DEFER;
                return dev_err_probe(&cqspi->pdev->dev, ret, "No Rx DMA available\n");
        }
        init_completion(&c

    - Keerthy