Received: by 2002:a05:7412:8d09:b0:fa:4c10:6cad with SMTP id bj9csp365891rdb; Tue, 16 Jan 2024 02:52:34 -0800 (PST) X-Google-Smtp-Source: AGHT+IHj8F8rru53WXTgCJtPS7X/tO9N49iJnFF1Grv47FXHuteQbMz2l869FRfN0wGt0onCbYBd X-Received: by 2002:a05:6402:27c8:b0:558:fbad:f98c with SMTP id c8-20020a05640227c800b00558fbadf98cmr2425218ede.80.1705402354776; Tue, 16 Jan 2024 02:52:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705402354; cv=none; d=google.com; s=arc-20160816; b=O5Ly6QJCVbRYypXcQHFP0Lx0PHFVEgUnfszTPNL88nSZu6xY7GgGTiB6YwE9aipXNl C+9YVSwZfigktSf1DwkLqG86HcH9gOKS8gDGl/PBeCN88z4Gl1b9V4eLkDKPB0WEFs5v rGYHaP8+v4FGNmenRPZC4KFRjjO3iAI8+VkdA0c9WoZg8WqG4NXPOfqmSU6lTkgnUZx3 U+GzOZyzu2np6W4GFfXpi6vWilHnWtQf9GKHUNAPNZ3As+06warmLKVpyt2oKYFIQwG8 Mt7lcAd/JtOT5cMrrt/OMfAMWVPJrRjlg2V6zxsCQgJDunggMBgB+ckIAEjlFU/K13jQ NQaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=vpCSz1gcu23O1tNH4aKrk8Zne4yNYvGJlTPWJ2tDpcU=; fh=EUO5FRhk270zfNEw8/LZoQm+MoCGmHhKK7Z1Y5QIng0=; b=TcFBxAkw3cKPmLGsgP6ZMRcFUpdQLVrnSyC/X0RKVFhz8ctcCMO9zWzGHssIgArF3c EZDvrmVjM00tEC4jTMzPBzCRtAjglJWQWFExBlakpPWnS208axInbXS/ojC6Cfmr+doy BsPey59tmSEGK8D4MGMhewnsfzL2HYY+g9qucG5S04ZUQ+R9r5dUXMaIQlc4XRrPzH2S ANXc8XdBpp26A+i5Udk6eSeIa0ItlCXCFoaKd5JIBxD/+PRZi5a1lXQLcKBHwNQN6L/p wMZTv9MEEakQz9uu6dBi6Rj6qHxqWsEN1au+A02ug9ORPyDBtOtBiZo+XopI/4Ei3/E0 kTrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="q/siWHr/"; spf=pass (google.com: domain of linux-kernel+bounces-27275-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-27275-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id bf14-20020a0564021a4e00b0055829fda74fsi4668017edb.652.2024.01.16.02.52.34 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jan 2024 02:52:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-27275-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="q/siWHr/"; spf=pass (google.com: domain of linux-kernel+bounces-27275-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-27275-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 8611A1F23734 for ; Tue, 16 Jan 2024 10:52:34 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 0ADBE19474; Tue, 16 Jan 2024 10:52:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="q/siWHr/" Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2F5D918ED4; Tue, 16 Jan 2024 10:52:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 01973C433C7; Tue, 16 Jan 2024 10:52:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705402335; bh=BpbxDcIY7558bHQDUuyuGyNMq+oP8ZHFVNuaKBYpl5M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=q/siWHr/EtfTYBSZGrMUixPO2QBiptnFHYjLQBr5LUvxrxyXz3BlOhinXJ4TE8w0N 1Y327yig1QkwHLajIcsJePKdi752w8xm1aZrrC4Ge5ijT2a9BgTrv8hh0JgzmSeF/+ 58GadoI3bn7VV6u5xfgV4qUTtVOQxjrza4YtsS+/Dei5SnoGt6wciahu96xVjDioch fzSY4/Za0lY023dsWvm9kOFtzUeTqR4gAMUNc2s/aIm4nn523DK9Lr+CcO7j7BSdfa XqseLTVloahJwwqWXjNr06aZSHCkKJfXWrgyDJUq1Veh2SRH5cV+Ov7U5B2LRhORpq zAeOIKsleeZLg== Received: from johan by xi.lan with local (Exim 4.96.2) (envelope-from ) id 1rPh3I-0005Z7-38; Tue, 16 Jan 2024 11:52:17 +0100 Date: Tue, 16 Jan 2024 11:52:16 +0100 From: Johan Hovold To: Konrad Dybcio Cc: Bryan O'Donoghue , Krishna chaitanya chundru , Bjorn Andersson , Bjorn Helgaas , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Manivannan Sadhasivam , Rob Herring , Johan Hovold , Brian Masney , Georgi Djakov , linux-arm-msm@vger.kernel.org, vireshk@kernel.org, quic_vbadigan@quicinc.com, quic_skananth@quicinc.com, quic_nitegupt@quicinc.com, linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v6 3/6] PCI: qcom: Add missing icc bandwidth vote for cpu to PCIe path Message-ID: References: <20240112-opp_support-v6-0-77bbf7d0cc37@quicinc.com> <20240112-opp_support-v6-3-77bbf7d0cc37@quicinc.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Jan 12, 2024 at 11:33:15PM +0100, Konrad Dybcio wrote: > On 12.01.2024 16:17, Bryan O'Donoghue wrote: > > On 12/01/2024 14:22, Krishna chaitanya chundru wrote: > >> CPU-PCIe path consits for registers PCIe BAR space, config space. > >> As there is less access on this path compared to pcie to mem path > >> add minimum vote i.e GEN1x1 bandwidth always. > >> > >> In suspend remove the cpu vote after register space access is done. > >> > >> Fixes: c4860af88d0c ("PCI: qcom: Add basic interconnect support") > > > > If this patch is a Fixes then don't you need the accompanying dts change as a parallel Fixes too ? > > > > i.e. without the dts update - you won't have the nodes in the dts to consume => applying this code to the stable kernel absent the dts will result in no functional change and therefore no bugfix. > > The Fixes tag denotes a bug fix, its use for backport autosel is just > a nice "coincidence". > > Fixing a lack of a required icc path and having to rely on BL leftovers > / keepalive bus settings is definitely worth this tag in my eyes. An incomplete implementation can sometimes be considered a bug, but not always. If this is needed to enable a new use case, then it's hard to argue that the original omission was a bug. And as I just mentioned to Krishna, the above Fixes tag is not correct as that commit did not *introduce* any issue. It solved the bit that was strictly needed for sc8280xp, but now it seems you may need something more for an even newer platform (even if no details and motivation was included in the commit message as it should have been). Johan