diff for duplicates of <ZCrR+Vbhycm0TTel@shell.armlinux.org.uk>

diff --git a/a/1.txt b/N1/1.txt
index 230f8e2..217347d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,2 +1,34 @@
-The content of this message was lost. It was probably cross-posted to
-multiple lists and previously handled on another list.
+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
diff --git a/a/content_digest b/N1/content_digest
index da6bac4..5c6620f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,10 +1,57 @@
- "From\0linux@armlinux.org.uk\0"
+ "ref\0ea5147ee8606c47e4d714f8a3e0143d0fd9a1599.camel@googlemail.com\0"
+ "ref\080286c54-c617-d790-b7dc-efd4e52259eb@rock-chips.com\0"
+ "ref\031b64d9aa694524d60c814469d620c8e15479222.camel@googlemail.com\0"
+ "From\0Russell King (Oracle) <linux@armlinux.org.uk>\0"
  "Subject\0Re: rk3399 issue: no DMA in Linux with mainline TF-A and U-Boot SPL\0"
- "Date\0Mon, 03 Apr 2023 13:18:01 +0000\0"
- "To\0op-tee@lists.trustedfirmware.org\0"
- "\01:1\0"
+ "Date\0Mon, 3 Apr 2023 14:17:45 +0100\0"
+ "To\0Christoph Fritz <chf.fritz@googlemail.com>\0"
+ "Cc\0Kever 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
+ " \345\274\240\345\255\246\345\271\277 <sugar.zhang@rock-chips.com>\0"
+ "\00:1\0"
  "b\0"
- "The content of this message was lost. It was probably cross-posted to\n"
- multiple lists and previously handled on another list.
+ "On Mon, Apr 03, 2023 at 12:11:40PM +0200, Christoph Fritz wrote:\n"
+ "> > \n"
+ "> > \302\240\302\240\302\240\302\240 The ARM PL330 DMA driver in kernel only relate to:\n"
+ "> > \n"
+ "> > - DTS kernel used, can be check in /proc/device-tree/\n"
+ "> > \n"
+ "> > - kernel driver which should mach the compatible name.\n"
+ "> \n"
+ "> drivers/dma/pl330.c needs also a successfully matched amba, but this\n"
+ "> fails when using mainline TF-A and U-Boot SPL.\n"
+ "> \n"
+ "> I'm using the same kernel and devicetree on both tests, the only thing\n"
+ "> changed is TF-A and U-Boot SPL   vs   mini-loader and rk3399_bl31.\n"
+ "> \n"
+ "> > This driver should has nothing to do with U-Boot SPL or TF-A, because we \n"
+ "> > don't have any special setting for PL330 in loader stage.\n"
+ "> \n"
+ "> It is drivers/amba/bus.c, which is unable to find an AMBA_CID on the\n"
+ "> ARM bus. The DMA driver not loading is just a symptom of this issue.\n"
+ "\n"
+ "That brings up the obvious question: why is it unable to find the AMBA\n"
+ "CID? Is that because some resource needed to read it hasn't been\n"
+ "enabled yet? If the AMBA CID is not accessible, presumably the rest of\n"
+ "the PL330 also isn't accessible, so even if we could bind the driver,\n"
+ "it still wouldn't work?\n"
+ "\n"
+ "-- \n"
+ "RMK's Patch system: https://www.armlinux.org.uk/developer/patches/\n"
+ "FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!\n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-arm-kernel mailing list\n"
+ "linux-arm-kernel@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 
-d47d2e28de9b3646ef5bb4c7c489b25773fa5816b2cd90f4cb7388277b897ec3
+fae31e816febc5b825935a014af827127afc5e51f8442abebdba9ec4d54d29ff
