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 B3B61C433FE for ; Thu, 31 Mar 2022 18:32:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234556AbiCaSeI (ORCPT ); Thu, 31 Mar 2022 14:34:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46186 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232464AbiCaSeH (ORCPT ); Thu, 31 Mar 2022 14:34:07 -0400 Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DE39D1C2330 for ; Thu, 31 Mar 2022 11:32:16 -0700 (PDT) Received: by mail-ot1-x32c.google.com with SMTP id k25-20020a056830151900b005b25d8588dbso488708otp.4 for ; Thu, 31 Mar 2022 11:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=t6GsqwNN9llZCnAliYpOilY5j9SHoFYzbGwsekdtfa4=; b=XYn4Prc7x7Wi0lnnkWc4y98ocH9lAtL/28wpaZwgzRg4BI4YGIrPG7wIlzCXxjqyNY k3WGyiFN5UA9k1BmqJPJLUv8BPxVmuTpjSs+RZr3/VELAJ6Z6AcMrALui7s73PJjngT0 0y44DKaVWVk5krVho5gepvYG6wgoCz+z/ME1/b3Pi1pM8kf8KmeCWA/xgS7X7sQz9TG+ JchT0nwF9cTscAFn1bZrG2xYXqKQ/y3gDUMA3vye2BDSsLUtTbo4y7JA9/jSESu4ZJL9 WS+V0bHPEa0qyul0WFwqAuU9CmAsXcfM0HTzQXpDOhQUN1RSwFQSbeYfxQLz6o+Q19DY +ZcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=t6GsqwNN9llZCnAliYpOilY5j9SHoFYzbGwsekdtfa4=; b=Nhz3Z3Ak84aHIwyDObMySAsyPmfSgIArOUfEIJZiPt4Ocg1bYLbWc39cB0KvBokrP/ q1Sxvao5wvx2rCYZu66hZtrGxz0ofkWV8o/ufMxBgAm5q5/z5ULxMezMAuFJQ3eXfAtD QiLzwyvCVpm7hPx0gsgh+jgbZo0DTXO76b/XTXkPOBfrpR4qVj2p9hRZ25LbciPbO2k6 9IIlCx3dEG0gRe9npDPlIrLvgYufh9dt3LWoDPG0KEkj7S/RUcqgoNO1amHeHnx1TJov 1DoehFNjPeOXnz3lEhHmfitiZiCh/xtMt9RBxJqsBHdYRIE4CpsW75Po81i8y/3ALnoo 82Jw== X-Gm-Message-State: AOAM532rWdDZcQBgiOHm2MD3JAxWsrVzHtHB/i4aq+VIThFKRCaLEHDj zRpByIln6hXv5vwiOSzD1YqXZw== X-Google-Smtp-Source: ABdhPJz26GMP6kACUt//jU5Az91bnlmsy5wYYd312LDn8aDW6jY3j9fs4jPdZV2Yqp9tCIl7SyygEQ== X-Received: by 2002:a9d:6409:0:b0:5ad:2055:9bdc with SMTP id h9-20020a9d6409000000b005ad20559bdcmr6171517otl.93.1648751536168; Thu, 31 Mar 2022 11:32:16 -0700 (PDT) Received: from ripper ([2600:1700:a0:3dc8:205:1bff:fec0:b9b3]) by smtp.gmail.com with ESMTPSA id s125-20020acaa983000000b002ecdbaf98fesm64878oie.34.2022.03.31.11.32.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 31 Mar 2022 11:32:15 -0700 (PDT) Date: Thu, 31 Mar 2022 11:34:45 -0700 From: Bjorn Andersson To: Viresh Kumar Cc: Dmitry Baryshkov , Andy Gross , "Rafael J. Wysocki" , linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org, Thara Gopinath Subject: Re: [PATCH v4 0/4] cpufreq: qcom-hw: Fixes for cpu hotplug support Message-ID: References: <20220326155153.7377-1-dmitry.baryshkov@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220326155153.7377-1-dmitry.baryshkov@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Sat 26 Mar 08:51 PDT 2022, Dmitry Baryshkov wrote: > This patchseries aims at fixing and improving CPU hotplug support on > Qualcomm platforms. First three patches are the fixes for the LMH > support in the cpufreq driver. The last patch adds support for > lightweight offline() and online() callbacks which are used instead of > exit() and init() each time the CPU is put offline or back online. > > Patches 1-3 being pure simple fixes can be applied during the -rc > stage, while patch 4 is targeting next development cycle > Viresh, please consider picking up patch 1-3 for v5.18-rc. Thanks, Bjorn > Changes since v3: > - Readd throttled_freq calculation disappearing from the third patch. > > Changes since v2: > - Point Fixes tag from the first patch to the correct commit > - Replace huge patch 2 with one-liner thanks to being able to use > policy->related_cpus instead of policy->cpus > > Changes since v1: > - Update commit message for the first patch to describe why dropping > affinity hint is required (before calling free_irq()), > - Fixed commit message for the second patch to include messages > generated using the mainline kernel w/o additional patches, > - Changed third patch to use dev_warn_ratelimited(), > - Reworked last patch to move request_irq/free_irq to online()/offline() > to make sure that the IRQ isn't left enabled after the CPU has been > put offline. > > > Dmitry Baryshkov (4): > cpufreq: qcom-hw: drop affinity hint before freeing the IRQ > cpufreq: qcom-hw: fix the race between LMH worker and cpuhp > cpufreq: qcom-hw: fix the opp entries refcounting > cpufreq: qcom-hw: provide online/offline operations > > drivers/cpufreq/qcom-cpufreq-hw.c | 45 ++++++++++++++++++++++++++----- > 1 file changed, 38 insertions(+), 7 deletions(-) > > -- > 2.35.1 >