From: Igor Plyatov <plyatov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nicolas Ferre
<nicolas.ferre-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Cyrille Pitchen
<cyrille.pitchen-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
Subject: spi-atmel.c: regression
Date: Mon, 2 Oct 2017 17:45:07 +0300 [thread overview]
Message-ID: <0876ce0a-cb93-07b7-8019-e365d08cca2a@gmail.com> (raw)
Hello!
please help to manage issue with data corruption by PDC of SPI.
I have compared operation of Linux-2.6.39 and linux4sam kernel 4.9.36+
on the AT91SAM9G20 (Stamp9G20 SOM from Taskit.de) and found regression
in the spi-atmel.c.
New spi-atmel.c driver works very bad with SPI speeds above 6 MHz. I see
corruption in data received by Linux and SPI overruns when OS has big
CPI and IO load.
Old kernel works fine at 22 MHz with the same device driver and hardware.
Can somebody comment and/or help on how to resolve this issue?
Best wishes.
--
Igor Plyatov
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-10-02 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:45 Igor Plyatov [this message]
[not found] ` <0876ce0a-cb93-07b7-8019-e365d08cca2a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-05 7:05 ` spi-atmel.c: regression Igor Plyatov
2017-10-25 9:24 ` Mark Brown
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=0876ce0a-cb93-07b7-8019-e365d08cca2a@gmail.com \
--to=plyatov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cyrille.pitchen-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nicolas.ferre-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).