On Fri, Jan 15, 2021 at 9:10 AM Viresh Kumar viresh.kumar@linaro.org wrote:
On 12-01-21, 15:47, Arnd Bergmann wrote:
The acpi_device_id has the same purpose as of_device_id, but uses a different namespace and is only used on PC-style machines.
$ git grep -wl "i2c_driver|spi_driver" drivers sound | wc -l 1424 $ git grep -wl "i2c_driver|spi_driver" drivers sound | xargs git grep -l of_device_id | wc -l 876 $ git grep -wl "i2c_driver|spi_driver" drivers sound | xargs git grep -l acpi_device_id | wc -l 145
I am not sure I follow what we are discussing here, must be something I am missing.
But from my point of view, the guest OS will always use the same i2c driver irrespective of the controller IP used:
drivers/staging/greybus/i2c.c
While the host will keep using the controller specific drivers + something that connects them to the greybus message receiver.
What I'm talking about above is the driver for the i2c slave device that is attached to the i2c controller. We would always just use one i2c controller driver (greybus or virtio) for any slave, but as i2c has no built-in discovery mechanism, the kernel still needs to be told what is attached to it.
Arnd