The qnap-mcu is firmware running on a Weltrend WT61P803 MCU and there is
an eeprom connected to it, that can be read via the serial interface.

The eeprom is somewhat important, as it contains for example the
assigned mac address for the rk3568's gmac interface on TSx33 devices.

So add a nvmem driver for it and hook it into the mfd.


This needs to be applied on top of
commit a141f0ff2548 ("mfd: qnap-mcu: Include linux/types.h in qnap-mcu.h
shared header") to not cause build failures.

changes in v4:
- add missing linux/slab.h include for kzalloc and kfree prototypes

changes in v3:
- rebase on top of 6.18-rc3
- the compile error the kernel-test-robot reported in v2 should've
  fixed itself with the patch applied before 6.18-rc1 .

changes in v2:
- drop binding patch, already applied
- split up nvmem driver and qnap-mcu-mfd subdevice addition (Lee)
- add Srinivas' Ack for the nvmem driver

Heiko Stuebner (2):
  nvmem: Add driver for the eeprom in qnap-mcu controllers
  mfd: qnap-mcu: Hook up the eeprom sub-device

 drivers/mfd/qnap-mcu.c          |   1 +
 drivers/nvmem/Kconfig           |   9 +++
 drivers/nvmem/Makefile          |   2 +
 drivers/nvmem/qnap-mcu-eeprom.c | 111 ++++++++++++++++++++++++++++++++
 4 files changed, 123 insertions(+)
 create mode 100644 drivers/nvmem/qnap-mcu-eeprom.c

-- 
2.47.2

On Tue, 04 Nov 2025 00:29:40 +0100, Heiko Stuebner wrote:
> The qnap-mcu is firmware running on a Weltrend WT61P803 MCU and there is
> an eeprom connected to it, that can be read via the serial interface.
> 
> The eeprom is somewhat important, as it contains for example the
> assigned mac address for the rk3568's gmac interface on TSx33 devices.
> 
> So add a nvmem driver for it and hook it into the mfd.
> 
> [...]

Applied, thanks!

[1/2] nvmem: Add driver for the eeprom in qnap-mcu controllers
      commit: 0cf064be87a6ae0708f171c6b863b26ba9453054

Best regards,
-- 
Srinivas Kandagatla <srini@kernel.org>