On Friday 07 March 2014 11:49 AM, Rob Herring wrote:
> On Thu, Mar 6, 2014 at 3:19 AM, Santosh Shilimkar
> <santosh.shilim...@ti.com> wrote:
>> From: Grygorii Strashko <grygorii.stras...@ti.com>
>>
>> Retrieve DMA configuration from DT and setup platform device's DMA
>> parameters.
>>
>> The DMA configuration in DT has to be specified using "dma-ranges"
>> property if supported. The DMA configuration applied
>> by dt_dma_configure() as following:
>> - call of_get_dma_range() and get supported DMA range info
>> (dma_addr, cpu_addr, dma_size);
>> - if "not found" then fill dma_mask as DMA_BIT_MASK(32)
>> (this is default behaviour);
>> - if "failed" then clean up dma_mask (DMA not supported)
>> - if ok then update devices DMA configuration:
>> set dma_mask to (dma_addr + dma_size - 1)
>> set dma_pfn_offset to PFN_DOWN(cpu_addr - dma_addr)
>>
>> Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
>> Cc: Russell King <li...@arm.linux.org.uk>
>> Cc: Arnd Bergmann <a...@arndb.de>
>> Cc: Olof Johansson <o...@lixom.net>
>> Cc: Grant Likely <grant.lik...@linaro.org>
>> Cc: Rob Herring <robh...@kernel.org>
>> Cc: Catalin Marinas <catalin.mari...@arm.com>
>> Cc: Linus Walleij <linus.wall...@linaro.org>
>> Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
>> Signed-off-by: Santosh Shilimkar <santosh.shilim...@ti.com>
>> ---
>> drivers/of/platform.c | 75
>> +++++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 72 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/of/platform.c b/drivers/of/platform.c
>> index bd080db..53bb12f 100644
>> --- a/drivers/of/platform.c
>> +++ b/drivers/of/platform.c
>> @@ -187,6 +187,77 @@ struct platform_device *of_device_alloc(struct
>> device_node *np,
>> EXPORT_SYMBOL(of_device_alloc);
>>
>> /**
>> + * dt_dma_configure - apply default DMA configuration from dt
[..]
>> +
>> + ret = dma_set_mask(dev, dma_mask);
>> + if (ret < 0) {
>> + dev_err(dev, "failed to set DMA mask %pad\n", &dma_mask);
>> + dev->dma_mask = NULL;
>> + return;
>> + }
>> +
>> + dev_dbg(dev, "dma_pfn_offset(%#08lx) dma_mask(%pad)\n",
>> + dev->dma_pfn_offset, dev->dma_mask);
>> +
>> + ret = dma_set_coherent_mask(dev, dma_mask);
>
> I think these 2 calls belong in the drivers, not here.
>
I also had same initial thought but Arnd mentioned that its a
shared responsibility between ARCH and drivers. Driver which
could be common between arches not always have the correct
mask information and it can change based on which arch it
is running.
With some discussion back and forth, we thought updating
the dma_mask while the device getting created, would be
better place since we can find the arch capability at
this centralise code and update it.
Ofcourse its bit debatable as the question you asked is
bit obvious as well. I let Arnd give his view here.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
