From: Marek Vasut <marek.vasut@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa@the-dreams.de>,
devicetree@vger.kernel.org,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: Add /soc dma-ranges
Date: Mon, 30 Sep 2019 17:38:32 +0200 [thread overview]
Message-ID: <9ff6eb72-a01d-37de-8aa1-671406f3d7ac@gmail.com> (raw)
In-Reply-To: <CAL_JsqJf-TGE-SWWj=6AVbpfuN1AsEdDTSOCOk+iUzTT3yZSgw@mail.gmail.com>
On 9/30/19 5:08 PM, Rob Herring wrote:
> On Mon, Sep 30, 2019 at 7:45 AM Marek Vasut wrote:
>>
>> On 9/24/19 12:33 AM, Rob Herring wrote:
>>> On Fri, Sep 13, 2019 at 10:14 AM Rob Herring wrote:
>>>>
>>>> On Sat, Sep 7, 2019 at 5:16 PM wrote:
>>>>>
>>>>> From: Marek Vasut
>>>>>
>>>>> 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.
>>>>
>>>> FYI, I've started working on this problem and issues around
>>>> dma-ranges/dma_mask. Hopefully I'll get some patches out next week.
>>>
>>> I've pushed out a branch here:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git dma-masks
>>>
>>> Can you test it on Renesas. I don't have a real platform having the issue.
>>
>>
>> With the following patches applied:
>> https://patchwork.ozlabs.org/patch/1144870/
>
> I'd rather not have yet another instance of {dma-}ranges parsing code.
> With this series[1], dma-ranges gets parsed into resource list for
> you.
>
>> https://patchwork.ozlabs.org/patch/1144871/
>
> How can this one be applied? It would conflict horribly. Plus I think
> it duplicates what's in my series.
I fixed it up real quick, but apparently these are not needed indeed.
[...]
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2019-09-30 15:38 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
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 [this message]
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=9ff6eb72-a01d-37de-8aa1-671406f3d7ac@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@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).