[PATCH] SPI: bcm2835: move to the transfer_one driver model

Stephen Warren swarren at wwwdotorg.org
Thu Mar 26 10:47:24 PDT 2015

On 03/26/2015 11:35 AM, Mark Brown wrote:
> On Thu, Mar 26, 2015 at 11:08:36AM +0100, Martin Sperl wrote:
>> This also allows for GPIO-CS to get used removing the limitation of
>> 2/3 SPI devises on the SPI bus.
> This doesn't apply against current code, please check and resend.  As
> previously mentioned please use subject lines matching the style for the
> subsystem.  A few other things below but it's basically all good.
>> So the question is if we should depreciate native chip-selects for this
>> driver with one of those future improvements listed below.
> Given that this driver is only going to be used with a single SoC (or
> perhaps a very limited set of SoCs, I don't know if it's the same driver
> in the Pi 2) even if the DT specifies a hardware chip select we should
> be able to look up which pin that's brought out to and put it into GPIO
> mode if that's the most sensible thing for the driver.

The Pi and Pi2 are essentially identical with the exception of the CPU, 
so yes this driver should run there too (and the GPIO and pinmux are 
identical too AFAIK, so any interaction there ought to work the same).

More information about the linux-rpi-kernel mailing list