From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 687E7CA5FA2 for ; Mon, 28 Sep 2026 20:41:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=NLW0Xvdr0NdDdNm3pJOiMfwy/Xm72khh3QPraAupQ7Y=; b=d85qPC1MsyEGzT2BT73JpWxFEB WJdTml8Sy18+c14rbmbH9nVOTTZW7lxCj7UVi/WV4H+ayxtWdCQtgFtE8O+4NnrSuxbNieN4pY/9G gcKURHbZw5EjOkjtrbpHiWIfWLEZaq3hYaZLJ+rm0oAcMdfHp/InEj0YE3qstc3ohgqQxdOp6ePKg ZzqkiO1MSRuWhZ1vD0t2AV+bAzZ3u/4Bgp3a4nAL9C4OWeb1gMFWQ4tJ1XGE9Kb+RhUMU3A/l462x fhfzXMA0dfUAfgx5vrUnOu/lTYkQBGVDdqsDS/aoCs9odcJzSkEQRpg7JB8Zbx4QHakkStGVF5dLD dvpHdwZA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBI9n-00000001akP-2aBi; Mon, 28 Sep 2026 20:41:03 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBI9m-00000001ak7-421o; Mon, 28 Sep 2026 20:41:02 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 310FA43D23; Mon, 28 Sep 2026 20:41:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C6D5E1F00898; Mon, 28 Sep 2026 20:41:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790628062; bh=NLW0Xvdr0NdDdNm3pJOiMfwy/Xm72khh3QPraAupQ7Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=egMXFZSFJB8mIyXxncXKqSPcoR7YjAGqoqd1U9D9l0YRxjjUjZRzlxCONoBn5oAms I3tRdMjjkNFhoZqWIMId7vW1XmU2yi/unDIg2XY2LRHTGafQ0aMZzjp/rhfkoWUxEE o5wMXTad/9D4Rpwpgmh+Qk4aCNKVo01HPLlEuOJ6/XrVZ4LSxVdoWg8TnYbkI/fOOy 60ouPKeoRXjipb+i/MjB2mtzMDzpfGvVnNjGhosiUNudr8tV9mW0dYhdFNl8cfY80z LsCuhOsxDNHPMzD6WhRGaJSSg54X96OQq2mD2UAvdeYavujR8brUKcWIi0e5IyyuoN TKXUO1R/PMAdQ== Date: Mon, 28 Sep 2026 15:40:59 -0500 From: Rob Herring To: Maxime Ripard Cc: Neil Armstrong , Jessica Zhang , David Airlie , Simona Vetter , Maarten Lankhorst , Thomas Zimmermann , Krzysztof Kozlowski , Conor Dooley , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , Florian Fainelli , Broadcom internal kernel review list , Andrzej Hajda , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Luca Ceresoli , Albert Esteve , Dave Stevenson , Javier Martinez Canillas , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org, llvm@lists.linux.dev, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Benjamin Tissoires Subject: Re: [PATCH 1/6] dt-bindings: display: Add panel-mipi-dsi-bpf generic panel binding Message-ID: <20260928204059.GA515872-robh@kernel.org> References: <20260928-drm-mipi-dsi-panel-ebpf-v1-0-5244926aace4@kernel.org> <20260928-drm-mipi-dsi-panel-ebpf-v1-1-5244926aace4@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260928-drm-mipi-dsi-panel-ebpf-v1-1-5244926aace4@kernel.org> X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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