Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "DATACOM - Jonatas.Rech" <jonatas.rech@datacom.ind.br>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: fsl-espi: fix behaviour for full-duplex xfers
Date: Wed, 22 Apr 2015 20:57:46 +0100	[thread overview]
Message-ID: <20150422195746.GM22845@sirena.org.uk> (raw)
In-Reply-To: <363371145.339730.1429715343024.JavaMail.zimbra@datacom.ind.br>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Wed, Apr 22, 2015 at 12:09:03PM -0300, DATACOM - Jonatas.Rech wrote:

Don't top post (context is important for people to know what you are
talking about) and please fix your mailer to word wrap within
paragraphs so your mail can be read and replied to more readily.

> The m25p80 driver can send down a message that's bigger than the
> amount the spi-fsl-espi driver can handle in a single espi_transfer
> (64KiB), when the application wants to read the whole memory content,
> for instance. In this case, the Freescale driver splits the message in
> 64KiB chunks, adding a "Read the next 64KiB" command in the TX buffer
> so the flash memory can output data from the expected offset. In the
> end, the m25p80 driver sees all the data as one big rx_buf, as it
> expected in the first place.

This is completely broken.

> Unfortunately, I don't know how many protocol drivers currently rely
> on this, or even how other controller drivers deal with this expected
> behavior.

This is not expected behaviour for anything and should be fixed
urgently.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-04-22 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 15:23 [PATCH] spi: fsl-espi: fix behaviour for full-duplex xfers Jonatas Rech
2015-04-18 12:55 ` Mark Brown
     [not found]   ` <20150418125556.GR26185-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-22 15:09     ` DATACOM - Jonatas.Rech
2015-04-22 19:57       ` Mark Brown [this message]
     [not found]         ` <20150422195746.GM22845-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-23 18:06           ` Jonatas Rech
2015-04-24 18:17             ` Mark Brown
     [not found]               ` <20150424181745.GG22845-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-24 20:03                 ` Jonatas Rech
     [not found]                   ` <20150424200326.GA14443-rCUF4CxDseZknzVnJbg3IA@public.gmane.org>
2015-04-25 13:01                     ` 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=20150422195746.GM22845@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jonatas.rech@datacom.ind.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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