From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] device: introduce per device dma_pfn_offset
Date: Thu, 6 Mar 2014 17:19:52 +0800 [thread overview]
Message-ID: <1394097598-17622-2-git-send-email-santosh.shilimkar@ti.com> (raw)
In-Reply-To: <1394097598-17622-1-git-send-email-santosh.shilimkar@ti.com>
On few architectures, there are few restrictions on DMAble area of system
RAM. That also means that devices needs to know about this restrictions so
that the dma_masks can be updated accordingly and dma address translation
helpers can add/subtract the dma offset.
In most of cases DMA addresses can be performed using offset value of
Bus address space relatively to physical address space as following:
PFN->DMA: __pfn_to_phys(pfn + [-]dma_pfn_offset)
DMA->PFN: __phys_to_pfn(dma_addr) + [-]dma_pfn_offset
So we introduce per device dma_pfn_offset which can be popullated
by architectures init code while creating the devices.
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>
Cc: Grant Likely <grant.likely@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
include/linux/device.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/device.h b/include/linux/device.h
index 952b010..6940b25 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -688,6 +688,7 @@ struct acpi_dev_node {
* @coherent_dma_mask: Like dma_mask, but for alloc_coherent mapping as not all
* hardware supports 64-bit addresses for consistent allocations
* such descriptors.
+ * @dma_pfn_offset: offset of DMA memory range relatively of RAM
* @dma_parms: A low level driver may set these to teach IOMMU code about
* segment limitations.
* @dma_pools: Dma pools (if dma'ble device).
@@ -753,6 +754,7 @@ struct device {
not all hardware supports
64 bit addresses for consistent
allocations such descriptors. */
+ unsigned long dma_pfn_offset;
struct device_dma_parameters *dma_parms;
--
1.7.9.5
next prev parent reply other threads:[~2014-03-06 9:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:19 [PATCH 0/7] of: setup dma parameters using dma-ranges and dma-coherent Santosh Shilimkar
2014-03-06 9:19 ` Santosh Shilimkar [this message]
2014-03-06 9:19 ` [PATCH 2/7] of: introduce of_dma_get_range() helper Santosh Shilimkar
2014-03-06 9:19 ` [PATCH 3/7] of: introduce of_dma_is_coherent() helper Santosh Shilimkar
2014-03-07 3:13 ` Rob Herring
2014-03-07 3:44 ` Santosh Shilimkar
[not found] ` <53194092.7010809-l0cyMroinI0@public.gmane.org>
2014-03-07 3:55 ` Rob Herring
2014-03-07 4:18 ` Santosh Shilimkar
2014-03-07 16:09 ` Arnd Bergmann
2014-03-10 13:28 ` Santosh Shilimkar
2014-03-06 9:19 ` [PATCH 4/7] of: configure the platform device dma_mask and dma_pfn_offset Santosh Shilimkar
[not found] ` <1394097598-17622-5-git-send-email-santosh.shilimkar-l0cyMroinI0@public.gmane.org>
2014-03-07 3:49 ` Rob Herring
[not found] ` <CAL_Jsq+Y8w0sLLdh5vcWMnW3ohEafAFRWubtCK66P1axsf1wRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-07 4:16 ` Santosh Shilimkar
[not found] ` <53194817.70802-l0cyMroinI0@public.gmane.org>
2014-03-07 16:02 ` Arnd Bergmann
[not found] ` <201403071702.41716.arnd-r2nGTMty4D4@public.gmane.org>
2014-03-08 20:11 ` Rob Herring
[not found] ` <CAL_JsqLu_16p-8FLjBYt7xQA2eAyiprPML2q5R3fnivZPrvPug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-09 6:39 ` Arnd Bergmann
[not found] ` <201403090739.18351.arnd-r2nGTMty4D4@public.gmane.org>
2014-03-12 0:15 ` Rob Herring
[not found] ` <CAL_Jsq+KPpqmF3eU49AeWO2Q0d4uBon_67+zUz6dXKtfsjA3Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-12 13:19 ` Grygorii Strashko
[not found] ` <53205EF4.3070308-l0cyMroinI0@public.gmane.org>
2014-03-12 16:58 ` Arnd Bergmann
2014-03-14 14:14 ` Rob Herring
[not found] ` <CAL_JsqKbtAxDBrF3O=C8exke9HVU0_ZC-vWZKiiftR+YMaUwMw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-14 17:25 ` Arnd Bergmann
2014-03-14 18:32 ` Rob Herring
2014-03-25 18:06 ` Santosh Shilimkar
2014-03-14 18:32 ` Rob Herring
2014-03-06 9:19 ` [PATCH 5/7] of: Add set_arch_dma_coherent_ops() and setup coherent dma_ops Santosh Shilimkar
2014-03-06 9:19 ` [PATCH 6/7] ARM: dma: Use dma_pfn_offset for dma address translation Santosh Shilimkar
2014-03-06 9:19 ` [PATCH 7/7] ARM: dma: implement set_arch_dma_coherent_ops() 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=1394097598-17622-2-git-send-email-santosh.shilimkar@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.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).