From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>, x86@kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
rjw@rjwysocki.net, anshuman.gupta@intel.com,
linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH v2] x86: i8237: Register based on FADT legacy boot flag
Date: Wed, 14 Mar 2018 14:48:27 +0200 [thread overview]
Message-ID: <1521031707.10722.632.camel@linux.intel.com> (raw)
In-Reply-To: <1521004627-30329-1-git-send-email-rajneesh.bhardwaj@intel.com>
On Wed, 2018-03-14 at 10:47 +0530, Rajneesh Bhardwaj wrote:
> 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 refer to chapter 21 of 6th Generation Intel® Core™ Processor
> Platform Controller Hub Family: BIOS Specification.
>
> https://www.intel.in/content/www/in/en/embedded/products/skylake/u-mob
> ile/software-and-drivers.html
>
> Cc: Alan Cox <alan@linux.intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
> ---
> Changes in v2:
> * changed to dma_inb()
>
> This depends on recently introduced dmi_get_bios_year() helper.
> https://patchwork.kernel.org/patch/10252151/
> arch/x86/kernel/i8237.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/x86/kernel/i8237.c b/arch/x86/kernel/i8237.c
> index 8eeaa81de066..bf5d8104e17b 100644
> --- a/arch/x86/kernel/i8237.c
> +++ b/arch/x86/kernel/i8237.c
> @@ -9,6 +9,7 @@
> * your option) any later version.
> */
>
> +#include <linux/dmi.h>
> #include <linux/init.h>
> #include <linux/syscore_ops.h>
As kbuild bot rightfully noticed, you need to add
x86_init.h inclusion to the driver.
>
> @@ -49,6 +50,30 @@ static struct syscore_ops i8237_syscore_ops = {
>
> static int __init i8237A_init_ops(void)
> {
> + /*
> + * From SKL PCH onwards, the port 0x61 bit 4 would stop
> toggle and
> + * the legacy DMA device is removed in which the I/O ports
> (81h-83h,
> + * 87h, 89h-8Bh, 8Fh) related to it are removed as well. All
> + * removed ports must return 0xff for a inb() request.
> + *
> + * Note: DMA_PAGE_2 (port 0x81) should not be checked for
> detecting
> + * the presence of DMA device since it may be used by BIOS to
> decode
> + * LPC traffic for POST codes. Original LPC only decodes one
> byte of
> + * port 0x80 but some BIOS may choose to enhance PCH LPC port
> 0x8x
> + * decoding.
> + */
> + if (dma_inb(DMA_PAGE_0) == 0xFF)
> + return -ENODEV;
> +
> + /*
> + * It should be OK to not load this driver as newer SoC may
> not
> + * support 8237 DMA or bus mastering from LPC. Platform
> firmware
> + * must announce the support for such legacy devices via
> + * ACPI_FADT_LEGACY_DEVICES field in FADT table.
> + */
> + if (!x86_platform.legacy.devices.pnpbios &&
> dmi_get_bios_year() >= 2017)
> + return -ENODEV;
> +
> register_syscore_ops(&i8237_syscore_ops);
> return 0;
> }
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-03-14 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 5:17 [PATCH v2] x86: i8237: Register based on FADT legacy boot flag Rajneesh Bhardwaj
2018-03-14 12:48 ` Andy Shevchenko [this message]
2018-03-14 15:07 ` Thomas Gleixner
[not found] ` <20180319104627.GA2959@anshuman.gupta@intel.com>
2018-03-19 10:57 ` Thomas Gleixner
2018-03-22 10:21 ` [PATCH v3] " Anshuman Gupta
2018-03-22 11:05 ` Rajneesh Bhardwaj
2018-03-22 11:17 ` Thomas Gleixner
2018-03-25 11:50 ` Thomas Gleixner
2018-03-26 5:48 ` Rajneesh Bhardwaj
2018-03-26 9:11 ` Thomas Gleixner
2018-03-26 10:34 ` hpa
2018-03-26 10:51 ` Rajneesh Bhardwaj
2018-03-26 14:55 ` Alan Cox
2018-03-29 15:06 ` [PATCH v4] " Anshuman Gupta
2018-04-27 15:06 ` [tip:x86/dma] x86/i8237: Register device " tip-bot for Rajneesh Bhardwaj
2018-03-26 14:52 ` [PATCH v3] x86: i8237: Register " Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1521031707.10722.632.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rajneesh.bhardwaj@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox