iMX8MM ECSPI not probed in Kirkstone

[dpog]

We recently moved from Yocto Dunfell to Kirkstone and switched the Kernel from 5.4 to 6.0 and 5.15 (we tried both approaches to solve this)

After doing so, the ECSPI is not probed any more in the Kernel boot. Did any changes occur, so that the device tree might not be parsed correctly, or did some Configurations change? 

The working DTS-part from 5.4 looks like this:

&ecspi1 {

    #address-cells = <1>;

    #size-cells = <0>;

    fsl,spi-num-chipselects = <1>;

    pinctrl-names = "default";

    pinctrl-0 = <&pinctrl_ecspi1 &pinctrl_ecspi1_cs>;

    cs-gpios = <&gpio5 9 GPIO_ACTIVE_LOW>;

    status = "okay";

    spidev0: spi@0 {

        reg = <0>;

        compatible = "linux,spidev";

        spi-max-frequency = <10000000>;

    };

};

pinctrl_ecspi1: ecspi1grp {

        fsl,pins = <

            MX8MM_IOMUXC_ECSPI1_SCLK_ECSPI1_SCLK    0x82

            MX8MM_IOMUXC_ECSPI1_MOSI_ECSPI1_MOSI    0x82

            MX8MM_IOMUXC_ECSPI1_MISO_ECSPI1_MISO    0x82

        >;

    };

    pinctrl_ecspi1_cs: ecspi1csgrp {

        fsl,pins = <

            MX8MM_IOMUXC_ECSPI1_SS0_GPIO5_IO9       0x82

        >;

    };

[Dhruvit · Accepted solution]

Hi @dpog,

I hope you are doing well.

This issue seems to be due to compatible string issue in spidev.

In the latest version of spidev.c driver support for the "spidev" compatible string is removed because of the below reason.

spi: spidev: Make probe to fail early if a spidev compatible is used

One can use any other compatible property from spidev_dt_ids[] table in drivers/spi/spidev.c

For example:

  spidev0: spi@0 {

        reg = <0>;

        compatible = "rohm,dh2228fv";

        spi-max-frequency = <10000000>;

    };

Thanks & Regards,

Dhruvit Vasavada