Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4462846imw; Tue, 12 Jul 2022 08:20:30 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v46fJNDfPLfh1VqWCKq66KqIoqxCrzBZ3o4XhiyUQpO+aLEwYJ49Dv5Tj7yjoU4IhMYuyh X-Received: by 2002:a17:906:5d08:b0:6ff:8ed:db63 with SMTP id g8-20020a1709065d0800b006ff08eddb63mr24847113ejt.408.1657639230273; Tue, 12 Jul 2022 08:20:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657639230; cv=none; d=google.com; s=arc-20160816; b=wpfIsWJmQ05D2UalWfWPbI+/GSYl8/Hj7t6w7AN1IZh8iuVNx7uUPINs03IPyaxv3m dM8uZPRCP7aM+ze1qRJ62p8sewcFAjisVJSQf8dLsMq+FAwkpWb2etcrsW3s16Tz28Cg fdF+kZ5yx9UNeQigNt2/sSWB4QHoBAbD/TvyOogZXLBq42aD0DhVNtY/xukBthbEU2ID RN+z1FBCHTGbLNQeGimZNn1WObUHjJZ8rXtwBoH82Ko5HfbuveRggqcO050ov18AUFLU VjiiEybnzmsa8TmZ6IDRBsPLB+3sRr57vAQ3YlD7Mco/3G6cR80+YTqYxHcWC6P7B86G 9n6A== 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=7TYVOf8/efgouGZK4RqgP4QKPGVfUqbi3GLKIE9xRx8=; b=ZrA7rUxemcGDzEZG3vgkrPyHMkF/WVmK3Dux87CbWsCNBeEdGbElBS6icNMEc2+8pT GIEiQfFil7e0Lo9gHQ3ZAQad6lZNguFWzLq3yXTQ4TajYmDUkw+mr5V3Ow+gKMId0hVc 4EQewr6KaRtTs0Sb4pP3vNKU3wOqHHyVqeuo56dcSYlCxrgBMc8/hcC8/+IlFtXGX2pA +w3M2Y//C8yfxFNLRhuiqXoeTd+KDUlDOqglS4WjDjJCPminbAGvbKwsaCMcZNO8jP4A /g8lNyH4TDnv6dvIcH36kkLVe1NZomVc5bX4HlVNhmEQ00uz84xXUsNDNT13vzhrb5xf 8oYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=kuVF7pg7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a6-20020a1709064a4600b0072a4249e9b5si13290790ejv.17.2022.07.12.08.20.04; Tue, 12 Jul 2022 08:20:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=kuVF7pg7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233424AbiGLPFC (ORCPT + 99 others); Tue, 12 Jul 2022 11:05:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54398 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233936AbiGLPEJ (ORCPT ); Tue, 12 Jul 2022 11:04:09 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B4AD63A8; Tue, 12 Jul 2022 08:00:13 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 0553061221; Tue, 12 Jul 2022 15:00:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 33461C341CF; Tue, 12 Jul 2022 15:00:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1657638011; bh=4stto/0WdKGy1PAM7cobud0ZktYRhwuIUHvFotEri6o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kuVF7pg7PKX53+paGnLUTnLYkCzxjavhSjkjkPKVKfMA6yBWwbCM0eCa78ysbYzNl /MNYBktPDvvt3nGQrZjSbRkLOf1ESWkBOaEbCBCeZl/LmGhdm0XazCO7iCzetTzxIX j/8bpJQgHZVljOZo/nXxlh/v2mhOWJCsztl4lFmK2yQEo4sZ8g+2UfzA712XvxDoOh RH1IEtLDCFibFK4/zR50dUYCyCc+ctEcCTnsu9SkDMSAvJRbzc4JN6vKWjCFQ2Mx6/ rzouqEz4GAccJHA9K1XFes2H5kROO5Ial9u2R0uNkybUoEdu5dxxGZ4jaU0P+kGh91 kGqYwjooNtovA== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1oBHMz-0002FB-38; Tue, 12 Jul 2022 17:00:13 +0200 Date: Tue, 12 Jul 2022 17:00:13 +0200 From: Johan Hovold To: Bjorn Andersson , Rob Herring Cc: Andy Gross , Konrad Dybcio , Johan Hovold , Rob Herring , Krzysztof Kozlowski , manivannan.sadhasivam@linaro.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp: Add lost ranges for timer Message-ID: References: <20220707160858.3178771-1-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 12, 2022 at 04:53:48PM +0200, Johan Hovold wrote: > On Mon, Jul 11, 2022 at 07:28:26PM -0700, Bjorn Andersson wrote: > > On Mon 11 Jul 01:56 PDT 2022, Johan Hovold wrote: > > > > > On Thu, Jul 07, 2022 at 09:08:58AM -0700, Bjorn Andersson wrote: > > > > The timer node needs ranges specified to map the 1-cell children to the > > > > 2-cell address range used in /soc. This addition never made it into the > > > > patch that was posted and merged, so add it now. > > > > > > > > Fixes: 152d1faf1e2f ("arm64: dts: qcom: add SC8280XP platform") > > > > Signed-off-by: Bjorn Andersson > > > > --- > > > > arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 1 + > > > > 1 file changed, 1 insertion(+) > > > > > > > > diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > > > index 2bdb42c88311..37a4cd6f85b6 100644 > > > > --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > > > +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > > > @@ -1667,6 +1667,7 @@ timer@17c20000 { > > > > reg = <0x0 0x17c20000 0x0 0x1000>; > > > > #address-cells = <1>; > > > > #size-cells = <1>; > > > > + ranges = <0 0 0 0x20000000>; > > > > > > While addressing the current issue, this looks odd to me. Why not use a > > > non-zero parent bus address here instead? > > > > > > > I guess we could express the frames relative the timer range, but that > > would imply that anyone porting downstream dts snippets would have to > > translate these addresses - or more likely would end up just copying the > > existing cases. > > > > > And please use hex notation consistently for the addresses. > > > > That seems like a reasonable ask, I can fix that up. But on both > > accounts this matches what I merged for all the other platforms in: > > > > 458ebdbb8e5d ("arm64: dts: qcom: timer should use only 32-bit size") > > > > > > So I guess we'll also need to go back and fix up the style of all the > > other platforms - just because we're not allowed to express the frames > > in 64-bits according to the binding... > > Would have been easier to just amend the binding. I don't think that > #size-cells = 1 constraint is set in stone as it was added when > converting to DT schema. Ok, maybe it was done on purpose since Rob later merged c5c689d3221e ("dt-bindings: timer: Use non-empty ranges in example") which suggests we should use a non-empty ranges as I mentioned above. Any comments, Rob? > I also don't think you need to fixup the hex notation elsewhere, it's > quite inconsistent currently, but no need to make it worse. > > But you probably should amend the commit message and mention that this > fixes time keeping. I had recently noticed that something was off > (journals rotating, and erratic cursor blinking) but didn't realise that > timers were broken until you posted this. Johan