On 10/09/18 13:22, Bartosz Golaszewski wrote:
While one can argue that nvmem_device_cell_read/write() may be needed in some strange corner case now, once we add the cell lookup API, we can safely remove it and force users to do the right thing.
I agree!I don't have very strong reason to stop removing nvmem_device_cell_read/write().
Lets see how it turns out! I would still want nvmem config to have ability to setup static cell list. --srini
