public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] spi: sunxi: expose maximum transfer size limit
Date: Wed, 1 Jun 2016 20:14:39 +0200	[thread overview]
Message-ID: <20160601181439.GB4908@lukather> (raw)
In-Reply-To: <CAOMqctQdbipvvTnF253S4jGDos1crYXk9nuzDcRvy4geeS=GrQ@mail.gmail.com>

On Mon, May 30, 2016 at 10:57:10AM +0200, Michal Suchanek wrote:
> Hello,
> 
> On 30 May 2016 at 10:37, Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> > On Thu, May 26, 2016 at 07:25:24PM -0000, Michal Suchanek wrote:
> >> The sun4i spi hardware can trasfer at most 63 bytes of data without DMA
> >> support so report the limitation. Same on sun6i.
> >
> > Is it? Is there timeouts on the A31 and later SoCs?
> >
> 
> I have no sun6i hardware to test with.
> 
> This is an advisory limit you can query and it better be smaller
> rather than unreliable. The hard limit in the driver is still
> SUN6I_FIFO_DEPTH (which is 128 bytes on sun6i).
> 
> You can test his without any actual SPI device. Unused pins you can
> multiplex as SPI suffice.

Ok, for the time being:

Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160601/13d59b09/attachment.sig>

  reply	other threads:[~2016-06-01 18:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 22:56 [PATCH 0/5] sunxi spi fixes Michal Suchanek
2016-05-26 19:25 ` [PATCH 1/5] spi: sunxi: fix transfer timeout Michal Suchanek
2016-05-27  2:05   ` [linux-sunxi] " Julian Calaby
2016-05-27  5:05     ` Michal Suchanek
2016-05-27  5:10       ` Julian Calaby
2016-05-30 11:23         ` Mark Brown
2016-05-31 11:52           ` Michal Suchanek
2016-06-01 18:20           ` Maxime Ripard
2016-05-30  9:44   ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 2/5] spi: sun4i: fix FIFO limit Michal Suchanek
2016-05-30  8:37   ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 3/5] spi: sunxi: expose maximum transfer size limit Michal Suchanek
2016-05-30  8:37   ` Maxime Ripard
2016-05-30  8:57     ` Michal Suchanek
2016-06-01 18:14       ` Maxime Ripard [this message]
2016-05-26 19:25 ` [PATCH 4/5] spi: sunxi: set maximum and minimum speed of SPI master Michal Suchanek
2016-05-30  9:17   ` Maxime Ripard
2016-05-26 19:25 ` [PATCH 5/5] RFC spi: sun4i: add DMA support Michal Suchanek
2016-05-30 11:26   ` Mark Brown
2016-05-30 12:11     ` Geert Uytterhoeven
2016-05-30 15:03       ` Mark Brown
2016-05-30 15:28         ` Michal Suchanek
2016-05-30 15:50           ` Mark Brown
2016-05-31 10:44             ` Michal Suchanek
2016-05-31 13:27               ` Mark Brown
2016-05-31 14:19                 ` Michal Suchanek
2016-06-02  8:18                   ` Maxime Ripard
2016-06-01 18:00             ` Maxime Ripard
2016-06-02  4:42               ` [linux-sunxi] " Priit Laes
2016-06-02  9:18                 ` Mark Brown
2016-06-02 12:14                 ` Michal Suchanek
2016-06-02 14:26                   ` Mark Brown
2016-06-05 11:27                     ` Michal Suchanek
2016-06-06 11:36                       ` 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=20160601181439.GB4908@lukather \
    --to=maxime.ripard@free-electrons.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