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 63580C32763 for ; Tue, 26 Jul 2022 13:45:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230487AbiGZNt1 (ORCPT ); Tue, 26 Jul 2022 09:49:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32832 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238916AbiGZNtX (ORCPT ); Tue, 26 Jul 2022 09:49:23 -0400 Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 16667205EF for ; Tue, 26 Jul 2022 06:49:21 -0700 (PDT) Received: by mail-lj1-x22f.google.com with SMTP id m9so16516807ljp.9 for ; Tue, 26 Jul 2022 06:49:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=Y5BRR0iNLx6aBIjbVl9ArC7hjqevnrWy8iJkMFg13Gw=; b=dT2fn0qmN08x8rHVL25zAPZPXxb9sSxyHNjZVrrW2S0kNRdHOsJe3cOdw+SNGK+6pb GuLEbjj3CsXGw9nRB38q61/3XyYl1ssLvLP0iuIIruAR9Xjo8ir7ULdYlxFFMJHQXnwP 4ghhgnbIWtNl3Ba41DwCv8guPqyb1YwPRU/FuN830CkRRByk4dt/ReYyePn36G30bYxR PpSQ+eMpVbvtbSOaPPM3PZkYIeJFI3b9AI/jkmLA9qeJMmk4zllanXgUM2Z/Y7lj/Psi vG6uCGIhjiydmCr6okRuZz7dIaEzpt/g0I59gQVWTD2ESoYOt3oAUOIiRFofMAYNXAgF Ty0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=Y5BRR0iNLx6aBIjbVl9ArC7hjqevnrWy8iJkMFg13Gw=; b=mkHW/VkxwIGpUoT8uX6rg59NCpM7kgt0khmKIVplsjxruO6w8+tBzEVc7L8cQkjuvT mXSL4JFl8TazxZvqGTfP4Abqxsv5udFiJ3Po2sWJ2cgxT/nKykBEi9+Ii7rnOpaOwquD Qu44zP5jSWzSg8GJYgIlQevS25BT8oojcsB6Ser+vEXMIii0BYB2LdzQYGklmstx0wX+ A1okmY5fjL7SBFdrMPIOqeMpNP6EEnBwRqdIy3F9N44svQHuh3CtLxELlO/TFIlab3KQ SPtWPweOZ98DCuk6ZwfIbskQDESguGBwj3OfRAK1KnXYsYYYj30oMC4FOIdYkshi8jBV jfYw== X-Gm-Message-State: AJIora9OH72YWS46HVoF2ygaNs0kyDlAfw4Ue1t7jS7ZUd30AzuIngXS tNs5jCbsmglX2MJsSRV3kl1DzA== X-Google-Smtp-Source: AGRyM1uQNkFPqhr+UY20E19CB6pxfKs587FemzdiLwf9fjReDOp5EzYTe0h56cIIqJGEJrhs0ZzNuA== X-Received: by 2002:a2e:7108:0:b0:25d:eacb:964d with SMTP id m8-20020a2e7108000000b0025deacb964dmr6560570ljc.232.1658843359139; Tue, 26 Jul 2022 06:49:19 -0700 (PDT) Received: from [192.168.3.197] (78-26-46-173.network.trollfjord.no. [78.26.46.173]) by smtp.gmail.com with ESMTPSA id 197-20020a2e05ce000000b0025d70efeaaasm3313237ljf.75.2022.07.26.06.49.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jul 2022 06:49:18 -0700 (PDT) Message-ID: Date: Tue, 26 Jul 2022 15:49:17 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH 10/10] arm64: dts: qcom: sdm845: add LLCC BWMON Content-Language: en-US To: Sibi Sankar , Steev Klimaszewski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Georgi Djakov , Rob Herring , linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org 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> <25321f37-dbea-188b-1b11-e983a00701b2@quicinc.com> <3325c626-f1af-2e95-fc53-68cf3d427a88@quicinc.com> From: Krzysztof Kozlowski In-Reply-To: <3325c626-f1af-2e95-fc53-68cf3d427a88@quicinc.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 26/07/2022 14:01, Sibi Sankar wrote: >>>> 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. > > From what I see we can probably get away with restricting the llcc_base > reg region to just llcc0_common region and leave the lcc-bwmon as is. Och, that IO mapping for llcc is quite big. I'll try that. Best regards, Krzysztof