[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150609173004.GO14071@sirena.org.uk>
Date: Tue, 9 Jun 2015 18:30:04 +0100
From: Mark Brown <broonie@...nel.org>
To: Cyrille Pitchen <cyrille.pitchen@...el.com>
Cc: nicolas.ferre@...el.com, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, robh+dt@...nel.org, pawel.moll@....com,
mark.rutland@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org
Subject: Re: [PATCH v3 3/3] spi: atmel: add support to FIFOs
On Tue, Jun 09, 2015 at 01:53:54PM +0200, Cyrille Pitchen wrote:
> To enable the FIFO feature a "atmel,fifo-size" attribute with a strictly
> positive value must be added into the node of the device-tree describing
> the spi controller.
I'd expect the driver to use FIFOs any time they make sense, I wouldn't
expect this to be something that requires configuration - I'd expect
that there's going to be at least some FIFO in all versions of the IP,
even if the size varies. Is that not the case?
> When FIFOs are enabled, the RX one is forced to operate in SINGLE data
> mode because this driver configures the spi controller as a master. In
> master mode only, the Received Data Register has an additionnal Peripheral
> Chip Select field, which prevents us from reading more than a single data
> at each register access.
>
> Besides, the TX FIFO operates in MULTIPLE data mode. However, even when a
This is very hard to understand as I have no idea what single and
multiple data modes are, sorry. Please write your commit messages so
they can be read by people who aren't familiar with the internals of the
IP.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists