On Thu, 12 Sep 2013, Russell King - ARM Linux wrote:
On Thu, Sep 12, 2013 at 12:48:31PM +0100, Mark Brown wrote:
On Thu, Sep 12, 2013 at 12:17:45PM +0100, David Woodhouse wrote:
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?
It's a very common abbreviation - Look Up Table.
More specifically, it's a set of registers which give the SPI controller
a sequence of 16-bit commands to execute, which tell it what to do on
the SPI bus. Each register contains two commands, and it executes them
...
A bit of an odd name when used in this context I think; LUTs are usually
used to perform mapping or transformation functions, e.g. looking up a
value 'y' given an input value 'x'. In this case it's just a table of
commands to be executed. But I guess the name LUT has been used in some
hardware specification so there's not much we can do about it.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
