From: Robin Murphy <robin.murphy@arm.com>
To: Roger Quadros <rogerq@ti.com>, tony@atomide.com
Cc: hch@lst.de, robh+dt@kernel.org, nm@ti.com, t-kristo@ti.com,
nsekhar@ti.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2] ARM: dts: dra7: Add bus_dma_limit for L3 bus
Date: Fri, 13 Mar 2020 15:05:33 +0000 [thread overview]
Message-ID: <fb916d06-1521-25a5-2eae-94244a3f9d06@arm.com> (raw)
In-Reply-To: <20200313094717.6671-1-rogerq@ti.com>
On 2020-03-13 9:47 am, Roger Quadros wrote:
> The L3 interconnect's memory map is from 0x0 to
> 0xffffffff. Out of this, System memory (SDRAM) can be
> accessed from 0x80000000 to 0xffffffff (2GB)
>
> DRA7 does support 4GB of SDRAM but upper 2GB can only be
> accessed by the MPU subsystem.
>
> Add the dma-ranges property to reflect the physical address limit
> of the L3 bus.
>
> Issues ere observed only with SATA on DRA7-EVM with 4GB RAM
> and CONFIG_ARM_LPAE enabled. This is because the controller
> supports 64-bit DMA and its driver sets the dma_mask to 64-bit
> thus resulting in DMA accesses beyond L3 limit of 2G.
>
> Setting the correct bus_dma_limit fixes the issue.
Neat! In principle you should no longer need the specific dma-ranges on
the PCIe nodes, since AIUI those really only represent a subset of this
general limitation, but given the other inheritance issue you saw it's
probably safer to leave them as-is for now.
FWIW,
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Cc: stable@kernel.org
> ---
>
> Changelog:
> v2:
> - Revised patch with minimal intrusion. i.e. don't change #size-cells
> of device node.
>
> arch/arm/boot/dts/dra7.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
> index d78b684e7fca..058b8cbb8ef3 100644
> --- a/arch/arm/boot/dts/dra7.dtsi
> +++ b/arch/arm/boot/dts/dra7.dtsi
> @@ -148,6 +148,7 @@
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0x0 0x0 0x0 0xc0000000>;
> + dma-ranges = <0x80000000 0x0 0x80000000 0x80000000>;
> ti,hwmods = "l3_main_1", "l3_main_2";
> reg = <0x0 0x44000000 0x0 0x1000000>,
> <0x0 0x45000000 0x0 0x1000>;
>
next prev parent reply other threads:[~2020-03-13 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 9:47 Roger Quadros
2020-03-13 14:41 ` Tony Lindgren
2020-03-13 15:05 ` Robin Murphy [this message]
2020-03-13 15:15 ` Tony Lindgren
2020-03-16 8:35 ` Roger Quadros
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=fb916d06-1521-25a5-2eae-94244a3f9d06@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=stable@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®