linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/7] of: fix size when dma-range is not used
Date: Fri, 6 Feb 2015 15:26:55 -0500	[thread overview]
Message-ID: <54D5238F.4030608@ti.com> (raw)
In-Reply-To: <20150206151210.GC23190@e104818-lin.cambridge.arm.com>

On 02/06/2015 10:12 AM, Catalin Marinas wrote:
> On Fri, Feb 06, 2015 at 02:54:23PM +0000, Murali Karicheri wrote:
>> On 02/06/2015 09:38 AM, Catalin Marinas wrote:
>>> On Thu, Feb 05, 2015 at 09:52:55PM +0000, Murali Karicheri wrote:
>>>> Fix the dma-range size when the DT attribute is missing. i.e  set size to
>>>> dev->coherent_dma_mask + 1 instead of dev->coherent_dma_mask. Also add
>>>> code to check invalid values of size configured in DT and log error.
>>>>
>>>> Cc: Joerg Roedel<joro@8bytes.org>
>>>> Cc: Grant Likely<grant.likely@linaro.org>
>>>> Cc: Rob Herring<robh+dt@kernel.org>
>>>> Cc: Bjorn Helgaas<bhelgaas@google.com>
>>>> Cc: Will Deacon<will.deacon@arm.com>
>>>> Cc: Russell King<linux@arm.linux.org.uk>
>>>> Cc: Arnd Bergmann<arnd@arndb.de>
>>>> Cc: Suravee Suthikulpanit<Suravee.Suthikulpanit@amd.com>
>>>>
>>>> Signed-off-by: Murali Karicheri<m-karicheri2@ti.com>
>>>> ---
>>>>    drivers/of/device.c |   17 ++++++++++++++++-
>>>>    1 file changed, 16 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/of/device.c b/drivers/of/device.c
>>>> index 2de320d..314c8a9 100644
>>>> --- a/drivers/of/device.c
>>>> +++ b/drivers/of/device.c
>>>> @@ -105,9 +105,24 @@ void of_dma_configure(struct device *dev, struct device_node *np)
>>>>    	ret = of_dma_get_range(np,&dma_addr,&paddr,&size);
>>>>    	if (ret<   0) {
>>>>    		dma_addr = offset = 0;
>>>> -		size = dev->coherent_dma_mask;
>>>> +		size = dev->coherent_dma_mask + 1;
>>>>    	} else {
>>>>    		offset = PFN_DOWN(paddr - dma_addr);
>>>> +
>>>> +		/*
>>>> +		 * Add a work around to treat the size as mask + 1 in case
>>>> +		 * it is defined in DT as a mask.
>>>> +		 */
>>>> +		if (size&   1) {
>>>> +			dev_warn(dev, "Invalid size 0x%llx for dma-range\n",
>>>> +				 size);
>>>> +			size = size + 1;
>>>> +		}
>>>> +
>>>> +		if (!size) {
>>>> +			dev_err(dev, "Adjusted size 0x%llx invalid\n", size);
>>>> +			return;
>>>> +		}
>>>
>>> Would it make sense to set coherent_dma_mask to 0 here to make this more
>>> noticeable? It can be done together with the mask calculation from size.
>>
>> I guess you are the following in the code.
>>
>> if (!size) {
>> 		dev->coherent_dma_mask = 0;
>> 		dev_err(dev, "Adjusted size 0x%llx invalid\n", size);
>> 		return;
>> }
>>
>> Not sure how this is going to help and how this get handled by the
>> caller and subsequent logic. Probably it will cause probe to fail, with
>> some helpful error code.
>
> Not sure how it will fail, maybe the driver figures out that DMA isn't
> available and say something or switch to PIO. I guess you can leave it
> as 32-bit mask by default for now even in case of size == 0.
>
> BTW, since pci_device_add() already sets coherent_dma_mask, you could
> add another check at the beginning of of_dma_configure():
>
> 	if (!dev->coherent_dma_mask)
> 		dev->coherent_dma_mask = DMA_BIT_MASK(32);
>
> That's more of a nitpick as the values are both the same.
>
Catalin,

Just posted a patch for size based dma mask with title "of: calculate 
masks of the device based on dma-range size". Please review and comment

-- 
Murali Karicheri
Linux Kernel, Texas Instruments

  reply	other threads:[~2015-02-06 20:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 21:52 [PATCH v6 0/7] PCI: get DMA configuration from parent device Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 1/7] of: iommu: add ptr to OF node arg to of_iommu_configure() Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 2/7] of: move of_dma_configure() to device.c to help re-use Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 3/7] of: fix size when dma-range is not used Murali Karicheri
2015-02-06 14:38   ` Catalin Marinas
2015-02-06 14:54     ` Murali Karicheri
2015-02-06 15:12       ` Catalin Marinas
2015-02-06 20:26         ` Murali Karicheri [this message]
2015-02-05 21:52 ` [PATCH v6 4/7] PCI: add helper functions pci_get[put]_host_bridge_device() Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 5/7] of/pci: add of_pci_dma_configure() update dma configuration Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 6/7] PCI: update dma configuration from DT Murali Karicheri
2015-02-25  1:53   ` Bjorn Helgaas
2015-02-25 16:03     ` Murali Karicheri
2015-02-25 16:09       ` Arnd Bergmann
2015-02-25 20:45         ` Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 7/7] arm: dma-mapping: limit iommu mapping size Murali Karicheri
2015-02-05 21:59 ` [PATCH v6 0/7] PCI: get DMA configuration from parent device Murali Karicheri
2015-02-06 15:15 ` Catalin Marinas
2015-02-06 15:28   ` Murali Karicheri
2015-02-06 17:53     ` Bjorn Helgaas
2015-02-06 18:36       ` Murali Karicheri
2015-02-11 16:54         ` Murali Karicheri
2015-02-11 16:58           ` Murali Karicheri
2015-02-23 22:08             ` Murali Karicheri
2015-02-23 22:15               ` Bjorn Helgaas
2015-02-23 22:44                 ` Murali Karicheri
2015-02-09  5:23 ` Suravee Suthikulpanit
2015-02-09 17:26   ` Murali Karicheri
2015-02-09  5:48 ` Will Deacon
2015-02-25 22:20 ` Bjorn Helgaas

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=54D5238F.4030608@ti.com \
    --to=m-karicheri2@ti.com \
    --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 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).