Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp674480ybb; Fri, 10 Apr 2020 07:54:17 -0700 (PDT) X-Google-Smtp-Source: APiQypKneVWNU/crphnrmE4VIGt/Zuz+u6q2782NLMIzZavKAVcUw0sTkuHC1AZhv5r9x/Tfyvg3 X-Received: by 2002:a05:620a:1292:: with SMTP id w18mr4552362qki.276.1586530457267; Fri, 10 Apr 2020 07:54:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586530457; cv=none; d=google.com; s=arc-20160816; b=o755PYUVReRTSYymBOX3+v/zDycnGpfnBroab865TfjvRISysSGKiS7D1r5HE+STR6 OQiDwi4wPNnJJdhLaVqoCRI0ChO48ajO821eMSPep5oqCoJepcxSvKbkGIMbqHTdt8xD eITAf5YkZ9TV4y68uSmooRme96JwM3a4iKYJafb7CkDoc7BCUHfzI7fwUh3+0XiGU2ci R45SdyFhTBpB0Iq/dS+LPIU92KRcRjfleePCFJXBz8gzQ8j6G1mDyODprHgAzFRxzKkd 5lN0rM2r8MR0Lm2USxeU2Kq36MxRNYLCgYs1J3vFUX0Gv7WTjzxW4h3fpY0SlwC9P5eu iWTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=sXbs2eSo2cip0Bhx0gise5pTsMBWhGiPepQWudlrrKs=; b=akH6FA7jcD3BeYDg0L5py21kUM6pHQyHK95sW/nEwQ8pZzpOgmpFTgF4d3OkFvW9Dm X13itFjGFrjXWjCOyNybqfI/1oeAlXOAzstNpwONc/obM2NlZf/moJKdfFTX/wDmkUB5 BO4Fm1A+YqdDIACFAOMenDfvdr6jMtf4D9T+T1CEQri9fGRfE5y8vbzeVCv/lAnrXrVD xxUcJgDCnQjQBgN3CUuMtPN9gN6FzFnv8MFgRQg617gnb6gnqqjvPn5XShPK/OgriFHv yWpkSnCkv66OoMr+ERL3o5cG/Q9lZmUrQp0cpDiplved38p9fogR9bekHmPLBOX8hzeL 3+1A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=IQaN9Kus; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m23si1280059qtn.35.2020.04.10.07.54.01; Fri, 10 Apr 2020 07:54:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=IQaN9Kus; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726659AbgDJOxH (ORCPT + 99 others); Fri, 10 Apr 2020 10:53:07 -0400 Received: from mail-vk1-f193.google.com ([209.85.221.193]:42735 "EHLO mail-vk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726145AbgDJOxH (ORCPT ); Fri, 10 Apr 2020 10:53:07 -0400 Received: by mail-vk1-f193.google.com with SMTP id q7so586995vkb.9 for ; Fri, 10 Apr 2020 07:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sXbs2eSo2cip0Bhx0gise5pTsMBWhGiPepQWudlrrKs=; b=IQaN9KussGunjaHK0pdxgBSCx4RVNoghmD135k0hs2w75kdaoTKcoRE1PJ5lbo93ww lGQAaiETFOrzVMXrOQGyjT5Xw7dQCwQsxq8RN1dcYWo8GLAEt4ygV3NHbzzeGeRNmO1k cewZcsSAJHMTeay1xQEeMe5Po0m1DEfvIB4yE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sXbs2eSo2cip0Bhx0gise5pTsMBWhGiPepQWudlrrKs=; b=NV3UO6YnD8vmFeoDrH/pv1rBUNh8uY5zFw6ROPD8ADn8aD22LsmBEVNz9CmALNewpK 9Ym8s/NYNKDONyTt7Zapuf2XCUge9LP13AHPuVW5Xi/k7eQWQzQJHezcylpvwI83+k1d h7VXpIvKDvScvam0LpK7VztfdWB7hc7Cc1XyRFnbmi7X+WArxPiNCZ/LstXjStR1bBYD +Chkbrgpm/g3BzlD2M4QLBN5IESkiahHGoIWyMRIgUMgRPM0Q8rafeVkB2NameS0uVdR dKBLYxy7JQ4JJhvz65scfM0C3P/h0TLez3u4ubKXV/tSHFdBjQV6LRp4PKQ8zEQFcrCZ cf1g== X-Gm-Message-State: AGi0Pua5kxm3JjM1Ru6bEKGRz6jewIRFmYtaMwYfnJbNP7FBRyr2f9m4 Ea5KWlsvHh4t4yl4mEb7IrkCsLGlxec= X-Received: by 2002:a1f:3a0a:: with SMTP id h10mr3632417vka.43.1586530385804; Fri, 10 Apr 2020 07:53:05 -0700 (PDT) Received: from mail-ua1-f49.google.com (mail-ua1-f49.google.com. [209.85.222.49]) by smtp.gmail.com with ESMTPSA id w1sm657101vkm.45.2020.04.10.07.53.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Apr 2020 07:53:04 -0700 (PDT) Received: by mail-ua1-f49.google.com with SMTP id c7so686423uap.12 for ; Fri, 10 Apr 2020 07:53:04 -0700 (PDT) X-Received: by 2002:a9f:27ca:: with SMTP id b68mr1030762uab.8.1586530383958; Fri, 10 Apr 2020 07:53:03 -0700 (PDT) MIME-Version: 1.0 References: <1586154741-8293-1-git-send-email-mkshah@codeaurora.org> <1586154741-8293-5-git-send-email-mkshah@codeaurora.org> <158649213142.77611.5740203322498170248@swboyd.mtv.corp.google.com> In-Reply-To: <158649213142.77611.5740203322498170248@swboyd.mtv.corp.google.com> From: Doug Anderson Date: Fri, 10 Apr 2020 07:52:52 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v16 4/6] soc: qcom: rpmh: Invoke rpmh_flush() for dirty caches To: Stephen Boyd Cc: Maulik Shah , Bjorn Andersson , Evan Green , LKML , linux-arm-msm , Andy Gross , Matthias Kaehlcke , Rajendra Nayak , Lina Iyer , lsrao@codeaurora.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Thu, Apr 9, 2020 at 9:15 PM Stephen Boyd wrote: > > > int rpmh_flush(struct rpmh_ctrlr *ctrlr) > > This function name keeps throwing me off. Can we please call it > something like rpmh_configure_tcs_sleep_wake()? The word "flush" seems > to imply there's some sort of cache going on, but that's not really the > case. We're programming a couple TCS FIFOs so that they can be used > across deep CPU sleep states. I'm hoping this rename can be deferred until Maulik's series and my cleanup series land. While I agree that rpmh_flush() is a bit of a confusing name, it's not a new name and renaming it midway through when there are a bunch of patches in-flight is going to be a hassle. Assuming others agree, my thought is that Maulik will do one more v17 spin with small nits fixed up, then his series can land early next week when (presumably) -rc1 comes out. If my current cleanup doesn't apply cleanly (or if Bjorn/Andy don't want to fix the two nits in commit messages when applying) I can repost my series and that can land in short order. Once those land: * Maulik can post this rpmh_flush() rename atop. * I can post the patch to remove the "pm_lock" that was introduced in this series. A preview at . * Maulik can post some of the cleanups that Maulik wanted to do in rpmh.c with regards to __fill_rpmh_msg() ...assuming those are not controversial perhaps they can be reviewed quickly and land quickly? I suppose I can always dream... -Doug