...
The kernel has been updated from version 5.10 to 6.1. The stable As the basis serves version 6.1.46 and of the real-time stable kernel and version 6.1.46-rt13 serve as the basis.of the real-time kernel. Beside bug fixes and improvements in drivers and subsystems the following has changed:
TPM:
In the current kernel version, the TPM interrupt is now supported, so that the processor load is reduced when using the TPM. In addition, it is now ensured that the TPM chip is correctly taken out of reset and recognized at boot timeremoved from the reset during booting and correctly recognized when loading the driver.
piControl:
The piControl kernel module has been largely reworked to internally use a "Serdev" device registered with the Linux kernel for the RS485 serial port. This has reduced latencies when communicating via the piBridge and shortened cycle times.
RS485:
On the Connect4 and the Flat, there were previously warnings in the log file when RS485 termination was turned on. This problem has now been fixed.
USB:
Fixed a bug in the XHCI controller that could cause an interrupt storm. This caused the processor load to exceed 20 percent for a long time, even if no data was currently going through the USB. Part of the previous functionality has been outsourced to a driver that registers with the Linux kernel as a "serdev" device and handles all communication via RS485 on the PiBridge. By default this driver is already included in the RevPi kernel, so as before only the piControl module needs to be loaded to communicate with the RevPi devices.
When building your own kernel, the driver can be built as an independent kernel module "pibridge.ko". For this the configuration parameter CONFIG_SERIAL_DEV_MUX_PIBRIDGE must be changed from 'y' to 'm' in the kernel configuration. When using the pibridge driver as a standalone kernel module, it must be loaded before loading the piControl module.
By offloading the data traffic on the PiBridge the latencies for the communication with connected RevPi modules have decreased, so that now shorter cycle times are achieved when querying and setting device states.
RTC:
The timestamping feature has been deactivated for the PCF2127. This avoids a hardware error where a bit in one of the RTC interrupt registers was set by mistake during a restart. The errornoues set bit led to a malfunction of the watchdog.