Re: [PATCH v5 00/21] nvmem: core: introduce NVMEM layouts

[Srinivas Kandagatla]

Hi Michael/Miquel,

I had to revert Layout patches due to comments from Greg about Making 
the layouts as built-in rather than modules, he is not ready to merge 
them as it is.

His original comment,

"Why are we going back to "custom-built" kernel configurations?  Why can
this not be a loadable module?  Distros are now forced to enable these
layout and all kernels will have this dead code in the tree without any
choice in the matter?

That's not ok, these need to be auto-loaded based on the hardware
representation like any other kernel module.  You can't force them to be
always present, sorry.
"

I have applied most of the patches except

nvmem: core: introduce NVMEM layouts
nvmem: core: add per-cell post processing
nvmem: core: allow to modify a cell before adding it
nvmem: imx-ocotp: replace global post processing with layouts
nvmem: cell: drop global cell_post_process
nvmem: core: provide own priv pointer in post process callback
nvmem: layouts: add sl28vpd layout
MAINTAINERS: add myself as sl28vpd nvmem layout driver
nvmem: layouts: Add ONIE tlv layout driver
MAINTAINERS: Add myself as ONIE tlv NVMEM layout maintainer
nvmem: core: return -ENOENT if nvmem cell is not found
nvmem: layouts: Fix spelling mistake "platforn" -> "platform"
dt-bindings: nvmem: Fix spelling mistake "platforn" -> "platform"
nvmem: core: fix nvmem_layout_get_match_data()

Please rebase your patches on top of nvmem-next once layouts are 
converted to loadable modules.

thanks,
srini



On 03/01/2023 15:39, Miquel Raynal wrote:
> Hi Srinivas,
>
> michael@xxxxxxxx wrote on Tue,  6 Dec 2022 21:07:19 +0100:
>
> > This is now the third attempt to fetch the MAC addresses from the VPD
> > for the Kontron sl28 boards. Previous discussions can be found here:
> > https://lore.kernel.org/lkml/20211228142549.1275412-1-michael@xxxxxxxx/
> >
> >
> > NVMEM cells are typically added by board code or by the devicetree. But
> > as the cells get more complex, there is (valid) push back from the
> > devicetree maintainers to not put that handling in the devicetree.
> >
> > Therefore, introduce NVMEM layouts. They operate on the NVMEM device and
> > can add cells during runtime. That way it is possible to add more complex
> > cells than it is possible right now with the offset/length/bits
> > description in the device tree. For example, you can have post processing
> > for individual cells (think of endian swapping, or ethernet offset
> > handling).
> >
> > The imx-ocotp driver is the only user of the global post processing hook,
> > convert it to nvmem layouts and drop the global post pocessing hook.
> >
> > For now, the layouts are selected by the device tree. But the idea is
> > that also board files or other drivers could set a layout. Although no
> > code for that exists yet.
> >
> > Thanks to Miquel, the device tree bindings are already approved and merged.
> >
> > NVMEM layouts as modules?
> > While possible in principle, it doesn't make any sense because the NVMEM
> > core can't be compiled as a module. The layouts needs to be available at
> > probe time. (That is also the reason why they get registered with
> > subsys_initcall().) So if the NVMEM core would be a module, the layouts
> > could be modules, too.
>
> I believe this series still applies even though -rc1 (and -rc2) are out
> now, may we know if you consider merging it anytime soon or if there
> are still discrepancies in the implementation you would like to
> discuss? Otherwise I would really like to see this laying in -next a
> few weeks before being sent out to Linus, just in case.
>
> Thanks,
> Miquèl