From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yx2-f13.google.com (mail-yx2-f13.google.com [74.125.224.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 019B84E3238 for ; Wed, 30 Sep 2026 14:02:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.224.141 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790776930; cv=none; b=N1A6OUf/aWJ4mcIPtE741aD5xCg74H/EUS/zGGN/86ZwB/7dG2RaF/gM0lXgJtA9+UARcJczyq29zzkKwoyZ8b/zABabJevXXyGjx+QzxL7DSg4rFWlLrfWL/wH/xeqj0wUDkOAGOrreCRNkogKgxKdoz/Q+9Jh613mBUpRFS1k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790776930; c=relaxed/simple; bh=1F1V/rD1y614TqPYCfWDNkmVlHzqqdQCMZ9Th+5moL0=; h=Message-ID:Date:MIME-Version:From:Subject:To:Cc:References: In-Reply-To:Content-Type; b=IJRp1SIj+EzqejsQFI7NZoreLtJdW5lRX4pS2KtZRLkidojHqWZrykgNhOMwt/vttOGSeEVKqCv9RdpeLJKn/Qz+Ewi8U79Q3VWFGJUbqQA6o3ze35nT6CQM1zWBNXUlO92E+VpXS+TIcpkwLLMEXy1Wdk09/i5JzrDjurK7T0Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=twEtjkYX; arc=none smtp.client-ip=74.125.224.141 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="twEtjkYX" Received: by mail-yx2-f13.google.com with SMTP id 956f58d0204a3-66e4aa8d882so6090966d50.0 for ; Wed, 30 Sep 2026 07:02:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1790776921; x=1791381721; darn=vger.kernel.org; h=content-transfer-encoding:content-type:in-reply-to:organization :autocrypt:content-language:references:cc:to:subject:reply-to:from :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to:content-type; bh=qs9QTXyZYNRiUfQ+wZvKCopWk12AffrP+uIc+6uA/NY=; b=twEtjkYXug3JBx6a9VqoPJbXVGWrkEe/btz0u9qN+OOUm/cmw+/ufq5ef2mY+n0W8g rb2PBghFyAImnAvv+mBWnOexAQi/vDGEcU33O6w54g6iXmvp5rtZcCZyW1Y+5NBLPVyw wcsaoho5r9ThEqmSJVQ9cFq8MuBVqENVWAy5LrhtRITkkv6SS9CDys9dWl1dKC6uDsOy hcrCVEo69SJK/ghkJMAH49WDTtQ18miaZ0YUJwAuNLJGHayFIbYfg/vuBWkc5eIE3uQU MdUON6q3dwLIq/4AoapfNbGYwqDEcAuq2bOEzHMvGYVwllygz7pzOvYRdL02mnCZ52Ok 5c9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790776921; x=1791381721; h=content-transfer-encoding:content-type:in-reply-to:organization :autocrypt:content-language:references:cc:to:subject:reply-to:from :user-agent:mime-version:date:message-id:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to:content-type; bh=qs9QTXyZYNRiUfQ+wZvKCopWk12AffrP+uIc+6uA/NY=; b=pDRNdLrazNOVS73PRebKe6aaJ19vMuTDSnxyeW1z5apYHj5RW5ii1VxSRqrCOXB+ev crcQrxtoaWe2X1PrCB5c0AaKkuA43rqzOEa2RAi4otmdnj744J0jCCmn6TDWwlGQuK/I 69sdff/8ouQMswtJXJMWMTVOOJJvequMM0OWymkNLY7609opWMgFwG+oEr6NWdRSkGqO fc/B68b173NE25W30ZNHs35BqCoyNmP7jd52Fw6PlABjP7yah1q8TQKeJnRHPZEBTYC5 3Yxk1d6/O4TmK/bp2YHW78/gIyx9MdxCNqaM1cRkdj8kAXX/29n50/+7qD8LhjYc7iEd 1Y8Q== X-Forwarded-Encrypted: i=1; AKwUvByTW6uZpqLqOKKfgPJf5nzBmtI18ADM2sNwVd9g3RURXZxIskpCxdz2x16mPIeM7zmZYmBN+F6YO+wKeY0=@vger.kernel.org X-Gm-Message-State: AFq9FYKKf4PZZ8rH6cVQHupD19rQrjdm2ikq0wfX2PUx1OUtTSTU9aLP 6UlOMhSBkpAz9dMtbysOgt8oBgQwLLlDW7UiTBst02/22a/o6m3FZzFUiXkok0o0U+E= X-Gm-Gg: AYBFou22Gt5KPVKWui/sKHcnHCmuKvlD/ntuDlDMllWUxiQroHdjj4FZHDrVHtJooT0 dgTBMcvzhMDJY6CpyK/nhfpAKO+H2TBDqyG9FFW9I0XjMftdvExLqdzYf1mzET8+5fJnkA/0kKg /v8BkEBQHeKXJqbU8hVjameDxqykd3tNdaPHLGjvkWh/0TywBu7YI8/4FU9xB2D6gXWQfWmYiqX mv98i8HEeDilN5u+Xo9FQllh7xsHea40xQEeMZs27fi69Nnb1N46WGd91GXDLelYHiT4DURlIbf wN0WqhTUfGrgp41X7zK3r2RFvKfdhhSwZvm5yuh5zneXpdLJn55K6jXB3S6UpijpG0eWy58iqJr 7jfbXa0CpR/lNJ0A3PO7EoRazLc60oEQ/RABaoPfmf3yY9PMMweKIa2YKBiuVcFfs1gXvkD26Ic gNHzVA/uIz7tIFCF14D1Nj2XL4sqNDS46Fv+CANpmUDiXXuKtK6Gns9un9/at5MNOi4ZzDh5mby KLvHe2OV4ojL8lsEyAUH2oEBHRmbCp6G6e+QSkv/ieSJlcaqtEQUnLzl4etEFnCN+pav5sdq7/P oSAeGJmi88ZLj9FpOw== X-Received: by 2002:a05:690e:484d:b0:66f:c238:7657 with SMTP id 956f58d0204a3-67683530372mr445880d50.76.1790776917625; Wed, 30 Sep 2026 07:01:57 -0700 (PDT) Received: from [10.21.51.184] (ipagstaticip-88fc351e-cb28-db3e-3f52-ad13c70f08da.sdsl.bell.ca. [142.127.77.63]) by smtp.gmail.com with ESMTPSA id 956f58d0204a3-67680ac3521sm764290d50.1.2026.09.30.07.01.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Sep 2026 07:01:56 -0700 (PDT) Message-ID: <6c581ae0-2480-47a2-b46e-97afadbc7c1f@linaro.org> Date: Wed, 30 Sep 2026 16:01:52 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Neil Armstrong Reply-To: Neil Armstrong Subject: Re: [PATCH 0/6] drm/bridge: Add a BPF-based MIPI-DSI panel driver To: Jani Nikula , Maxime Ripard , Jessica Zhang , David Airlie , Simona Vetter , Maarten Lankhorst , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , Florian Fainelli , Broadcom internal kernel review list Cc: 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 References: <20260928-drm-mipi-dsi-panel-ebpf-v1-0-5244926aace4@kernel.org> <054ef52478fc93fc213a9dae23ea77f73094aaf2@intel.com> Content-Language: en-US, fr Autocrypt: addr=neil.armstrong@linaro.org; keydata= xsBNBE1ZBs8BCAD78xVLsXPwV/2qQx2FaO/7mhWL0Qodw8UcQJnkrWmgTFRobtTWxuRx8WWP GTjuhvbleoQ5Cxjr+v+1ARGCH46MxFP5DwauzPekwJUD5QKZlaw/bURTLmS2id5wWi3lqVH4 BVF2WzvGyyeV1o4RTCYDnZ9VLLylJ9bneEaIs/7cjCEbipGGFlfIML3sfqnIvMAxIMZrvcl9 qPV2k+KQ7q+aXavU5W+yLNn7QtXUB530Zlk/d2ETgzQ5FLYYnUDAaRl+8JUTjc0CNOTpCeik 80TZcE6f8M76Xa6yU8VcNko94Ck7iB4vj70q76P/J7kt98hklrr85/3NU3oti3nrIHmHABEB AAHNKk5laWwgQXJtc3Ryb25nIDxuZWlsLmFybXN0cm9uZ0BsaW5hcm8ub3JnPsLAkQQTAQoA OwIbIwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgBYhBInsPQWERiF0UPIoSBaat7Gkz/iuBQJk Q5wSAhkBAAoJEBaat7Gkz/iuyhMIANiD94qDtUTJRfEW6GwXmtKWwl/mvqQtaTtZID2dos04 YqBbshiJbejgVJjy+HODcNUIKBB3PSLaln4ltdsV73SBcwUNdzebfKspAQunCM22Mn6FBIxQ GizsMLcP/0FX4en9NaKGfK6ZdKK6kN1GR9YffMJd2P08EO8mHowmSRe/ExAODhAs9W7XXExw UNCY4pVJyRPpEhv373vvff60bHxc1k/FF9WaPscMt7hlkbFLUs85kHtQAmr8pV5Hy9ezsSRa GzJmiVclkPc2BY592IGBXRDQ38urXeM4nfhhvqA50b/nAEXc6FzqgXqDkEIwR66/Gbp0t3+r yQzpKRyQif3OwE0ETVkGzwEIALyKDN/OGURaHBVzwjgYq+ZtifvekdrSNl8TIDH8g1xicBYp QTbPn6bbSZbdvfeQPNCcD4/EhXZuhQXMcoJsQQQnO4vwVULmPGgtGf8PVc7dxKOeta+qUh6+ SRh3vIcAUFHDT3f/Zdspz+e2E0hPV2hiSvICLk11qO6cyJE13zeNFoeY3ggrKY+IzbFomIZY 4yG6xI99NIPEVE9lNBXBKIlewIyVlkOaYvJWSV+p5gdJXOvScNN1epm5YHmf9aE2ZjnqZGoM Mtsyw18YoX9BqMFInxqYQQ3j/HpVgTSvmo5ea5qQDDUaCsaTf8UeDcwYOtgI8iL4oHcsGtUX oUk33HEAEQEAAcLAXwQYAQIACQUCTVkGzwIbDAAKCRAWmrexpM/4rrXiB/sGbkQ6itMrAIfn M7IbRuiSZS1unlySUVYu3SD6YBYnNi3G5EpbwfBNuT3H8//rVvtOFK4OD8cRYkxXRQmTvqa3 3eDIHu/zr1HMKErm+2SD6PO9umRef8V82o2oaCLvf4WeIssFjwB0b6a12opuRP7yo3E3gTCS KmbUuLv1CtxKQF+fUV1cVaTPMyT25Od+RC1K+iOR0F54oUJvJeq7fUzbn/KdlhA8XPGzwGRy 4zcsPWvwnXgfe5tk680fEKZVwOZKIEuJC3v+/yZpQzDvGYJvbyix0lHnrCzq43WefRHI5XTT QbM0WUIBIcGmq38+OgUsMYu4NzLu7uZFAcmp6h8g Organization: Linaro In-Reply-To: <054ef52478fc93fc213a9dae23ea77f73094aaf2@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 9/29/26 11:03, Jani Nikula wrote: > On Mon, 28 Sep 2026, Maxime Ripard wrote: >> Panels in general, and MIPI-DSI panels in particular, are pretty >> difficult to support and require pretty much a panel driver for each >> panel produced. Most of them are pretty simple, and require an opaque >> initialization sequence that is usually poorly documented. >> >> This creates a tension between OEMs and distros because OEMs will >> typically get a new panel to react to a sourcing issue during >> production, and thus need some swift turnaround between getting their >> new panel and it being operational in the OS. Distributions on the other >> hand can take years to ship a kernel with that new panel driver. >> >> To solve this, I followed the example of HID-BPF and wrote a panel >> driver that will rely on BPF programs to perform the panel >> initialization. That way, we can ship the programs separately from the >> kernel, and with a different lifecycle. If this driver is accepted, the >> plan is to have a userspace component started by udev to identify and >> load the right BPF program for the panels found on the device. > > I'd think for most panels it would suffice to have a declarative > language describing what to do at what points in time. For example, at > poweron, enable this GPIO, wait a little, write this set of DSI > commands, etc. You rarely need actual programming, or even ability to > read-modify-write something. Yes we could have a similar panel-simple but with init tables, but in reality those panels offers much more features we don't handle because the DDIC vendors and panel integrators just don't care exposing those features, but they get handled by vendor implementation like for Phones. > > It could be, say, YAML converted to some binary representation. Maybe > that could be in the DT, or maybe you could override it with the > firmware loader. And obviously any vendor "blob" could be trivially > converted back to YAML and upstreamed. I don't think we want this, downstream vendors does that and we don't want to go there. > > Where that falls short, you could always have a dedicated driver, or > extend the declarative stuff. > > Now, the question is, how much more BPF solves over that, without > requiring a dedicated driver, and is the added complexity worth it? This is my global question, and this is what I'm evaluating here, and so far is created more problem that solutions. > > FWIW, on the Intel platforms that support DSI, all of the > initialization, poweron/poweroff, backlight on/off etc. sequences like > that are stored in the BIOS, defined by the OEM. A plethora of DSI > panels, one driver. Don't look at it for examples how to implement it, > but I think the basic idea is workable. For _some_ panels, here, as a general solution no because we really want to have full support for panel features. Neil > > > BR, > Jani. > >