Gx Chip Driver -

can occur if status register is not cleared exactly once. 6. Debugging GX Drivers Without Vendor Support 6.1 Tools & Methods | Tool | Purpose | |------|---------| | devmem2 | Read/write raw registers (e.g., devmem2 0xF0000020 ) | | strace | Trace ioctl calls to DRM/V4L2 | | dmesg -w | Watch driver prints (enable with DYNAMIC_DEBUG ) | | cat /sys/kernel/debug/dri/*/state | DRM state | | gdb + KGDB | Kernel debugging over serial | 6.2 Common Errors & Fixes Error: gx_vpu: timeout waiting for interrupt → Check VPU clock (is it enabled?), firmware loaded? Try clk_enable(vpu_clk) .

#define I2C_CON 0x00 #define I2C_TAR 0x04 #define I2C_DATA_CMD 0x10 #define I2C_ENABLE 0x6C static inline void gx_i2c_writel(struct gx_i2c *i2c, u32 val, u32 reg) gx chip driver

Example (display vsync):

gx_mem: allocation failed (size=4194304) → Increase CMA size in bootargs: cma=384M or adjust per-pool sizes in device tree. 7. Device Tree Bindings (Example for GX350) &gx_vpu compatible = "nationalchip,gx350-vpu"; reg = <0x0 0xf1000000 0x0 0x4000>; interrupts = <0 33 4>; clocks = <&clkc GX350_CLK_VPU>, <&clkc GX350_CLK_VPU_AXI>; clock-names = "core", "bus"; firmware-name = "gx_vpu_fw.bin"; memory-region = <&vpu_mem>; ; &gx_disp compatible = "nationalchip,gx350-disp"; reg = <0x0 0xf0000000 0x0 0x2000>; interrupts = <0 25 4>; ports disp_out: endpoint remote-endpoint = <&hdmi_in>; ; ; ; can occur if status register is not cleared exactly once

GX PM is notoriously minimal : only suspend/resume for system sleep, no runtime PM. Causes high idle power. Try clk_enable(vpu_clk)