Received: by 2002:a05:7412:da14:b0:e2:908c:2ebd with SMTP id fe20csp327884rdb; Fri, 6 Oct 2023 05:02:05 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFvyv3QFh4YckufhlwStN7kCy3SJNfdqTSPqp7fjfdquZoglXTrSsHTECx47oVagE0jQ0FH X-Received: by 2002:a05:6358:921:b0:143:8f7f:9150 with SMTP id r33-20020a056358092100b001438f7f9150mr9012295rwi.13.1696593725318; Fri, 06 Oct 2023 05:02:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696593725; cv=none; d=google.com; s=arc-20160816; b=JF4CJex5DLezttuBg6nKvNKwIOM1fivViW53Wh0iF2Sw4lZIzhXklLVQUrbHgQ9irQ gZpAe4bcUkDuRNzDVW7abmjFIOgLpdD16HKs/1dirZQPvta/maWq3tCfePxpCHfuiGs7 QcCSvGPt9mUohrk1WwH2svdvPB4ioZoRURsIJQPHMmaYe9LwxwRG689scQFJ0q1zcvSO /geEbKQ5iNe16H5tiHCVkSoDJyZKYiRrbzCRwAltQCp0JYfq0OjoqnqESOVrT5HnuWlT G+0D0ITfibckQp+W1xri9bQudnQW2NldB3pnLDJdwYlHWoyDyoxhGz8jg0cZHpkj89kH d1gg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=lpD2epWNlmiS8XYq+aJ7VOLQ2+oJck78368nfWClxjI=; fh=wRP2X+abPQ9dUYYzTShLwLXJkqnUFuK1jvIr5TcWOtw=; b=kK99TcFUz4BNbofwIPEgQoQUzSKEY93Psg+8b+gWxuWVTjYZNh2rfBXus1dEZvLRfG bASIN3EOedBOySAe/m7D96NR3F/rXpAt6kSjwaWUkK3/+xRbloVP8wElWHjzp/+XXMKa CfN69Gc+at20Gd8mXaX99MrO2JApLCC2UdEQnsvw9tBxyQ/Jtq+/E3gPa+pUC1MrIooi L7yxQZE++pytMYfwIUpFqAx4b4ihm/r3o6s1SrY17nyuspx7vqIxyV9hre1vLbRcCAJ7 8ETkDK4AZmQgQ6hxNhkqCaE8C4KqgC8jRm+aFCT6qqhMuP5BzbzroEmXQ0L8ikIN2p7k xdBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=pwuld3sX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from howler.vger.email (howler.vger.email. [23.128.96.34]) by mx.google.com with ESMTPS id k185-20020a6384c2000000b00578db71453esi3575060pgd.468.2023.10.06.05.01.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Oct 2023 05:02:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=pwuld3sX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 9E8BF82A6752; Fri, 6 Oct 2023 05:01:49 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232169AbjJFMBf (ORCPT + 99 others); Fri, 6 Oct 2023 08:01:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54996 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232178AbjJFMBb (ORCPT ); Fri, 6 Oct 2023 08:01:31 -0400 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC97BE4; Fri, 6 Oct 2023 05:01:29 -0700 (PDT) Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 396C1MdI105328; Fri, 6 Oct 2023 07:01:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1696593682; bh=lpD2epWNlmiS8XYq+aJ7VOLQ2+oJck78368nfWClxjI=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=pwuld3sXHg6btu5ribAn9L4pEvYqbAA6wkP2e1Zimg9ZRuWjlCbNLGeII1WhmAnAd 42/SI6FvGoKbpvZMJja090NvkC/jxi/f8LKJQ9x0HFvTIjvZafStlhCiHNgHKUtdef tFACG0/6JM1/wtHdzI+/lTdFgf6HrIEA7l0kgdjc= Received: from DLEE103.ent.ti.com (dlee103.ent.ti.com [157.170.170.33]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 396C1MPV125837 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 6 Oct 2023 07:01:22 -0500 Received: from DLEE105.ent.ti.com (157.170.170.35) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Fri, 6 Oct 2023 07:01:22 -0500 Received: from lelv0327.itg.ti.com (10.180.67.183) by DLEE105.ent.ti.com (157.170.170.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Fri, 6 Oct 2023 07:01:22 -0500 Received: from localhost (ileaxei01-snat.itg.ti.com [10.180.69.5]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 396C1MHN032309; Fri, 6 Oct 2023 07:01:22 -0500 Date: Fri, 6 Oct 2023 07:01:22 -0500 From: Nishanth Menon To: "J, KEERTHY" CC: , , , , , , , , Subject: Re: [PATCH v7 5/7] arm64: dts: ti: k3-j784s4-mcu: Add the mcu domain watchdog instances Message-ID: <20231006120122.qkohphk6uq6kmxgm@pueblo> References: <20231006042901.6474-1-j-keerthy@ti.com> <20231006042901.6474-6-j-keerthy@ti.com> <20231006113410.tibvxxkeuujqnbv4@evolution> <9e3489f0-98f4-48ac-89a8-ea4ad3ee115c@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <9e3489f0-98f4-48ac-89a8-ea4ad3ee115c@ti.com> X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=2.7 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on howler.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Fri, 06 Oct 2023 05:01:49 -0700 (PDT) X-Spam-Level: ** On 17:22-20231006, J, KEERTHY wrote: > > > On 10/6/2023 5:04 PM, Nishanth Menon wrote: > > On 09:58-20231006, Keerthy wrote: > > > There are totally 2 instances of watchdog module in MCU domain. > > > These instances are coupled with the MCU domain R5F instances. > > > > > Disabling them as they are not used by Linux. > > Device tree is hardware description - not tied to how Linux uses it. > > > > Reason these wdts are disabled by default is because they are tightly > > coupled with R5Fs. > > > > > > > > Signed-off-by: Keerthy > > > --- > > > .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 24 +++++++++++++++++++ > > > 1 file changed, 24 insertions(+) > > > > > > diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi > > > index a7b5c4cb7d3e..809a0b1cf038 100644 > > > --- a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi > > > +++ b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi > > > @@ -714,4 +714,28 @@ > > > ti,esm-pins = <63>; > > > bootph-pre-ram; > > > }; > > > + > > Nishanth, > > Below i have addressed the coupling with R5Fs & MCU domains watcdogs. > > > > + /* > > > + * The 2 RTI instances are couple with MCU R5Fs so keeping them > > > + * disabled as these will be used by their respective firmware This description is best in the commit message > > > + */ > > > + mcu_watchdog0: watchdog@40600000 { > > > + compatible = "ti,j7-rti-wdt"; > > > + reg = <0x00 0x40600000 0x00 0x100>; > > > + clocks = <&k3_clks 367 1>; > > > + power-domains = <&k3_pds 367 TI_SCI_PD_EXCLUSIVE>; > > > + assigned-clocks = <&k3_clks 367 0>; > > > + assigned-clock-parents = <&k3_clks 367 4>; > > > + status = "disabled"; > > > + }; > > > + > > > + mcu_watchdog1: watchdog@40610000 { > > > + compatible = "ti,j7-rti-wdt"; > > > + reg = <0x00 0x40610000 0x00 0x100>; > > > + clocks = <&k3_clks 368 1>; > > > + power-domains = <&k3_pds 368 TI_SCI_PD_EXCLUSIVE>; > > > + assigned-clocks = <&k3_clks 368 0>; > > > + assigned-clock-parents = <&k3_clks 368 4>; > > > > Please DONOT ignore the review comments - I did ask the documentation in > > dts as well. reason being that this is what people will see rather than > > dig up the commit log. it should be intutive when reading the dts why > > nodes are disabled by default Vs the standard of leaving it enabled by > > default. Given esp that these peripherals do not have anything to do > > with board semantics (pinmux or something similar) to be complete. > > As mentioned above. I added single comment for addressing both the > watchdogs. I missed it completely. Now that I think of it, I seem to have missed having seen it in previous rev reviews as well, and there is a reason for it: See [1] clarifying comment - nodes reserved for firmware usage have convention of "reserved" as status and documentation immediately above the status to help clarify the reason in-context. That is more readable than having to scroll up to find the rationale. [1] https://lore.kernel.org/all/20231006114422.avymeap7h5ocs6zq@dreadlock/ -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D