In kernel 6.12, only with `loglevel=0` boot argument, sometimes we have
modem FW asserts (ucode 0x4091 means _empty RFs_):
```
"vpp.service","dpdk             [notice]: 0003:01:00.0: Firmware error detected, assert codes FW 0x00004610, UCODE 0x00004091"
```

Armada 8k has 4 x PCI: cp0_pcie0, cp0_pcie1, cp1_pcie0, cp1_pcie1. The
issue happens when they are not probed in this order, for example
cp0_pcie1, cp1_pcie0, cp1_pcie1 and only then cp0_pcie0. This PR adds
support for node dependencies, so the right order can be enforced:
```
&cp0_pcie1 {
    [...]
    depends-on = <&cp0_pcie0>;
};
```

At boot:
```
[   21.784820] armada8k-pcie f2620000.pcie: deferred probe: /cp0/pcie@f2600000 not ready
[   21.785034] armada8k-pcie f4600000.pcie: deferred probe: /cp0/pcie@f2620000 not ready
[   21.785223] armada8k-pcie f4620000.pcie: deferred probe: /cp1/pcie@f4600000 not ready
```

In kernel 6.12, only with `loglevel=0` boot argument, sometimes we have
modem FW asserts (ucode 0x4091 means _empty RFs_):
```
"vpp.service","dpdk             [notice]: 0003:01:00.0: Firmware error detected, assert codes FW 0x00004610, UCODE 0x00004091"
```

Armada 8k has 4 x PCI: cp0_pcie0, cp0_pcie1, cp1_pcie0, cp1_pcie1. The
issue happens when they are not probed in this order, for example
cp0_pcie1, cp1_pcie0, cp1_pcie1 and only then cp0_pcie0. This PR adds
support for node dependencies, so the right order can be enforced:
```
&cp0_pcie1 {
    [...]
    depends-on = <&cp0_pcie0>;
};
```

At boot:
```
[   21.784820] armada8k-pcie f2620000.pcie: deferred probe: /cp0/pcie@f2600000 not ready
[   21.785034] armada8k-pcie f4600000.pcie: deferred probe: /cp0/pcie@f2620000 not ready
[   21.785223] armada8k-pcie f4620000.pcie: deferred probe: /cp1/pcie@f4600000 not ready
```

In kernel 6.12, only with `loglevel=0` boot argument, sometimes we have
modem FW asserts (ucode 0x4091 means _empty RFs_):
```
"vpp.service","dpdk             [notice]: 0003:01:00.0: Firmware error detected, assert codes FW 0x00004610, UCODE 0x00004091"
```

Armada 8k has 4 x PCI: cp0_pcie0, cp0_pcie1, cp1_pcie0, cp1_pcie1. The
issue happens when they are not probed in this order, for example
cp0_pcie1, cp1_pcie0, cp1_pcie1 and only then cp0_pcie0. This PR adds
support for node dependencies, so the right order can be enforced:
```
&cp0_pcie1 {
    [...]
    depends-on = <&cp0_pcie0>;
};
```

At boot:
```
[   21.784820] armada8k-pcie f2620000.pcie: deferred probe: /cp0/pcie@f2600000 not ready
[   21.785034] armada8k-pcie f4600000.pcie: deferred probe: /cp0/pcie@f2620000 not ready
[   21.785223] armada8k-pcie f4620000.pcie: deferred probe: /cp1/pcie@f4600000 not ready
```

In kernel 6.12, only with `loglevel=0` boot argument, sometimes we have
modem FW asserts (ucode 0x4091 means _empty RFs_):
```
"vpp.service","dpdk             [notice]: 0003:01:00.0: Firmware error detected, assert codes FW 0x00004610, UCODE 0x00004091"
```

Armada 8k has 4 x PCI: cp0_pcie0, cp0_pcie1, cp1_pcie0, cp1_pcie1. The
issue happens when they are not probed in this order, for example
cp0_pcie1, cp1_pcie0, cp1_pcie1 and only then cp0_pcie0. This PR adds
support for node dependencies, so the right order can be enforced:
```
&cp0_pcie1 {
    [...]
    depends-on = <&cp0_pcie0>;
};
```

At boot:
```
[   21.784820] armada8k-pcie f2620000.pcie: deferred probe: /cp0/pcie@f2600000 not ready
[   21.785034] armada8k-pcie f4600000.pcie: deferred probe: /cp0/pcie@f2620000 not ready
[   21.785223] armada8k-pcie f4620000.pcie: deferred probe: /cp1/pcie@f4600000 not ready
```