On Mon, Sep 28, 2026 at 06:22:01PM +0200, Maxime Ripard wrote: > Most MIPI-DSI panel drivers follow an identical pattern: acquire > regulators and GPIOs, perform a reset pulse with specific timing, > send a vendor-supplied sequence of DSI commands, then enable the > display. The only truly panel-specific part is the init sequence > and power-on/off timing. > > The panel-mipi-dsi-bpf driver replaces per-panel kernel modules > with a single generic driver whose panel-specific behavior is > provided by BPF programs loaded from userspace at runtime, > following the HID-BPF model. This enables new panel support > without kernel patches. > > Panel DT nodes use a two-entry compatible with the panel-specific > string first and "panel-mipi-dsi-bpf" as fallback. The generic > driver matches on the fallback, while the first compatible is used > to identify which BPF program to load.
If you need the 1st compatible anyways, what is the point of the second one? Also, I assume there is at least some panel supported in the kernel you might want to convert to this. That panel would not have the fallback (and the DT is fixed). And I agree with Neil's comment. At least until we start embedding BPF into DT directly. ;) Rob
