From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B772A547059; Thu, 1 Oct 2026 07:22:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790839382; cv=none; b=bmBtKIZOU8c6MREeoIS/T39d4lhKzK9y22x0M1JWBtmn+9kDmMnB9LmC3kpz+OGNqGKDX+gN/Q8uFgHf+R5pIArCF2lyUTKhZmTTOaJq5PdhWTemQFESLcOt+NNV5VpjtBB9ROe61lZBVRcWWvX02WR2e5UR/H3WFhD1iwGNewQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790839382; c=relaxed/simple; bh=vYPo30L+yzg4zdvP/9QG8tpdh1hu1GaLdI0m5fTJPic=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GgGPaEd/cVGmunUW8FNg0hgK9MEZltYm027T/HfQtb6RhpzrSWJ45U1Rd0fzdP5SgCzkhbUYDwIfddhqLLXeLQxj4IdgHLLbaZI9c0SJxPcPCh7noQrRSTSU21CwOxiOtSvKzkbvbU94DGc+5YnLEMUwH++0pWdjRjKFvr/JtAQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=XJ2wVMP6; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="XJ2wVMP6" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6F1281F000FF; Thu, 1 Oct 2026 07:22:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790839372; bh=vYPo30L+yzg4zdvP/9QG8tpdh1hu1GaLdI0m5fTJPic=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=XJ2wVMP6oeCv2GMjeOm0YD3l3EXN0xvYQRaArKhqbXcJi/lNWtYs7qDSfg4TNpFHp tcHiVxH+QjxL8CjN1f+z89ZIvf1Hou6pJ+j3Gi4E0x7pkQH9tWnm9d/UEcIoEotgFM jEramHJxTxiy5ABlYpKM8jY/3lCZctNaM4HAj0ioXvpnzhunNw8rs1zD+Y1lvpO0ah zySagzh5ov5stXJ4/RdnmgKqzpmBViqdr2Aw/xyL+lqBNt0GxrcBa8WKGCkeNfiEa0 KgL8Iw7YwmuN/1nwxruU2fGL9KgLKqXzIBVRIXaif+Z96HE8O2YrtJvwiBfYJm0ITH 1rxAUcnnoRAVQ== Date: Thu, 1 Oct 2026 09:22:48 +0200 From: Maxime Ripard To: Rob Herring 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: References: <20260928-drm-mipi-dsi-panel-ebpf-v1-0-5244926aace4@kernel.org> <20260928-drm-mipi-dsi-panel-ebpf-v1-1-5244926aace4@kernel.org> <20260928204059.GA515872-robh@kernel.org> <20260929222822.GA2933878-robh@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha384; protocol="application/pgp-signature"; boundary="eh5wavyv7nnca5rg" Content-Disposition: inline In-Reply-To: --eh5wavyv7nnca5rg Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH 1/6] dt-bindings: display: Add panel-mipi-dsi-bpf generic panel binding MIME-Version: 1.0 On Wed, Sep 30, 2026 at 02:07:39PM -0500, Rob Herring wrote: > On Wed, Sep 30, 2026 at 3:04=E2=80=AFAM Maxime Ripard wrote: > > > > On Tue, Sep 29, 2026 at 05:28:22PM -0500, Rob Herring wrote: > > > On Tue, Sep 29, 2026 at 10:39:24AM +0200, Maxime Ripard wrote: > > > > On Mon, Sep 28, 2026 at 03:40:59PM -0500, Rob Herring wrote: > > > > > 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 timin= g, > > > > > > 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. >=20 > [snip a bunch of irrelevant shit] >=20 > > > > So, let's phrase this differently: what's different about the > > > > description than panel-mipi-dsi-spi, or any other binding already in > > > > tree? > > > > > > There's all of 3 panels supported. Compared to all the other panels we > > > have, hardly the rule over the exception. You can always fine "bad" > > > examples or exceptions. > > > > > > That one defines a single supply. Any other MIPI SPI panel with > > > different supplies or GPIO controls probably has its own binding. Try= ing > > > to parameterize that in DT doesn't work. We've rejected trying to do > > > that in DT over and over. What's your story here for that? > > > > Sigh... Look, I really don't care about an argument DT maintainers use > > at their discretion for this. We both know full well that it's been and > > still is inconsistenly applied, and you also know that it's not like > > I've been playing the DT game since pretty much the beginning (on ARM > > anyway). So it's not like I don't want to make it work, I do. But what I > > care about is enabling that driver to work. > > > > I reused exactly the same binding than the last major binding that was > > merged for panels, and support about the same number of panels. I guess > > that was a mistake, so sorry for that. > > > > I'm fine with reworking the binding any way you want as long as it still > > allows for the same use-case, but I would have hoped for a better > > feedback on how to do so than "oh what a huge pile of shit this is". >=20 > When you can answer my question above rather than make up shit I > didn't say, maybe I'll reply again on this thread. Otherwise I'm done > here. I don't need this abuse for the thankless job of DT > maintainership. It's been the whole tone of the reviews, so I'm sorry if you were caught in the crossfire and you didn't mean that. And I'm sorry it made your DT maintainership work harder than it already is. I do mean what I said before though. I have no problem changing the binding the way you want, but I need to know what to change in the first place, otherwise it's really no better than a NAK, or we're bound to have the same exchange for the v2, and I'd rather not. I indeed missed your question, but now I'm not sure I understand what you mean by "paremeterize that in DT"? The supplies in the binding are an aggregate of all the possible supplies a panel can take. They are not a wildcard, but they all have their own semantics that are used by panels right now. I don't expect any new supply to be introduced, unless there's a major panel technology change such as the one we had with the introduction of OLED. Would you prefer to reduce the number of supplies to the minimum we need right now, and extend it as needed? Maxime --eh5wavyv7nnca5rg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iJUEABMJAB0WIQTkHFbLp4ejekA/qfgnX84Zoj2+dgUCar4KSAAKCRAnX84Zoj2+ drKVAYDR/ZDwDXBZxoJ1vN0aVjc4QVJvpsXjDFhzm6g8ERdGmINbKbE3z4HYkf8L rASKMl0BfRPGtCXfDtr+Ev35B1QViTxFnNv9Js2+WdypHe0kKGcY7E/8p6hiGNzS J8y0tgD50Q== =lNbO -----END PGP SIGNATURE----- --eh5wavyv7nnca5rg--