From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] spi: omap2-mcspi: Fix PM regression with deferred probe for pm_runtime_reinit
Date: Thu, 11 Feb 2016 18:36:40 +0000 [thread overview]
Message-ID: <20160211183640.GB1953@sirena.org.uk> (raw)
In-Reply-To: <20160211173620.GU19432@atomide.com>
On Thu, Feb 11, 2016 at 09:36:20AM -0800, Tony Lindgren wrote:
> * Mark Brown <broonie@kernel.org> [160211 07:54]:
> > This does sound like there's been a change in the interface compared to
> > what users are actually doing - is this an actual problem or is it just
> > a divergence from docs?
> It's an actual problem at least on omaps as the omap_device code
> is very picky about the hardware state.
> Depending how the PM runtime is implemented, it may be a problem
> for some other cases too.
Or people just aren't testing mainline that well (if this is broken in
v4.5 that suggests nobody noticed in -next) - do you know when this
broke? It really seems like we may need to spin round on how this is
deployed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160211/f1717419/attachment.sig>
next prev parent reply other threads:[~2016-02-11 18:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 23:02 [PATCH 0/7] PM runtime regression fixes for omaps Tony Lindgren
2016-02-10 23:02 ` [PATCH 1/7] mmc: omap_hsmmc: Fix PM regression with deferred probe for pm_runtime_reinit Tony Lindgren
2016-02-11 10:18 ` Ulf Hansson
2016-02-11 15:02 ` Tony Lindgren
2016-02-11 15:13 ` Ulf Hansson
2016-02-11 17:26 ` Tony Lindgren
2016-02-12 12:59 ` Ulf Hansson
2016-02-22 17:54 ` Tony Lindgren
2016-02-10 23:02 ` [PATCH 2/7] i2c: omap: " Tony Lindgren
2016-02-11 17:34 ` Wolfram Sang
2016-02-11 17:56 ` Tony Lindgren
2016-02-12 12:50 ` Ulf Hansson
2016-02-12 18:43 ` Wolfram Sang
2016-02-10 23:02 ` [PATCH 3/7] spi: omap2-mcspi: " Tony Lindgren
2016-02-11 11:51 ` Mark Brown
2016-02-11 15:08 ` Tony Lindgren
2016-02-11 15:52 ` Mark Brown
2016-02-11 17:36 ` Tony Lindgren
2016-02-11 18:36 ` Mark Brown [this message]
2016-02-11 18:52 ` Tony Lindgren
2016-02-12 12:51 ` Ulf Hansson
2016-02-10 23:02 ` [PATCH 4/7] serial: 8250_omap: " Tony Lindgren
2016-02-12 3:17 ` Greg Kroah-Hartman
2016-02-12 12:52 ` Ulf Hansson
2016-02-10 23:02 ` [PATCH 5/7] serial: omap: " Tony Lindgren
2016-02-12 12:52 ` Ulf Hansson
2016-02-10 23:02 ` [PATCH 6/7] ARM: OMAP2+: Improve omap_device error for driver writers Tony Lindgren
2016-02-12 1:13 ` Kevin Hilman
2016-02-12 12:53 ` Ulf Hansson
2016-02-10 23:02 ` [PATCH 7/7] ARM: OMAP2+: Fix omap_device for module reload on PM runtime forbid Tony Lindgren
2016-02-12 1:13 ` Kevin Hilman
2016-02-12 12:54 ` Ulf Hansson
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=20160211183640.GB1953@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).