You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's I original ticket posting from several years ago.
The driver for the Linux-4.4.6 kernel supplied with the 'trunk' source code, gives the following message when the eSPI driver is initialized.
Kernel boot printk's...
spidev spi32766.0: buggy DT: spidev listed directly in DT
Upon looking into this apparently this diagnostic was added for some reason which seems to be impossible to find.
In any case, the 'solution' that was proposed in one of the messages I found discussing the problem was to 'modify the driver' to accept the spi device in question... which in my opinion corrupts the whole business of the Device Tree, and no other description was give on how to correct the Device Tree to match someone's expectation of what it should be.
The irony is that when I ignore the error message, the devices are entered in to the /dev/spidevX.Y correctly
When I remove the offending 'spidev' compatibility tag, the instances fail to appear.
The text was updated successfully, but these errors were encountered:
jeclark20006:
Here's I original ticket posting from several years ago.
The driver for the Linux-4.4.6 kernel supplied with the 'trunk' source code, gives the following message when the eSPI driver is initialized.
Kernel boot printk's...
spidev spi32766.0: buggy DT: spidev listed directly in DT
Upon looking into this apparently this diagnostic was added for some reason which seems to be impossible to find.
In any case, the 'solution' that was proposed in one of the messages I found discussing the problem was to 'modify the driver' to accept the spi device in question... which in my opinion corrupts the whole business of the Device Tree, and no other description was give on how to correct the Device Tree to match someone's expectation of what it should be.
The irony is that when I ignore the error message, the devices are entered in to the /dev/spidevX.Y correctly
When I remove the offending 'spidev' compatibility tag, the instances fail to appear.
The text was updated successfully, but these errors were encountered: