mtd: spi-nor: add a new framework for SPI NOR
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] mtd: spi-nor: add a new framework for SPI NOR
Quoted 16 lines · Angus Clark
Hi Pekon,
Quoted 2 lines · Pekon
Unless a register is controlling a status of internal state-machine, or something It should be instantaneously writable.
Yes, that is my point. Some register writes are instant, other are not, particularly those that involve non-volatile status or configuration bits.
Quoted 7 lines
Also polling should not be part of this particular *(write_reg), if a register needs to be polled then it should be part of *(write) or *(read) .. Like WIP: Write-in-progress bit of flash
generic_flash_write(...){while ((read_reg(STATUS_REG) & WIP) || ~timeout) {
Quoted 8 lines
Quoted 3 lines
timeout--; };I am in two minds about where the WTR loop should live. On the one hand, moving it to the "
generic_flash_write()" call offers H/W controllers the opportunity to optimise the polling, if they support such a feature (I know of some that will in the future).
I disagree we should bloat the API with features, that will be used by "possible future controllers" or "possible single controller", right from the start. The real question here is, can the API be designed in such a way, that the SR polling will happen in software NOW and only when a controller appears that can do polling in HW will the API be extended to support it ?
Quoted 12 lines
However, requiring the H/W driver to perform the polling, including knowledge of the STATUS CMD, and the WIP bit-field, just seems like moving too much "intelligence" away from the spi-nor layer. What concerns me is when we get on to reading/clearing error flags (as now mandated on some Serial Flash devices, e.g. n25p512 and n25q00a), this will also need to be part of the generic write.
Quoted 2 lines
With this it just came to my mind, that you also need a 'timeout' field in 'struct spinor-cfg'.
Yes, that is a good point.
Quoted 10 lines
I would propose that the spi-nor layer retains responsibility for determining whether or not 'WTR' is required for a particular operation, and a suitable timeout. At some point, during initialisation, the H/W driver will need to inform the spi-nor layer about its capabilities (e.g. support for DUAL or QUAD mode, any warm-reset requirements, etc), and native support of WIP polling could be part of this set. The spi-nor layer could then decide whether to add the WTR flag and timeout to the spinor-cfg transfer, or to take responsibility itself, and execute its own polling loop. This gives greatest flexibility, which seems to be an important factor, while retaining the knowledge in the spi-nor layer.
Sounds good!
Quoted 3 lines
Cheers,
Angus
Best regards,
Marek Vasut