Add the Quadspi driver for vf610-twr
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 21/210 of 8 patches 0 repliesNew
- v3 posting 20/210 of 8 patches 0 repliesSuperseded
- v3 posting 19/210 of 8 patches 0 repliesSuperseded
Earlier versions · 18
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v3 posting 18/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 17/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 16/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 15/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 14/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 13/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 12/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 11/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 10/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 9/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 8/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 7/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 6/21 | 2 of 8 patches | 0 replies | Superseded | |
| v3 posting 5/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 4/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 3/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 2/21 | 0 of 8 patches | 0 replies | Superseded | |
| v3 posting 1/21 | 0 of 8 patches | 0 replies | Superseded |
Patches in v3 posting 21/21 No applies recorded yet
None of the 8 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/8] Add the Quadspi driver for vf610-twr
Quoted 9 lines · David Woodhouse
Quoted 6 lines · Mark Brown
Quoted 1 line
[ potential "LUT" optimization, implementation details ]
AFAICT the big issue with the LUTs in this controller is that they are expensive to reprogram so things are going to work better if there is a small set of known operations that will happen repeatedly. Otherwise walking the transfer list at runtime isn't too hard.
Quoted 5 lines
I think you can drop the word "known" there. With decent management of the LUT as a kind of LRU cache of recent operations, surely you'll quickly get into a situation where the operations you're actually *doing* on the flash are all already in the LUT and you're never actually *having* to reprogram it?
Yeah, assuming it's not too annoying to identify the repeated patterns
and doesn't blow up horribly just caching should work fine.
-------------- 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/20130918/41f92132/attachment.sig>