On 7/8/2013 3:42 AM, Russell King - ARM Linux wrote:
The problem is the way the arm_dma_limit is set up, all dma allocations
are currently broken regardless of if the actual device supports 64-bit
addresses or not.
Please explain this statement.
The statement was a bit shortsighted given re
On 7/3/2013 7:15 AM, Ming Lei wrote:
On Sat, Apr 27, 2013 at 5:32 AM, Rob Herring wrote:
On 04/26/2013 03:31 PM, Laura Abbott wrote:
Currently, of_platform_device_create_pdata always sets the
coherent DMA mask to 32 bits. On ARM systems without CONFIG_ZONE_DMA,
arm_dma_limit gets set to ~0 or
prevents any dma_coherent
allocation from succeeding unless clients manually set the
dma mask first. Rather than make every client on an LPAE system set
the mask manually, account for the size of dma_addr_t when setting
the coherent mask.
Signed-off-by: Laura Abbott
---
drivers/of/platform.c |2
On 4/26/2013 1:03 PM, Rob Herring wrote:
On 04/26/2013 01:06 PM, Laura Abbott wrote:
Currently, of_platform_device_create_pdata always sets the
coherent DMA mask to 32 bits. On ARM systems without CONFIG_ZONE_DMA,
arm_dma_limit gets set to ~0 or 0x on LPAE based
systems. Since
prevents any dma_coherent
allocation from succeeding unless clients manually set the
dma mask first. Rather than make every client on an LPAE system set
the mask, set the mask to a 64 bit value on systems with 64-bit
dma addresses.
Signed-off-by: Laura Abbott
---
drivers/of/platform.c |4
1
On 4/26/2013 3:00 AM, Catalin Marinas wrote:
On Thu, Apr 25, 2013 at 06:09:57PM +0100, Laura Abbott wrote:
On 4/25/2013 6:33 AM, Catalin Marinas wrote:
On Wed, Apr 24, 2013 at 01:50:49AM +0100, Laura Abbott wrote:
By default on ARM systems, the coherent DMA mask (lowest
address) is set to ~0
On 4/25/2013 6:33 AM, Catalin Marinas wrote:
On Wed, Apr 24, 2013 at 01:50:49AM +0100, Laura Abbott wrote:
By default on ARM systems, the coherent DMA mask (lowest
address) is set to ~0 or 0x. Currently,
of_platform_device_create_pdata sets the coherent DMA mask to
32 bits. This
make every client
on an LPAE system set the mask, set the mask to a 64 bit value on
ARM LPAE systems.
Signed-off-by: Laura Abbott
---
drivers/of/platform.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/of/platform.c b/drivers/of/platform.c
index 0970505
Hi,
On 4/11/2013 4:22 AM, Marek Szyprowski wrote:
...
+
diff --git a/drivers/base/dma-contiguous.c b/drivers/base/dma-contiguous.c
index 01fe743..6a8abab 100644
--- a/drivers/base/dma-contiguous.c
+++ b/drivers/base/dma-contiguous.c
@@ -24,6 +24,9 @@
#include
#include
+#include
+#include
On 3/15/2013 8:21 AM, Marek Szyprowski wrote:
This scheme of associating devices with CMA regions by base does not
work if you want to let CMA figure out where to place the region (base
= 0). Can we use the name to associate the device with the region? I
had been working on something similar int
Hi,
On 2/14/2013 4:45 AM, Marek Szyprowski wrote:
+name: an name given to the defined region.
+base-address: the base address of the defined region.
+size: the size of the memory region.
+linux,contiguous-region: property indicating that the defined memory
+ re
Hi,
On 2/14/2013 4:45 AM, Marek Szyprowski wrote:
This patch cleans the initialization of dma contiguous framework. The
all-in-one dma_declare_contiguous() function is now separated into
dma_contiguous_reserve_area() which only steals the the memory from
memblock allocator and dma_contiguous_add
Several flattened device tree functions are missing stub functions
when CONFIG_OF_FLATTREE is not selected, creating compilation
errors. Add the stub functions.
Signed-off-by: Laura Abbott
---
include/linux/of_fdt.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a
13 matches
Mail list logo
