Hi Pavel, On Fri, Jun 16, 2017 at 02:42:42PM +0200, Pavel Machek wrote: > Hi! > > > These types devices aren't directly related to the sensor, but are > > nevertheless handled by the smiapp driver due to the relationship of these > > component to the main part of the camera module --- the sensor. > > > > Additionally, for the async sub-device registration to work, the notifier > > containing matching fwnodes will need to be registered. This is natural to > > perform in a sensor driver as well. > > > > This does not yet address providing the user space with information on how > > to associate the sensor, lens or EEPROM devices but the kernel now has the > > necessary information to do that. > > Do I understand it correctly that basically every sensor driver (in my > case et8ek8) needs to get this kind of support? I2c leds are cheap, > and may be asociated with pretty much any sensor, AFAICT. That's right. > > This is quite a lot of boilerplate for that. Would it make sense to > provide helper function at least for this? Yes. I've been thinking of having helper functions for notifiers and sub-notifiers. Most of the receiver drivers are implementing exactly the same thing but with different twists (read: bugs). -- Regards, Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
