Open Source Summit India 2026

Modern embedded audio devices increasingly run mainline Linux, but achieving deterministic low-latency multi-channel audio processing remains a challenge. While heterogeneous SoCs include DSP accelerators capable of handling signal processing workloads efficiently, integrating these accelerators into a standard Linux audio stack without proprietary middleware is non-trivial.
This talk presents a practical, upstream-friendly approach to building a zero-copy DSP offload framework using mainline Linux components such as remoteproc, rpmsg, and ALSA. Instead of relying on custom kernel patches or vendor-specific frameworks, the solution leverages DMA-backed shared memory and rpmsg-based signaling to enable efficient inter-processor communication between ARM application cores and a DSP.
A key focus of this session is eliminating redundant memory copies across kernel and user space boundaries. By designing a ping-pong buffer architecture with shared memory mapping and pointer-based synchronization, we achieved deterministic real-time streaming with significantly reduced CPU utilization and improved latency characteristics.

Practical guide to writing Devicetree sources (DTS) and bindings for the Linux kernel. Jump in if you want to know:
1. What compatibility means between devices and how to express it in DTS.
2. What can be in DTS and what cannot.
3. Fastest way to upstream your DTS (no need for 10 iterations!).
4. Validate your DTS and live error-free ever after.

The talk will focus on Devicetree (DTS and bindings) in the context of Linux kernel, which is also applicable to several other projects like U-boot.

Connected medical devices (IoMT) increasingly depend on Yocto‑based Embedded Linux platforms to perform critical, patient‑impacting functions. As cyberattacks on healthcare rise, securing these devices is now central to patient safety, regulatory compliance, and lifecycle quality. This session provides a practical, defense‑in‑depth blueprint for hardening IoMT devices—starting from secure boot and measured trust to OS‑level hardening, system integrity, secure OTA updates, sandboxing, runtime protection, and zero‑trust device‑to‑cloud communication.
We will map real‑world cyber trends to specific embedded mitigations and align them with global regulatory expectations for medical devices. The session also demonstrates how open‑source tools within the Yocto ecosystem can enforce reproducible security controls, generate SBOMs, and support automated vulnerability triage throughout the device lifecycle.
Attendees will gain engineering‑ready patterns to build secure, maintainable Linux‑based devices—applicable not only in healthcare, but also industrial IoT, automotive, and safety‑critical embedded domains.

Zephyr is officially 10 years old and many silicon manufacturers are moving towards it as a de-facto RTOS. With over 3000+ contributors and 15,000+ commits per release, Zephyr is one of the fastest moving open source RTOS projects today.
Linumiz is a software partner with silicon manufacturers like Infineon and Texas Instruments, maintaining open source downstream Zephyr releases for their customers. This involves backporting bug fixes, security fixes, rebasing, and moving to new release cycles to keep up with Zephyr's upstream development pace.
In this talk, I will walk through how we manage these downstream releases and cope with upstream pace - what works, what doesn't, and what product developers should keep in mind when building long-term products on Zephyr.

Ten years ago, the Zephyr Project set out to build an open, scalable real-time operating system for connected and resource-constrained devices. Today, Zephyr powers a rapidly growing ecosystem spanning IoT, industrial systems, automotive platforms, and edge computing.

This session celebrates Zephyr’s first decade and explores what has driven its success—from technical architecture and open governance to a vibrant global contributor community. Drawing on insights from a new Linux Foundation Research study, the discussion will highlight key milestones, ecosystem growth, and the forces shaping Zephyr’s future.

In this session, we’ll explore:

-The Zephyr features that are most valued
-How open collaboration accelerates RTOS innovation
-Growth of the global Zephyr developer ecosystem
-Real-world Zephyr practitioner use cases & insights

Key questions:
-How is Zephyr being used across embedded products?
-What are the defining features of Zephyr that have contributed to its adoption?
-What are the attributes of the Zephyr community that contribute to the project's growth and health?

Cameras are no longer just for pictures, they are now real-time data pipelines that send information to ISPs, NPUs, and control logic. This is because edge AI is becoming a most wanted vision systems. Zephyr is good at deterministic embedded control, but AI-driven camera workloads need new architectural features like zero-copy buffer sharing, accelerator coordination, bounded latency, metadata synchronization, and controlled backpressure.

This talks about what needs to change in Zephyr's camera and driver architecture to make AI vision work in the real world. Based on our experience with Linux media pipelines and setting up embedded cameras, we look at where traditional RTOS-style camera models fail and what simple abstractions are needed to make them work without adding too much complexity.

The goal is not to make Linux features equal, but to make the architecture better. This includes designing pipelines, structuring buffer ownership, making streaming states more predictable, and making things easier to see. The goal is to keep Zephyr lightweight while also allowing robotics, industrial, and mission-critical systems to work with the next generation of AI cameras.

This session compares how camera support is built in the Zephyr Project and in the Linux kernel camera subsystem.

Zephyr focuses on real-time behavior, low memory usage, and simple system design, making it suitable for small, low-power vision devices. Linux, through frameworks such as Video4Linux2 and the Media Controller subsystem, provides a more structured and scalable approach capable of handling complex camera pipelines, multiple cameras, and advanced processing.

The session examines architectural trade offs between the two camera subsystems, comparing their design approaches and highlighting differences in driver structure, pipeline design, and overall system integration. It also explores how Zephyr’s camera architecture can evolve to support more advanced and scalable vision needs, moving closer to Linux capabilities.