That's right. 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.
I don't think a controller driver should make this kind of assumption on how protocol (slave device) drivers intend to use it. Instead, I think this kind of intelligence (about fragmentation and replaying of TX commands) should be in the protocol drivers themselves, aware of the maximum message length the hardware can handle. Unfortunately, I don't know how many protocol drivers currently rely on this, or even how other controller drivers deal with this expected behavior. ----- Original Message ----- From: "Mark Brown" <broo...@kernel.org> To: "DATACOM" <jonatas.r...@datacom.ind.br> Cc: linux-...@vger.kernel.org, linux-kernel@vger.kernel.org Sent: Saturday, April 18, 2015 9:55:56 AM Subject: Re: [PATCH] spi: fsl-espi: fix behaviour for full-duplex xfers On Wed, Apr 15, 2015 at 12:23:18PM -0300, Jonatas Rech wrote: > Furthermore, this correction has exposed an inconsistency in the > protocol driver <-> controller driver interaction. The spi-fsl-espi > driver artificially inserts TX bytes when message fragmentation is > necessary (due to SPCOM_TRANLEN_MAX) instead of informing the > protocol driver of the hardware limitation. This was tested with the > m25p80 NOR flash protocol driver. Since fixing this issue may cause > other client drivers to malfunction, it was left as is. Sorry, you're saying that the driver is sending more data than it's being asked to in some situations? That is a *very* serious bug in both this driver and any other driver which relies on (as opposed to merely tolerates) this behaviour. If that is the case it really needs to be fixed fairly urgently. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
