> > > The device tree is a modified version of the
> > > upstream linux device tree file "mediatek/mt7986a-bananapi-bpi-r3.dtb"
> >
> > Can you share those changes? I analyzed and enabled modules purely on
> > what's available upstream.
>
> Yes, I just need to tidy them up into a series of git commits. I don't
> think I had to change anything module related,
Ok, I use the "compatible" string to figure out what modules are needed.
There is still some work to be done, but I fixed up most of the device tree schema errors. I also just tested a freshly built .dtb file from the branch after fixing things and I still get the same boot log with the v6.10 rc3 kernel.
I did notice an interesting schema error though related to the crypto device:
arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: crypto@10320000: interrupts: [[0, 116, 4], [0, 117, 4], [0, 118, 4], [0, 119, 4]] is too short
from schema $id:
http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml#arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: crypto@10320000: interrupt-names: ['ring0', 'ring1', 'ring2', 'ring3'] is too short
from schema $id:
http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml#
I do not know if this is related to the boot errors I am seeing or not.