DMA Engine development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ben Collins" <bcollins@kernel.org>
Cc: dmaengine@vger.kernel.org, "Vinod Koul" <vkoul@kernel.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	"Robin Murphy" <robin.murphy@arm.com>
Subject: Re: [PATCH] fsldma: Support 40 bit DMA addresses where capable
Date: Wed, 23 Apr 2025 15:49:16 +0200	[thread overview]
Message-ID: <06765168-a36a-4229-b03b-6ea91157237a@app.fastmail.com> (raw)
In-Reply-To: <2025042216-hungry-hound-77ecae@boujee-and-buff>

On Tue, Apr 22, 2025, at 23:10, Ben Collins wrote:
> On Tue, Apr 22, 2025 at 11:25:40AM -0500, Arnd Bergmann wrote:
>> On Tue, Apr 22, 2025, at 10:56, Ben Collins wrote:
>>
>> >> > I'll check on this, but I think it's a seperate issue. The main thing is
>> >> > just to configure the dma hw correctly.
>> >> 
>> >> I think it's still important to check this before changing the
>> >> driver: if the larger mask doesn't actually have any effect now
>> >> because the DT caps the DMA at 4GB, then it might break later
>> >> when someone adds the correct dma-ranges properties.
>> >
>> > I'm adding dma-ranges to my dt for testing.
>> 
>> Ok. The other thing you can try is to printk() the dev->bus_dma_limit
>> to see if it even tries to use >32bit addressing.
>
> Did that. Every combination of IOMMU on/off and dma-ranges in my dt always
> showed bus_dma_limit as 0x0.

Strange, either something changed since I last looked at this code,
or there is something on Freescale SoCs that avoids the
default logic.

There was originally a hack for powerpc that allowed DMA to be
done in the absence of a dma-ranges property in the bus node, but
limit it to 32-bit addressing for backwards compatibility, while
all other architectures should require either an empty dma-ranges
to allow full addressing or a specific translation if there is
a bus specific limit and/or offset.

Looking at the current code I don't see that any more, so it's
possible that now any DMA is allowed even if there is no
dma-ranges property at all.

> As an aside, if you could give this a quick check, I can send the revised
> patch. Appreciate the feedback.
>
> https://github.com/benmcollins/linux/commit/2f2946b33294ebff2fdaae6d1eadc976147470d6

This looks correct to me, but I would change two things:

 - remove the debug message, which you probably left by accident
 - instead of the explicit of_device_is_compatible(), change it
   to use the .data field of the of_device_id table instead.

       Arnd

  reply	other threads:[~2025-04-23 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  2:49 [PATCH] fsldma: Support 40 bit DMA addresses where capable Ben Collins
2025-04-22  6:34 ` Arnd Bergmann
2025-04-22  7:12   ` Ben Collins
2025-04-22  7:59     ` Arnd Bergmann
2025-04-22  8:56       ` Ben Collins
2025-04-22  9:25         ` Arnd Bergmann
2025-04-22 21:10           ` Ben Collins
2025-04-23 13:49             ` Arnd Bergmann [this message]
2025-04-23 20:41               ` Ben Collins
2025-04-23 20:56                 ` Arnd Bergmann

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=06765168-a36a-4229-b03b-6ea91157237a@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=bcollins@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robin.murphy@arm.com \
    --cc=vkoul@kernel.org \
    /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