mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: linux@bigler.io
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Stefan Moring <stefan.moring@technolution.nl>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: spi: imx: Increase imx51 ecspi burst length fails on imx6dl and imx8mm
Date: Mon, 20 Nov 2023 11:17:56 +0100	[thread overview]
Message-ID: <ZVsyVAapXTWnznFd@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <6322fd4c1967a518310140c35ab34f65@mail.infomaniak.com>

On Mon, Nov 20, 2023 at 10:33:38AM +0100, linux@bigler.io wrote:
> I run the test and it worked fine. The transmitted data matches with
> the recived data, no diff.
ok, thanks for confirming. At least we are on the same page.

> BUT!!! on the MDIO it is completly different !!!
> When I request to send 4kB Data I measure on the line 16384Byte.
> 
> The data is again   3Dummy Bytes followed by the databyte.
> So the error symetic on send and recive

ok, that's annoying. I wonder if the loopback test could be improved to
spot such kind of issues, maybe we could verify if the execution time
is reasonable given the SPI clock frequency and the payload size ...

Francesco


  reply	other threads:[~2023-11-20 10:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 14:25 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 [this message]
     [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
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=ZVsyVAapXTWnznFd@francesco-nb.int.toradex.com \
    --to=francesco@dolcini.it \
    --cc=broonie@kernel.org \
    --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

all inboxes | Powered by JetHome®