From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ARM: mvebu: mvebu-mbus and I/O coherency fixes
Date: Tue, 30 Dec 2014 18:20:50 +0100 [thread overview]
Message-ID: <20141230182050.0550ccdc@free-electrons.com> (raw)
In-Reply-To: <20141230162716.GC24811@lunn.ch>
Dear Andrew Lunn,
On Tue, 30 Dec 2014 17:27:16 +0100, Andrew Lunn wrote:
> [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.
Right.
> [PATCH 2/6] bus: mvebu-mbus: fix support of MBus window 13
> branch fixes for next -rc
Correct.
> [PATCH 3/6] ARM: mvebu: fix compatible strings of MBus on Armada 375 and Armada 38x
> branch fixes for next -rc
Correct, since this is needed for PATCH 2/6 to work properly.
> [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?
Indeed, next merge window is good enough for this one: the mv_cesa
patches have not even been posted yet. I'm not sure whether the mv_cesa
stuff will be ready for 3.20, or 3.21 anyway. But having for sure this
mvebu-mbus improvement already scheduled for 3.20 means one less
dependency to handle when we'll submit the mv_cesa patches.
> [PATCH 5/6] bus: mvebu-mbus: use automatic I/O synchronization barriers
> branch fixes for next -rc
Right.
> [PATCH 6/6] ARM: mvebu: use arm_coherent_dma_ops
> Here i'm unsure. Is this a fix, or a cleanup?
It's a fix, because it is what brings this part of the cover letter:
* It allows to switch to use the existing arm_coherent_dma_ops
instead of mvebu specific DMA operations. arm_coherent_dma_ops
make sure that DMA coherent mappings are mapped cacheable (which
is possible in a cache-coherent platform), which is a necessary
to make sure that both CPU-side and device-side accesses are
done in a cacheable way. Without this, CPU-side accesses to DMA
coherent mappings were made uncached, while device-side accesses
were made in a cacheable way, leading to potentially
unpredictable behavior.
Which is really a fix. So it should go in 3.19-rc.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-30 17:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 12:43 [PATCH 0/6] ARM: mvebu: mvebu-mbus and I/O coherency fixes Thomas Petazzoni
2014-12-30 12:43 ` [PATCH 1/6] dt: bindings: update mvebu-mbus DT binding with new compatible properties Thomas Petazzoni
2015-01-09 16:53 ` Andrew Lunn
2015-01-19 22:25 ` Andrew Lunn
2014-12-30 12:43 ` [PATCH 2/6] bus: mvebu-mbus: fix support of MBus window 13 on Armada XP/375/38x Thomas Petazzoni
2015-01-18 15:50 ` [PATCH] bus: mvebu-mbus: fix support of MBus window 13 Andrew Lunn
2015-01-18 15:53 ` Andrew Lunn
2015-01-18 16:29 ` Thomas Petazzoni
2015-01-19 22:14 ` Andrew Lunn
2015-01-19 22:29 ` [PATCH 2/6] bus: mvebu-mbus: fix support of MBus window 13 on Armada XP/375/38x Andrew Lunn
2015-01-20 15:05 ` Thomas Petazzoni
2014-12-30 12:43 ` [PATCH 3/6] ARM: mvebu: fix compatible strings of MBus on Armada 375 and Armada 38x Thomas Petazzoni
2015-01-19 22:33 ` Andrew Lunn
2014-12-30 12:43 ` [PATCH 4/6] bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window Thomas Petazzoni
2015-01-09 16:59 ` Andrew Lunn
2015-01-19 22:34 ` Andrew Lunn
2014-12-30 12:43 ` [PATCH 5/6] bus: mvebu-mbus: use automatic I/O synchronization barriers Thomas Petazzoni
2014-12-30 12:43 ` [PATCH 6/6] ARM: mvebu: use arm_coherent_dma_ops Thomas Petazzoni
2014-12-30 16:27 ` [PATCH 0/6] ARM: mvebu: mvebu-mbus and I/O coherency fixes Andrew Lunn
2014-12-30 17:20 ` Thomas Petazzoni [this message]
2015-01-09 15:52 ` Thomas Petazzoni
2015-01-10 16:30 ` Andrew Lunn
2015-01-10 16:50 ` Thomas Petazzoni
2015-01-10 17:16 ` Andrew Lunn
2015-01-10 18:56 ` Arnd Bergmann
2015-01-10 19:57 ` Thomas Petazzoni
2015-01-10 20:40 ` Arnd Bergmann
2015-01-10 21:36 ` Thomas Petazzoni
2015-01-10 21:51 ` Arnd Bergmann
2015-01-12 12:36 ` Russell King - ARM Linux
2015-01-12 12:41 ` Thomas Petazzoni
2015-01-10 16:33 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141230182050.0550ccdc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.