linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Priit Laes <plaes@plaes.org>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-sunxi <linux-sunxi@googlegroups.com>,
	Chen-Yu Tsai <wens@csie.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-sunxi] Re: [PATCH 5/5] RFC spi: sun4i: add DMA support
Date: Sun, 5 Jun 2016 13:27:11 +0200	[thread overview]
Message-ID: <CAOMqctQwFif=yFF1snfZJc7+sGS7wcC-6oNTCfjW_MSUWHw+xQ@mail.gmail.com> (raw)
In-Reply-To: <20160602142649.GJ2282@sirena.org.uk>

On 2 June 2016 at 16:26, Mark Brown <broonie@kernel.org> wrote:
> On Thu, Jun 02, 2016 at 02:14:26PM +0200, Michal Suchanek wrote:
>> On 2 June 2016 at 06:42, Priit Laes <plaes@plaes.org> wrote:
>> > On Wed, 2016-06-01 at 20:00 +0200, Maxime Ripard wrote:
>
>> > Actually it non-DMA case works fine if you don't need SPI transfers
>> > larger than SUN4I_FIFO_DEPTH - 1, which is 63 bytes.
>
>> > This was addressed by this patch, but was never applied:
>> > http://permalink.gmane.org/gmane.linux.kernel.spi.devel/18950
>
>> And the code added in that patch will never run unless you
>
>> 1) use long spi transfers
>> 2) compile in/load SPI without DMA support
>
>> There is no reason for doing 2) since we have do DMA support for sunxi.
>
> Well, presumably such code exists and is being worked on?

Which code are you referring to?

This is a reply to patch which adds DMA support to the SPI driver so
that it can work for arbitrarily long transfers.

So there is code for fully working driver.

>
>> So that's another code path that needs maintenance and testing and
>> likely will not get it.
>
> Oh, come on.  You might not want to use it yourself but the chances are
> that someone will want to use it just like the situation with all the
> other SPI drivers.  It's a perfectly reasonable and sensible feature to
> support upstream.

Is it?

Once we have *one* driver that works for arbitrarily long transfers
and it works out of the box with the board defconfig 99% of people who
will use the SPI driver for anything will use this driver. Any other
variant will go untested.

And for the driver to also work without DMA you have to *tell* it to
probe without DMA because it cannot know you are not going to load a
DMA driver later.

>
> I really do not understand why there is such a strong desire to have
> these devices be a special snowflake here, the worst that's likely to
> happen here is that you're going to end up having to either remove the
> DMA controller from the DT or load the driver for it neither of which
> seem like the end of the world.

Why would you do that?

Thanks

Michal

  reply	other threads:[~2016-06-05 11:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1464130597.git.hramrach@gmail.com>
     [not found] ` <e315008b5e9dc3f1490507508fd2f6e94767dfbb.1464130597.git.hramrach@gmail.com>
2016-05-30  8:37   ` [PATCH 2/5] spi: sun4i: fix FIFO limit Maxime Ripard
     [not found] ` <5fffb7eca6f4b70853d92be2403595d6d06bede7.1464130597.git.hramrach@gmail.com>
2016-05-30  8:37   ` [PATCH 3/5] spi: sunxi: expose maximum transfer size limit Maxime Ripard
2016-05-30  8:57     ` Michal Suchanek
2016-06-01 18:14       ` Maxime Ripard
     [not found] ` <7292b1fa08de4f453a643beb63e9faa7826726f6.1464130597.git.hramrach@gmail.com>
2016-05-30  9:17   ` [PATCH 4/5] spi: sunxi: set maximum and minimum speed of SPI master Maxime Ripard
     [not found] ` <cb90b922caa6ac07c1425d726ea19709ee5284f4.1464130597.git.hramrach@gmail.com>
2016-05-27  2:05   ` [linux-sunxi] [PATCH 1/5] spi: sunxi: fix transfer timeout 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
     [not found] ` <ba0d6eb37cc4b0d2c46acbf9fcd7d644b3545ce8.1464130597.git.hramrach@gmail.com>
2016-05-30 11:26   ` [PATCH 5/5] RFC spi: sun4i: add DMA support 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 [this message]
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='CAOMqctQwFif=yFF1snfZJc7+sGS7wcC-6oNTCfjW_MSUWHw+xQ@mail.gmail.com' \
    --to=hramrach@gmail.com \
    --cc=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=plaes@plaes.org \
    --cc=wens@csie.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).