From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: sunxi: spi: use proper errno when message is too long.
Date: Sun, 26 Apr 2015 14:54:21 +0200 [thread overview]
Message-ID: <20150426125421.GH5627@lukather> (raw)
In-Reply-To: <CAOMqctS3oXd5Wg7vu6xLtA6gDKgY0c9rHER48Grt7tnw53Zo1w@mail.gmail.com>
On Sun, Apr 26, 2015 at 01:42:51PM +0200, Michal Suchanek wrote:
> On 26 April 2015 at 10:42, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Sat, Apr 25, 2015 at 09:21:07PM +0200, Michal Suchanek wrote:
> >> Signed-off-by: Michal Suchanek <hramrach@gmail.com>
> >
> > No commit log?
> >
> >> ---
> >> drivers/spi/spi-sun4i.c | 2 +-
> >> drivers/spi/spi-sun6i.c | 2 +-
> >> 2 files changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/spi/spi-sun4i.c b/drivers/spi/spi-sun4i.c
> >> index fbb0a4d..8238b4e 100644
> >> --- a/drivers/spi/spi-sun4i.c
> >> +++ b/drivers/spi/spi-sun4i.c
> >> @@ -176,7 +176,7 @@ static int sun4i_spi_transfer_one(struct spi_master *master,
> >>
> >> /* We don't support transfer larger than the FIFO */
> >> if (tfr->len > SUN4I_FIFO_DEPTH)
> >> - return -EINVAL;
> >> + return -EMSGSIZE;
> >
> > Is it still a thing? The patch to remove such limit hasn't been merged
> > yet?
>
> Yes, seems so unless the patches are queued somewhere but not merged yet.
>
> >
> >> reinit_completion(&sspi->done);
> >> sspi->tx_buf = tfr->tx_buf;
> >> diff --git a/drivers/spi/spi-sun6i.c b/drivers/spi/spi-sun6i.c
> >> index ac48f59..0f5dd91 100644
> >> --- a/drivers/spi/spi-sun6i.c
> >> +++ b/drivers/spi/spi-sun6i.c
> >> @@ -166,7 +166,7 @@ static int sun6i_spi_transfer_one(struct spi_master *master,
> >>
> >> /* We don't support transfer larger than the FIFO */
> >> if (tfr->len > SUN6I_FIFO_DEPTH)
> >> - return -EINVAL;
> >> + return -EMSGSIZE;
> >
> > Eventually, we should move to using DMA for these messages longer than
> > the FIFO.
> >
> > I should post these patches.
> >
>
> Do you have those in a branch somewhere?
Not in a good shape, or at least, in a shape that have any chance to
be merged.
At the time I tried, I couldn't make the generic DMA work, so I had to
bypass that for my tests.
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: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150426/061f786d/attachment-0001.sig>
next prev parent reply other threads:[~2015-04-26 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1430034797.git.hramrach@gmail.com>
2015-04-25 19:21 ` [PATCH 3/3] ARM: sunxi: spi: use proper errno when message is too long Michal Suchanek
2015-04-26 8:42 ` Maxime Ripard
2015-04-26 11:42 ` Michal Suchanek
2015-04-26 12:54 ` Maxime Ripard [this message]
2015-04-26 8:15 ` [PATCH 1/3] ARM: dts: sunxi: A10s Olinuxino add missing SPI and simplefb Michal Suchanek
2015-04-26 8:39 ` Maxime Ripard
2015-04-26 9:21 ` Michal Suchanek
2015-04-26 12:52 ` 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=20150426125421.GH5627@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;
as well as URLs for NNTP newsgroup(s).