On Thursday 29 May 2014 03:24 PM, Arnd Bergmann wrote:
> On Thursday 29 May 2014 10:08:10 Santosh Shilimkar wrote:
>> On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
>>> On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
>>> wrote:
On Wednesday 28 May 2014 09:32 AM, Linus Walleij
On Thursday 29 May 2014 10:08:10 Santosh Shilimkar wrote:
> On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
> > On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
> > wrote:
> >> On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
> >
> I suspect what you want is
>
>
On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
> On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
> wrote:
>> On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
>
I suspect what you want is
dma-ranges = <0x8000 0 0x8000>;
to translate
On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
wrote:
> On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
>>> I suspect what you want is
>>>
>>> dma-ranges = <0x8000 0 0x8000>;
>>>
>>> to translate dma_addr_t 0x8000-0x to phys_addr_t 0x0-0x7fff
>>>
On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
I suspect what you want is
dma-ranges = 0x8000 0 0x8000;
to translate dma_addr_t 0x8000-0x to phys_addr_t 0x0-0x7fff
On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
I suspect what you want is
dma-ranges = 0x8000 0 0x8000;
to translate
On Thursday 29 May 2014 10:08:10 Santosh Shilimkar wrote:
On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
I suspect what you want is
On Thursday 29 May 2014 03:24 PM, Arnd Bergmann wrote:
On Thursday 29 May 2014 10:08:10 Santosh Shilimkar wrote:
On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Wednesday 28 May 2014 09:32 AM, Linus
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
> On Wed, May 28, 2014 at 3:29 PM, Arnd Bergmann wrote:
>> On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
>
>>> model = "ARM Integrator/AP";
>>> compatible = "arm,integrator-ap";
>>> + dma-ranges = <0x8000
On Wed, May 28, 2014 at 3:29 PM, Arnd Bergmann wrote:
> On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
>> model = "ARM Integrator/AP";
>> compatible = "arm,integrator-ap";
>> + dma-ranges = <0x8000 0x8 0x 0x8000>;
>>
>> aliases {
>>
On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
> diff --git a/arch/arm/boot/dts/integratorap.dts
> b/arch/arm/boot/dts/integratorap.dts
> index b10e6351da53..f0c397fd45c5 100644
> --- a/arch/arm/boot/dts/integratorap.dts
> +++ b/arch/arm/boot/dts/integratorap.dts
> @@ -8,6 +8,7 @@
> / {
>
On Tue, May 27, 2014 at 3:30 PM, Arnd Bergmann wrote:
> On Tuesday 27 May 2014 13:56:55 Grant Likely wrote:
>> Come to think of it, doesn't PCI DMA have to deal with that situation if
>> the PCI window is not 1:1 mapped into the CPU address space?
>
> I think all PCI buses we support so far only
On Tue, May 27, 2014 at 3:30 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 27 May 2014 13:56:55 Grant Likely wrote:
Come to think of it, doesn't PCI DMA have to deal with that situation if
the PCI window is not 1:1 mapped into the CPU address space?
I think all PCI buses we support so
On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
diff --git a/arch/arm/boot/dts/integratorap.dts
b/arch/arm/boot/dts/integratorap.dts
index b10e6351da53..f0c397fd45c5 100644
--- a/arch/arm/boot/dts/integratorap.dts
+++ b/arch/arm/boot/dts/integratorap.dts
@@ -8,6 +8,7 @@
/ {
On Wed, May 28, 2014 at 3:29 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
model = ARM Integrator/AP;
compatible = arm,integrator-ap;
+ dma-ranges = 0x8000 0x8 0x 0x8000;
aliases {
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote:
On Wed, May 28, 2014 at 3:29 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 28 May 2014 10:23:09 Linus Walleij wrote:
model = ARM Integrator/AP;
compatible = arm,integrator-ap;
+ dma-ranges = 0x8000 0x8
On Tuesday 27 May 2014 13:56:55 Grant Likely wrote:
> On Fri, 02 May 2014 11:58:30 +0200, Arnd Bergmann wrote:
> > On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
> > > > > I've got two concerns here. of_dma_get_range() retrieves only the
> > > > > first
> > > > > tuple from the dma-ranges
On Fri, 02 May 2014 11:58:30 +0200, Arnd Bergmann wrote:
> On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
> > > > I've got two concerns here. of_dma_get_range() retrieves only the first
> > > > tuple from the dma-ranges property, but it is perfectly valid for
> > > > dma-ranges to contain
On Fri, 02 May 2014 11:58:30 +0200, Arnd Bergmann a...@arndb.de wrote:
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the first
tuple from the dma-ranges property, but it is perfectly valid for
dma-ranges to contain
On Tuesday 27 May 2014 13:56:55 Grant Likely wrote:
On Fri, 02 May 2014 11:58:30 +0200, Arnd Bergmann a...@arndb.de wrote:
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the
first
tuple from the dma-ranges
On Tuesday 06 May 2014 04:44 PM, Santosh Shilimkar wrote:
> On Tuesday 06 May 2014 05:40 AM, Arnd Bergmann wrote:
>> On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
>>
>>> + dev->coherent_dma_mask = DMA_BIT_MASK(32);
>>> + if (!dev->dma_mask)
>>> + dev->dma_mask =
On Tuesday 06 May 2014 04:44 PM, Santosh Shilimkar wrote:
On Tuesday 06 May 2014 05:40 AM, Arnd Bergmann wrote:
On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
+ dev-coherent_dma_mask = DMA_BIT_MASK(32);
+ if (!dev-dma_mask)
+ dev-dma_mask =
On Tuesday 06 May 2014 05:40 AM, Arnd Bergmann wrote:
> On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
>
>> + dev->coherent_dma_mask = DMA_BIT_MASK(32);
>> + if (!dev->dma_mask)
>> + dev->dma_mask = >coherent_dma_mask;
>> +
>> + /*
>> +* if
On Tuesday 06 May 2014 05:54 AM, Arnd Bergmann wrote:
> On Tuesday 06 May 2014 13:44:38 Benjamin Herrenschmidt wrote:
>> On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
>>> I still wonder whether arm, powerpc, and tile (and I just noticed
>>> microblaze also has a similar
On Tuesday 06 May 2014 13:44:38 Benjamin Herrenschmidt wrote:
> On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
> > I still wonder whether arm, powerpc, and tile (and I just noticed
> > microblaze also has a similar dma_direct_map_page()) could all be
> > handled by attaching devices to a
On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
> + dev->coherent_dma_mask = DMA_BIT_MASK(32);
> + if (!dev->dma_mask)
> + dev->dma_mask = >coherent_dma_mask;
> +
> + /*
> +* if dma-ranges property doesn't exist - just return else
> +* setup
On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
+ dev-coherent_dma_mask = DMA_BIT_MASK(32);
+ if (!dev-dma_mask)
+ dev-dma_mask = dev-coherent_dma_mask;
+
+ /*
+* if dma-ranges property doesn't exist - just return else
+* setup the
On Tuesday 06 May 2014 13:44:38 Benjamin Herrenschmidt wrote:
On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
I still wonder whether arm, powerpc, and tile (and I just noticed
microblaze also has a similar dma_direct_map_page()) could all be
handled by attaching devices to a generic
On Tuesday 06 May 2014 05:54 AM, Arnd Bergmann wrote:
On Tuesday 06 May 2014 13:44:38 Benjamin Herrenschmidt wrote:
On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
I still wonder whether arm, powerpc, and tile (and I just noticed
microblaze also has a similar dma_direct_map_page())
On Tuesday 06 May 2014 05:40 AM, Arnd Bergmann wrote:
On Monday 05 May 2014 17:47:32 Santosh Shilimkar wrote:
+ dev-coherent_dma_mask = DMA_BIT_MASK(32);
+ if (!dev-dma_mask)
+ dev-dma_mask = dev-coherent_dma_mask;
+
+ /*
+* if dma-ranges property
On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
> I still wonder whether arm, powerpc, and tile (and I just noticed
> microblaze also has a similar dma_direct_map_page()) could all be
> handled by attaching devices to a generic trivial IOMMU driver
> parameterized with the appropriate
On Mon, May 5, 2014 at 2:55 PM, Arnd Bergmann wrote:
> On Monday 05 May 2014 14:45:21 Bjorn Helgaas wrote:
>> [+cc Ben, Chris]
>>
>> On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann wrote:
>> > On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
>> >> > +static void of_dma_configure(struct device
On Mon, May 5, 2014 at 4:47 PM, Santosh Shilimkar
wrote:
> On Thursday 01 May 2014 08:49 PM, Rob Herring wrote:
>> On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
>> wrote:
> Updated patch with above minor updates.
>
> From 80a9f06a09a90801d8ee337d9b2d155c43da8f23 Mon Sep 17 00:00:00 2001
>
On Thursday 01 May 2014 08:49 PM, Rob Herring wrote:
> On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
> wrote:
>> Retrieve DMA configuration from DT and setup platform device's DMA
>> parameters. The DMA configuration in DT has to be specified using
>> "dma-ranges" and "dma-coherent"
On Monday 05 May 2014 14:45:21 Bjorn Helgaas wrote:
> [+cc Ben, Chris]
>
> On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann wrote:
> > On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
> >> > +static void of_dma_configure(struct device *dev)
> >> > +{
> >> > + u64 dma_addr, paddr, size;
> >>
[+cc Ben, Chris]
On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann wrote:
> On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
>> > +static void of_dma_configure(struct device *dev)
>> > +{
>> > + u64 dma_addr, paddr, size;
>> > + int ret;
>> > +
>> > + dev->coherent_dma_mask =
[+cc Ben, Chris]
On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
+static void of_dma_configure(struct device *dev)
+{
+ u64 dma_addr, paddr, size;
+ int ret;
+
+ dev-coherent_dma_mask =
On Monday 05 May 2014 14:45:21 Bjorn Helgaas wrote:
[+cc Ben, Chris]
On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
+static void of_dma_configure(struct device *dev)
+{
+ u64 dma_addr, paddr, size;
+
On Thursday 01 May 2014 08:49 PM, Rob Herring wrote:
On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Retrieve DMA configuration from DT and setup platform device's DMA
parameters. The DMA configuration in DT has to be specified using
dma-ranges and
On Mon, May 5, 2014 at 4:47 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Thursday 01 May 2014 08:49 PM, Rob Herring wrote:
On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Updated patch with above minor updates.
From
On Mon, May 5, 2014 at 2:55 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 05 May 2014 14:45:21 Bjorn Helgaas wrote:
[+cc Ben, Chris]
On Fri, May 2, 2014 at 12:59 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
+static void
On Mon, 2014-05-05 at 16:28 -0600, Bjorn Helgaas wrote:
I still wonder whether arm, powerpc, and tile (and I just noticed
microblaze also has a similar dma_direct_map_page()) could all be
handled by attaching devices to a generic trivial IOMMU driver
parameterized with the appropriate constant
On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
> > +static void of_dma_configure(struct device *dev)
> > +{
> > + u64 dma_addr, paddr, size;
> > + int ret;
> > +
> > + dev->coherent_dma_mask = DMA_BIT_MASK(32);
> > + if (!dev->dma_mask)
> > + dev->dma_mask =
On Thu, Apr 24, 2014 at 11:30:04AM -0400, Santosh Shilimkar wrote:
> Retrieve DMA configuration from DT and setup platform device's DMA
> parameters. The DMA configuration in DT has to be specified using
> "dma-ranges" and "dma-coherent" properties if supported.
>
> We setup dma_pfn_offset using
On Friday 02 May 2014 09:13:48 Santosh Shilimkar wrote:
> On Friday 02 May 2014 05:58 AM, Arnd Bergmann wrote:
> > On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
> I've got two concerns here. of_dma_get_range() retrieves only the first
> tuple from the dma-ranges property, but it
On Friday 02 May 2014 05:58 AM, Arnd Bergmann wrote:
> On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the first
tuple from the dma-ranges property, but it is perfectly valid for
dma-ranges to contain multiple
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
> > > I've got two concerns here. of_dma_get_range() retrieves only the first
> > > tuple from the dma-ranges property, but it is perfectly valid for
> > > dma-ranges to contain multiple tuples. How should we handle it if a
> > > device has
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the first
tuple from the dma-ranges property, but it is perfectly valid for
dma-ranges to contain multiple tuples. How should we handle it if a
device has multiple ranges
On Friday 02 May 2014 05:58 AM, Arnd Bergmann wrote:
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the first
tuple from the dma-ranges property, but it is perfectly valid for
dma-ranges to contain multiple tuples. How should
On Friday 02 May 2014 09:13:48 Santosh Shilimkar wrote:
On Friday 02 May 2014 05:58 AM, Arnd Bergmann wrote:
On Thursday 01 May 2014 14:12:10 Grant Likely wrote:
I've got two concerns here. of_dma_get_range() retrieves only the first
tuple from the dma-ranges property, but it is perfectly
On Thu, Apr 24, 2014 at 11:30:04AM -0400, Santosh Shilimkar wrote:
Retrieve DMA configuration from DT and setup platform device's DMA
parameters. The DMA configuration in DT has to be specified using
dma-ranges and dma-coherent properties if supported.
We setup dma_pfn_offset using
On Friday 02 May 2014 10:54:59 Bjorn Helgaas wrote:
+static void of_dma_configure(struct device *dev)
+{
+ u64 dma_addr, paddr, size;
+ int ret;
+
+ dev-coherent_dma_mask = DMA_BIT_MASK(32);
+ if (!dev-dma_mask)
+ dev-dma_mask = dev-coherent_dma_mask;
On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
wrote:
> Retrieve DMA configuration from DT and setup platform device's DMA
> parameters. The DMA configuration in DT has to be specified using
> "dma-ranges" and "dma-coherent" properties if supported.
>
> We setup dma_pfn_offset using
On Thursday 01 May 2014 09:12 AM, Grant Likely wrote:
> On Wed, 30 Apr 2014 10:19:15 -0400, Santosh Shilimkar
> wrote:
>> Hi Grant,
>>
>> On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
>>> On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
>>> wrote:
Retrieve DMA configuration
On Wed, 30 Apr 2014 10:19:15 -0400, Santosh Shilimkar
wrote:
> Hi Grant,
>
> On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
> > On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
> > wrote:
> >> Retrieve DMA configuration from DT and setup platform device's DMA
> >> parameters. The
On Wed, 30 Apr 2014 10:19:15 -0400, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Hi Grant,
On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Retrieve DMA configuration from DT and setup
On Thursday 01 May 2014 09:12 AM, Grant Likely wrote:
On Wed, 30 Apr 2014 10:19:15 -0400, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Hi Grant,
On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
santosh.shilim...@ti.com
On Thu, Apr 24, 2014 at 10:30 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Retrieve DMA configuration from DT and setup platform device's DMA
parameters. The DMA configuration in DT has to be specified using
dma-ranges and dma-coherent properties if supported.
We setup dma_pfn_offset
Hi Grant,
On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
> On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
> wrote:
>> Retrieve DMA configuration from DT and setup platform device's DMA
>> parameters. The DMA configuration in DT has to be specified using
>> "dma-ranges" and
Hi Grant,
On Tuesday 29 April 2014 10:41 AM, Grant Likely wrote:
On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Retrieve DMA configuration from DT and setup platform device's DMA
parameters. The DMA configuration in DT has to be specified using
On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
wrote:
> Retrieve DMA configuration from DT and setup platform device's DMA
> parameters. The DMA configuration in DT has to be specified using
> "dma-ranges" and "dma-coherent" properties if supported.
>
> We setup dma_pfn_offset using
On Thu, 24 Apr 2014 11:30:04 -0400, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Retrieve DMA configuration from DT and setup platform device's DMA
parameters. The DMA configuration in DT has to be specified using
dma-ranges and dma-coherent properties if supported.
We setup
62 matches
Mail list logo
