Michal, thank you very much - your kind advice really helped me to solve this problem! :) Please review a solution at https://review.coreboot.org/c/coreboot/+/38241/
On Tue, Jan 7, 2020 at 12:12 PM Michal Zygowski michal.zygowski@3mdeb.com wrote:
Hi Mike,
XHCI is muxed with EHCI on binaryPI 16h, so it might be teh same for fam16kb. When XHCI dev 10.0 is disabled, one has to flip bits in the PM registers additionally. If the board has no IRQ config for EHCI (probably because XHCI is the default supported option) you probably have to add these.
From what I see in the irq_tables.c file for this board, there is no routing set for device 0x16. Secondly, there is no device 0x16 in the devicetree of AM1I-A. Moreover mainboard_{pirq,intr,picr}_data table does not contain entries for the EHCI 0x16 device at all so IRQ is not programmed (only USB 0x12 and 0x13 devices are available from what i see). You would have to refer to a BKDG for your processor and chipset to check whether these problems I have listed are not copy-paste problems and EHCI 0x16 is really available for use without XHCI (IMO it should be).
Regards, Michał
On 06.01.2020 22:15, Mike Banon wrote:
My AM1I-A config is similar to G505S in this relation:
# CONFIG_HUDSON_XHCI_FWM is not set # CONFIG_HUDSON_XHCI_ENABLE is not set
Since XHCI is disabled, I expect its' USB 3.0 ports to work as USB 2.0, just like they are working on G505S. However, on AM1I-A they don't work at all, and I see this at dmesg kernel log:
ehci-pci 0000:00:16.2: can't derive routing for PCI INT B ehci-pci 0000:00:16:2: PCI INT B: no GSI ehci-pci 0000:00:16.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:16.2 setup! ehci-pci 0000:00:16:2: init 0000:00:16:2 fail, -19 ehci-platform: EHCI generic platform driver
ohci-pci 0000:00:16.0: can't derive routing for PCI INT A ohci-pci 0000:00:16:0: PCI INT A: no GSI ohci-pci 0000:00:16.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:16.0 setup! ohci-pci 0000:00:16:0: init 0000:00:16:0 fail, -19 ohci-platform: OHCI generic platform driver
I tried explicitly enabling 16.0 and 16.2 at devicetree.cb (they weren't mentioned here), but it doesn't help. What are my next steps?
Best regards, Mike Banon _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-- Michał Żygowski Firmware Engineer http://3mdeb.com | @3mdeb_com
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org