On Thu, Sep 05, 2024 at 11:14:58AM -0700, Doug Anderson wrote: > On Thu, Sep 5, 2024 at 8:10 AM Chen-Yu Tsai <wenst@xxxxxxxxxxxx> wrote: > > This next item would be a later enhancement (which isn't implemented in > > this series anyway): > > - optional prober callback that does actual probing > > In our case it would only be used for cases where an HID-over-I2C > > component shares the same address as a non-HID one, and some extra > > work is needed to determine which type it is. I still need to think > > about the structure of this. > IMO _that_ would be a great option to the i2c prober. It feels like > you could have an optional register read that needs to match to have > the i2c prober succeed. Most people would leave it blank (just the i2c > device existing is enough) but probably a single register read would > be enough to confirm you got the right device. Most i2c devices have > some sort of "version" / "vendor" / "id" type register somewhere. I'm not so sure about the "most" there - it depends quite a bit on the class of device. This also imply that the prober would have a regmap config as well...
Attachment:
signature.asc
Description: PGP signature
