On Wed, Sep 11, 2013 at 10:38:02AM +0800, Huang Shijie wrote:

? 2013?09?11? 02:07, Mark Brown ??:

quoted

don't need to reimplement the logic and new chips with new opcodes don't
need to be added to multiple drivers.

Since there is no standard for SPI-NOR commands, we _should_ add new
code for
new chips with new opcodes. For example, if a new chip supports the
quad-read with
a new command 0xef, we can submit a small patch for m25p80 to fix it.

We have to do it in such way, no shortcut.

So why does the SPI driver have references to the opcodes in it?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130911/39d0f44d/attachment-0001.sig>