On 05.04.23 15:29, Ricardo Cañuelo wrote: > Hi Martin, > > On lun 27-12-2021 19:00:24, Martin Blumenstingl wrote: >> The dt-bindings for the UART controller only allow the following values >> for Meson6 SoCs: >> - "amlogic,meson6-uart", "amlogic,meson-ao-uart" >> - "amlogic,meson6-uart" >> >> Use the correct fallback compatible string "amlogic,meson-ao-uart" for >> AO UART. Drop the "amlogic,meson-uart" compatible string from the EE >> domain UART controllers. > > KernelCI detected that this patch introduced a regression in > stable-rc/linux-4.14.y on a meson8b-odroidc1. > After this patch was applied the tests running on this platform don't > show any serial output. > > This doesn't happen in other stable branches nor in mainline, but 4.14 > hasn't still reached EOL and it'd be good to find a fix. > > Here's the bisection report: > https://groups.io/g/kernelci-results/message/40147 > > KernelCI info: > https://linux.kernelci.org/test/case/id/64234f7761021a30b262f776/ Wait, what? A patch (5225e1b87432 ("ARM: dts: meson: Fix the UART compatible strings")) that was merged for v5.17-rc4 and is not in the list of patches that were in 4.14.312-rc1 (https://lore.kernel.org/all/20230403140351.636471867@xxxxxxxxxxxxxxxxxxx/ ) is meant to suddenly cause this? How is this possible? Am I totally on the wrong track here and misunderstanding something, or is this a bisection that went horribly sideways? Ciao, Thorsten > Test log: > https://storage.kernelci.org/stable-rc/linux-4.14.y/v4.14.311-43-g88e481d604e9/arm/multi_v7_defconfig/gcc-10/lab-baylibre/baseline-meson8b-odroidc1.html > > Thanks, > Ricardo > > #regzbot introduced: 5225e1b87432dcf0d0fc3440824b91d04c1d6cc1 > #regzbot title: no serial output in KernelCI tests on meson8b-odroidc1 > for stable-4.14 > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
