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 BED0FCEACC8 for ; Tue, 1 Oct 2024 14:14:40 +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-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=HkIi6vdWzZRL9mRqwCQESkyqXZUUQQRvVyjVDYHczpM=; b=a1yblGJ4foSqjcuVsvAxqB4icJ upOyqSs+TReqNg+o0evEY6MmWY87DN2XxJ0YqpRi/YVav40IVaAzReLa05N/kzYFY/R9BfEABMQbd V18smlb+P6lPoU3bLO3u5ZJf2cfD7Zu8rc76IOtSYmswIYyhQ2mfdM97zHX/rmi5xum/HI7zIOO4D jvBfdxMNODd/LsPBHYVmuvZWVDEwhLw3yxDr1AhJPs6G0KaQjQoP0+RH+L8lEp3pCC+r/wpkI8gLl 1HWasAxv6JI6bQlBzkibnJUh2NkIlFYG6yfjklY+zhy2woiQrTGZzc5Z164qWzzmOMicoa+0rYNnc zADKZroA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1svde0-000000036OD-1sPz; Tue, 01 Oct 2024 14:14:28 +0000 Received: from mail11.truemail.it ([217.194.8.81]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1svdcd-000000035mO-18C8 for linux-arm-kernel@lists.infradead.org; Tue, 01 Oct 2024 14:13:05 +0000 Received: from gaggiata.pivistrello.it (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 780F01F9BE; Tue, 1 Oct 2024 16:13:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1727791981; bh=HkIi6vdWzZRL9mRqwCQESkyqXZUUQQRvVyjVDYHczpM=; h=Received:From:To:Subject; b=spjDrQm6RjfD+ES2VkYGpNMvdca/QmvzvP6MXC0fmwGxrAbgSdz7UwYAmX6PFx7zI uwxc4Fn6lACjXQyDQNFDZ0Umt4t2ntYnTiXSN4hRiD8+bRTpDQuBmwDjRqVFOU53zY 36NNeUAVjrtPfve5B9OZt0bJr7ctLH465/OyEWTpRhyjPllzC3gT/FtlkZpN/aikkx 4FWoVuZ7a3rtzbrBl/7j86JepQDqqFCp1neXYIGPKOayaKUiKNQLArTCmjmfjfw3kj VTsuL1y58XI26bRfZKKa8mZbcYN3HpISD93SZrx4JSVnHU3ujGO8xIiE6d9mi5gbkt r76CSW6vPcPXA== Received: by gaggiata.pivistrello.it (Postfix, from userid 1000) id 15CCF7F919; Tue, 1 Oct 2024 16:13:01 +0200 (CEST) Date: Tue, 1 Oct 2024 16:13:01 +0200 From: Francesco Dolcini To: Krzysztof Kozlowski Cc: Francesco Dolcini , Nishanth Menon , =?iso-8859-1?Q?Jo=E3o_Paulo_Gon=E7alves?= , Vignesh Raghavendra , Tero Kristo , Rob Herring , Krzysztof Kozlowski , Conor Dooley , =?iso-8859-1?Q?Jo=E3o_Paulo_Gon=E7alves?= , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1] arm64: dts: ti: k3-am62-verdin: Update tla2024 adc compatible Message-ID: References: <20241001111413.10390-1-jpaulo.silvagoncalves@gmail.com> <20241001130128.GA36341@francesco-nb> <3d9de1b8-488b-4df5-b984-7581b1d02241@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3d9de1b8-488b-4df5-b984-7581b1d02241@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241001_071303_683165_D99090D4 X-CRM114-Status: GOOD ( 40.81 ) 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 Tue, Oct 01, 2024 at 03:59:39PM +0200, Krzysztof Kozlowski wrote: > On 01/10/2024 15:01, Francesco Dolcini wrote: > > On Tue, Oct 01, 2024 at 01:54:56PM +0200, Krzysztof Kozlowski wrote: > >> On 01/10/2024 13:14, João Paulo Gonçalves wrote: > >>> From: João Paulo Gonçalves > >>> > >>> With commit f1c9ce0ced2d ("iio: adc: ti-ads1015: Add TLA2024 support") a > >>> new compatible was introduced for TLA2024 ADC. Update the device > >>> tree to use the correct compatible for the Verdin-AM62 hardware. > >>> > >>> Signed-off-by: João Paulo Gonçalves > >>> --- > >>> arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi | 2 +- > >>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>> > >>> diff --git a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi > >>> index 5bef31b8577b..f201722d81b3 100644 > >>> --- a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi > >>> +++ b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi > >>> @@ -1220,7 +1220,7 @@ sensor@48 { > >>> }; > >>> > >>> adc@49 { > >>> - compatible = "ti,ads1015"; > >>> + compatible = "ti,tla2024"; > >> > >> So it is not always TI, who breaks their users. :) (as pointed out in > >> LPC DT BoF). > > > > So, let's adjust what I said at that time, I think is important, and I > > appreciate you giving me an excuse for doing that :-) > > > > Lately as Toradex we are working a lot with TI, and one of the reasons is > > that they have a great software support, backed-up by a great strategy > > on the way they contribute to the various upstream projects they build > > their SDK on top (Linux, U-Boot, and more). > > > > With that is normal that while working so closely with them we find > > issues, everybody have those, it's just that those are the one we > > care the most at the moment :-). Not to mention that we started working > > with TI a couple of years ago, so TI is still somehow "new" to us and we > > are still "learning". > > > > On this regards I was recently working on updating our BSP to the > > latest SDK from TI, that is based on a v6.6 stable kernel and looking at > > the patches we had to apply on top, the total counts of the patches we > > do not have in mainline to support the board subject of this patch is > > just _zero_. This to me is a great achievement. > > > > Nishant: this is also for you, and feel free to "market" this > > internally/externally :-) > > > > > >> If you want to break users, sure, but at least explain in commit msg why. > > > > Now, on this specific topic, the actual device that is assembled on this > > board is a TI TLA2024, and it's like that since ever, the board never > > changed. The current compatible is not matching what is assembled on > > board. It works because the device is close enough to TI ADS1015. > > > > With that said, I do not think this is breaking any actual compatibility > > issue. > > > > - The old DTB will keep working with old and new kernel. > > New DTB stops working with old kernel and this is what we talked about > during LPC. My mind at that time was really on using old DTB with a new kernel, not that other way around. In any case, I do not think that this comment applies on this specific case, as I wrote you cannot really run this board on a kernel that does not support the ti,tla2024 compatible. > All out-of-tree users of this DTS, like other operating systems, will be > affected as well probably. Well, yes. From what I know those user do not exist and this is just theoretical, but, I might be as well wrong and I see your point. So, let me try to sum it up, I see 2 options: 1 - we drop this change. this is fine for me. 2 - we add a comment in the commit message that this is a breaking change, and while I am not aware of any impact with real software that is available today, I might have incomplete information. Francesco