From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E009C43334 for ; Tue, 26 Jul 2022 11:32:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237807AbiGZLcJ (ORCPT ); Tue, 26 Jul 2022 07:32:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230198AbiGZLcH (ORCPT ); Tue, 26 Jul 2022 07:32:07 -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 D1ED127CCE; Tue, 26 Jul 2022 04:32:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1658835126; x=1690371126; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=DzB9acxU3JB4UtdY7GBGshAn56Crt8vbSHYd7HbxwEg=; b=kKT3fS5UoKaDpp81xs721WKQ6KIyTDeKhxO81jdmJ8fbwFsBebXVYUlw 3NWVS0MZepx03gZzWvFTau0q4mhfSg2lkGL+dNyj6LEqhSmwXEogfU/PZ ZC19DU8VvRihu604oeYITutu23yFV7a/saXhROKtB7g72G3JdK0pypaKs M=; Received: from unknown (HELO ironmsg02-sd.qualcomm.com) ([10.53.140.142]) by alexa-out-sd-02.qualcomm.com with ESMTP; 26 Jul 2022 04:32:06 -0700 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg02-sd.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jul 2022 04:32:06 -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, 26 Jul 2022 04:32:05 -0700 Received: from [10.79.43.230] (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, 26 Jul 2022 04:32:02 -0700 Subject: Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON To: Krzysztof Kozlowski , Steev Klimaszewski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Georgi Djakov , Rob Herring , , , , CC: Rajendra Nayak References: <20220720192807.130098-1-krzysztof.kozlowski@linaro.org> <20220720192807.130098-11-krzysztof.kozlowski@linaro.org> <25673493-4171-62b0-f696-1316d115f388@kali.org> <96552a95-8939-3ac2-c9b3-14dabaf53923@linaro.org> From: Sibi Sankar Message-ID: <25321f37-dbea-188b-1b11-e983a00701b2@quicinc.com> Date: Tue, 26 Jul 2022 17:01:59 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/23/22 2:06 PM, Krzysztof Kozlowski wrote: > On 23/07/2022 04:37, Steev Klimaszewski wrote: >>> >>> Currently it's 5.19.0-rc7 (torvalds tree at 4ba1329c) with a few extra >>> patches on top, the bwmon set included.  It's possible that secure >>> world uses it, but I do not know enough about that to say one way or >>> the other. > > To test patches you should apply them on maintainer's tree or > linux-next. Applying on other trees of course might be useful for > testing some backports, but it is independent process and different issue. > >>> >>> -- steev >>> >> I think you may be right; I just applied this patchset to -next >> (20220722) and i do not see the error message there.  On my 5.19-rc7 >> tree, i am also testing a patchset that enables qcom devices to access >> efivars, so possibly we are ending up in secure world there? > > Actually mapping of IO space should not touch secure world, so this was > a long shot assuming you test it on the next. > The memory region specified in device tree overlaps with the llcc system cache controller node. Steev probably had the QCOM_LLCC config enabled when he tested it out on his branch. > > Best regards, > Krzysztof >