From: Sebastian Reichel <sre@kernel.org>
To: Michael Welling <mwelling@ieee.org>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Tony Lindgren" <tony@atomide.com>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Nishanth Menon" <nm@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux 4.2-rc1 broken Nokia N900
Date: Wed, 22 Jul 2015 04:03:07 +0200 [thread overview]
Message-ID: <20150722020306.GA8379@earth> (raw)
In-Reply-To: <20150722001741.GA7950@deathstar>
[-- Attachment #1: Type: text/plain, Size: 2878 bytes --]
Hi,
On Tue, Jul 21, 2015 at 07:17:41PM -0500, Michael Welling wrote:
> On Tue, Jul 21, 2015 at 11:34:41AM +0200, Pavel Machek wrote:
>
> This code has my head spinning.
>
> I found that the errors do not occur when the driver is built into the kernel.
>
> I also found that with the patch below the errors go away.
>
> Not sure if it is acceptible but see if it fixes things on your side.
>
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index cf8b91b..3164d13 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1801,11 +1801,11 @@ int spi_setup(struct spi_device *spi)
> if (!spi->max_speed_hz)
> spi->max_speed_hz = spi->master->max_speed_hz;
>
> - spi_set_cs(spi, false);
> -
> if (spi->master->setup)
> status = spi->master->setup(spi);
>
> + spi_set_cs(spi, false);
> +
> dev_dbg(&spi->dev, "setup mode %d, %s%s%s%s%u bits/w, %u Hz max --> %d\n",
> (int) (spi->mode & (SPI_CPOL | SPI_CPHA)),
> (spi->mode & SPI_CS_HIGH) ? "cs_high, " : "",
mh. maybe a runtime PM issue?
* external abort on non-linefetch: address cannot be accessed,
since the module's clocks are disabled
* built-in works, module not: built-in is probably a little bit
faster (module must not be loaded from filesystem), so that
the device has not yet been suspended
* Before 4.2, omap2_mcspi_set_cs() was called in the setup
routine, which acquired runtime PM
* In 4.2, omap2_mcspi_set_cs() seems to be called without a
prior pm_runtime_get_sync()
* With your workaround, the device has not yet returned to
suspend after the runtime PM acquisition in setup()
So I suggest trying the following (compile tested only) patch:
-- Sebastian
diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
index 5867384..f7d9ffd 100644
--- a/drivers/spi/spi-omap2-mcspi.c
+++ b/drivers/spi/spi-omap2-mcspi.c
@@ -245,6 +245,7 @@ static void omap2_mcspi_set_enable(const struct spi_device *spi, int enable)
static void omap2_mcspi_set_cs(struct spi_device *spi, bool enable)
{
+ struct omap2_mcspi *mcspi = spi_master_get_devdata(spi->master);
u32 l;
/* The controller handles the inverted chip selects
@@ -255,6 +256,8 @@ static void omap2_mcspi_set_cs(struct spi_device *spi, bool enable)
enable = !enable;
if (spi->controller_state) {
+ pm_runtime_get_sync(mcspi->dev);
+
l = mcspi_cached_chconf0(spi);
if (enable)
@@ -263,6 +266,9 @@ static void omap2_mcspi_set_cs(struct spi_device *spi, bool enable)
l |= OMAP2_MCSPI_CHCONF_FORCE;
mcspi_write_chconf0(spi, l);
+
+ pm_runtime_mark_last_busy(mcspi->dev);
+ pm_runtime_put_autosuspend(mcspi->dev);
}
}
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-22 2:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 12:05 linux 4.2-rc1 broken Nokia N900 Pali Rohár
2015-07-13 6:44 ` Tony Lindgren
2015-07-13 8:09 ` Sebastian Reichel
2015-07-13 17:03 ` Michael Welling
2015-07-13 17:09 ` Pali Rohár
2015-07-13 17:56 ` Michael Welling
2015-07-13 20:28 ` Michael Welling
2015-07-13 20:34 ` Pali Rohár
2015-07-13 21:52 ` Michael Welling
2015-07-13 22:02 ` Pali Rohár
2015-07-13 22:36 ` Michael Welling
2015-07-14 7:14 ` Pali Rohár
2015-07-14 7:45 ` Tony Lindgren
2015-07-14 16:33 ` Michael Welling
2015-07-14 20:01 ` Pavel Machek
2015-07-14 20:17 ` Michael Welling
2015-07-15 19:49 ` Pavel Machek
2015-07-15 20:10 ` Michael Welling
2015-07-21 7:31 ` Pavel Machek
2015-07-21 7:33 ` Pavel Machek
2015-07-21 8:04 ` Pali Rohár
2015-07-20 20:48 ` Michael Welling
2015-07-20 20:46 ` Michael Welling
2015-07-20 20:58 ` Pali Rohár
2015-07-21 9:34 ` Pavel Machek
2015-07-21 21:28 ` Michael Welling
2015-07-22 0:17 ` Michael Welling
2015-07-22 2:03 ` Sebastian Reichel [this message]
2015-07-22 5:13 ` Michael Welling
2015-07-22 7:27 ` Pali Rohár
2015-07-22 13:33 ` Sebastian Reichel
2015-07-22 14:27 ` Pali Rohár
2015-07-22 13:30 ` Pavel Machek
2015-07-25 8:55 ` Pali Rohár
2015-07-28 8:39 ` Pali Rohár
2015-07-28 12:26 ` Sebastian Reichel
2015-07-28 12:32 ` Pali Rohár
2015-07-13 11:10 ` Pali Rohár
2015-07-13 13:26 ` Tony Lindgren
2015-07-13 15:51 ` Sebastian Reichel
2015-07-13 16:05 ` Pali Rohár
2015-07-13 19:32 ` Sebastian Reichel
2015-07-14 0:18 ` Krzysztof Kozlowski
2015-07-24 8:18 ` Dave Young
2015-07-24 8:30 ` Ivaylo Dimitrov
2015-07-24 10:28 ` Dave Young
2015-07-24 10:53 ` Pali Rohár
2015-07-24 8:40 ` Pali Rohár
2015-07-24 10:33 ` Dave Young
2015-07-24 10:52 ` Pali Rohár
2015-07-24 15:50 ` Pali Rohár
2015-07-24 8:51 ` Pavel Machek
2015-07-24 10:39 ` Dave Young
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=20150722020306.GA8379@earth \
--to=sre@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mwelling@ieee.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=tony@atomide.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).