Help for using SPI with INT needed

Device: OrangePi PC
OS: OpenWRT 18.06. Snapshot
Kernel: 14.4.156
i like to use the MCP2515 with SPI, so i have recompiled the device against 18.06, but cannot get the spi transfers to work.
First i recompiled the dtb File to dts and modified SPI to:

spi@01c68000 {
compatible = "allwinner,sun8i-h3-spi";
reg = <0x1c68000 0x1000>;
interrupts = <0x0 0x41 0x4>;
clocks = <0x2 0x1e 0x2 0x52>;
clock-names = "ahb", "mod";
dmas = <0xe 0x17 0xe 0x17>;
dma-names = "rx", "tx";
pinctrl-names = "default";
pinctrl-0 = <0xf>;
resets = <0x2 0xf>;
status = "okay";
#address-cells = <0x1>;
#size-cells = <0x0>;

		can@0 {
			compatible = "microchip,mcp2515";
			reg = <0x0>;
			clocks = <0x20>;
			spi-max-frequency = <0x1e8480>;
			interrupt-parent = <0x6>;
			interrupts = <0x0 0x7 0x2>;
			pinctrl-names = "default";
                        pinctrl-0 = <0x21>;
			vdd-supply = <0x22>;
			xceiver-supply = <0x22>;

The "pinctrl@01c20800 " supplemented by the additional entry:

can0_pin_irq@0 {
pins = "PA7";
function = "irq";
drive-strength = <0x0>;
linux,phandle = <0x21>;
phandle = <0x21>;

and a additional Clock with phandle 0x20 ("fixed-clock" with 8Mhz Frequency).

it seems to be running:

Fri Nov 29 16:11:04 2019 kern.debug kernel: [ 6.878956] mcp251x spi0.0: CANCTRL 0x87
Fri Nov 29 16:11:04 2019 kernel: [ 6.879549] mcp251x spi0.0 can0: MCP2515 successfully initialized.

A device "can0" is created, but after "ifonfig can0 up" in the log is reported

Tue Dec 10 19:07:01 2019 kern.debug kernel: [ 94.366327] mcp251x spi0.0: CNF: 0x07 0xed 0x01

and no more communication is possible.
measurement with the oscilloscope shows the INT Pin of the MCP2515 is pulled to LOW, but no interrupt is muxed to the driver, the Pin does not respond.

in tests with the Armbian OS, the communication MCP -> SPI -> OS worked perfectly.

what am I doing wrong?
Do a driver need parameters (like the W1-driver...)?

Does anyone have any suggestions? I am out of ideas.

I got it to fly.

I know this question is a few years old, but do you still know what was needed to make it work?

Yes, that was a long time ago. I don't remember what the problem was. Possibly it was a problem with the bootloader.