All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Martin Sperl <kernel@martin.sperl.org>, Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in Linux next with SPI pump changes
Date: Wed, 23 Jan 2019 16:11:37 -0800	[thread overview]
Message-ID: <20190124001136.GL5720@atomide.com> (raw)
In-Reply-To: <20190123215642.GK5720@atomide.com>

* Tony Lindgren <tony@atomide.com> [190123 21:57]:
> Hi all,
> 
> Commit 412e60373245 ("spi: core: avoid waking pump thread from spi_sync
> instead run teardown delayed") caused a PM regression in Linux next
> where a SPI device (drivers/spi/spi-omap2-mcspi.c) no longer idles
> for PM runtime.
> 
> Looks like this also breaks suspend as reported at [0].

Oh and looks like Jon already also came to the conclusion
that PM runtime is now broken at [1]. Sorry forgot to add
Jon to Cc earlier, added now.

Regards,

Tony


[0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1899265.html
[1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1901285.html

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Martin Sperl <kernel@martin.sperl.org>, Mark Brown <broonie@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Regression in Linux next with SPI pump changes
Date: Wed, 23 Jan 2019 16:11:37 -0800	[thread overview]
Message-ID: <20190124001136.GL5720@atomide.com> (raw)
In-Reply-To: <20190123215642.GK5720@atomide.com>

* Tony Lindgren <tony@atomide.com> [190123 21:57]:
> Hi all,
> 
> Commit 412e60373245 ("spi: core: avoid waking pump thread from spi_sync
> instead run teardown delayed") caused a PM regression in Linux next
> where a SPI device (drivers/spi/spi-omap2-mcspi.c) no longer idles
> for PM runtime.
> 
> Looks like this also breaks suspend as reported at [0].

Oh and looks like Jon already also came to the conclusion
that PM runtime is now broken at [1]. Sorry forgot to add
Jon to Cc earlier, added now.

Regards,

Tony


[0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1899265.html
[1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1901285.html

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-24  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 21:56 Regression in Linux next with SPI pump changes Tony Lindgren
2019-01-23 21:56 ` Tony Lindgren
2019-01-24  0:11 ` Tony Lindgren [this message]
2019-01-24  0:11   ` Tony Lindgren

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=20190124001136.GL5720@atomide.com \
    --to=tony@atomide.com \
    --cc=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kernel@martin.sperl.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.