From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: keystone: Use dma-ranges for dma_pfn_offset configuration
Date: Tue, 25 Feb 2014 09:35:05 +0100 [thread overview]
Message-ID: <13859197.4VXqXcWsT4@wuerfel> (raw)
In-Reply-To: <530BBBB8.3020607@ti.com>
On Monday 24 February 2014 16:38:00 Santosh Shilimkar wrote:
> > I also wonder if this shouldn't be in ARM architecture wide code
> > rather than platform code. Unfortunately it can't be in drivers/base
> > since the offset is stored in an ARM specific location.
> >
> Notifier callback is in mach code mainly because platform's might have to
> do custom things here. Like setting up the coherent masters,
> populating the dma_pfn_offset or populating custom dma_ops etc.
> As such the in these callbacks is not much and I see only
> couple of machines using it.
Yes, but since "dma-ranges" is a standard property, I think we should
provide a generic implementation so other platforms don't have to
copy one. Most platforms today are never cache-coherent and have
a trivial mapping, so they don't need this function, but I suppose
the case you have is getting more popular. I think shmobile is in
exactly the same position with their new r-car parts for instance.
Arnd
next prev parent reply other threads:[~2014-02-25 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 20:53 [PATCH 0/4] ARM: mm: Use dma-ranges for dma address translation Santosh Shilimkar
2014-02-24 20:53 ` [PATCH 1/4] ARM: mm: Introduce archdata.dma_pfn_offset Santosh Shilimkar
2014-02-24 20:53 ` [PATCH 2/4] ARM: mm: Remove unsed dma_to_virt() Santosh Shilimkar
2014-02-24 20:53 ` [PATCH 3/4] ARM: dts: keystone: Use dma-ranges property Santosh Shilimkar
2014-02-24 20:53 ` [PATCH 4/4] ARM: keystone: Use dma-ranges for dma_pfn_offset configuration Santosh Shilimkar
2014-02-24 21:11 ` Arnd Bergmann
2014-02-24 21:38 ` Santosh Shilimkar
2014-02-25 8:35 ` Arnd Bergmann [this message]
2014-02-25 14:14 ` Grygorii Strashko
2014-02-25 13:37 ` Arnd Bergmann
2014-02-25 15:19 ` Grygorii Strashko
2014-02-25 14:37 ` Arnd Bergmann
2014-02-25 16:05 ` Grygorii Strashko
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=13859197.4VXqXcWsT4@wuerfel \
--to=arnd@arndb.de \
--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.