All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Kasagar, Srinidhi" <srinidhi.kasagar@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: Fri, 21 Aug 2015 09:36:41 +0300	[thread overview]
Message-ID: <20150821063641.GK30005@lahna.fi.intel.com> (raw)
In-Reply-To: <20150821121152.GA26813@intel-desktop>

On Fri, Aug 21, 2015 at 05:41:52PM +0530, Kasagar, Srinidhi wrote:
> On Thu, Aug 20, 2015 at 03:38:05PM +0300, Mika Westerberg wrote:
> > +Heikki
> > 
> > On Thu, Aug 20, 2015 at 10:46:07PM +0530, Srinidhi Kasagar wrote:
> > > LPSS devices in Braswell and Baytrail does not need the default
> > > 10ms d3_delay imposed by PCI specification. Removing this
> > > unnecessary delay significantly reduces the resume time
> > > (~200ms on Braswell/Cherrytrail) on these platforms.
> > > 
> > > Signed-off-by: Srinidhi Kasagar <srinidhi.kasagar@intel.com>
> > > Signed-off-by: Kumar P Mahesh <mahesh.kumar.p@intel.com>
> > 
> > Have you tested this on Asus T100? The delay was actually needed in
> > order to restore the context IIRC.
> 
> Sorry, I do not have T100 h/w :(

OK. We have one and I'm going to test this patch on it. In particular
the T100 needed to have these delays otherwise writes failed.

> > 
> > Also you are saying Braswell and Baytrail but...
> > 
> > > ---
> > >  drivers/acpi/acpi_lpss.c |   59 ++++++++++++++++++++++++++++++++++++----------
> > >  1 file changed, 46 insertions(+), 13 deletions(-)
> > > 
> 
> [...]
> 
> > > @@ -219,13 +247,13 @@ static const struct acpi_device_id acpi_lpss_device_ids[] = {
> > >  	{ "8086228E", LPSS_ADDR(bsw_spi_dev_desc) },
> > >  	{ "808622C1", LPSS_ADDR(byt_i2c_dev_desc) },
> > >  
> > > -	{ "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) },
> > > +	{ "INT3430", LPSS_ADDR(bsw_lpt_dev_desc) },
> > > +	{ "INT3431", LPSS_ADDR(bsw_lpt_dev_desc) },
> > > +	{ "INT3432", LPSS_ADDR(bsw_lpt_i2c_dev_desc) },
> > > +	{ "INT3433", LPSS_ADDR(bsw_lpt_i2c_dev_desc) },
> > > +	{ "INT3434", LPSS_ADDR(bsw_lpt_uart_dev_desc) },
> > > +	{ "INT3435", LPSS_ADDR(bsw_lpt_uart_dev_desc) },
> > > +	{ "INT3436", LPSS_ADDR(bsw_lpt_sdio_dev_desc) },
> > 
> > ... these are Broadwell devices. Have you tested that this won't break
> > existing Broadwell systems?
> 
> You mean these are Broadwell devices too? As of now I have
> tested these devices to be working on Braswell and Cherrytrail.

Yes, the ACPI IDs you are changing above are Broadwell ACPI IDs
(INT34xx).

  reply	other threads:[~2015-08-21  6:36 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 [this message]
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
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=20150821063641.GK30005@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=heikki.krogerus@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mahesh.kumar.p@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinidhi.kasagar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.