From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpout-02.galae.net (smtpout-02.galae.net [185.246.84.56]) (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 83AF1201033; Tue, 2 Dec 2025 11:19:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.84.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764674351; cv=none; b=mbSho09cG0QMwAnYX4fb0tRG2MrKS49Z6Lpe7IE6ykaPgiJiAx4kf/BfC3xByxU/2kQfWrcGAKx96QDHI6sH6upIeF0oWl4k2+M9BGPlyv0T8jdlxdQ9i/S021MC6/K4+2s1M8C7QpekBub/sI+M0ITMWs+auwR8f8qRVYcXPwE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764674351; c=relaxed/simple; bh=bsZpWTbJA5Ji4ZEdCb6pkFF0SUzTtbhhOzyCxRyrtPw=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=KVdD7beGMxLwDJheWGDQT7iJAvIuZHkQDa6Oal4CqsQzMF7mBo5ClxUZuGYv06MaFJtRlBhssXaj8kIqvY644fZ5FAqGRSEVZc6tA0dBucYJmakbIk+xONh7Qm71vqrUDSj6ANCe9zVlwmwvtrSoIMLcnieUyaVhUA4vtAjj6Ms= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=d66PwGmR; arc=none smtp.client-ip=185.246.84.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="d66PwGmR" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-02.galae.net (Postfix) with ESMTPS id BEFCE1A1EC6; Tue, 2 Dec 2025 11:19:05 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 89707606D3; Tue, 2 Dec 2025 11:19:05 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 7C9671191942B; Tue, 2 Dec 2025 12:18:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1764674344; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=8V3hIJFvUgVjg0/tUj7NHCN4G/8vGDXw+L9NVOOC8l4=; b=d66PwGmR6xFbSkXchCyHcaQzFN5GVfO0AyQo/yODXfML8MFJHVb0alTIT5YUTicejcOvx4 WDFeB0rvweqZyxxHICzE+GJbKYhzXn/S7QGhfXb8QP7Wyri9kUPa1RRK/AxC5kd1lyfrHh MQC4tkv0f6Dh67I+pxemljbxllZ1m6dtuqhGriKAHFtr9RjD18MfgIge+QugD3v9DbyhLC sL9V3E2tlzC1fQ6Fdo+4GK31D26/trGGWTlMZ3OWOYVuLwdDe/CgNbWPGvm6QRncih3lsQ krrXozHuRqjPvJASDOxJlvad8izQr/VZJXsOprzRGc3PQXTN7wimnZbgIn1VWw== Date: Tue, 2 Dec 2025 12:18:56 +0100 From: Kory Maincent To: Krzysztof Kozlowski Cc: Tomi Valkeinen , Markus Schneider-Pargmann , Luca Ceresoli , Louis Chauvet , Thomas Petazzoni , Miguel Gazquez , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Jyri Sarha , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Russell King , Bartosz Golaszewski , Tony Lindgren , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec Subject: Re: [PATCH 05/21] ARM: dts: omap: Bind panel to panel-dpi instead of ti,tilcdc,panel driver Message-ID: <20251202121856.0da62885@kmaincent-XPS-13-7390> In-Reply-To: <94e254fa-289d-41ed-909f-1742cfbb2690@kernel.org> References: <20251126-feature_tilcdc-v1-0-49b9ef2e3aa0@bootlin.com> <20251126-feature_tilcdc-v1-5-49b9ef2e3aa0@bootlin.com> <96b1b7bf-ddbe-4213-a201-dc89cf2998dd@ideasonboard.com> <3bc5bf92-05c3-4841-ab28-9bab2bb31cd5@kernel.org> <20251202104244.59a9e83d@kmaincent-XPS-13-7390> <20251202114416.09624a4b@kmaincent-XPS-13-7390> <94e254fa-289d-41ed-909f-1742cfbb2690@kernel.org> Organization: bootlin X-Mailer: Claws Mail 4.2.0 (GTK 3.24.41; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Last-TLS-Session-Version: TLSv1.3 On Tue, 2 Dec 2025 11:47:40 +0100 Krzysztof Kozlowski wrote: > On 02/12/2025 11:44, Kory Maincent wrote: > > On Tue, 2 Dec 2025 11:28:55 +0100 > > Krzysztof Kozlowski wrote: > > =20 > >> On 02/12/2025 10:42, Kory Maincent wrote: =20 > >>> =20 > >>>> Stuffing DTS change in the middle of the driver change tries to hide > >>>> impact, which is not nice on its own. =20 > >>> > >>> As it needs driver change before the removal for not breaking things = it > >>> can't be done at the beginning of the series. =20 > >> > >> And that is the problem which should stop you there and rethink how to > >> organize it without impacting users. DTS cannot go via DRM. If that was > >> your intention, that's my: > >> > >> NAK =20 > >=20 > > My intention was to raise discussion over the ugly and legacy tilcdc-pa= nel > > binding and what to do with it. But it seems you don't want to, that's a > > shame. =20 >=20 > I don't see how you get to these conclusions. I comment that putting > here DTS in the middle without any explanation of the impact is not > correct and this one alone I disagree with. Because you didn't replied to the first line of my answer: "Yes, I know this but I still wanted to try and begin a discussion on this,= as I really thought it is not a good idea to add and maintain an new non-standard panel driver solely for this tilcdc panel binding." But indeed you are right, I should have put more explanation on why there i= s DTS and binding change in the middle of the series. Sorry for that. =20 > From that you claim I don't want to fix things... >=20 > DTS cannot go to drm, which means you either need to separate the change > and make entire work bisectable and backwards compatible for some time > OR at least document clearly the impact as we always ask. The thing is, if I split it, it has to be in 3. One for the of DRM bus flags support, a second for the the devicetree and binding change and a third for= the whole tilcdc and tda998x cleaning stuff. I think I will go for one series, = with better documentation. Now, what is your point of view on my question. Will you nak any binding removal even if the binding is ugly and legacy and imply maintaining an non-standard tilcdc panel driver? I know it breaks DTB compatibility but th= ere is several argument to not keep it. See patch 6. Regards, --=20 K=C3=B6ry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com