From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Barrier changes with !ARM_DMA_MEM_BUFFERABLE
Date: Fri, 25 Jun 2010 17:00:35 +0100 [thread overview]
Message-ID: <1277481635.13134.62.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <20100621115703.7162.95491.stgit@e102109-lin.cambridge.arm.com>
Russell,
On Mon, 2010-06-21 at 13:23 +0100, Catalin Marinas wrote:
> The patches are relatively simple but without them the RealView boards
> cannot be used with L210/L220 enabled (hardware deadlock, not a software
> issue).
>
> Catalin Marinas (2):
> ARM: Do not use outer_sync() in mb() if !ARM_DMA_MEM_BUFFERABLE
> ARM: Do not enable ARM_DMA_MEM_BUFFERABLE for some RealView boards
Are you ok with these patches, especially the first one?
Alternatively, I can implement the barriers in the RealView code (though
the second patch is still needed as I'll drop the outer_sync() for ARMv6
RealView).
Thanks.
--
Catalin
prev parent reply other threads:[~2010-06-25 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 12:23 [PATCH 0/2] Barrier changes with !ARM_DMA_MEM_BUFFERABLE Catalin Marinas
2010-06-21 12:23 ` [PATCH 1/2] ARM: Do not use outer_sync() in mb() if !ARM_DMA_MEM_BUFFERABLE Catalin Marinas
2010-06-21 12:23 ` [PATCH 2/2] ARM: Do not enable ARM_DMA_MEM_BUFFERABLE for some RealView boards Catalin Marinas
2010-06-25 16:00 ` Catalin Marinas [this message]
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=1277481635.13134.62.camel@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).