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 B60CEC433EF for ; Fri, 8 Apr 2022 04:39:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To: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=m+AQ48A345c8zl+Z4bbFHvwdFfEek/QhRA+vwMUArYc=; b=x4sZRkYAbocqlC oIFlZALautcA3ZuhtgouLlG3vcRogxNZ1txIEbUB9x5S+8SVjNWRTmq81D0zceVY8L3p7dfy4RYw7 DChgRl408YA5EtN87gCpayLVXlwvehcLToDZjbqbLImhsa1lrEXwNi5F37nReFCoXqSpCJIGdLffi 14iaWDjKCH0bSMxF7DFq1gSAnm6O0F6WndlONhFNUrQy6q6W4SYZVGMNKOwy93xFrkYZSby25L5uC qP5mwRg/vJtofrHgybMDom0zkf8PKPkKbUHDK/B013A5alds3y9Y+a0ig/1QAaGc7OoTRmw5d2FQJ dlDtDtFtqWU/TKKwjH1Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncgOD-00Ewdc-GS; Fri, 08 Apr 2022 04:38:29 +0000 Received: from muru.com ([72.249.23.125]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncgOA-00EwdH-1Q for linux-arm-kernel@lists.infradead.org; Fri, 08 Apr 2022 04:38:27 +0000 Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id D501C8125; Fri, 8 Apr 2022 04:36:00 +0000 (UTC) Date: Fri, 8 Apr 2022 07:38:23 +0300 From: Tony Lindgren To: Nishanth Menon Cc: Daniel Lezcano , Thomas Gleixner , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Keerthy , Krzysztof Kozlowski , Rob Herring , Vignesh Raghavendra Subject: Re: [PATCH 1/4] dt-bindings: timer: Add am6 compatible for ti-timer Message-ID: References: <20220407071006.37031-1-tony@atomide.com> <20220407133344.v2x2b6rkmskatips@handled> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220407133344.v2x2b6rkmskatips@handled> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220407_213826_160941_53E8F499 X-CRM114-Status: GOOD ( 14.28 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, * Nishanth Menon [220407 13:31]: > On 10:10-20220407, Tony Lindgren wrote: > > diff --git a/Documentation/devicetree/bindings/timer/ti,timer.txt b/Documentation/devicetree/bindings/timer/ti,timer.txt > > --- a/Documentation/devicetree/bindings/timer/ti,timer.txt > > +++ b/Documentation/devicetree/bindings/timer/ti,timer.txt > > @@ -14,6 +14,7 @@ Required properties: > > ti,omap5430-timer (applicable to OMAP543x devices) > > ti,am335x-timer (applicable to AM335x devices) > > ti,am335x-timer-1ms (applicable to AM335x devices) > > + ti,am6-timer (applicable to AM6 devices) > > Suggestion: > > Could we call this ti,am65-timer instead? AM6 is a bit nuanced and spans > a couple of sub SoC architectures. I think the timer hardware is the same across am64, am65 and j7. So we should pick something to represent the am6 timers as it would allow using shared dtsi files for the 16 - 30 timers there are. Using shared timer dtsi files should work as long as the clocks are defined in include/dt-bindings/clock for each SoC, and assuming we can use the same compatible property for the timers. Of course if the timers are really different across am64, am65 and j72 then multiple compatible properties are neeeded. If the timer hardware is the same, then I guess we should just pick the earliest version, so how about using ti,am64-timer? Regards, Tony _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel