On Fri, 17 Aug 2018 18:27:20 +0200 Boris Brezillon <boris.brezillon@xxxxxxxxxxx> wrote: > Hi Bartosz, > > On Fri, 10 Aug 2018 10:05:03 +0200 > Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > > From: Alban Bedel <albeu@xxxxxxx> > > > > Allow drivers that use the nvmem API to read data stored on MTD devices. > > For this the mtd devices are registered as read-only NVMEM providers. > > > > Signed-off-by: Alban Bedel <albeu@xxxxxxx> > > [Bartosz: > > - use the managed variant of nvmem_register(), > > - set the nvmem name] > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> > > What happened to the 2 other patches of Alban's series? I'd really > like the DT case to be handled/agreed on in the same patchset, but > IIRC, Alban and Srinivas disagreed on how this should be represented. > I hope this time we'll come to an agreement, because the MTD <-> NVMEM > glue has been floating around for quite some time... These other patches were to fix what I consider a fundamental flaw in the generic NVMEM bindings, however we couldn't agree on this point. Bartosz later contacted me to take over this series and I suggested to just change the MTD NVMEM binding to use a compatible string on the NVMEM cells as an alternative solution to fix the clash with the old style MTD partition. However all this has no impact on the code needed to add NVMEM support to MTD, so the above patch didn't change at all. Alban
Attachment:
pgpKO8VWEs9P1.pgp
Description: OpenPGP digital signature
