public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ssuloev@orpaltech.com (Sergey Suloev)
To: linux-arm-kernel@lists.infradead.org
Subject: sun6i SPI driver issue
Date: Mon, 19 Mar 2018 18:43:43 +0300	[thread overview]
Message-ID: <536bf3b1-4440-d060-b22f-2ce7321f4c13@orpaltech.com> (raw)

Hi guys,

I have recently found a critical issue with sun6i SPI driver. It 
actually found it long time ago while using spidev but I didn't 
considered it as something important. Now it seems like a blocking issue 
that prevents using the driver in any serious application.
I have created a DRM driver for a ili9488-based display, its source is 
available here [1] and device tree overlay [2]. The driver has been 
successfully verified on RPi3, but? it is failing on sunxi: the driver 
gets loaded, display seems working but SPI transfers are periodically 
failing with error -110 (timeout). Due to the issue the picture is 
frozen and completely refreshed again from time to time.

The problem is reproduced on OrangePi PC and BananaPi M2. I am providing 
dmesg from my OrangePi PC [3].

Let know if you need any additional info.

Thanks

-------------------------------------------------------------------

[1] https://github.com/sergey-suloev/tinydrm/blob/master/ili9488.c

[2] 
https://github.com/sergey-suloev/tinydrm/blob/master/overlays/sunxi/mainline/sun8i-h3-ertft0356-drm.dts 


[3] https://pastebin.com/xYqWKcJ2

             reply	other threads:[~2018-03-19 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 15:43 Sergey Suloev [this message]
2018-03-26 11:45 ` sun6i SPI driver issue Maxime Ripard
     [not found]   ` <1aab0d1b-cdd4-cdbc-0242-af5d180e581b@orpaltech.com>
2018-03-27  7:47     ` Maxime Ripard
  -- strict thread matches above, loose matches on Subject: below --
2018-03-24  6:42 sun6i spi " Sergey Suloev
2018-03-27  7:49 ` 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=536bf3b1-4440-d060-b22f-2ce7321f4c13@orpaltech.com \
    --to=ssuloev@orpaltech.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