On 2018-05-14 10:55, iallende wrote: > Hi everyone, > > There is a problem with Jailhouse and the last ZCU102 DTBs. > > Xilinx provides a Linux repository. The releases before 2016 works perfectly > with Jailhouse. However, 2017 and 2018 versions do not. > > When a I try to use the GIC-Demo, the second UART does not show anything. > Nevertheless, using the the Debug Console worked in the Uart 0. > > Therefore, I have been looking for the differences and Xilinx configs the > clks differently in the DTB. > > https://github.com/Xilinx/linux-xlnx/blob/xilinx-v2017.4/arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi > > https://github.com/Xilinx/linux-xlnx/blob/xilinx-v2016.4/arch/arm64/boot/dts/xilinx/zynqmp-clk.dtsi > > I know the source of the problem, but not the solution. In the last DTB the > uart is configured: > > &uart1 { > clocks = <&clkc 57>, <&clkc 31>; > }; > > If you change this line to "clocks = <&clk100 &clk100>;" works perfectly. > Therefore, it is something related with the clock.
Unfortunately, I'm not familiar enough with the platform to explain what the meaning of that change is. > > However, I do not know how/where does Jailhouse configure the peripheral > clocks. > For the Xilinx UART, Jailhouse does not configure any clocks so far, neither in the hypervisor nor in the inmate library. It relies on the root Linux to set the clocks as needed to operate the UARTs. We likely need to figure out which clock gates need to be switched, add the required code to the uart_init handler and set the related parameter in the cell/platform configurations. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
