This is not really a question.
I asked the same question previously (link above) and did not get a response.
Now I found a solution, so I thought I'd share it.
The problem was that connecting an AM335x RMII2 to a KSZ8895 in U-Boot did not work.
The chips are connected using RMII2, MDIO and SPI.
First of all, U-boot has a bug, which always will force the use of RMII1 if only one RMII port is used.
I will forward a patch for that to U-Boot.
The second issue is that the Switch does not establish a link on RMII2.
This switch when configured in SPI mode, disables itself and you have to write 0x61 to register 1 to enable it.
Since I have 4 chip selects on SPI1 and the OMAP driver only supports 2 chipselects, I wrote a bitbanging driver.
This driver had a problem, which allowed reading from the switch.
The SPI bus was not available on any test pins, but connected to an FPGA.
The FPGAs were to be configured by SPI1 as well using a new driver, and I only got configuration working last week.
I now detected the problem of the SPI bitbang driver, the clock did not return to 0 at the end when in mode 0,
and the switch did not accept the write.
After fixing the driver, I managed to write to the switch over SPI, and by writing 0x61 to register 1,
the chip was enabled, and the network link was suddenly up and running.
