All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI / LPSS: Remove lpss_iosf_enter_d3_state()
Date: Tue, 27 Jun 2017 16:31:16 +0300	[thread overview]
Message-ID: <1498570276.22624.191.camel@linux.intel.com> (raw)
In-Reply-To: <20170626215700.14445-2-hdegoede@redhat.com>

On Mon, 2017-06-26 at 23:57 +0200, Hans de Goede wrote:

I didn't get why the first patch exists if you effectively remove what
it brought here.

> If lpss_iosf_enter_d3_state() hits the code path where it actually
> puts the DMA controllers into D3, then, at least on Bay Trail, the
> LPSS
> PWM controller will stop working / gets stuck. After this happening
> the
> PWM controller's control reg will always reads 0x00010000 and writes
> seem to be ignored.
> 
> Note that the chances of this code-path actually being hit are
> actually
> very low. On Bay Trail devices with an AXP288 PMIC and on any Cherry
> Trail
> device, the I2C controller connected to the PMIC has (runtime) suspend
> disabled, so the condition of all LPSS and SCC devices being in D3
> will
> never happen.
> 
> Even on Bay Trail devices with another PMIC testing has shown that
> lpss_iosf_enter_d3_state() will only put the DMA controllers in D3
> during
> early boot when not all devices have been initialized yet, which is
> enough
> to get the PWM controller stuck, while not resulting in any
> significant
> power saving as this only happens during boot.
> 
> So in practice lpss_iosf_enter_d3_state() is almost always a no-op and
> when it is not, it is causing problems. Therefor this commit simply
> removes it.

Let's continue discuss in your letter regarding IOSF LPSS stuff.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-06-27 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 21:56 [PATCH 1/2] ACPI / LPSS: Call lpss_iosf_exit_d3_state on device activate Hans de Goede
2017-06-26 21:57 ` [PATCH 2/2] ACPI / LPSS: Remove lpss_iosf_enter_d3_state() Hans de Goede
2017-06-27 13:31   ` Andy Shevchenko [this message]
2017-06-27 13:56     ` Hans de Goede
2017-06-27 14:38       ` Andy Shevchenko
2017-06-28 17:29 ` [PATCH 1/2] ACPI / LPSS: Call lpss_iosf_exit_d3_state on device activate kbuild test robot

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=1498570276.22624.191.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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.