On Tue, Dec 13, 2022 at 07:27:01AM -0500, Brian Masney wrote: > We can't add a generic qcom,spidev compatible to the spidev driver since > this is just a software abstraction. Instead, each type of device will > need to have it's own compatible that uniquely describes the type of > device. So you might have a compatible like qcom,spi-video-codec. There > will need to be a DT binding added that describes the hardware. I suspect > that a SPI device can simply be added to trivial-devices.yaml. Once the > DT binding is accepted, the compatible can be added to the spidev.c > driver. If an in-kernel driver is written in the future, then the > compatible can be moved from spidev to the new driver. > Mark: Is my understanding above correct? If so, will it be a problem to > get a compatible added to spidev.c if the corresponding userspace code is > closed source and proprietary? No restriction on what the userspace is.
Attachment:
signature.asc
Description: PGP signature
