Re: [PATCH 2/3] nvmem: Add Sophgo SG2044 eFuse driver

[Chen Wang]

On 10/15/2026 5:03 PM, Inochi Amaoto wrote:
> On Thu, Oct 15, 2026 at 02:43:40PM +0800, Chen Wang wrote:
> > Hello,
> >
> > On 10/14/2026 3:45 PM, Inochi Amaoto wrote:
> > > Sophgo SoCs such as SG2044 contain eFuses used to store
> > > factory-programmed data.
> > >
> > > As for SG2044, HW automatically loads the eFuse content
> > > into shadow registers which are organized as 32bit values
> > > exposed as MMIO.
> > >
> > > Signed-off-by: Inochi Amaoto <inochiama@xxxxxxxxx>
> > > ---
> > >    drivers/nvmem/Kconfig        |  12 +++
> > >    drivers/nvmem/Makefile       |   2 +
> > >    drivers/nvmem/sophgo-efuse.c | 176 +++++++++++++++++++++++++++++++++++
> > >    3 files changed, 190 insertions(+)
> > >    create mode 100644 drivers/nvmem/sophgo-efuse.c
> > >
> > > diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> > > index c36c2a4c2a0b..a7936dd65bdd 100644
> > > --- a/drivers/nvmem/Kconfig
> > > +++ b/drivers/nvmem/Kconfig
> > > @@ -465,6 +465,18 @@ config NVMEM_SNVS_LPGPR
> > >    	  This driver can also be built as a module. If so, the module
> > >    	  will be called nvmem-snvs-lpgpr.
> > > +config NVMEM_SOPHGO_EFUSE
> > > +	tristate "Sophgo eFuse support"
> > > +	depends on ARCH_SOPHGO || COMPILE_TEST
> > > +	default ARCH_SOPHGO
> > > +	help
> > > +	  Say y here to enable support for reading eFuses on Sophgo SoCs
> > > +	  such as the CV1800B. These are e.g. used to store factory programmed
> > Why is "CV1800B"?
> This is an old mistake, this patch follows Jishengs's patch in the first
> design. But then almost everything changed and only thing for SG2044 left.
> This is the thing that is left to change.
>
> I am not sure whether it should keep this generic name as I see it should
> be compatible for most sophgo SoCs (at least it should be for CV1800X,
> by just change offset). Feel free to give if you have some suggestion for
> a better name

I raise this point because the subject of your patch indicates it is 
intended for the SG2044.

If you are simply using it as an example （"such as ..."）, then 
specifying "SG2044" is sufficient, even though, based on your current 
explanation, it would also apply to other Sophgo chips, such as the CV1800X.

> Regards,
> Inochi