USB not woking in 5.4 kernel

Products Support DragonBoard 820c
#1

Hi ,

i am using 5.4 kernel but usb doesn’t work,
i have applied the following patch but still facing the usb issue,
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/commit/?h=release/qcomlt-5.4&id=00a8066121a92c84cc6427a7ea4e4721f7111351

[ 0.977446] usbcore: registered new interface driver usbfs
[ 0.977494] usbcore: registered new interface driver hub
[ 0.977617] usbcore: registered new device driver usb
[ 8.250640] qcom-qusb2-phy 7411000.phy: Looking up vdda-pll-supply from device tree
[ 8.250750] qcom-qusb2-phy 7411000.phy: Looking up vdda-phy-dpdm-supply from device tree
[ 8.251120] qcom-qusb2-phy 7412000.phy: Looking up vdda-pll-supply from device tree
[ 8.251202] qcom-qusb2-phy 7412000.phy: Looking up vdda-phy-dpdm-supply from device tree
[ 13.524355] usbcore: registered new interface driver rtl8150
[ 13.527181] usbcore: registered new interface driver r8152
[ 13.532774] usbcore: registered new interface driver asix
[ 13.538090] usbcore: registered new interface driver ax88179_178a
[ 13.543522] usbcore: registered new interface driver cdc_ether
[ 13.549607] usbcore: registered new interface driver dm9601
[ 13.555316] usbcore: registered new interface driver net1080
[ 13.560847] usbcore: registered new interface driver plusb
[ 13.566698] usbcore: registered new interface driver cdc_subset
[ 13.571976] usbcore: registered new interface driver zaurus
[ 13.577833] usbcore: registered new interface driver cdc_ncm
[ 13.602930] dwc3-qcom 76f8800.usb: IRQ hs_phy_irq not found
[ 13.612998] dwc3-qcom 76f8800.usb: IRQ dp_hs_phy_irq not found
[ 13.623497] dwc3-qcom 76f8800.usb: IRQ dm_hs_phy_irq not found
[ 13.633914] dwc3-qcom 76f8800.usb: IRQ ss_phy_irq not found
[ 13.755623] dwc3-qcom 6af8800.usb: IRQ hs_phy_irq not found
[ 13.765683] dwc3-qcom 6af8800.usb: IRQ dp_hs_phy_irq not found
[ 13.776194] dwc3-qcom 6af8800.usb: IRQ dm_hs_phy_irq not found
[ 13.786613] dwc3-qcom 6af8800.usb: IRQ ss_phy_irq not found
[ 13.917604] usbcore: registered new interface driver usb-storage
[ 13.921816] usbcore: registered new interface driver usbserial_generic
[ 13.927961] usbserial: USB Serial support registered for generic
[ 13.945579] usbcore: registered new interface driver xpad
[ 13.949291] usbcore: registered new interface driver usb_acecad
[ 13.954817] usbcore: registered new interface driver aiptek
[ 13.960540] usbcore: registered new interface driver gtco
[ 13.966105] usbcore: registered new interface driver hanwang
[ 13.971659] usbcore: registered new interface driver kbtab
[ 14.157148] usbcore: registered new interface driver usbhid
[ 14.159245] usbhid: USB HID core driver
[ 14.233634] usbcore: registered new interface driver snd-usb-audio
[ 15.079481] qcom-qusb2-phy 7411000.phy: Looking up vdda-pll-supply from device tree
[ 15.079658] qcom-qusb2-phy 7411000.phy: Looking up vdda-phy-dpdm-supply from device tree
[ 15.080212] qcom-qusb2-phy 7411000.phy: Registered Qcom-QUSB2 phy
[ 15.080606] qcom-qusb2-phy 7412000.phy: Looking up vdda-pll-supply from device tree
[ 15.080777] qcom-qusb2-phy 7412000.phy: Looking up vdda-phy-dpdm-supply from device tree
[ 15.081260] qcom-qusb2-phy 7412000.phy: Registered Qcom-QUSB2 phy
[ 15.712449] dwc3-qcom 76f8800.usb: IRQ hs_phy_irq not found
[ 15.722514] dwc3-qcom 76f8800.usb: IRQ dp_hs_phy_irq not found
[ 15.733015] dwc3-qcom 76f8800.usb: IRQ dm_hs_phy_irq not found
[ 15.743446] dwc3-qcom 76f8800.usb: IRQ ss_phy_irq not found
[ 15.952357] dwc3-qcom 6af8800.usb: IRQ hs_phy_irq not found
[ 15.963357] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 15.967935] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.976013] dwc3-qcom 6af8800.usb: IRQ dp_hs_phy_irq not found
[ 15.989023] usb usb1: Product: xHCI Host Controller
[ 15.993786] usb usb1: Manufacturer: Linux 5.4.0-qcomlt-arm64 xhci-hcd
[ 15.998404] dwc3-qcom 6af8800.usb: IRQ dm_hs_phy_irq not found
[ 16.010733] usb usb1: SerialNumber: xhci-hcd.0.auto
[ 16.015830] dwc3-qcom 6af8800.usb: IRQ ss_phy_irq not found
[ 16.077704] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 16.082544] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 16.090504] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 16.116455] usb usb2: Product: xHCI Host Controller
[ 16.120870] usb usb2: Manufacturer: Linux 5.4.0-qcomlt-arm64 xhci-hcd
[ 16.137632] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 16.347806] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 16.361151] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 16.379369] usb usb3: Product: xHCI Host Controller
[ 16.393257] usb usb3: Manufacturer: Linux 5.4.0-qcomlt-arm64 xhci-hcd
[ 16.404884] usb usb3: SerialNumber: xhci-hcd.1.auto
[ 16.476636] usb usb4: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 16.476734] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 16.498965] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 16.498989] usb usb4: Product: xHCI Host Controller
[ 16.509868] usb usb4: Manufacturer: Linux 5.4.0-qcomlt-arm64 xhci-hcd
[ 16.514373] usb usb4: SerialNumber: xhci-hcd.1.auto

Please suggest some pointers to debug this issue.

Regards,
Ajith.Preformatted text

#2

What did you apply that commit to?

#3

Hi,
Thanks for the response,

i have downloaded the following source

checked out on this commid id : e2e8f9f and then added config from commit id 80fba46

Regards,
Ajith.

#4

Ah, I remember you now… You’re using a custom board, not a DB820c.

In fact, on a genuine DB820c, using the included DTS, USB will definitely work from the commit that you are using. Also note that the commit you reference is already in that kernel, so I presume that what you applied it to is your custom DTS.

Judging by your log, it looks like it found the USB controllers, but its having some IRQ errors. That’s probably where you need to focus in your DTS.

#5

So… it is OK to discuss boards like this on the forum but it is good etiquette to indicate when you start a topic that you are not, in fact, using a 96Boards product.

#6

Hi,

Since i asked this query under Products Support / Dragonboard 820c custom_board, I didn’t mention that again in the question.
Sorry for the confusion anyways.

#7

I’m afraid not… you didn’t add the custom_board… I did that!

#8

I thought i added under custom category, Sorry for the inconvenience.

#10

Hi @doitright

This is my dts entry

usb2: usb@76f8800 {
compatible = “qcom,msm8996-dwc3”, “qcom,dwc3”;
reg = <0x76f8800 0x400>;
#address-cells = <1>;
#size-cells = <1>;
ranges;

    clocks = <&gcc GCC_PERIPH_NOC_USB20_AHB_CLK>,
            <&gcc GCC_USB20_MASTER_CLK>,
            <&gcc GCC_USB20_MOCK_UTMI_CLK>,
            <&gcc GCC_USB20_SLEEP_CLK>,
            <&gcc GCC_USB_PHY_CFG_AHB2PHY_CLK>;

    assigned-clocks = <&gcc GCC_USB20_MOCK_UTMI_CLK>,
                      <&gcc GCC_USB20_MASTER_CLK>;
    assigned-clock-rates = <19200000>, <60000000>;

    power-domains = <&gcc USB30_GDSC>;
    status = "disabled";

    dwc3@7600000 {
            compatible = "snps,dwc3";
            reg = <0x7600000 0xcc00>;
            interrupts = <0 138 IRQ_TYPE_LEVEL_HIGH>;
            phys = <&hsusb_phy2>;
            phy-names = "usb2-phy";
            snps,dis_u2_susphy_quirk;
            snps,dis_enblslpm_quirk;
    };

};

usb@76f8800 {
status = “okay”;

dwc3@7600000 {
	dr_mode = "host";
	maximum-speed = "high-speed";
};

};

Regards,
Ajith

#11

I really can’t help you with that, if you can’t figure it out on your own, you probably should contact the board vendor for their assistance.

#12

I had a very similar problem when working with the Eragon820 board by eInfoChips. I do not understand the following patch (in the link), but applying it allowed USB to work.