From: Fabio Estevam <festevam@gmail.com>
To: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: Clark Wang <xiaoning.wang@nxp.com>,
Mark Brown <broonie@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
NXP Linux Team <linux-imx@nxp.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] spi: imx: enable runtime pm support
Date: Fri, 13 Nov 2020 08:26:07 -0300 [thread overview]
Message-ID: <CAOMZO5AVJjhqEvkiB3mXc24RNy+Ac3VW_CTg6BGNsqfSVLq0Sg@mail.gmail.com> (raw)
In-Reply-To: <20201113091800.27469-1-nikita.shubin@maquefel.me>
Hi Nikita,
On Fri, Nov 13, 2020 at 6:18 AM Nikita Shubin <nikita.shubin@maquefel.me> wrote:
>
> 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 ?
Could you please try this patch from Sascha?
https://lkml.org/lkml/2020/10/12/981
next prev parent reply other threads:[~2020-11-13 11:26 UTC|newest]
Thread overview: 6+ 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 13:57 ` Mark Brown
2020-11-13 9:18 ` Nikita Shubin
2020-11-13 11:26 ` Fabio Estevam [this message]
2020-11-13 12:04 ` nikita.shubin
2020-11-24 8:57 ` [EXT] " 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=CAOMZO5AVJjhqEvkiB3mXc24RNy+Ac3VW_CTg6BGNsqfSVLq0Sg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=broonie@kernel.org \
--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=nikita.shubin@maquefel.me \
--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 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).