Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp3832175iog; Tue, 28 Jun 2022 03:49:33 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vBTp39iLBMhIVfxrRxa8cVGMTaCIOdnADsnin9E3N12S9rvjZ5/jD2fcCDBGb5mTCcSTj8 X-Received: by 2002:a17:903:18f:b0:16a:5c43:9a85 with SMTP id z15-20020a170903018f00b0016a5c439a85mr4297629plg.122.1656413373720; Tue, 28 Jun 2022 03:49:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656413373; cv=none; d=google.com; s=arc-20160816; b=Ht21cWSkGuyuY+fw7f1MJ/9jAAvDCOrLHP7xw5UViwEttXxyZTd1qy+BRGmm1Zh2c6 qhvmh05aDsr1RLDv41xoqyIZqPpdelgQHm+rk3aVagxBZjWwTIZbhiTM2EAZkVGoB3jk wMXnCfuY7oTnz+DOIRjkXE0m+EIQYjw40n2dkUvtvaJLPiZU2aIj9K+pyI+PRPYNxfdU Pcb+thv0eW6znvWCIKbKKY+OrjyHBdC5DblueO0FfeTPzOfc8gpUft1pDpwzH0Lvdkqx /7TYDpHlMNePQR1aIcQcHmSBad6sWVJSVk99UCTz3gnLGz2B/XnIHs3mJIJkpw5R9OPn o0dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=MfHIr6ZUWBTFFLdaK7ESXAbC7f2cS5qTkodIJ8o5Ypg=; b=Q48Y78FHjoNKSrFBLFSLe4wjx39bcM4uAXmucepvQKnILZioALbTsiUk906D10WVir 1DGm+iSgeh6qqtIGAcxJV7vQ2KegikC+4qaO2FHY89T0ehS66j6WcUU3ko97lS6p9SIy 5qdyFUudGdEPS3mGtwqlwDAOu99ljrdtd7y1ELN5c0+A/ahR0VhpC73E/7+QRjyRobKR 7r56ARCowEx9k1s1RsnxtrpPrlJ308DnEEBpV5yXJSHssi+eSk2gMi8iMQvA5Cm/Kcul hwZ8Ktr5svkBcuhaF73bNt/mNk1eMhxSCzV2atXg7bnDc7881Yf4ieGRSaiPf8PYx91X Nzvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcdkim header.b=nchn7YPf; 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=quicinc.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id nv13-20020a17090b1b4d00b001ed53b28e8dsi13479089pjb.84.2022.06.28.03.49.21; Tue, 28 Jun 2022 03:49:33 -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=@quicinc.com header.s=qcdkim header.b=nchn7YPf; 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=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344790AbiF1KnS (ORCPT + 99 others); Tue, 28 Jun 2022 06:43:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245069AbiF1KnQ (ORCPT ); Tue, 28 Jun 2022 06:43:16 -0400 Received: from alexa-out-sd-02.qualcomm.com (alexa-out-sd-02.qualcomm.com [199.106.114.39]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 575702F398; Tue, 28 Jun 2022 03:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1656412995; x=1687948995; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=MfHIr6ZUWBTFFLdaK7ESXAbC7f2cS5qTkodIJ8o5Ypg=; b=nchn7YPfkBZ/2IzX2HG4WC/w0RJtk34QRaESRZVPPw16DQyhT9TJfVTl FdZXqtNDZ7IV+wSb+XS8psYWplIFQ0M3DB+qqt9EfwA+jCAnYzwyl24CF M0d0OrY1jV64JFjKE+UGW9U95NIqygDUm1Uh5yP0HjKZp1RtHDwmAjboy E=; Received: from unknown (HELO ironmsg05-sd.qualcomm.com) ([10.53.140.145]) by alexa-out-sd-02.qualcomm.com with ESMTP; 28 Jun 2022 03:43:15 -0700 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg05-sd.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2022 03:43:14 -0700 Received: from nalasex01a.na.qualcomm.com (10.47.209.196) by nasanex01c.na.qualcomm.com (10.47.97.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Tue, 28 Jun 2022 03:43:13 -0700 Received: from [10.216.26.50] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Tue, 28 Jun 2022 03:43:06 -0700 Message-ID: Date: Tue, 28 Jun 2022 16:13:01 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: [PATCH v4 1/4] dt-bindings: interconnect: qcom,sdm845-cpu-bwmon: add BWMON device Content-Language: en-US To: Bjorn Andersson CC: Krzysztof Kozlowski , Andy Gross , Georgi Djakov , Rob Herring , Catalin Marinas , Will Deacon , , , , , , "Rob Herring" References: <20220601101140.170504-1-krzysztof.kozlowski@linaro.org> <20220601101140.170504-2-krzysztof.kozlowski@linaro.org> <3e4e504c-5a38-43cd-ea8d-afbbb72eacad@linaro.org> From: Rajendra Nayak In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01a.na.qualcomm.com (10.47.209.196) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, 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 6/26/2022 8:49 AM, Bjorn Andersson wrote: > On Wed 22 Jun 06:58 CDT 2022, Rajendra Nayak wrote: > >> >> >> On 6/7/2022 12:20 PM, Krzysztof Kozlowski wrote: >>> On 06/06/2022 23:11, Bjorn Andersson wrote: >>>> On Wed 01 Jun 03:11 PDT 2022, Krzysztof Kozlowski wrote: >>>> >>>>> Add bindings for the Qualcomm Bandwidth Monitor device providing >>>>> performance data on interconnects. The bindings describe only BWMON >>>>> version 4, e.g. the instance on SDM845 between CPU and Last Level Cache >>>>> Controller. >>>>> >>>>> Signed-off-by: Krzysztof Kozlowski >>>>> Reviewed-by: Rob Herring >>>>> Acked-by: Georgi Djakov >>>>> --- >>>>> .../interconnect/qcom,sdm845-cpu-bwmon.yaml | 97 +++++++++++++++++++ >>>>> 1 file changed, 97 insertions(+) >>>>> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sdm845-cpu-bwmon.yaml >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,sdm845-cpu-bwmon.yaml b/Documentation/devicetree/bindings/interconnect/qcom,sdm845-cpu-bwmon.yaml >>>>> new file mode 100644 >>>>> index 000000000000..8c82e06ee432 >>>>> --- /dev/null >>>>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,sdm845-cpu-bwmon.yaml >>>>> @@ -0,0 +1,97 @@ >>>>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause >>>>> +%YAML 1.2 >>>>> +--- >>>>> +$id: http://devicetree.org/schemas/interconnect/qcom,sdm845-cpu-bwmon.yaml# >>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>>> + >>>>> +title: Qualcomm Interconnect Bandwidth Monitor >>>>> + >>>>> +maintainers: >>>>> + - Krzysztof Kozlowski >>>>> + >>>>> +description: >>>>> + Bandwidth Monitor measures current throughput on buses between various NoC >>>>> + fabrics and provides information when it crosses configured thresholds. >>>>> + >>>>> +properties: >>>>> + compatible: >>>>> + enum: >>>>> + - qcom,sdm845-cpu-bwmon # BWMON v4 >>>> >>>> It seems the thing that's called bwmon v4 is compatible with a number of >>>> different platforms, should we add a generic compatible to the binding >>>> as well, to avoid having to update the implementation for each SoC? >>>> >>>> (I.e. "qcom,sdm845-cpu-bwmon", "qcom,bwmon-v4") >> >> it seems pretty useful to have the "qcom,bwmon-v4" and "qcom,bwmon-v5" >> compatibles, I tried these patches on a sc7280 device which has a bwmon4 >> between the cpu and caches (and also has a bwmon5 between the caches and DDR) >> and the driver works with zero changes. >> > > But does the '4' and '5' has a relation to the hardware? Or is just the > 4th and 5th register layout supported by the downstream driver? Right, it was just based on the downstream driver register layouts, i could not find these numbers in HW specs anywhere, but that said I do see 2 instances of these, one of them called the LAGG bwmon which is the one between the LLCC and DDR and is documented as part of the LLCC specs. I'll try and dig somemore into the documentation to see how we could define compatibles to match hw revs. > > Regards, > Bjorn