Received: by 10.213.65.68 with SMTP id h4csp1058906imn; Sun, 25 Mar 2018 22:54:48 -0700 (PDT) X-Google-Smtp-Source: AG47ELv5/DSGVDraR29t3NYIpifDlINZ/cWVqAvfEcaF6eo11UmJcvIu/S1iXNlxB4uUh9xS7ygu X-Received: by 2002:a17:902:2f03:: with SMTP id s3-v6mr18131870plb.274.1522043688806; Sun, 25 Mar 2018 22:54:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522043688; cv=none; d=google.com; s=arc-20160816; b=ShwVFsuVirbbULCoVOiLhoiWBNpwK+gB0MKgNblV2XCL0TGL94IXIpRFCldbfj9M9Z MNdRKZT5hPI5fbjlQmtb3m5lVNjwGsXd3fMcIb1fJbnCn0vm4VYDuaZgyG14gbkxfBUk IlnIcvwmp4GBevbxP+FwAiDM4S5jjZDIu0zuA9JDO4vAjUaeYSQPBPnaOJbj0lZxsTIk 2VAb0FBYhiWI0S5Dsce6+mOILvh8uV+j8BldvgGgeXKXphwOhFcgYHETGnicN6uKr379 C67Sk2JUxZm968pvj4JN8xavcafjHnqI4p6x1DomFLn14ztySBJ0jdDHm1UIAqAR0avT go4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=FguBYHgwQWSp04TAdZjWRHn4d4fjlhdivr76mA1Znr0=; b=qsfZdHeHYoerYfVE0UTxmWTAMVPI8zge5z7lktWvO1Mk6GdmeLIZ3ha8CI3NGFpM7/ yN3WTpvDufVK/7Cxi6DDJsy/8TH5AWEWGcJTQ4f0qQ1xeV9/KOD0hJMlza16ApcQY3H5 VpVfndUQY3eZf8oUEmmjeMe7q3Y0UE7UzJLXq/ZuMmiSNJpsh4EuIWi+7wPtY6fzRfIU jUEUnBPHZLaLTV28qaLE35mxrKpK6mL+tnTrZIsA35ydDlsuZZw1ceInZynZbVFlU/pC 5RjSNvN26CZKgRYDn52wornNhEhyzyFrwmQNekcaQUDGX47b9ZJz632oaugmuH0QRwHA Tk+w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f61-v6si10291701plb.291.2018.03.25.22.54.33; Sun, 25 Mar 2018 22:54:48 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750961AbeCZFxj (ORCPT + 99 others); Mon, 26 Mar 2018 01:53:39 -0400 Received: from mga07.intel.com ([134.134.136.100]:7637 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750813AbeCZFxi (ORCPT ); Mon, 26 Mar 2018 01:53:38 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Mar 2018 22:53:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,363,1517904000"; d="scan'208";a="41213467" Received: from raj-desk2.iind.intel.com ([10.223.107.30]) by fmsmga001.fm.intel.com with ESMTP; 25 Mar 2018 22:53:35 -0700 Date: Mon, 26 Mar 2018 11:18:33 +0530 From: Rajneesh Bhardwaj To: Thomas Gleixner Cc: Anshuman Gupta , glx@linutronix.de, x86@kernel.org, mingo@redhat.com, hpa@zytor.com, rjw@rjwysocki.net, andriy.shevchenko@linux.intel.com, alan@linux.intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] x86: i8237: Register based on FADT legacy boot flag Message-ID: <20180326054833.GA25173@raj-desk2.iind.intel.com> References: <1521714118-31282-1-git-send-email-anshuman.gupta@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 25, 2018 at 01:50:40PM +0200, Thomas Gleixner wrote: > On Thu, 22 Mar 2018, Anshuman Gupta wrote: > > > From: Rajneesh Bhardwaj > > > > >From Skylake onwards, the platform controller hub (Sunrisepoint PCH) does > > not support legacy DMA operations to IO ports 81h-83h, 87h, 89h-8Bh, 8Fh. > > Currently this driver registers as syscore ops and its resume function is > > called on every resume from S3. On Skylake and Kabylake, this causes a > > resume delay of around 100ms due to port IO operations, which is a problem. > > > > This change allows to load the driver only when the platform bios > > explicitly supports such devices or has a cut-off date earlier than 2017. > > Please explain WHY 2017 is the cut-off date. I still have no clue how that > is decided aside of being a random number. Hello Thomas, We tested on few Intel platforms such as Skylake, Kabylake, Geminilake etc and realized that the BIOS always sets the FADT flag to be true though the device may not be physically present on the SoC. This is a BIOS bug. To keep the impact minimum, we decided to add a cut-off date since we are not aware of any BIOS (other than the coreboot link provided in the commit msg) that properly sets this field. SoCs released after Skylake will not have this DMA device on the PCH. So, because of these two reasons, we decided to add a cut-off date as 2017. Please let us know if you feel strongly about it and we can change it or remove it if you feel so. Ideally, we didnt want to add this BIOS check at all and only wanted to use inb() approch but unfortunately, that too was broken for port 0x81. @Rafael / Alan / Andy - Please add more or correct me in case of anything missed or not communicated fully. > > Thanks, > > tglx -- Best Regards, Rajneesh