From: Murali Karicheri <m-karicheri2@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: <linux@arm.linux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <arnd@arndb.de>,
<will.deacon@arm.com>, <grant.likely@linaro.org>,
<robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dma-mapping: limit dma_mask in arch_setup_dma_ops()
Date: Tue, 13 Jan 2015 15:38:02 -0500 [thread overview]
Message-ID: <54B5822A.8050506@ti.com> (raw)
In-Reply-To: <1419458139-4034-1-git-send-email-m-karicheri2@ti.com>
On 12/24/2014 04:55 PM, Murali Karicheri wrote:
> dma_mask should be limited to minimum of the default dma mask
> and dma-range size configured in DT for proper operation.
>
> Signed-off-by: Murali Karicheri<m-karicheri2@ti.com>
> Reviewed-by: Arnd Bergmann<arnd@arndb.de>
> ---
> arch/arm/mm/dma-mapping.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
> index 7864797..5cea1fc 100644
> --- a/arch/arm/mm/dma-mapping.c
> +++ b/arch/arm/mm/dma-mapping.c
> @@ -2053,6 +2053,7 @@ void arch_setup_dma_ops(struct device *dev, u64 dma_base, u64 size,
> {
> struct dma_map_ops *dma_ops;
>
> + *dev->dma_mask = min((*dev->dma_mask), (dma_base + size - 1));
> dev->archdata.dma_coherent = coherent;
> if (arm_setup_iommu_dma_ops(dev, dma_base, size, iommu))
> dma_ops = arm_get_iommu_dma_map_ops(coherent);
Please discard this as this is still a work in progress. Any change if
required will be added to my series with subject "PCI: get DMA
configuration from parent device"
Thanks.
--
Murali Karicheri
Linux Kernel, Texas Instruments
next prev parent reply other threads:[~2015-01-13 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 21:55 [PATCH] dma-mapping: limit dma_mask in arch_setup_dma_ops() Murali Karicheri
2015-01-13 20:38 ` Murali Karicheri [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-24 21:51 Murali Karicheri
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=54B5822A.8050506@ti.com \
--to=m-karicheri2@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
/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