Linux Kernel · Android BSP · Camera / ISP · Edge AI
"The best way to predict the future is to invent it." — Alan Kay
struct engineer biren = {
.years = 15,
.path = "bare-metal → camera architecture → upstream",
.happy_when = "the flaky repro finally triggers",
.pet_peeve = "a manual mutex_unlock left in an error path",
.current_mood = "reaching for edge AI & robotics",
};I work the whole stack — kernel → drivers → DMA → V4L2/ISP → HAL3 → framework. But the interesting bugs don't live inside a layer. They live in the seams between them. That's where I'm useful.
Transition-window corruption in stateful pipelines. The instant a system switches configuration — zoom ratio, sensor mode, power state, buffer ownership — is the instant its coherence assumptions quietly break. Find the seam, find the bug.
- 🐧 Kernel & drivers — kernel internals, device drivers, DMA-BUF, runtime PM, Device Tree, Binder, SELinux
- 📷 Camera & imaging — Camera HAL3 / Camera2, V4L2 & media controller, ISP pipeline, sensor bring-up, MIPI CSI-2, 3A
- 🧱 Platform & system — Android BSP / AOSP, board bring-up, Treble, boot-time / power / performance tuning, system architecture
- 🤖 Edge — embedded vision, on-device inference, the front half of a robot's perception stack
Silicon I've shipped on:
Qualcomm Snapdragon · Samsung Exynos · MediaTek · Broadcom · TI OMAP · NXP i.MX
Active upstream contributor, with patches across Media (V4L2), I²C, IIO, DRM, and Android Binder — runtime-PM leaks, use-after-free, race conditions, resource-lifetime and subsystem cleanup. Plus a filed camera-imaging patent (under examination) for real-time smart-composition and duplicate detection.
Kernel upstream work · AI accelerators (GPU / NPU) · embedded vision & Physical AI · robotics software stack · Android Automotive (AAOS)
My career recapitulates the boot order. I started at the metal and grew upward, layer by layer, until I was architecting the top of the pipeline. That's why I can chase a problem from a sensor's I²C register all the way to the HAL — and actually find where it breaks.
▲
│ 15 years climbing the stack — metal → architecture
│
┌───────────────────────────────────────────────────────────────────────────────┐
│ APPLICATION · IMAGING ARCHITECTURE │
│ Camera HAL3 · multi-camera · Night Mode/HDR · 3A · bring-up automation │
│ Samsung R&D · 2022-present │
└───────────────────────────────────────────────────────────────────────────────┘
│
┌───────────────────────────────────────────────────────────────────────────────┐
│ FRAMEWORK · MULTIMEDIA │
│ Android TV framework · ALSA/TIF/S-PDIF · camera HAL porting · certs │
│ Vantiva · LeEco · Zebra · 2016-2022 │
└───────────────────────────────────────────────────────────────────────────────┘
│
┌───────────────────────────────────────────────────────────────────────────────┐
│ KERNEL · RF · PROTOCOL STACKS │
│ board bring-up · LTE RFFE · RRC/NAS/IMS · USB peripherals · factory tools │
│ Motorola · 2013-2016 │
└───────────────────────────────────────────────────────────────────────────────┘
│
┌───────────────────────────────────────────────────────────────────────────────┐
│ DEVICE DRIVERS · BOARD BRING-UP │
│ drivers + HAL (AM3517) · bootloader/board-config · display, touch, PMIC, GPIO │
│ 3Di · Motorola Mobility · 2011-2013 │
└───────────────────────────────────────────────────────────────────────────────┘
│
┌───────────────────────────────────────────────────────────────────────────────┐
│ BARE METAL │
│ 8/16/32-bit MCUs · OMAP/i.MX/Cortex-M bring-up · LCD, touch, RFID, GSM │
│ Edutech · 2010-2011 │
└───────────────────────────────────────────────────────────────────────────────┘
│
○ started here (2010)
Now the arc loops back: contributing down into the kernel core upstream, while reaching forward into edge AI and robotics — where this same sensor-to-compute pipeline becomes a machine's perception.
📍 Bengaluru, India · 🔗 linkedin.com/in/pbiren · curious, always, about where hardware and software meet.