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 AE86FC7EE2F for ; Fri, 3 Mar 2023 11:35:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231143AbjCCLfk (ORCPT ); Fri, 3 Mar 2023 06:35:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230118AbjCCLfg (ORCPT ); Fri, 3 Mar 2023 06:35:36 -0500 Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9FC25F235 for ; Fri, 3 Mar 2023 03:35:06 -0800 (PST) Received: by mail-wm1-x32e.google.com with SMTP id c18so1371856wmr.3 for ; Fri, 03 Mar 2023 03:35:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1677843302; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=++lCtQQa7+X6IbJitqa270p6tBDtglh3sC+2diUC4Wc=; b=P7KeZy0MbCpa8uokBo1HcPwWSBQ8BXNQBUVd/JOxbqUC4BgUIsA9wMjfs2JzHZQCid iYQ951Q3cExe7aIGtiEBWNWn5M+P8WsrHYoKScLTNJxMnbp8FraohdsXBMJ5/T8dHiv4 ro2RXVqixmyKiPfFo8Luu7OF8KbASxrvdJwX+tJcJHb2uKj+bVnaWUrcWAgAqF1xwpy8 /Mxr66G/ELW35keugG/WhgmVkGT4muQDK0SrS4M5h9uWAICgZ8Ujj4af4VSvl5A0kMKq 6aOvco6ZhlXKEoBB7+Cu8N+9tTbhSgwDCPN6Ox7sDePyHZxLVrYmr/pnzcDVZ1cqhJ2T hsbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677843302; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=++lCtQQa7+X6IbJitqa270p6tBDtglh3sC+2diUC4Wc=; b=FBSe6d+HbuiBoquuqMK8G8d8JrF4VEpV4rgpqWlDL1sjan2vSP0URMyeR5ixY6h9NW l5ZFsoPueEd84ZobVxQp1WJ4FPllLWlUW8h46VT+ttEi4VCovTw+GtcoxgipPDspFAY/ m4SMzdTKFLtepn3siyfu4Rpx6fTNVqy8B+zhw9DKUmIebCerrTW37aCc1Wmz1B68wijv OinhN3RmFnWBqisbWKMpI3LYQKCRsibkTkKUeYgKAfKyBcGfr06vOYSKhhXL13E0weXA GVNt6JLOOYuLEUcG87qgFF8Sfl3x3oz+1I0bea6/Fkot53hf+pvJhY2m2/0Iw6e1DaBp o/og== X-Gm-Message-State: AO0yUKULyidA/e+lJBiDEVbYQNPXh5VwspXgG5Rwo+qVJUjM4YEF2nDe bhahSbuDJ77XcipPbJtzAz7h0w== X-Google-Smtp-Source: AK7set/VoPy0DxdZaW+WU3Wk6rHfqx1Y9qwEwjfuG55qWo8QfcgBp4oUSSpbHD6h7QM5bXlu0pwfhQ== X-Received: by 2002:a05:600c:5101:b0:3e0:17d:aeaf with SMTP id o1-20020a05600c510100b003e0017daeafmr1296633wms.7.1677843302111; Fri, 03 Mar 2023 03:35:02 -0800 (PST) Received: from [192.168.0.162] (188-141-3-169.dynamic.upc.ie. [188.141.3.169]) by smtp.gmail.com with ESMTPSA id m18-20020a05600c3b1200b003db0ad636d1sm6390616wms.28.2023.03.03.03.35.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Mar 2023 03:35:01 -0800 (PST) Message-ID: <3116a08a-30a8-c9b9-f079-26739c9e6d49@linaro.org> Date: Fri, 3 Mar 2023 11:35:00 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [RFC PATCH] interconnect: qcom: icc-rpm: Don't call __qcom_icc_set twice on the same node Content-Language: en-US To: Konrad Dybcio , linux-arm-msm@vger.kernel.org, andersson@kernel.org, agross@kernel.org Cc: marijn.suijten@somainline.org, Georgi Djakov , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230303023500.2173137-1-konrad.dybcio@linaro.org> <59b28fb4-1367-9872-ed63-90847e380bb6@linaro.org> <29513b9e-8561-7f7e-370e-7515116c7ee6@linaro.org> From: Bryan O'Donoghue In-Reply-To: <29513b9e-8561-7f7e-370e-7515116c7ee6@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/03/2023 11:33, Konrad Dybcio wrote: > > > On 3.03.2023 12:32, Bryan O'Donoghue wrote: >> On 03/03/2023 02:35, Konrad Dybcio wrote: >>> Currently, when sync_state calls set(n, n) all the paths for setting >>> parameters on an icc node are called twice. Avoid that. >>> >>> Fixes: 751f4d14cdb4 ("interconnect: icc-rpm: Set destination bandwidth as well as source bandwidth") >>> Signed-off-by: Konrad Dybcio >>> --- >>> RFC comes from the fact that I *believe* this should be correct, but I'm >>> not entirely sure about it.. >>> >>> >>>   drivers/interconnect/qcom/icc-rpm.c | 2 +- >>>   1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/drivers/interconnect/qcom/icc-rpm.c b/drivers/interconnect/qcom/icc-rpm.c >>> index a6e0de03f46b..d35db1af9b08 100644 >>> --- a/drivers/interconnect/qcom/icc-rpm.c >>> +++ b/drivers/interconnect/qcom/icc-rpm.c >>> @@ -387,7 +387,7 @@ static int qcom_icc_set(struct icc_node *src, struct icc_node *dst) >>>       ret = __qcom_icc_set(src, src_qn, sum_bw); >>>       if (ret) >>>           return ret; >>> -    if (dst_qn) { >>> +    if (dst_qn && src_qn != dst_qn) { >>>           ret = __qcom_icc_set(dst, dst_qn, sum_bw); >>>           if (ret) >>>               return ret; >> >> Is it possible for src_qn == dst_qn ? > As the commit message says, sync_state calls set(n, n) in > drivers/interconnect/core.c : icc_sync_state(struct device *dev) So you've _seen_ that happen ?