From: oss@buserror.net (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 06/10] soc/qbman: Add ARM equivalent for flush_dcache_range()
Date: Thu, 16 Mar 2017 15:08:32 -0500 [thread overview]
Message-ID: <1489694912.2944.30.camel@buserror.net> (raw)
In-Reply-To: <VI1PR04MB3216490369A82C7A79302C4C86260@VI1PR04MB3216.eurprd04.prod.outlook.com>
On Thu, 2017-03-16 at 00:43 +0000, Roy Pledge wrote:
> Just wanted to follow up on this - turns out the no-map; attribute is
> what I was missing. I now have the suggested mechanism working for ARM.
> However when I went to test on PowePC the region wasn't being enabled
> properly. It turns out the Kconfig in arch/powerpc doesn't define
> HAVE_GENERIC_DMA_COHERENT so this mechanism isn't available. However I
> added it and everything worked on my PPC board as it did on ARM.
>
> Does anyone know why HAVE_GENERIC_DMA_COHERENT isn't defined for
> PowerPC? I did a quick search but didn't see previous discussion on this
> topic.
Probably because nothing on PPC needed it.
In any case, the problems with doing this on PPC run deeper than that, as I
pointed out in:
https://www.spinics.net/lists/arm-kernel/msg560020.html
-Scott
next prev parent reply other threads:[~2017-03-16 20:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 22:39 [PATCH 00/10] fsl/qbman: ARM Enablement Roy Pledge
2017-01-18 22:39 ` [PATCH 01/10] soc/qbman: Use portable mapping for the FQD reserved memory Roy Pledge
2017-01-18 22:39 ` [PATCH 02/10] soc/qbman: Drop set/clear_bits usage Roy Pledge
2017-01-18 22:39 ` [PATCH 03/10] soc/qbman: Drop L1_CACHE_BYTES compile time check Roy Pledge
2017-01-18 22:39 ` [PATCH 04/10] soc/qbman: Fix ARM32 typo Roy Pledge
2017-01-18 22:39 ` [PATCH 05/10] soc/qbman: Rework ioremap() calls for ARM/PPC Roy Pledge
2017-01-18 22:39 ` [PATCH 06/10] soc/qbman: Add ARM equivalent for flush_dcache_range() Roy Pledge
2017-01-18 23:12 ` Russell King - ARM Linux
2017-01-18 23:36 ` Scott Wood
2017-01-23 19:24 ` Roy Pledge
2017-01-25 21:20 ` Arnd Bergmann
2017-01-26 5:08 ` Scott Wood
2017-01-27 16:41 ` Arnd Bergmann
2017-01-28 2:34 ` Scott Wood
2017-01-30 15:31 ` Robin Murphy
2017-01-30 19:04 ` Roy Pledge
2017-02-01 13:03 ` Robin Murphy
2017-02-01 22:51 ` Scott Wood
2017-02-06 22:26 ` Roy Pledge
2017-02-06 22:37 ` Russell King - ARM Linux
2017-02-07 16:44 ` Roy Pledge
2017-02-07 18:25 ` Robin Murphy
2017-02-13 21:26 ` Roy Pledge
2017-03-16 0:43 ` Roy Pledge
2017-03-16 20:08 ` Scott Wood [this message]
2017-03-29 21:19 ` Roy Pledge
2017-01-30 15:19 ` Russell King - ARM Linux
2017-02-01 12:47 ` Arnd Bergmann
2017-02-01 23:16 ` Russell King - ARM Linux
2017-02-02 17:21 ` Roy Pledge
2017-01-30 15:04 ` Russell King - ARM Linux
2017-02-01 12:52 ` Arnd Bergmann
2017-01-30 15:12 ` Russell King - ARM Linux
2017-01-18 22:39 ` [PATCH 07/10] soc/qbman: add QMAN_REV32 Roy Pledge
2017-01-18 22:39 ` [PATCH 08/10] soc/qbman: different register offsets on ARM Roy Pledge
2017-01-18 22:39 ` [PATCH 09/10] soc/qbman: Add missing headers " Roy Pledge
2017-01-18 22:39 ` [PATCH 10/10] fsl/qbman: Enable FSL_LAYERSCAPE config " Roy Pledge
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=1489694912.2944.30.camel@buserror.net \
--to=oss@buserror.net \
--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).