ARM: mvebu: mvebu-mbus and I/O coherency fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 6 patches 0 repliesNew
2 of 6 patches are in this archive. The cover letter announces 6.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | dt: bindings: update mvebu-mbus DT binding with new compatible properties | +0 | 0 replies | |
| 4/6 | bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] ARM: mvebu: mvebu-mbus and I/O coherency fixes
Hi Thomas
I'm probably getting ahead of myself here, since there has not been any review comments, but i'm trying to figure out what should be submitted for -rc3 and which can wait for the next merge window.
[PATCH 1/6] dt: bindings: update mvebu-mbus DT binding with new branch dt for next merge window, since it is not strictly a fix.
[PATCH 2/6] bus: mvebu-mbus: fix support of MBus window 13 branch fixes for next -rc
[PATCH 3/6] ARM: mvebu: fix compatible strings of MBus on Armada 375 and Armada 38x branch fixes for next -rc
[PATCH 4/6] bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window branch drivers for next merge window. I assume it is only a run time dependency for the mv_cesa patches?
[PATCH 5/6] bus: mvebu-mbus: use automatic I/O synchronization barriers branch fixes for next -rc
[PATCH 6/6] ARM: mvebu: use arm_coherent_dma_ops
Here i'm unsure. Is this a fix, or a cleanup?
Thanks
Andrew