On Thu, 2013-09-12 at 12:48 +0100, Mark Brown wrote:

On Thu, Sep 12, 2013 at 12:17:45PM +0100, David Woodhouse wrote:

quoted

Right. The issue here is that the LUT is currently *pre-populated*, with
an incestuously-"known" set of commands that the slave is expected to
support.

So, to repeat my earlier question can someone tell me what a LUT is?

I only know what's in the patch that you have also received, but it
seems to be a table of commands. To send a given command to the flash,
you write the actual command to the some slot in the LUT, then 'trigger'
it by writing its index to another register.

I think this whole thing is about the fact that they are *prepopulating*
the LUT with a set of 'known' commands, and have incestuous knowledge
about what commands will be used, rather than being a truly generic SPI
driver and being able to cope with *any* commands that might be sent to
the slave(s), dynamically setting up to the LUT as required.

-- 
dwmw2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5745 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130912/929d12e1/attachment.bin>