linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, rafael.j.wysocki@intel.com,
	Kumar P Mahesh <mahesh.kumar.p@intel.com>,
	Heikki Krogerus <heikki.krogerus@intel.com>
Subject: Re: [PATCH] ACPI / LPSS: Ignore 10ms delay for Braswell and Baytrail
Date: Thu, 27 Aug 2015 21:43:21 +0530	[thread overview]
Message-ID: <20150827161321.GA9886@intel-desktop> (raw)
In-Reply-To: <20150827071414.GB28428@lahna.fi.intel.com>

On Thu, Aug 27, 2015 at 10:14:14AM +0300, Mika Westerberg wrote:
> On Thu, Aug 27, 2015 at 08:09:55PM +0530, Kasagar, Srinidhi wrote:
> > On Mon, Aug 24, 2015 at 12:44:55PM +0300, Mika Westerberg wrote:
> > > On Mon, Aug 24, 2015 at 10:39:21PM +0530, Kasagar, Srinidhi wrote:
> > > > Ok, then we have two options:
> > > > 
> > > > Let's drop LPSS_NO_D3_DELAY for BYT and duplicate the common devices which
> > > > are shared between Braswell and BYT & keep LPSS_NO_D3_DELAY only for BSW.
> > > 
> > > That sounds the safest option for now.
> > > 
> > > > OR
> > > > Use the cpu id to detect the platform which I believe not a good idea..
> > > > 
> > > > Because of few devices, I do not think it make sense to compromise on
> > > > the significant reduction in the resume delay.
> > > 
> > > I agree.
> > 
> > Refreshed the patch (below) affecting BSW platform alone.
> > 
> > But this does not solve your earlier concern on Broadwell which
> > shares the same acpi ids..
> 
> It does not share IDs:

Oh, Thanks..

> 
>         /* Braswell LPSS devices */
>         { "80862288", LPSS_ADDR(byt_pwm_dev_desc) },
>         { "8086228A", LPSS_ADDR(byt_uart_dev_desc) },
>         { "8086228E", LPSS_ADDR(bsw_spi_dev_desc) },
>         { "808622C1", LPSS_ADDR(byt_i2c_dev_desc) },
> 
> 	/* The following are Broadwell LPSS IDs _not_ Braswell */
>         { "INT3430", LPSS_ADDR(lpt_dev_desc) },
>         { "INT3431", LPSS_ADDR(lpt_dev_desc) },
>         { "INT3432", LPSS_ADDR(lpt_i2c_dev_desc) },
>         { "INT3433", LPSS_ADDR(lpt_i2c_dev_desc) },
>         { "INT3434", LPSS_ADDR(lpt_uart_dev_desc) },
>         { "INT3435", LPSS_ADDR(lpt_uart_dev_desc) },
>         { "INT3436", LPSS_ADDR(lpt_sdio_dev_desc) },
>         { "INT3437", },
> 
> So please make the patch touch only the four 808622* devices above
> unless you have tested this on Broadwell as well.
> 
> Otherwise the patch looks good to me.

Here is the patch..

>From 970c704dbb05aa8392b6e1090ceaf9ed76b6436b Mon Sep 17 00:00:00 2001
From: Srinidhi Kasagar <srinidhi.kasagar@intel.com>
Date: Thu, 27 Aug 2015 21:30:55 +0530
Subject: [PATCH] ACPI / LPSS: Ignore 10ms delay for Braswell

LPSS devices in Braswell does not need the default 10ms
d3_delay imposed by PCI specification. Removing this
unnecessary delay significantly reduces the resume time
approximately upto 200ms on this platform.

Signed-off-by: Srinidhi Kasagar <srinidhi.kasagar@intel.com>
---
 drivers/acpi/acpi_lpss.c |   38 ++++++++++++++++++++++++++++++++------
 1 file changed, 32 insertions(+), 6 deletions(-)

diff --git a/drivers/acpi/acpi_lpss.c b/drivers/acpi/acpi_lpss.c
index 46b58abb08c5..10020e04f574 100644
--- a/drivers/acpi/acpi_lpss.c
+++ b/drivers/acpi/acpi_lpss.c
@@ -60,6 +60,7 @@ ACPI_MODULE_NAME("acpi_lpss");
 #define LPSS_CLK_DIVIDER		BIT(2)
 #define LPSS_LTR			BIT(3)
 #define LPSS_SAVE_CTX			BIT(4)
+#define LPSS_NO_D3_DELAY		BIT(5)
 
 struct lpss_private_data;
 
@@ -156,6 +157,10 @@ static const struct lpss_device_desc byt_pwm_dev_desc = {
 	.flags = LPSS_SAVE_CTX,
 };
 
+static const struct lpss_device_desc bsw_pwm_dev_desc = {
+	.flags = LPSS_SAVE_CTX | LPSS_NO_D3_DELAY,
+};
+
 static const struct lpss_device_desc byt_uart_dev_desc = {
 	.flags = LPSS_CLK | LPSS_CLK_GATE | LPSS_CLK_DIVIDER | LPSS_SAVE_CTX,
 	.clk_con_id = "baudclk",
@@ -163,6 +168,14 @@ static const struct lpss_device_desc byt_uart_dev_desc = {
 	.setup = lpss_uart_setup,
 };
 
+static const struct lpss_device_desc bsw_uart_dev_desc = {
+	.flags = LPSS_CLK | LPSS_CLK_GATE | LPSS_CLK_DIVIDER | LPSS_SAVE_CTX
+			| LPSS_NO_D3_DELAY,
+	.clk_con_id = "baudclk",
+	.prv_offset = 0x800,
+	.setup = lpss_uart_setup,
+};
+
 static const struct lpss_device_desc byt_spi_dev_desc = {
 	.flags = LPSS_CLK | LPSS_CLK_GATE | LPSS_CLK_DIVIDER | LPSS_SAVE_CTX,
 	.prv_offset = 0x400,
@@ -178,8 +191,15 @@ static const struct lpss_device_desc byt_i2c_dev_desc = {
 	.setup = byt_i2c_setup,
 };
 
+static const struct lpss_device_desc bsw_i2c_dev_desc = {
+	.flags = LPSS_CLK | LPSS_SAVE_CTX | LPSS_NO_D3_DELAY,
+	.prv_offset = 0x800,
+	.setup = byt_i2c_setup,
+};
+
 static struct lpss_device_desc bsw_spi_dev_desc = {
-	.flags = LPSS_CLK | LPSS_CLK_GATE | LPSS_CLK_DIVIDER | LPSS_SAVE_CTX,
+	.flags = LPSS_CLK | LPSS_CLK_GATE | LPSS_CLK_DIVIDER | LPSS_SAVE_CTX
+			| LPSS_NO_D3_DELAY,
 	.prv_offset = 0x400,
 	.setup = lpss_deassert_reset,
 };
@@ -214,11 +234,12 @@ static const struct acpi_device_id acpi_lpss_device_ids[] = {
 	{ "INT33FC", },
 
 	/* Braswell LPSS devices */
-	{ "80862288", LPSS_ADDR(byt_pwm_dev_desc) },
-	{ "8086228A", LPSS_ADDR(byt_uart_dev_desc) },
+	{ "80862288", LPSS_ADDR(bsw_pwm_dev_desc) },
+	{ "8086228A", LPSS_ADDR(bsw_uart_dev_desc) },
 	{ "8086228E", LPSS_ADDR(bsw_spi_dev_desc) },
-	{ "808622C1", LPSS_ADDR(byt_i2c_dev_desc) },
+	{ "808622C1", LPSS_ADDR(bsw_i2c_dev_desc) },
 
+	/* Broadwell LPSS devices */
 	{ "INT3430", LPSS_ADDR(lpt_dev_desc) },
 	{ "INT3431", LPSS_ADDR(lpt_dev_desc) },
 	{ "INT3432", LPSS_ADDR(lpt_i2c_dev_desc) },
@@ -558,9 +579,14 @@ static void acpi_lpss_restore_ctx(struct device *dev,
 	 * The following delay is needed or the subsequent write operations may
 	 * fail. The LPSS devices are actually PCI devices and the PCI spec
 	 * expects 10ms delay before the device can be accessed after D3 to D0
-	 * transition.
+	 * transition. However some platforms like BSW does not need this delay.
 	 */
-	msleep(10);
+	unsigned int delay = 10;	/* default 10ms delay */
+
+	if (pdata->dev_desc->flags & LPSS_NO_D3_DELAY)
+		delay = 0;
+
+	msleep(delay);
 
 	for (i = 0; i < LPSS_PRV_REG_COUNT; i++) {
 		unsigned long offset = i * sizeof(u32);
-- 
1.7.9.5



  reply	other threads:[~2015-08-27  8:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1440090968-17728-1-git-send-email-srinidhi.kasagar@intel.com>
2015-08-20 12:38 ` [PATCH] ACPI / LPSS: Ignore 10ms delay for Braswell and Baytrail Mika Westerberg
2015-08-20 13:04   ` Heikki Krogerus
2015-08-21 12:16     ` Kasagar, Srinidhi
2015-08-21 12:11   ` Kasagar, Srinidhi
2015-08-21  6:36     ` Mika Westerberg
2015-08-21 13:20       ` Mika Westerberg
2015-08-24 12:51         ` Kasagar, Srinidhi
2015-08-24  8:59           ` Mika Westerberg
2015-08-24 17:09             ` Kasagar, Srinidhi
2015-08-24  9:44               ` Mika Westerberg
2015-08-27 14:39                 ` Kasagar, Srinidhi
2015-08-27  7:14                   ` Mika Westerberg
2015-08-27 16:13                     ` Kasagar, Srinidhi [this message]
2015-08-27  8:30                       ` Mika Westerberg
2015-08-27 17:26                         ` Rafael J. Wysocki

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=20150827161321.GA9886@intel-desktop \
    --to=srinidhi.kasagar@intel.com \
    --cc=heikki.krogerus@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mahesh.kumar.p@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).