Bug#932845: TS-219 RTC issue with Debian Buster

[Oliver Hartkopp <socketcan@hartkopp.net>]

Package: linux-image-4.19.0-5-marvell
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 97721
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: armel
Source: linux
Version: 4.19.37-5
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | 
linux-initramfs-tool
Recommends: firmware-linux-free, u-boot-tools, apparmor
Suggests: linux-doc-4.19, debian-kernel-handbook
Breaks: flash-kernel (<< 3.57~), initramfs-tools (<< 0.120+deb8u2)
Description: Linux 4.19 for Marvell Kirkwood/Orion
 The Linux kernel 4.19 and modules for use on Marvell Kirkwood and Orion
 based systems (https://wiki.debian.org/ArmEabiPort#Supported_hardware).
Homepage: https://www.kernel.org/



Hi Debian Kernel Team,

I'm running a TS-119P+ and a TS-219P II Qnap NAS with Debian Buster.
Both are now running a linux-image-4.19.0-5-marvell kernel.

But since my update from Linux 4.9 (Stretch) to Linux 4.19 (Buster) the 
hardware clock of both boxes refuse to work.

After some digging in kernel sources and re-installing Linux 4.9 on my 
Buster setup it turns out, that a change in the kernel config causes the 
problem:

4.19.0-5-marvell -> CONFIG_RTC_DRV_S35390A=m   (fails)

4.9.0-4-marvell -> CONFIG_RTC_DRV_S35390A=y    (works)

See details and solving process at:

https://marc.info/?l=linux-arm-kernel&m=156390875629259&w=2

Can you please revert the Kernel config parts for the RTC in a way that 
the RTC drivers are built into the marvell-arch kernel again instead of 
building them as modules?

As described in the referenced description the hwclock tool does not 
work on the machines.

Thanks & best regards,
Oliver