On Sat, 1 Jan 2022 13:12:37 +0530 Apurva Nandan <a-nandan@xxxxxx> wrote: > Manufacturers have been deviating from the standard SPI operations for > NAND flashes. There have been variations in non-page read/write > instructions too. Additionally, operations, including non-page r/w ops, > vary when flash is in different SPI mode, eg. Octal DTR. > > To avoid live-patching in hot-paths or vendor-specific adjustment, > it is better to have a set of operation templates and variants for > non-page read/write operations as well. These would get initialized at > the probe time or when flash changes modes. These would be called > 'ctrl_ops'. > > To make code better understandable, create two types of op templates > which are: data_ops and ctrl_ops. Reason for having two different type > of templates is the difference in their use cases i.e. it is possible > to have ops of different protocol for read/write/update simulatneously > in the data_ops, but all the ops in the ctrl_ops follow same protocol. > > Rename op_templates to data_ops, and the ctrl_ops would be introduced > in later commits. Didn't read till the end, but I don't see any overlap between the control and data operations in the first half of this series, so I'm wondering if the split is actually necessary.