spi: cadence_qspi: optimize & fix indirect rd-writes
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v1 Latest posting 7/70 of 7 patches 0 repliesNew
- v1 posting 6/70 of 7 patches 0 repliesSuperseded
- v1 posting 5/70 of 7 patches 0 repliesSuperseded
Earlier versions · 4
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 posting 4/7 | 0 of 7 patches | 0 replies | Superseded | |
| v1 posting 3/7 | 0 of 7 patches | 0 replies | Superseded | |
| v1 posting 2/7 | 0 of 7 patches | 0 replies | Superseded | |
| v1 posting 1/7 | 0 of 7 patches | 0 replies | Superseded |
Patches in v1 posting 7/7 No applies recorded yet
None of the 7 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 [U-Boot] [PATCH RESEND 0/7] spi: cadence_qspi: optimize & fix indirect rd-writes
Hi Vikas,
(added Marek to Cc)
Quoted 30 lines · vikasm
Quoted 29 lines · Stefan Roese
Hi Vikas,
Quoted 25 lines · Stefan Roese
Quoted 16 lines
Quoted 4 lines
Quoted 3 lines
In addition can you please check the patch causing this instability on socfpga. I don't like to bug you but to close this patchset, this info & tests mentioned above seems to be required.
Quoted 11 lines
Okay. I'll try to find some time this week to do some testing here. It seems
that the other cadence patchset from you ([v4 00/10] spi:cadence_qspi: sram depth from DT & fix for FIFO width) is not pulled into
mainline yet. To make it easier for me, could you perhaps publish a git repository that is based on current mainline. And has the mentioned above
patch series included. And all the patches in the latest version that are
currently causing these problems on SoCFPGA?Quoted 6 lines
The patchset was in u-boot-spi repository, yesterday pulled by Tom in mainline. I will rebase the patchset in discussion
(spi:cadence_qspi: optimize & fix indirect rd-writes) on mainline master & send the V2.Let me know if it is ok.
Okay, I'll try to find some time later this week or next week for some tests.
Quoted 8 lines
Quoted 6 lines
I couldn't find the required time to test these patches again yet. Sorry. And I'll leave for a short vacation tomorrow. So I won't be able to get to this issue before week 32.
Perhaps somebody else finds some time to look at this QSPI driver issue in the meantime
Any update ?
Not from me, sorry. And I really won't be able to dig into this in the next weeks.
Again, perhaps someone else finds the time to look at this QSPI driver issue in the meantime?
Thanks,
Stefan