Exynos 3830 - Driver Work

The Exynos 3830 is a Samsung SoC used in several devices (ARM Cortex-A15/A7 big.LITTLE). Writing or maintaining drivers for it means working across kernel device support (clock, power, interconnect, memory controller), SoC-specific peripherals (GIC, UART, MMC/EMMC, USB, GPU/3D, display controller), and platform integration (device tree, power domains, suspend/resume). Below is a concise, actionable guide for driver development and debugging targeted at Linux kernel drivers for Exynos 3830-based platforms.

With clocks semi-stable, the next wall was the GPIO controller.

The Exynos 3830 uses a pinctrl driver similar to the exynos5420 but with fewer banks. However, the interrupt controller is broken. The EINT (External Interrupt) handling on this chip is notoriously glitchy. exynos 3830 driver work

If you enable an interrupt on GPA2, it sometimes fires on GPA0. This is bad for buttons or touchscreens.

The fix: I had to disable the "wakeup" interrupt mask until after suspend-resume is fully initialized. In the vendor kernel, they added a 5ms delay in the interrupt handler (a dirty hack). I opted to rewrite the eint_gpio_irq map to use a linear mapping instead of the hierarchical one used by newer Exynos chips. The Exynos 3830 is a Samsung SoC used

Result? Buttons work. The touchpad on the test device (a Galaxy Tab 3 Lite) now responds.

The most intense driver development is around the GPU. The Exynos 3830 utilizes an ARM Mali GPU. Driver work is currently focused on: With clocks semi-stable, the next wall was the

If you are a developer or enthusiast interested in reviving an old Samsung tablet, track these repositories and lists: