All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/3] bus: mvebu-mbus: use automatic I/O synchronization barriers
Date: Thu, 28 May 2015 21:57:08 +0200	[thread overview]
Message-ID: <20150528215708.03cb616f@free-electrons.com> (raw)
In-Reply-To: <20150528194333.GA1468@aspire-one.musicnaut.iki.fi>

Dear Aaro Koskinen,

On Thu, 28 May 2015 22:43:33 +0300, Aaro Koskinen wrote:

> On Fri, Apr 17, 2015 at 12:45:34PM +0200, Nicolas Schichan wrote:
> > On 01/16/2015 05:11 PM, Thomas Petazzoni wrote:
> > > Instead of using explicit I/O synchronization barriers shoehorned
> > > inside the streaming DMA mappings API (in
> > > arch/arm/mach-mvebu/coherency.c), we are switching to use automatic
> > > I/O synchronization barrier.
> > 
> > Hello Thomas,
> > 
> > I'm affraid this patche causes issue on mv88f6282 (and most probably on
> > mv88f6281 as well): see below.
> 
> Is this issue already fixed in 4.1-rc5?

No. I just resent the patch from Nicolas earlier today, he has been
merged by one of the mvebu maintainer, and he will send a pull request
for it. So it should be part of the final 4.1, and the patch is also
marked for stable, so it will be backported to 4.0.x as well.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-05-28 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 16:11 [PATCHv2 0/3] ARM: mvebu: I/O coherency related fixes Thomas Petazzoni
2015-01-16 16:11 ` [PATCHv2 1/3] ARM: mvebu: completely disable hardware I/O coherency Thomas Petazzoni
2015-01-16 16:11 ` [PATCHv2 2/3] bus: mvebu-mbus: use automatic I/O synchronization barriers Thomas Petazzoni
2015-04-17 10:45   ` Nicolas Schichan
2015-04-17 11:23     ` Thomas Petazzoni
2015-04-24 14:44       ` [RFC PATCH] bus: mvebu-mbus: do not set WIN_CTRL_SYNCBARRIER on non io-coherent platforms Nicolas Schichan
2015-04-24 14:54         ` Thomas Petazzoni
2015-04-24 15:12       ` [PATCH] " Nicolas Schichan
2015-05-28 19:43     ` [PATCHv2 2/3] bus: mvebu-mbus: use automatic I/O synchronization barriers Aaro Koskinen
2015-05-28 19:57       ` Thomas Petazzoni [this message]
2015-01-16 16:11 ` [PATCHv2 3/3] ARM: mvebu: use arm_coherent_dma_ops and re-enable hardware I/O coherency Thomas Petazzoni
2015-01-16 16:15   ` Andrew Lunn
2015-01-16 16:20     ` Thomas Petazzoni
2015-01-19 22:36 ` [PATCHv2 0/3] ARM: mvebu: I/O coherency related fixes Andrew Lunn
2015-01-20 15:22   ` Thomas Petazzoni

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=20150528215708.03cb616f@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.