From: linux@bigler.io
To: Stefan Moring <stefan.moring@technolution.nl>
Cc: 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: Sat, 18 Nov 2023 18:59:38 +0100 [thread overview]
Message-ID: <2fcdd99eee9ee4f5d34fa1abab2f51bb@mail.infomaniak.com> (raw)
In-Reply-To: <CAB3BuKA+qOY+UhWR-9Ov3qsz3wQr8q8n38MrEMf3FMCthr04yA@mail.gmail.com>
Hi
I checked the code an printed the used parameters, the ‘bits_per_word’ is set to 8.
Best Regards
Stefan Bigler
Am 2023-11-18T17:54:26.000+01:00 hat Stefan Moring <stefan.moring@technolution.nl> geschrieben:
> Hi Thorsten,
>
> Looking at the data of your test, it appears as if your ‘bits_per_word’ are
> set to 32, where you would want 8.
>
> Can you verify this?
>
> Kind regards,
>
> Stefan Moring
>
> Op za 18 nov. 2023 om 16:15 schreef Thorsten Leemhuis <
> regressions@leemhuis.info>
>
>
> > On 18.11.23 16:13, Linux regression tracking (Thorsten Leemhuis) wrote:
> >
> > > [CCing people that worked on the relevant commits as well as the
> > > regression list, as it should be in the loop for regressions:
> > > https://docs.kernel.org/admin-guide/reporting-regressions.html]
> >
> > Sorry for the spam, hit "send" before actually adding Stefan and Mark,
> > which now are among the recipients.
> >
> >
> > > On 18.11.23 15:25, linux@bigler.io wrote:
> > >
> > > > After upgrade from kernel 6.5.11 to 6.6.1 the spi-devices on my hw
> > > > colibri-imx6dl and verdin-imx8mm are not working anymore (TPM2 and
> > > SPI-SRAM).
> > >
> > > >
> > > > >
> > > > > Analyzing the problem showed that the 2 commits introduced the problem:
> > > > >
> > > > > spi: Increase imx51 ecspi burst length based on transfer length
> > > > > 15a6af94a2779d5dfb42ee4bfac858ea8e964a3f
> > > > >
> > > > > spi: imx: Take in account bits per word instead of assuming 8-bits
> > > > > 5f66db08cbd3ca471c66bacb0282902c79db9274
> > > > >
> > > > > Reverting the commits solved the problem.
> > > > >
> > > > > The analyse with the logic-analyser showed a wrong number of
> > > > transmitted
> > > >
> > > > >
> > > > > > bytes and wrong data.
> > > > > > When I try to send 127 Byte with a incrementing pattern
> > > > > (0x01,0x02,0x03,..),
> > > > >
> > > > > >
> > > > > > > 504 Bytes are sent (0x00,0x00,0x01 0x00,0x00,0x00,0x02,
> > > > > > 0x00,0x00,0x00,0x03).
> > > > > >
> > > > > > >
> > > > > > > > We tested with different sizes and patterns, all are not ok.
> > > > > > > > While analysing the configuration and code I was not able to see any
> > > > > > > obvious
> > > > > > >
> > > > > > > >
> > > > > > > > > mistake.
> > > > > > > > >
> > > > > > > > > Has someone else discovered such misbehaviour or has any idea what is
> > > > > > > > wrong?
> > > > > > > >
> > > > > > > > >
> > > > > > > > > > Best Regards
> > > > > > > > >
> > > > > > > > > Thx for the report!
> > > > > > > > >
> > > > > > > > > [TLDR: I'm adding this report to the list of tracked Linux kernel
> > > > > > > > > regressions; the text you find below is based on a few templates
> > > > > > > > > paragraphs you might have encountered already in similar form.
> > > > > > > > > See link in footer if these mails annoy you.]
> > > > > > > > >
> > > > > > > > > To ensure the issue doesn't fall through the cracks unnoticed, I'm
> > > > > > > > > adding it to regzbot, the Linux kernel regression tracking bot:
> > > > > > > > >
> > > > > > > > > #regzbot ^introduced 15a6af94a27
> > > > > > > > > #regzbot title spi: spi-devices on colibri-imx6dl and verdin-imx8mm are
> > > > > > > > > not working anymore
> > > > > > > > > #regzbot ignore-activity
> > > > > > > > >
> > > > > > > > > This isn't a regression? This issue or a fix for it are already
> > > > > > > > > discussed somewhere else? It was fixed already? You want to clarify when
> > > > > > > > > the regression started to happen? Or point out I got the title or
> > > > > > > > > something else totally wrong? Then just reply and tell me -- ideally
> > > > > > > > > while also telling regzbot about it, as explained by the page listed in
> > > > > > > > > the footer of this mail.
> > > > > > > > >
> > > > > > > > > Developers: When fixing the issue, remember to add 'Link:' tags pointing
> > > > > > > > > to the report (the parent of this mail). See page linked in footer for
> > > > > > > > > details.
> > > > > > > > >
> > > > > > > > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> > > > > > > > > --
> > > > > > > > > Everything you wanna know about Linux kernel regression tracking:
> > > > > > > > > https://linux-regtracking.leemhuis.info/about/#tldr
> > > > > > > > > That page also explains what to do if mails like this annoy you.
> > > > > > > >
> > > > > > > >
> > > > > > > >
next prev parent reply other threads:[~2023-11-18 18:07 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 [this message]
[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
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=2fcdd99eee9ee4f5d34fa1abab2f51bb@mail.infomaniak.com \
--to=linux@bigler.io \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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).