Re: [PATCH] spi: spidev: Warn loudly if instantiated from DT as "spidev"

> On 23.04.2015, at 20:13, Mark Brown wrote: > > As *repeatedly* mentioned before please stop taking things off-list. I > really shouldn't need to remind you of this quite so often, I'm very > tempted to start ignoring such messages. > This was NOT my intention and I am really sorry for that.

Depreciated spi_master.transfer and "prepared spi messages" for an optimized pipelined-SPI-DMA-driver

Hi! I am currently writing an SPI driver for the raspberry pi that only relies on DMA for the whole transfer. It can already handle a FULL SPI_message with multiple transfers, CS_CHANGE, and speed_hz changes only by using DMA, so it is using the dma to the max... Right now (for the ease of "dev

Re: Adding/changing SPI device registrations on the fly via the load of a module

Any feedback? Thanks, Martin On 07.10.2013, at 13:47, Martin Sperl wrote: > Hi! > > A lot of people have been trying to get their preferred SPI devices working > on a Raspberry Pi (and probably some other development boards as well). > Most (newbies) of t

Adding/changing SPI device registrations on the fly via the load of a module

Hi! A lot of people have been trying to get their preferred SPI devices working on a Raspberry Pi (and probably some other development boards as well). Most (newbies) of them have failed because it requires a recompile of the kernel to change the default config from SPIDEV to any other device

Quick questions regarding the SPI interface

Hi! I am trying to drive the spi driver of the raspberry-pi towards a fully DMA driven interface and have come a few open points that - as far as I can tell - are not specified detail in the documentation or header-files. 1) is the spi callback blocking further actions on the spi-bus until it i