From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
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: Mon, 9 Sep 2019 10:42:47 +0200 [thread overview]
Message-ID: <b77e6a66-be14-4f94-c116-788b8fa18b31@gmail.com> (raw)
In-Reply-To: <CAMuHMdXkExZXeXnxuKkMC0J4m56cZUmJpcq2JCXuMv3PBzA0Dg@mail.gmail.com>
On 9/9/19 10:19 AM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> On Sat, Sep 7, 2019 at 6:16 PM <marek.vasut@gmail.com> wrote:
>> From: Marek Vasut <marek.vasut+renesas@gmail.com>
>>
>> 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.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Thanks for your patch!
>
>> NOTE: This is needed for the following patches to work correctly:
>> https://patchwork.ozlabs.org/patch/1144870/
>> https://patchwork.ozlabs.org/patch/1144871/
>
> What happens with the above patches applied, and without this one?
It triggers https://patchwork.kernel.org/patch/11087391/#22811745
> As PCI/OF driver patches go in through different trees, is it safe to apply
> this patch now?
> Should they go in together?
I didn't get any feedback on the other two patches, but this one here is
safe to go in either way.
>> arch/arm64/boot/dts/renesas/r8a7795.dtsi | 1 +
>> arch/arm64/boot/dts/renesas/r8a7796.dtsi | 1 +
>> arch/arm64/boot/dts/renesas/r8a77965.dtsi | 1 +
>
> Do we need similar patches for the other R-Car Gen3 and RZ/G2 DTS files?
> What about R-Car Gen2 and RZ/G1?
I suspect we need such patches for any ARM64 machine with PCIe with this
32bit limitation.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-09-09 8:42 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 [this message]
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
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=b77e6a66-be14-4f94-c116-788b8fa18b31@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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).