From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/7] dma: of: introduce of_dma_is_coherent() helper
Date: Mon, 3 Mar 2014 01:49:01 +0000 [thread overview]
Message-ID: <20140303014901.GA18773@localhost> (raw)
In-Reply-To: <53109A64.9030701@ti.com>
On Fri, Feb 28, 2014 at 09:17:08AM -0500, Santosh Shilimkar wrote:
> On Friday 28 February 2014 04:39 AM, Arnd Bergmann wrote:
> > On Thursday 27 February 2014 16:17:49 Santosh Shilimkar wrote:
> >> +
> >> +/**
> >> + * of_dma_is_coherent - Check if device is coherent
> >> + * @np: device node
> >> + *
> >> + * It returns true if "dma-coherent" property was found
> >> + * for this device in DT.
> >> + */
> >> +bool of_dma_is_coherent(struct device_node *np)
> >> +{
> >> + struct device_node *node = np;
> >> +
> >> + while (node) {
> >> + if (of_property_read_bool(node, "dma-coherent")) {
> >> + of_node_put(node);
> >> + return true;
> >> + }
> >> + node = of_get_next_parent(node);
> >> + }
> >> + return false;
> >> +}
> >> +EXPORT_SYMBOL_GPL(of_dma_is_coherent);
> >>
> >
> > This won't work on architectures that are always coherent and
> > did not need 'dma-coherent' properties before, such as IBM
> > Power servers.
> >
> > That said, I think the property makes sense, and we already have
> > platforms using it (highbank is the one I'm aware of).
> >
> > We probably need ways to override this function in both ways:
> > "always coherent" (powerpc, x86), and "never coherent" (keystone
> > without LPAE) from platform code, and it would be nice to put
> > either option into DT in a global location as well. We may have
> > to go through a few iterations of this patch to get the best
> > algorithm, but I think the interface is good at least.
>
> Probably we should discuss bit more next week at connect. The
> current 'dma-coherent' is a per device property. For arch's
> which are always coherent, the per device property doesn't make
> sense.
>
> BTW, the current users of this API is only ARM32 bit port
> and if this satisfies the ARM platforms, we should get
> this in kernel and then address other cases on need
> basis.
I have a suspicion that we'll need this API on arm64 at some point as
well. I get regular questions about DMA cache maintenance for arm64 and
I carried a patch in my tree for a long time (now in -next). While full
coherency is nice, there are some devices on certain SoCs that are more
efficient (power, speed) when they don't have to snoop the CPU caches.
--
Catalin
next prev parent reply other threads:[~2014-03-03 1:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:17 [PATCH v2 0/7] ARM: dma: Support dma-ranges and dma-coherent Santosh Shilimkar
2014-02-27 21:17 ` [PATCH v2 1/7] ARM: mm: Introduce archdata.dma_pfn_offset Santosh Shilimkar
2014-02-28 9:30 ` Arnd Bergmann
2014-03-05 4:45 ` Linus Walleij
2014-03-05 6:37 ` Santosh Shilimkar
2014-02-27 21:17 ` [PATCH v2 2/7] ARM: mm: Remove unsed dma_to_virt() Santosh Shilimkar
2014-02-28 9:31 ` Arnd Bergmann
2014-03-07 5:59 ` Greg Ungerer
2014-02-27 21:17 ` [PATCH v2 3/7] dma: of: introduce of_dma_get_range() helper Santosh Shilimkar
2014-02-27 21:17 ` [PATCH v2 4/7] dma: of: introduce of_dma_is_coherent() helper Santosh Shilimkar
2014-02-28 9:39 ` Arnd Bergmann
2014-02-28 14:17 ` Santosh Shilimkar
2014-03-03 1:49 ` Catalin Marinas [this message]
2014-02-28 15:14 ` Rob Herring
2014-02-28 15:17 ` Santosh Shilimkar
2014-02-28 15:24 ` Arnd Bergmann
2014-03-03 14:04 ` Rob Herring
2014-03-04 15:21 ` Will Deacon
2014-02-27 21:17 ` [PATCH v2 5/7] ARM: of: introduce common routine for DMA configuration Santosh Shilimkar
2014-02-28 10:00 ` Arnd Bergmann
2014-02-28 11:49 ` Grygorii Strashko
2014-02-28 11:14 ` Arnd Bergmann
2014-02-28 15:06 ` Santosh Shilimkar
2014-02-28 15:31 ` Arnd Bergmann
2014-02-28 15:35 ` Santosh Shilimkar
2014-03-07 3:15 ` Linus Walleij
2014-02-28 14:56 ` Rob Herring
2014-02-27 21:17 ` [PATCH v2 6/7] ARM: dts: keystone: Use dma-ranges property Santosh Shilimkar
2014-02-27 21:17 ` [PATCH v2 7/7] ARM: dts: keystone: Udate USB node for dma properties Santosh Shilimkar
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=20140303014901.GA18773@localhost \
--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).