From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa@the-dreams.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: Add /soc dma-ranges
Date: Sat, 14 Sep 2019 17:53:30 +0200 [thread overview]
Message-ID: <f1b11b42-99ee-0484-550e-8758ec6fa559@gmail.com> (raw)
In-Reply-To: <CAMuHMdXVhtE5Jmpu8QYv+P8pGtegr4MGhNGRwy4Y1wRQYmL2_Q@mail.gmail.com>
On 9/9/19 1:18 PM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> On Sat, Sep 7, 2019 at 6:16 PM Marek Vasut wrote:
>>
>> Add dma-ranges property into /soc node to describe the DMA capabilities
>> of the bus. This is currently needed to translate PCI DMA ranges, which
>> are limited to 32bit addresses.
>
>> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
>> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
>> @@ -330,6 +330,7 @@
>> #address-cells = <2>;
>> #size-cells = <2>;
>> ranges;
>> + dma-ranges = <0 0x40000000 0 0x40000000 0 0xc0000000>;
>
> Shouldn't the length be 0x80000000 (for all SoCs)?
Or should that match the amount of DRAM below 32bit boundary ?
> Or should we allow DMA to internal System RAM, too?
I think we should include SRAM, yes.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-09-14 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 16:16 [PATCH] arm64: dts: renesas: Add /soc dma-ranges marek.vasut
2019-09-09 8:19 ` Geert Uytterhoeven
2019-09-09 8:42 ` Marek Vasut
2019-09-09 9:05 ` Geert Uytterhoeven
2019-09-09 9:12 ` Marek Vasut
2019-09-09 11:18 ` Geert Uytterhoeven
2019-09-14 15:53 ` Marek Vasut [this message]
2019-09-14 16:33 ` Geert Uytterhoeven
2019-09-14 16:45 ` Marek Vasut
2019-09-15 13:11 ` Geert Uytterhoeven
2019-09-13 15:14 ` Rob Herring
2019-09-14 15:50 ` Marek Vasut
2019-09-23 22:33 ` Rob Herring
2019-09-26 20:02 ` Marek Vasut
2019-09-30 12:42 ` Marek Vasut
2019-09-30 15:08 ` Rob Herring
2019-09-30 15:38 ` Marek Vasut
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=f1b11b42-99ee-0484-550e-8758ec6fa559@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=wsa@the-dreams.de \
/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).