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: Fri, 17 Apr 2015 13:23:50 +0200 [thread overview]
Message-ID: <20150417132350.329bcace@free-electrons.com> (raw)
In-Reply-To: <5530E44E.8070105@freebox.fr>
Dear Nicolas Schichan,
On Fri, 17 Apr 2015 12:45:34 +0200, Nicolas Schichan wrote:
> I'm affraid this patche causes issue on mv88f6282 (and most probably on
> mv88f6281 as well): see below.
>
> [...]
>
> > diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
> > index eb7682d..398f0ee 100644
> > --- a/drivers/bus/mvebu-mbus.c
> > +++ b/drivers/bus/mvebu-mbus.c
> > @@ -69,6 +69,7 @@
> > */
> > #define WIN_CTRL_OFF 0x0000
> > #define WIN_CTRL_ENABLE BIT(0)
> > +#define WIN_CTRL_SYNCBARRIER BIT(1)
>
> In the 88f6282 datasheet this bit in the "WindowX Control Register" is
> documented as reserved on all windows but window 6 and 7.
>
> For windows 6 and 7 this bit is documented to write protect the window when set.
>
> In our configuration, this window gets chosen for the PCI memory accesses
> (target 0x4, attribute 0xe8) and we effectively end up only being able to read
> from the PCI devices (mwl8k fails to load the firmware and sky2 timeouts on
> MDIO accesses). Write accesses are silently discarded (no external aborts of
> any kind), but that's probably expected as the AHB error propagation is disabled.
>
> Reverting this patch made all the PCI device work correctly.
Ah, thanks a lot for the bug report. I'll cook a fix for this problem,
and Cc: you when submitting.
Thanks again!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-17 11:23 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 [this message]
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
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=20150417132350.329bcace@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.