Show me what you mean.and why is the stock overlay for SPI0 doing the same?
spidev delegates the device handling to user space. There can be only what bit of hardware/driver registered for each chip select. If you want to describe the specific hardware attached to a CS so that a dedicated kernel driver can be loaded, you first need to disable the spidev node that uses the same CS (unless you are using one of the "spi<n>-<m>cs" overlays that allows you to disable those chip-selects in advance).
Statistics: Posted by PhilE — Thu Feb 22, 2024 8:04 pm