Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp24962imu; Thu, 15 Nov 2018 21:18:34 -0800 (PST) X-Google-Smtp-Source: AJdET5dz0rWhO2q8dGg9ea5Dl5mOmpIN0k+Z8I5UDEm3Q+QsnBWnjoHcMA7NKFdJiHflHMuQtOvk X-Received: by 2002:a62:1b50:: with SMTP id b77mr9606952pfb.36.1542345514278; Thu, 15 Nov 2018 21:18:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542345514; cv=none; d=google.com; s=arc-20160816; b=LlJNuGuGOVIeuoXQ7yz6xIDEXIwgBUeT/eKJu2MHRo2Yt0rkPdxufuIupnhhPX0zBj nBzpd/wZkMaSHWZiJ1FelXIVHzji74C3TtIS7RHlOGZ9BtO0ua9y7qBrstbh6f6FrOUv irKtBOHPDcXC3MwRp3dB06ZHGTSahGQ7vludBP/kTReSF1/TD/8Huy7FPGN+yHu5GEdh TMkFtksPNLglqgEDAcdtbLDkHNg/d0vKFbNFpb2bT1Ol4oj7wNxFKqBlvh8UdK+JuBw3 cnTFu+Kpq8TlOcn4z0IMhP5G374IzALHTlHt8VbUv0R9q0lyAPaI9ODgeJnFLVmVY1T9 rcNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=bAxVsiSFq92VQEKTqjavP3tOvFFxpkKBGuWYD7oXRwM=; b=gil2jka8H8LsSYoQ4vT6F1h6y2pO5x74E5H4gbdjJSojQUM1gBieYhwpgDgwgKPMsR NZFVlhfXy6dgPR/uUu6ks4RhQ7YhHfTEZypTMUtk2sP/a6p6C/+RSlpB+37Sh6RRizGZ iDaWAhR12J0srfNXzo+AcZVLvCKByEYhAeanBfUcfgvw5XZIFVbKwldakiDkLGEr2/aK kHz911TvYH6jNKUPs833s9v3Lse4kxfm8UebGcuNN2JGycoe4JmfE0EQZYPKUS5i1344 qVPmXFhBpbLhhCef0cTMeolLEPjDdthl4GvNnxTBLIEBMm8Kou9q1F5IoGHTNCuo6L9/ FyuQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=EHA1zp59; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h14si19780385pgd.189.2018.11.15.21.18.18; Thu, 15 Nov 2018 21:18:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=EHA1zp59; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389139AbeKPP2V (ORCPT + 99 others); Fri, 16 Nov 2018 10:28:21 -0500 Received: from mail-io1-f67.google.com ([209.85.166.67]:33696 "EHLO mail-io1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727502AbeKPP2U (ORCPT ); Fri, 16 Nov 2018 10:28:20 -0500 Received: by mail-io1-f67.google.com with SMTP id f12-v6so16258710iog.0 for ; Thu, 15 Nov 2018 21:17:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bAxVsiSFq92VQEKTqjavP3tOvFFxpkKBGuWYD7oXRwM=; b=EHA1zp59VDC7n124NonEDDrxYlBvMF3xmxKhG5+5jrm24ANuDtH+4AaUbesROBRtGd 9bWCv1w7E+VFBI38NtDicalJReamHj4AsGdewm5JvIFfEIv4YIeAZI4FFrSLmH0Nf8GB ritKPX+Da9H03Q6nHU2h63rXkHfryiiSf4Nps= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bAxVsiSFq92VQEKTqjavP3tOvFFxpkKBGuWYD7oXRwM=; b=tjVJ2kmMPfdyhaVG/IBBBVGX1MeHoy9PvrpmWW+Ano9oxo9V8jsivGFWpzbRsFgrVM kamd5iiljJc4sIOnt8SAVwROERublSXkopaNNOrkGBmqDePA9/rKh8jFjIXXEU6U+/qO nfKf//m4vywWmWgVdPwMLLCQfFYKjSn9Dbo+h42UBCjrPcSL0EgHXLlvPqPMD4MM4LI8 hFCbvFUgKPlxlCBu0rG5kpqL8HYKGKWtJ/rhhxt+Dnikwg9VpfFScbkFRBOswFQcJ5Gj o0cssXjR2lXscYMvnU4Xcm/6pKzZWiMtcw6wuDvDqrpP1pnMAKBbFofGHRb5G51oU+dE jJDg== X-Gm-Message-State: AA+aEWbulqMuUGzWj2jkOku/hZBeyiLDS8scCRIPJiiPSBjqtGaKrfgF qpqJJEBYn4tM4Fgq/cmQR6hYq4j+F0Q5QkTUZ8UpHw== X-Received: by 2002:a6b:be02:: with SMTP id o2-v6mr6919027iof.41.1542345447219; Thu, 15 Nov 2018 21:17:27 -0800 (PST) MIME-Version: 1.0 References: <20181116004247.172977-1-dbasehore@chromium.org> In-Reply-To: From: "dbasehore ." Date: Thu, 15 Nov 2018 21:17:15 -0800 Message-ID: Subject: Re: [PATCH] arm64: dts: rockchip: rk3399: Add xin32k clk To: Doug Anderson Cc: linux-kernel , linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, =?UTF-8?B?6LCi5L+u6ZGr?= , Chris Zhong , ayaka@soulik.info, "nickey.yang" , Shunqian Zheng , klaus.goger@theobroma-systems.com, Brian Norris , enric.balletbo@collabora.com, =?UTF-8?Q?Heiko_St=C3=BCbner?= , Mark Rutland , robh+dt@kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 15, 2018 at 9:03 PM Doug Anderson wrote: > > Hi, > > On Thu, Nov 15, 2018 at 4:42 PM Derek Basehore wrote: > > > > This adds the xin32k clock to the RK3399 CPU. Even though it's not > > directly used, muxes will end up traversing the entire clk tree on > > calls to determine_rate if it doesn't exist. > > > > Signed-off-by: Derek Basehore > > --- > > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > > index 99e7f65c1779..6a32293982d0 100644 > > --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi > > +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > > @@ -191,6 +191,13 @@ > > #clock-cells = <0>; > > }; > > > > + xin32k: xin32k { > > nit: xin32k is the name of the clock that rk3399 consumes. It seems a > little weird to name this node with that name. Can you call this: > > ap_rtc_clk: ap-rtc-clk > > ...after the gru schematic? You wouldn't change the > clock-output-names, just the node name / label. > > > > + compatible = "fixed-clock"; > > + clock-frequency = <32000>; > > I checked the datasheet for the 32K clock and it shows that this is a > 32768 Hz clock, not a 32000 Hz one. I also checked the rk808 clock > driver (which is supposed to be compatible with rk3399) and it > produces a 32768 clock. Ok, sending out an updated patch that addresses these concerns.