Difference between revisions of "Zynq development issues"

Revision as of 21:02, 12 April 2016

ISSUE 1: USB

Description

• Stopped working after switching from 3.10 to 4.0 kernel

Config

• kernel: 4.0 (linux-xlnx 468329e7fac2b22e76897fbd40532cc0884ded2a)
• new device tree record:

...
  ps7_usb_0: ps7-usb@e0002000 {
    clocks = <&clkc 28>;
    compatible = "xlnx,zynq-usb-2.20a", "chipidea,usb2";
    reg = <0xe0002000 0x1000>;
    interrupt-parent = <&ps7_scugic_0>;
    interrupts = <0 21 4>;
    dr_mode = "host";
    phy_type = "ulpi";
    usb-phy = <&usb_phy0>;
  } ;
  ...
} ;
...
usb_phy0: phy0{
  compatible = "ulpi-phy";
  #phy-cells = <0>;
  reg = <0xe0002000 0x1000>;
  viewport = <0x170>;
} ;

• .config

CONFIG_USB_ULPI=y
CONFIG_USB_ULPI_VIEWPORT=y
CONFIG_USB_CHIPIDEA_DEBUG=y
CONFIG_USB_GPIO_VBUS=n
CONFIG_USB_OTG=n /*do not care if dr_mode = "host";*/
CONFIG_USB_GADGET=n

Log

• dmesg:

[    1.035759] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.042319] usbcore: registered new interface driver usb-storage
[    1.073619] e0002000.ps7-usb supply vbus not found, using dummy regulator
[    1.103560] Registering platform device 'ci_hdrc.0'. Parent at e0002000.ps7-usb
[    1.114806] ci_hdrc ci_hdrc.0: ChipIdea HDRC found, revision: 22, lpm: 0; cap: f00d4100 op: f00d4140
[    1.136023] ci_hdrc ci_hdrc.0: unable to init phy: -110
[    1.141232] ci_hdrc: probe of ci_hdrc.0 failed with error -110

a: vbus not found

• the problem is not critical

b: unable to init phy: -110

• Zynq Linux USB Device Driver - typo in docs but it's correct in the released image
• note: order in the device tree does not matter
• corrected the device tree record (s/viewport/view-port/):

 usb_phy0: phy0{
   compatible = "ulpi-phy";
   #phy-cells = <0>;
   reg = <0xe0002000 0x1000>;
   view-port = <0x170>;
 } ;

Links

• Zynq Linux USB Device Driver - typo came from here.
• A discussion.
• Forgot the contents, probably unrelated

ISSUE 2: VSC330X

• Config and the kernel are the same as in ISSUE 1

Log

[    1.069904] vsc330x 0-0001: vsc330x_i2c_probe:841 error writing
[    1.075745] vsc330x: probe of 0-0001 failed with error -5

Reason

• 10398 board, that has it, is not connected, that's it.