linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux@bigler.io
To: Stefan Moring <stefan.moring@technolution.nl>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	Francesco Dolcini <francesco@dolcini.it>
Subject: Re: spi: imx: Increase imx51 ecspi burst length fails on imx6dl and imx8mm
Date: Wed, 22 Nov 2023 14:26:38 +0100	[thread overview]
Message-ID: <dcf860a796c228920a79b62417f7cf6c@mail.infomaniak.com> (raw)
In-Reply-To: <44e61a3385f84aa417a208ca348e4b8c@mail.infomaniak.com>

Hi 

i did now  my test with the latest imx-sdma  firmware 4.6 from NXP
https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin
There is no improvement.
What is the HW that you use? What type of imx8?

Regards Stefan Bigler

Am 2023-11-21T11:34:26.000+01:00 hat  <linux@bigler.io> geschrieben:
>  Hi
> 
> At least in my test-case the  commit is NOT introducing this regression, because the bits_per_word is 8, so the result is the same
> spi: imx: Take in account bits per word instead of assuming 8-bits
> 5f66db08cbd3ca471c66bacb0282902c79db9274
> 
> I do not have the latest  mx-sdma firmware can you tell me where I get it. On 
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/imx/sdma
> the latest I found was 4.5
> 
> I tried to debug the code but it's hard vor me to understand where the problem could be.
> I saw then I disable the dma with set
> 
> imx51_ecspi_devtype_data {
> .has_dmamode = false,
> }
> the SPI is working fine.
> 
> Should I do some more tests, do some loggings.. 
> Please let me know
> 
> Regards 
> Stefan Bigler

  reply	other threads:[~2023-11-22 13:26 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 [this message]
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=dcf860a796c228920a79b62417f7cf6c@mail.infomaniak.com \
    --to=linux@bigler.io \
    --cc=broonie@kernel.org \
    --cc=francesco@dolcini.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --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).