linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: "Kever Yang" <kever.yang@rock-chips.com>,
	"U-Boot Mailing List" <u-boot@lists.denx.de>,
	"Quentin Schulz" <quentin.schulz@theobroma-systems.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Tony Xie" <tony.xie@rock-chips.com>,
	JuliusWerner <jwerner@chromium.org>,
	DanHandley <dan.handley@arm.com>,
	Rockchip <op-tee@rock-chips.com>,
	linux-arm-kernel@lists.infradead.org,
	op-tee@lists.trustedfirmware.org, tf-a@lists.trustedfirmware.org,
	张学广 <sugar.zhang@rock-chips.com>
Subject: Re: rk3399 issue: no DMA in Linux with mainline TF-A and U-Boot SPL
Date: Mon, 3 Apr 2023 14:17:45 +0100	[thread overview]
Message-ID: <ZCrR+Vbhycm0TTel@shell.armlinux.org.uk> (raw)
In-Reply-To: <31b64d9aa694524d60c814469d620c8e15479222.camel@googlemail.com>

On Mon, Apr 03, 2023 at 12:11:40PM +0200, Christoph Fritz wrote:
> > 
> >      The ARM PL330 DMA driver in kernel only relate to:
> > 
> > - DTS kernel used, can be check in /proc/device-tree/
> > 
> > - kernel driver which should mach the compatible name.
> 
> drivers/dma/pl330.c needs also a successfully matched amba, but this
> fails when using mainline TF-A and U-Boot SPL.
> 
> I'm using the same kernel and devicetree on both tests, the only thing
> changed is TF-A and U-Boot SPL   vs   mini-loader and rk3399_bl31.
> 
> > This driver should has nothing to do with U-Boot SPL or TF-A, because we 
> > don't have any special setting for PL330 in loader stage.
> 
> It is drivers/amba/bus.c, which is unable to find an AMBA_CID on the
> ARM bus. The DMA driver not loading is just a symptom of this issue.

That brings up the obvious question: why is it unable to find the AMBA
CID? Is that because some resource needed to read it hasn't been
enabled yet? If the AMBA CID is not accessible, presumably the rest of
the PL330 also isn't accessible, so even if we could bind the driver,
it still wouldn't work?

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-03 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ea5147ee8606c47e4d714f8a3e0143d0fd9a1599.camel@googlemail.com>
2023-04-03  8:37 ` rk3399 issue: no DMA in Linux with mainline TF-A and U-Boot SPL Kever Yang
2023-04-03 10:11   ` Christoph Fritz
2023-04-03 13:17     ` Russell King (Oracle) [this message]
2023-04-03 13:50       ` Christoph Fritz
2024-04-24  7:52   ` Jonathan Liu
2024-04-24  9:42     ` Christoph Fritz

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=ZCrR+Vbhycm0TTel@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=chf.fritz@googlemail.com \
    --cc=dan.handley@arm.com \
    --cc=heiko@sntech.de \
    --cc=jwerner@chromium.org \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=op-tee@rock-chips.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=sugar.zhang@rock-chips.com \
    --cc=tf-a@lists.trustedfirmware.org \
    --cc=tony.xie@rock-chips.com \
    --cc=u-boot@lists.denx.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).