Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-stable <stable@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	BERGER Olivier <olivier.berger@csgroup.eu>,
	TRINH-THAI Florent <florent.trinh-thai@csgroup.eu>,
	CASAUBON Jean-Michel <jean-michel.casaubon@csgroup.eu>
Subject: Re: Backport to 4.14 and 4.19 commits 24c363623361 and 17ecffa28948 and a798a7086c38
Date: Sun, 16 Jul 2023 21:11:56 +0200	[thread overview]
Message-ID: <2023071648-filling-unscented-d998@gregkh> (raw)
In-Reply-To: <5201aa35-5855-53ec-d123-1a88523971da@csgroup.eu>

On Thu, Jul 13, 2023 at 03:34:10PM +0000, Christophe Leroy wrote:
> Hi,
> 
> Could you please backport the three following commits to 4.14 and 4.19:
> 
> 24c363623361 ("spi: spi-fsl-spi: remove always-true conditional in 
> fsl_spi_do_one_msg")
> 17ecffa28948 ("spi: spi-fsl-spi: relax message sanity checking a little")
> a798a7086c38 ("spi: spi-fsl-spi: allow changing bits_per_word while CS 
> is still active")
> 
> Those three commits (the last one indeed) are needed to overcome a 
> problem introduced in 4.14.230 by commit 42c04316d927 ("spi: fsl-cpm: 
> Use 16 bit mode for large transfers with even size"), which leads to the 
> following error in certain cases:
> 
> [  174.900526] at25 spi0.3: bits_per_word/speed_hz should be same for 
> the same SPI transfer
> [  174.911844] spi_master spi0: failed to transfer one message from queue
> [  366.639467] INFO: task od:406 blocked for more than 120 seconds.
> [  366.645155]       Not tainted 4.14.320-s3k-dev-dirty #342
> [  366.652996] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
> disables this message.
> [  489.519450] INFO: task od:406 blocked for more than 120 seconds.
> [  489.525156]       Not tainted 4.14.320-s3k-dev-dirty #342
> [  489.532915] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
> disables this message.
> ...

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-07-16 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 15:34 Backport to 4.14 and 4.19 commits 24c363623361 and 17ecffa28948 and a798a7086c38 Christophe Leroy
2023-07-16 19:11 ` Greg Kroah-Hartman [this message]

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=2023071648-filling-unscented-d998@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=florent.trinh-thai@csgroup.eu \
    --cc=jean-michel.casaubon@csgroup.eu \
    --cc=linux-spi@vger.kernel.org \
    --cc=olivier.berger@csgroup.eu \
    --cc=stable@vger.kernel.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