From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: sun6i spi driver issue
Date: Tue, 27 Mar 2018 09:49:00 +0200 [thread overview]
Message-ID: <20180327074900.q57t3w2disku53eo@flea> (raw)
In-Reply-To: <16d32ee2-886a-a169-a1a8-f05ee6a09a66@orpaltech.com>
On Sat, Mar 24, 2018 at 09:42:24AM +0300, Sergey Suloev wrote:
> the following patch [1] isn't working on my BPi M2, OPi PC, OPi PC+. I have
> no more boards to test currently but I am sure it will fail on others too.
> As soon as the max transfer size is set to a value MORE THAN FIFO then most
> of transfers would end up with -110 (timeout).
>
> [1] https://patchwork.kernel.org/patch/9634315/
Is that related to your other discussion? Why did you drop most of the
recipients from that thread, including the SPI maintainer and the SPI
ML?
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180327/15a6ee24/attachment.sig>
next prev parent reply other threads:[~2018-03-27 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 6:42 sun6i spi driver issue Sergey Suloev
2018-03-27 7:49 ` Maxime Ripard [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-19 15:43 sun6i SPI " Sergey Suloev
2018-03-26 11:45 ` Maxime Ripard
[not found] ` <1aab0d1b-cdd4-cdbc-0242-af5d180e581b@orpaltech.com>
2018-03-27 7:47 ` Maxime Ripard
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=20180327074900.q57t3w2disku53eo@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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