Received: by 2002:a05:7412:8d09:b0:fa:4c10:6cad with SMTP id bj9csp366724rdb; Tue, 16 Jan 2024 02:54:58 -0800 (PST) X-Google-Smtp-Source: AGHT+IFx04NcCPIsfBZ4E4M6MQCwFtR8cxYNq0tRbDxyxozmpOQs5mxPLhlXztDTwwNe9omRDkJT X-Received: by 2002:a17:907:804:b0:a28:fb5a:510b with SMTP id wv4-20020a170907080400b00a28fb5a510bmr4348075ejb.108.1705402498677; Tue, 16 Jan 2024 02:54:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705402498; cv=none; d=google.com; s=arc-20160816; b=KJVqa1aA0gmB9lxReNYk8kfx2w8W3H/Z+ED97Qj6KecSL9omIbLJNSxEYK3duSMmj/ j+3e/jzrtRIWQjkT9HXDiGDLrHhp1ck5XNDGk/JJ/u/BsPmQImv4SGNTo3ZgnJdEpwBL 9qeUV9ofpoYqiVrUxqJg6xvqBkKYNSABurRC1105OmQmTZ/r88uynqL/jGadcoD5Ox6C 21m3jQ8ONPQs3QXhaE/hMVP4gGAm+xB08EW7VWMMnT+SxZh+eXrMb240CisgMcGeN4Im rnnUKDXtABL/UK6d/clz3guNsazrx0oyWhPr9xXWmlJbDqmsvsRMNEwIHppQ5Eu30EOw TyNw== 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=jep3hRKQAUFNzrTekGjAZFLRlMr02On0ShajImOef6Y=; fh=keOp1waVGFOIPsLyOD2PPyTrB1qft0ieUqMHB7Mne4s=; b=wasPO0AopWMBBZgHBPOaaRvYqEF+MWbM+0qgPONmZDBzDt4/xxNC/UMi3mbtGtzDQ/ 7culq78AocVhpimV7MfGG9I8mSfLAsOoY3P1Ut4o43SNLACKUY8nzJfYXnywTDOZT1P+ h0CtrlKCPchU7hy8sGdhzXt1y9P4oxU7/fBV5MPI8/iQK5PqVJvEeIjnSPInZEC4rgZg +OVpvwkD0i0dDwzjwp7uff4w+TgUuHDEm7KSSiSa6kezS/pDFfbma6LwgIWZ0kYXT4uB 9f2ZmByYYEuEaKVSB4vZaIgLKBDfFX42r2VWkQ6W2y0ewbIWHm9atdgAUoj4eeGx+CeC 3gwQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=CkibayD3; spf=pass (google.com: domain of linux-kernel+bounces-27279-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-27279-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. [147.75.80.249]) by mx.google.com with ESMTPS id v1-20020a170906180100b00a232a3191f0si4605039eje.254.2024.01.16.02.54.58 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jan 2024 02:54:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-27279-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=CkibayD3; spf=pass (google.com: domain of linux-kernel+bounces-27279-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-27279-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 4621A1F24073 for ; Tue, 16 Jan 2024 10:54:58 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id BF0CC19BAD; Tue, 16 Jan 2024 10:54:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CkibayD3" 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 E355A1946A; Tue, 16 Jan 2024 10:54:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B2429C433F1; Tue, 16 Jan 2024 10:54:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705402474; bh=/TPtCyoAj2paX8eC4HnNYeTrC2FQGolk8jnOVJ8gIv8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CkibayD3nkZ6flLmYjvkpiDDMSNhJ6bsH4iI5jBfozOGIlVv4NFG96Avn6FuypmNe LyURk6NvYS5ptoKaN04vXcxi3rwhXwcmIfiCS22xl4S/Gfbq5XXcIQsrIe1oBnOApw Ax44UY8Mdi9/eved8OsMDNFlRLAr1CrtE+K7OkieDG3eCyWPH5Wgy/z58EGNSqCKQW 1KnI0K4KhrRcwErjEnbKDnZF1NKjgs8yyNjUQ8wO9+hI0CIVbgxeRoQiXdIkkYOJzD 7u3NRwdlBS2SAeYNgRSFyxLOorDwox4jvaqfMZTAZpwf8fHC9EEGq7UKWNHDm2aflO P8OQMk3y9kBBA== Received: from johan by xi.lan with local (Exim 4.96.2) (envelope-from ) id 1rPh5Z-0005ZS-1a; Tue, 16 Jan 2024 11:54:37 +0100 Date: Tue, 16 Jan 2024 11:54:37 +0100 From: Johan Hovold To: Konrad Dybcio Cc: 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:37:03PM +0100, Konrad Dybcio wrote: > On 12.01.2024 16:59, Johan Hovold wrote: > > On Fri, Jan 12, 2024 at 07:52:02PM +0530, Krishna chaitanya chundru wrote: > >> CPU-PCIe path consits for registers PCIe BAR space, config space. > > > > consits? > > > >> As there is less access on this path compared to pcie to mem path > >> add minimum vote i.e GEN1x1 bandwidth always. > > > > gen1 bandwidth can't be right. > > > >> In suspend remove the cpu vote after register space access is done. > >> > >> Fixes: c4860af88d0c ("PCI: qcom: Add basic interconnect support") > >> cc: stable@vger.kernel.org > > > > This does not look like a fix so drop the above. > > > > The commit you refer to explicitly left this path unconfigured for now > > and only added support for the configuring the mem path as needed on > > sc8280xp which otherwise would crash. > > I only sorta agree. I'd include a fixes tag but point it to either 8450 > addition or original driver introduction, as this is patching up a real > hole (see my reply to Bryan). Right, the above Fixes tag is not correct in any case. And with a complete commit message it may be possible to tell whether a Fixes tag is warranted or not. Johan