Hi Maxime,
On Mon, Mar 4, 2024 at 11:20 AM Maxime Ripard mripard@kernel.org wrote:
On Mon, Mar 04, 2024 at 11:07:22AM +0100, Geert Uytterhoeven wrote:
On Mon, Mar 4, 2024 at 10:15 AM Maxime Ripard mripard@kernel.org wrote:
On Mon, Mar 04, 2024 at 09:12:38AM +0100, Geert Uytterhoeven wrote:
On Sun, Mar 3, 2024 at 10:30 AM Geert Uytterhoeven geert@linux-m68k.org wrote: ERROR: modpost: "__udivdi3" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined! make[3]: *** [scripts/Makefile.modpost:145: Module.symvers] Error 1 make[2]: *** [Makefile:1871: modpost] Error 2 make[1]: *** [Makefile:240: __sub-make] Error 2 make: *** [Makefile:240: __sub-make] Error 2
No warnings found in log. ------------------------------------------------------------------->8---
The driver is meant for a controller featured in an SoC with a Cortex-A8 ARM CPU and less than a GiB/s memory bandwidth.
Good, so the hardware cannot possibly need 64-bit pixel clock values ;-)
This is an early patch to convert that function into a framework hook implementation. HDMI 2.1 has a max TMDS character rate of slightly less than 6GHz, so larger than 2^32 - 1.
So yes, this driver doesn't need to. The framework does however.
That's gonna be interesting, as the Common Clock Framework does not support 64-bit clock rates on 32-bit platforms yet...
Gr{oetje,eeting}s,
Geert