2018-06-26 15:38 GMT+02:00 Bartosz Golaszewski <brgl@xxxxxxxx>: > 2018-06-26 15:21 GMT+02:00 Andrew Lunn <andrew@xxxxxxx>: >>> I see. I see it this way: the setup callback comes from the time when >>> we didn't have nvmem and should go away. I will protest loud whenever >>> someone will try to use it again and will work towards removing it as >>> soon as possible. >> >> The setup() callback could be moved into the nvmem framework, rather >> than in the at24 driver. Make the call when the cells have been >> connected to the backing store. >> > > This would at least make it more generic. And maybe I could also get > rid of the setup callback from the mityomapl138 board file. > > Bart > >>> I will give your problem a thought and will try to get back with some >>> proposals - maybe we should, as you suggested, extend nvmem even >>> further to allow to remove nvmem info entries etc. >> >> That does not help me too much. I have the same problem with i2c and >> MDIO. So i actually prefer to keep this the same as all others. >> >> Andrew Hi Andrew, MTD subsystem has the struct mtd_notifier and register_mtd_user(). I'm wondering if we could implement something like this as a generic nvmem functionality. What do you think? Bart -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
