linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Bigler <benjamin@bigler.one>
To: francesco@dolcini.it
Cc: broonie@kernel.org, linux-kernel@vger.kernel.org,
	linux-spi@vger.kernel.org,  linux@bigler.io,
	regressions@lists.linux.dev, stefan.moring@technolution.nl
Subject: Re: spi: imx: Increase imx51 ecspi burst length fails on imx6dl and imx8mm
Date: Sat, 25 Nov 2023 23:44:32 +0100	[thread overview]
Message-ID: <d795999676663a576f12f07a7013bee758fb781c.camel@bigler.one> (raw)
In-Reply-To: <ZVsyVAapXTWnznFd@francesco-nb.int.toradex.com>

Hello,

I'm uncertain whether this is the appropriate place to respond, but I
am encountering a similar issue on a phyboard-polis-rdk (imx8mm) with
Linux 6.7-rc2. My system uses the imx-sdma firmware version 4.6.

The problem is with the TPM, which fails to function correctly,
displaying the error message:
"tpm tpm0: TPM in field failure mode, requires firmware upgrade."

The issue is identical to the one reported by Stefan. It can be
resolved by reverting commits 15a6af94a2779d5dfb42ee4bfac858ea8e964a3f
and 5f66db08cbd3ca471c66bacb0282902c79db9274, after which the TPM works
again.

Additionally, I've conducted the tests which Francesco mentioned:

> ```
> cd /tmp
> 
> dd if=/dev/urandom of=4k-spi-test-data.bin bs=1 count=4k
> spidev_test -D "$device" -s 4000000 -i 4k-spi-test-data.bin -o 4k-
spi-test-result.bin
> 
> dd if=/dev/urandom of=16bytes-spi-test-data.bin bs=1 count=16
> spidev_test -D "$device" -s 16000 -i 16bytes-spi-test-data.bin -o
16bytes-spi-test-result.bin
> ```

The readback data is correct but on MOSI/MISO there are 16384 bytes.

Please let me know if I can do some more tests.

Best regards,

Benjamin Bigler

  parent reply	other threads:[~2023-11-25 22:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 14:25 spi: imx: Increase imx51 ecspi burst length fails on imx6dl and imx8mm linux
2023-11-18 15:13 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-18 15:15   ` Thorsten Leemhuis
     [not found]     ` <CAB3BuKA+qOY+UhWR-9Ov3qsz3wQr8q8n38MrEMf3FMCthr04yA@mail.gmail.com>
2023-11-18 17:59       ` linux
     [not found]         ` <CAB3BuKARgJhaVNFsP1FQ+2yLe18QU9H17fHKjc-Sf3izE+MZ1Q@mail.gmail.com>
2023-11-20  8:27           ` linux
2023-11-20  8:47             ` Francesco Dolcini
2023-11-20  9:33               ` linux
2023-11-20 10:17                 ` Francesco Dolcini
     [not found]                   ` <CAB3BuKDb6uucujD7ac-w4pa1GVNLSQUA4OGE7i074mQSU==WaA@mail.gmail.com>
2023-11-20 16:45                     ` linux
2023-11-20 17:48                     ` Francesco Dolcini
2023-11-21  9:06                       ` Thorsten Leemhuis
2023-11-21  9:16                         ` Francesco Dolcini
2023-11-21 10:10                           ` Francesco Dolcini
2023-11-21 10:34                           ` linux
2023-11-22 13:26                             ` linux
2023-11-25 22:44                   ` Benjamin Bigler [this message]
2023-11-26 13:19                     ` Benjamin Bigler
2023-11-27  9:09                       ` linux
2023-12-05 13:36                         ` Linux regression tracking (Thorsten Leemhuis)
2023-12-07 19:43                           ` Benjamin Bigler

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=d795999676663a576f12f07a7013bee758fb781c.camel@bigler.one \
    --to=benjamin@bigler.one \
    --cc=broonie@kernel.org \
    --cc=francesco@dolcini.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@bigler.io \
    --cc=regressions@lists.linux.dev \
    --cc=stefan.moring@technolution.nl \
    /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).