Hi Mark!
On 11.11.2013 12:18, Mark Brown wrote:
No, you're going off and talking about something else here. You are
very focused on the idea of skipping some of the setup but that's not
the only thing being discussed. Please try to separate the various
ideas.
Well - from my perspective (for which I also started this thread) it is
_all_ about skipping setup work (besides the question about
why spi_master.transfer is depreciated, which is unanswered).
If you want to discuss something in the same context, then please
start to state explicitly what you want to get addressed here as well.
Because I have also seen a disconnect in this discussion before
(including running in circles) and I had tried to summarize my
understanding of this disconnect earlier, but no response to that portion.
So to summarize my understanding of the disconnect again:
* your concern is "refactoring" message pump to reduce bus-driver code
* my concern is speed and latencies of SPI messages
And as far as I can see they primarily touch on the subject of functionality
both containing "prepare" but for different purpose - one for the
bus-driver interface and the other for the device driver interface.
So again, please state what you want to achieve in this context and how
you see the two subject are interconnected and why/how theyneed to
get handled together.
Thanks, Martin
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
