Re: [RFC] SPI API update

Jon Medhurst (Tixy) <tixy@...>

On Wed, 2016-09-14 at 09:31 +0200, Tomasz Bursztyka wrote:
This GPIO used as CS is a hack for - currently - DW controllers. When
integration makes it
available (it's possible on QuarkSE X86 core, not on QuarkSE ARC core
for instance).

So indeed, it's very much limited for now, but I don't see any reason
expose anything about it
in the public API. Hack should stay hidden, deep, in driver's specific
Not sure why you call this a 'hack'. Anyway, the serial device IP I'm
writing an SPI driver for (ARM's PL022) doesn't have a concept of a chip
select, so I'm going to have to implement this same 'hack'. Except I
won't, because making the current SPI APIs gate CS on every call to
tranceive makes them silly to use (the zero copy problem as mentioned in
the RFC). So, rather than upstreaming this driver along with other board
support, which is what my brief is, I'll just park this work in a fork
somewhere until Zephyr's APIs settle down to something more usable. :-(


Join to automatically receive all group messages.