On Tue, Nov 17, 2015 at 10:14:27AM -0300, Javier Martinez Canillas wrote: > On 11/16/2015 06:51 PM, Brian Norris wrote: > > Lest someone else wonder whether this is theoretical or not, I'll save > > them the work in pointing at an example: "st,st33zp24". See: > > Documentation/devicetree/bindings/security/tpm/st33zp24-*.txt > > and the code is in drivers/char/tpm/st33zp24/, sharing the same core > > library, suggesting that the devices really are the same except simply > > the bus. > Thanks for pointing out that example although for that specific case, > the drivers' compatible are "st,st33zp24-i2c" and "st,st33zp24-spi" to > avoid the issue explained before. Eew, that's gross. > I still didn't find an example where the same compatible string is > used for different drivers (i.e: "st,st33zp24" or "google,cros-ec") > but the fact that is possible for legacy and not for OF is worrisome. There's a bunch of audio CODEC and PMIC drivers, arizona is the first example that springs to mind but it's very common to have mixed signal devices devices which can run in both I2C and SPI modes.
Attachment:
signature.asc
Description: PGP signature
