Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp770344pxy; Wed, 28 Apr 2021 13:56:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwvjSLAOLGthU173f7bXZfkoFHxds9OeTA7VB3zX/+VKJWUVPfqSkzqTn/8MnbTnBx1dk44 X-Received: by 2002:aa7:c510:: with SMTP id o16mr7371500edq.310.1619643389373; Wed, 28 Apr 2021 13:56:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619643389; cv=none; d=google.com; s=arc-20160816; b=ZNm7PQDR8yUoIj8yaJUnc2aVpTmLGPrnfyb8izWc9v4gSUrDdzjshwN8sU5jQBRJUV corZ7HIQiWsLutOysFWO3YykRp12NBA/u9ERhNybJpz61lB14J4WVi9AuLYh4Zjv86Zn XyldC1t+XrocGTJDMxtcTH8sUZuhyhGsyBdqUlTYq/is8eNHMRRBwp0YW/ytfz9ac2fI KwJmIoFTf3zGAhbRr7iTNWnluAyniS5jk9SRh7KmVNcZhiAfGFdv14qVhH3ZflHYganL LQWj6Z+mQFNcV94uvojd1D8t/4EKEkBxovFJcJNVJMJKuNL51M+lyPX3+zh5IZ+M0xiK RODg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=OBkBXlgLdpycndjVNuWJIFPqFjnLpUllNGj/6rmLTSI=; b=FzFxbFt4V/LfWSpG00fJchj0riS5qV5Pz1njhsHVM8T37+dUh4l5L8Lr7ESN+RuBKl oPgQufNJzgAOpzD1q4jWe626+I+zihSaW1n7c8OvSqt+FORNZxSgDo51nMB53AZYFIrb J4z2dty4i6QMhSDNiKPWKMmPQJp0xeYLveIU/FtcYvUvNsuR8eemfN/OEq5XnbQJi5KF pXYTW+nYIrWBlILT0WmNiAKoh4m2sHwaYARD85T8BbfJhoQfDlbNzyslMIbVSjmUCW0F WAAt8QgVk1sBkcBNaPJ4tDg50AfjH4L5MwJUAqsRfx7pSol5o4fxiOl3ySaa7Fcn3ODb rd/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c3si1043135ejs.248.2021.04.28.13.56.03; Wed, 28 Apr 2021 13:56:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243591AbhD1SM6 (ORCPT + 99 others); Wed, 28 Apr 2021 14:12:58 -0400 Received: from 8bytes.org ([81.169.241.247]:36574 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240210AbhD1SM5 (ORCPT ); Wed, 28 Apr 2021 14:12:57 -0400 Received: by theia.8bytes.org (Postfix, from userid 1000) id 32FF9366; Wed, 28 Apr 2021 20:12:11 +0200 (CEST) Date: Wed, 28 Apr 2021 20:12:07 +0200 From: Joerg Roedel To: "Kuppuswamy, Sathyanarayanan" Cc: Bjorn Helgaas , rjw@rjwysocki.net, Len Brown , linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Joerg Roedel Subject: Re: [RFC PATCH] PCI/APCI: Move acpi_pci_osc_support() check to negotiation phase Message-ID: References: <20210428081857.10322-1-joro@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 28, 2021 at 10:21:12AM -0700, Kuppuswamy, Sathyanarayanan wrote: > > > On 4/28/21 1:18 AM, Joerg Roedel wrote: > > From: Joerg Roedel > > > > The acpi_pci_osc_support() does an _OSC query with _OSC supported set > > to what the OS supports but a zero _OSC control value. This is > > problematic on some platforms where the firmware allows to configure > > whether DPC is under OS or Firmware control. > > Do we run acpi_pci_osc_support() only to check whether _OSC is > supported ? Or does it serve any other purpose. I am not 100% sure, but to me it looks like the pure purpose of the acpi_pci_osc_support() call was indeed to check whether the firmware is willing to grant the OS control over some PCIe features. > > When DPC is configured to be under OS control these platforms will > > issue a warning in the firmware log that the OS does not support DPC. > > Also, is there any other benefit from this patch other than fixing > a warning message in firmware? Not much other benefit, besides some removed code. But those messages can confuse the system owner and are worth getting rid of imho. Regards, Joerg