Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp376849pxj; Thu, 13 May 2021 07:03:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxEl2tmgzLoqM8FKkHP6q3Fr880XWoXFr6apbyI9Au91lDdkAl97qP/ZYA8oktriAk7QyZO X-Received: by 2002:a2e:9dc3:: with SMTP id x3mr34522353ljj.206.1620914633960; Thu, 13 May 2021 07:03:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620914633; cv=none; d=google.com; s=arc-20160816; b=qKf6S6npcUCizSzE2ZDbZf4AJnqAq5ApVBo5qmB6ntWRqIy3OcCMorE7mfQLSus9QV 0ioh7hS5wYYMBRUmqPeq/G3ruN8h+fohOx0XSVUIFdCI8HNgb/pyPagUPO/yBMh8txnS E9J0Vb5y38ySz1+LQutSrq5O+7n3Fzgr9y4JRjo3oq0R2CO5DI+vDxfHmP+FXqLWyL5A KIv1/or3rx7ByGml1KqQURVvVvtBnhUGlcOkwEWHBboNGAkKowaV9ghS2+T1NWWhJNky ZvVjCVR/QzpS9tzYk1kp1jfxHEUe2FEqBZwyRLXEU8UEqZxTPWlICx7Wv3ZpBe23qXcr OLCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=BQCgGhWGz0vTO025MKhGuMXGkgB6UGEKQcS5I7SCzKE=; b=nvyVM3bAQL0ufksF7a5K6SeViKgeH4qXCqmPjWH/eWlEjjnFtK+S9O+qSb70bLuUB9 cXH0dVT6Ivy8PSm99gSDaKpuER3NOs05abr1t1WvnTSknVNqh1WjUg/NYXfYWZAEht57 AgctvkdvJ2WwiRTv32/3JcLuWp2sWn/qRo7O7K5JGazfTgNDYxDoJD+RjIv62LBgcxfu yiicu3ZRD3qethgMQU4KBs0MM49GHdWT/buyQ5TdMlQ/CuMGbqCwWl/yZ5LmF0EFLKha k1a9EhrgK5mHoiGViauHp0ZOLvR/qUiQ6cS8vMmk7HA3OoND5GZ3L6HU76iQj36nqLWq B7DA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=NyX+OYrq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 9si3813923lfy.485.2021.05.13.07.03.19; Thu, 13 May 2021 07:03:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=NyX+OYrq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234292AbhEMOC7 (ORCPT + 99 others); Thu, 13 May 2021 10:02:59 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:34750 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234125AbhEMOCz (ORCPT ); Thu, 13 May 2021 10:02:55 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 14DE1bi9024510; Thu, 13 May 2021 09:01:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1620914497; bh=BQCgGhWGz0vTO025MKhGuMXGkgB6UGEKQcS5I7SCzKE=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=NyX+OYrq5n27HuQTCdGRrMub2OsBylMv02whwA3zSuh1+fgSA7tbHQ71xVgCd28R+ zw5DuikToiYI+/khkXr9MtUjzmD6TCQjQZJG3q3fDs1K3JsrxbC8pObybGKDHURwTu CoaZ+ja775spZV5fFUlF43ngIpwJ3r/DhFt4hMAg= Received: from DFLE104.ent.ti.com (dfle104.ent.ti.com [10.64.6.25]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 14DE1bVX072091 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 13 May 2021 09:01:37 -0500 Received: from DFLE114.ent.ti.com (10.64.6.35) by DFLE104.ent.ti.com (10.64.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 13 May 2021 09:01:37 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE114.ent.ti.com (10.64.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2 via Frontend Transport; Thu, 13 May 2021 09:01:37 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 14DE1bXE029229; Thu, 13 May 2021 09:01:37 -0500 Date: Thu, 13 May 2021 09:01:37 -0500 From: Nishanth Menon To: Kishon Vijay Abraham I CC: Tero Kristo , Rob Herring , , , , Lokesh Vutla Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-j721e-main: Fix external refclk input to SERDES Message-ID: <20210513140137.5uvftgtsku3xfobz@engraving> References: <20210512151209.27560-1-kishon@ti.com> <20210512151209.27560-2-kishon@ti.com> <20210512185157.q5sr2xqf3w5igfte@imagines> <68c95cf1-84fa-2194-7bb1-e3c60e7f1fc0@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <68c95cf1-84fa-2194-7bb1-e3c60e7f1fc0@ti.com> User-Agent: NeoMutt/20171215 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17:41-20210513, Kishon Vijay Abraham I wrote: > Hi Nishanth, > > On 13/05/21 12:21 am, Nishanth Menon wrote: > > On 20:42-20210512, Kishon Vijay Abraham I wrote: > >> Rename the external refclk inputs to the SERDES from > >> dummy_cmn_refclk/dummy_cmn_refclk1 to cmn_refclk/cmn_refclk1 > >> respectively. Also move the external refclk DT nodes outside the > >> cbass_main DT node. Since in j721e common processor board, only the > >> cmn_refclk1 is connected to 100MHz clock, fix the clock frequency. > >> > >> Fixes: afd094ebe69f ("arm64: dts: ti: k3-j721e-main: Add WIZ and SERDES PHY nodes") > > > > Assume we want this part of 5.13 fixes? > > This doesn't fix any functionality. Okay for me to go in 5.14 along with > the rest of the series. > > > >> Signed-off-by: Kishon Vijay Abraham I > >> --- > >> .../dts/ti/k3-j721e-common-proc-board.dts | 4 ++ > >> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 58 ++++++++++--------- > >> 2 files changed, 34 insertions(+), 28 deletions(-) > >> > >> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts > >> index 60764366e22b..86f7ab511ee8 100644 > >> --- a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts > >> +++ b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts > >> @@ -635,6 +635,10 @@ > >> status = "disabled"; > >> }; > >> > >> +&cmn_refclk1 { > >> + clock-frequency = <100000000>; > >> +}; > >> + > >> &serdes0 { > >> serdes0_pcie_link: link@0 { > >> reg = <0>; > >> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi > >> index c2aa45a3ac79..002a0c1520ee 100644 > >> --- a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi > >> +++ b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi > >> @@ -8,6 +8,20 @@ > >> #include > >> #include > >> > >> +/ { > >> + cmn_refclk: cmn-refclk { > >> + #clock-cells = <0>; > >> + compatible = "fixed-clock"; > >> + clock-frequency = <0>; > >> + }; > >> + > >> + cmn_refclk1: cmn-refclk1 { > > > > Just curious: why cant we use the standard nodenames with clock? > > We can use standard names here. Is there any defined nodename for > clocks? clk or clock? Don't see $nodename defined for clocks in > dt-schema repository. Looking at the fixed-clock example, lets go with clock -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D