All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Shubin <nikita.shubin@maquefel.me>
To: xiaoning.wang@nxp.com
Cc: broonie@kernel.org, festevam@gmail.com, kernel@pengutronix.de,
	linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	s.hauer@pengutronix.de, shawnguo@kernel.org,
	Nikita Shubin <nikita.shubin@maquefel.me>
Subject: [PATCH] spi: imx: enable runtime pm support
Date: Fri, 13 Nov 2020 12:18:00 +0300	[thread overview]
Message-ID: <20201113091800.27469-1-nikita.shubin@maquefel.me> (raw)
In-Reply-To: <20200727063354.17031-1-xiaoning.wang@nxp.com>

Hello Clark, 

This patch breaks spi-imx on imx7d.
Toradex Colibri imx7d spi reports with:

    [    4.258468] inv-mpu6000-spi spi2.0: I/O Error in PIO
    [    4.264269] inv-mpu6000-spi spi2.0: SPI transfer failed: -110
    [    4.264305] spi_master spi2: failed to transfer one message from queue

We are using spi-imx with dma.

Reverting your patch fixes this issue.

The baseline commit 951cbbc386ff01b50da4f46387e994e81d9ab431 (tag: v5.9.8, stable/linux-5.9.y)

Could you please give some comments on this issue ?

WARNING: multiple messages have this Message-ID (diff)
From: Nikita Shubin <nikita.shubin@maquefel.me>
To: xiaoning.wang@nxp.com
Cc: Nikita Shubin <nikita.shubin@maquefel.me>,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	broonie@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
	festevam@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spi: imx: enable runtime pm support
Date: Fri, 13 Nov 2020 12:18:00 +0300	[thread overview]
Message-ID: <20201113091800.27469-1-nikita.shubin@maquefel.me> (raw)
In-Reply-To: <20200727063354.17031-1-xiaoning.wang@nxp.com>

Hello Clark, 

This patch breaks spi-imx on imx7d.
Toradex Colibri imx7d spi reports with:

    [    4.258468] inv-mpu6000-spi spi2.0: I/O Error in PIO
    [    4.264269] inv-mpu6000-spi spi2.0: SPI transfer failed: -110
    [    4.264305] spi_master spi2: failed to transfer one message from queue

We are using spi-imx with dma.

Reverting your patch fixes this issue.

The baseline commit 951cbbc386ff01b50da4f46387e994e81d9ab431 (tag: v5.9.8, stable/linux-5.9.y)

Could you please give some comments on this issue ?

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

  parent reply	other threads:[~2020-11-13  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  6:33 [PATCH] spi: imx: enable runtime pm support Clark Wang
2020-07-27  6:33 ` Clark Wang
2020-07-27 13:57 ` Mark Brown
2020-07-27 13:57   ` Mark Brown
2020-11-13  9:18 ` Nikita Shubin [this message]
2020-11-13  9:18   ` Nikita Shubin
2020-11-13 11:26   ` Fabio Estevam
2020-11-13 11:26     ` Fabio Estevam
2020-11-13 12:04     ` nikita.shubin
2020-11-13 12:04       ` nikita.shubin
2020-11-24  8:57   ` [EXT] " Clark Wang
2020-11-24  8:57     ` Clark Wang

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=20201113091800.27469-1-nikita.shubin@maquefel.me \
    --to=nikita.shubin@maquefel.me \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xiaoning.wang@nxp.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.