Message ID | 20221024125843.25261-1-johan+linaro@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp535423wru; Mon, 24 Oct 2022 09:12:54 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5ygAjJQVtgMhjUDU2CJWOnbRQXdJEtbf+R2MhK3lXHRkKvfyM8gqdllxNIUpfe5yQ2ieGp X-Received: by 2002:a05:6a00:189d:b0:56b:c3ff:26bc with SMTP id x29-20020a056a00189d00b0056bc3ff26bcmr6812317pfh.49.1666627973904; Mon, 24 Oct 2022 09:12:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666627973; cv=none; d=google.com; s=arc-20160816; b=AkuhArozi/GDWV2QIcW9obTgeXRaSDbuICcP4Nv8JSQSjxAcKHeIjxoItYzS29HWNu SOR8PQDOH0l7DGwELSJx5DLSDzYAd11taBPlA20thtG6DmVhLyCwyeUdUWI4wMBduYVd D44qG4ja8jjwSSTGcnY0EGXg8kv8nj36/b+5e1XXETd+3z5ZCi3NMFOfrFf2iSflONJq 8wyu0Jh5CwchUHJcHSlWP+/Mwom/KT0iRl+sOHftJ9nkhGVTFUX76D+KiDLWwT9CuMLc 4ZsjxBPp05pE83WWepXbZ/wUKUAn04MEot4stdq1b0S788urr9o+IJdspbt5QXs0INMc KIXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=ZPsFAwyCcHNCZ4QOkyaDRaPAtUTVeG+tPWNSNiPvSFI=; b=OKEvSPhVkacCiXBBcOEXnVvYai4rZVU1DODCktvurUoaDi+yXwrHiFzN8R11YHRFzT spmEcCy9nWVyYLxMvZ1/+sJj2f39PNjvX4gjpr3ViD2Y5s+JserZVq/CWMYGpmZjichL nRudUSCCJOr6o46Hr1DyEsMglCjoNQ0tUANapYuRLxN/DNylmvCWD6ax3oHH4UpWe15O MBsD7aqUuKTGXChz1XbKIhyW1z0zUy1w3T47vaRp6NVqS7COPeCYUoRGWttRb2cDW5L2 es2r/Z5lHmk1LNcwex73MPKTfme/9s2gn+GOitMt7u3vaAYZ+0YvjBPVzkkM0munoEa6 TTsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QiJ2HWpR; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id r19-20020a63ce53000000b0043c1cb75c22si35767388pgi.333.2022.10.24.09.12.40; Mon, 24 Oct 2022 09:12:53 -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=QiJ2HWpR; 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 S233851AbiJXQL6 (ORCPT <rfc822;pwkd43@gmail.com> + 99 others); Mon, 24 Oct 2022 12:11:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48670 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232549AbiJXQFS (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 24 Oct 2022 12:05:18 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A892928E30; Mon, 24 Oct 2022 07:58:15 -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 ams.source.kernel.org (Postfix) with ESMTPS id CBD4BB818EB; Mon, 24 Oct 2022 12:59:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7C885C433C1; Mon, 24 Oct 2022 12:59:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1666616357; bh=oluLS6fbx5EfX/bPAz59Gt0aLRFpB7IURLSW5kgk/l4=; h=From:To:Cc:Subject:Date:From; b=QiJ2HWpRBhnKcAElAuFNs74EX3ed3GFDZcLTiN6gPxrAmjXBmF5sIqthO572zpo4/ xCzupz3gxdHqZD33aRA2Vtc5llbsNkHMTi3dXI6HB3m8rUYdsYR4SVDScTTY5FZ0bz 6KzqI6K0XTj6ZA1E3Zq3mQTc7BTKq7si7mahrVcTShhpegeXuF/+9zl0JfT5Xk+jnc ZOig9AAgfGBHK4gmBfs9X+W9a1cWloaDh5bpU+q/LVRdXIPwazr7NAAjdsWgLD48Wt Z8HF7RVk8VHDKM3byAXlc0cYaa/wcXOltXua2+1zSl2kuWDVXH/+g59ubiDshPHd8o EMb2IP3SX2b2Q== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from <johan+linaro@kernel.org>) id 1omx2i-0006Zg-7u; Mon, 24 Oct 2022 14:59:01 +0200 From: Johan Hovold <johan+linaro@kernel.org> To: Bjorn Andersson <andersson@kernel.org> Cc: Andy Gross <agross@kernel.org>, Konrad Dybcio <konrad.dybcio@somainline.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Johan Hovold <johan+linaro@kernel.org> Subject: [PATCH] arm64: dts: qcom: sc8280xp: add TCSR node Date: Mon, 24 Oct 2022 14:58:43 +0200 Message-Id: <20221024125843.25261-1-johan+linaro@kernel.org> X-Mailer: git-send-email 2.37.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.6 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 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1747583313064766478?= X-GMAIL-MSGID: =?utf-8?q?1747586094498879888?= |
Series |
arm64: dts: qcom: sc8280xp: add TCSR node
|
|
Commit Message
Johan Hovold
Oct. 24, 2022, 12:58 p.m. UTC
Add the TCSR node which is needed for PCIe configuration.
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
---
arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 5 +++++
1 file changed, 5 insertions(+)
Comments
On Mon, Oct 24, 2022 at 10:09:51AM -0400, Krzysztof Kozlowski wrote: > On 24/10/2022 09:42, Johan Hovold wrote: > > On Mon, Oct 24, 2022 at 09:34:22AM -0400, Krzysztof Kozlowski wrote: > >> On 24/10/2022 08:58, Johan Hovold wrote: > >>> Add the TCSR node which is needed for PCIe configuration. > >>> > >>> Signed-off-by: Johan Hovold <johan+linaro@kernel.org> > >>> --- > >>> arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 5 +++++ > >> > >> Please send the patches together with the binding. There is no need to > >> have this split and it causes additional effort during review - lookup > >> of the binding. > > > > I was under the impression that the dts changes should be submitted > > separately from the binding as they go through different trees. (And > > last time I posted them together the subsystem maintainer ended up > > taking also the dts changes by mistake). > > Yes, that's also true. :) > > > The binding has been picked up by Lee now so I posted the dts change. > > Could have added a lore link though. > > This also would work and help a lot. > > It depends in general on the maintainer - for example Greg does not want > to deal with individual patches, especially if DTS is just one patch and > USB would be 10 of them. Our toolset is not good for picking up 10 out > of 11. For all such cases - please provide link to lore. > > If however there are just two patches - one DTS and one for maintainer - > then having them in one patchset should not cause additional effort for > the maintainer. I'm pretty sure I saw Lee complaining about Bjorn taking also the binding update through the qcom tree recently when someone did just that. Apparently it was TCSR related too: https://lore.kernel.org/all/Yzbk%2F6SQdpNQTahV@google.com/ Heh. That was you. :) > As you can see on the list, majority of patchsets consist of > bindings+DTS. Pretty often entire piece - bindings+driver+DTS. Yeah, and whatever alternative you go with, someone will get it wrong or complain it seems. Johan
On 24/10/2022 10:54, Johan Hovold wrote: >> >>> The binding has been picked up by Lee now so I posted the dts change. >>> Could have added a lore link though. >> >> This also would work and help a lot. >> >> It depends in general on the maintainer - for example Greg does not want >> to deal with individual patches, especially if DTS is just one patch and >> USB would be 10 of them. Our toolset is not good for picking up 10 out >> of 11. For all such cases - please provide link to lore. >> >> If however there are just two patches - one DTS and one for maintainer - >> then having them in one patchset should not cause additional effort for >> the maintainer. > > I'm pretty sure I saw Lee complaining about Bjorn taking also the > binding update through the qcom tree recently when someone did just > that. Apparently it was TCSR related too: > > https://lore.kernel.org/all/Yzbk%2F6SQdpNQTahV@google.com/ > > Heh. That was you. :) Yep. It was a patchset of 16 patches where one should go to MFD and 15 to Qualcomm SoC. > >> As you can see on the list, majority of patchsets consist of >> bindings+DTS. Pretty often entire piece - bindings+driver+DTS. > > Yeah, and whatever alternative you go with, someone will get it wrong or > complain it seems. :) Best regards, Krzysztof
diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi index b30c3b57fd13..79abe0e2c38d 100644 --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi @@ -984,6 +984,11 @@ tcsr_mutex: hwlock@1f40000 { #hwlock-cells = <1>; }; + tcsr: syscon@1fc0000 { + compatible = "qcom,sc8280xp-tcsr", "syscon"; + reg = <0x0 0x01fc0000 0x0 0x30000>; + }; + usb_0_hsphy: phy@88e5000 { compatible = "qcom,sc8280xp-usb-hs-phy", "qcom,usb-snps-hs-5nm-phy";