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;
Date:   Sun, 25 Mar 2018 13:50:40 +0200 (CEST)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Anshuman Gupta <anshuman.gupta@intel.com>
cc:     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,
        rajneesh.bhardwaj@intel.com
Subject: Re: [PATCH v3] x86: i8237: Register based on FADT legacy boot flag
In-Reply-To: <1521714118-31282-1-git-send-email-anshuman.gupta@intel.com>
Message-ID: <alpine.DEB.2.21.1803251348190.1481@nanos.tec.linutronix.de>
References: <alpine.DEB.2.21.1803191152450.2010@nanos.tec.linutronix.de> <1521714118-31282-1-git-send-email-anshuman.gupta@intel.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 22 Mar 2018, Anshuman Gupta wrote:

> From: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
> 
> >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.

Thanks,

	tglx