Date: Thu, 29 Jul 2021 11:20:13 +0000 From: Sha Faisal via freebsd-hackers <freebsd-hackers@FreeBSD.org> To: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@FreeBSD.org> Cc: Justin Hibbits <jhibbits@juniper.net>, Kumara N Babu <bkumara@juniper.net>, Vikram M Gadagkar <vikramg@juniper.net> Subject: Re: Generic-xhci driver issue and changes for 64-but physical memory space Message-ID: <1A9919BF-4D07-4D71-B795-D6CFF6CD0FF1@juniper.net> In-Reply-To: <30397365-BC3C-41C4-BF55-0D13778EF0A8@juniper.net> References: <5A15D0DF-6D41-4F17-B07A-D5A061057644@juniper.net> <30397365-BC3C-41C4-BF55-0D13778EF0A8@juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mailing to freebsd-hackers, after adding my email id to subscriber list. Please assist with the below query. Regards Faisal From: Sha Faisal <sfaisal@juniper.net> Date: Thursday, 29 July 2021 at 12:19 AM To: "hackers@freebsd.org" <hackers@freebsd.org> Cc: Justin Hibbits <jhibbits@juniper.net>, Kumara N Babu <bkumara@juniper.net>, Vikram M Gadagkar <vikramg@juniper.net> Subject: Generic-xhci driver issue and changes for 64-but physical memory space Hello FreeBSD-hackers Inn one of our new platforms we have physical RAM placed above the 4GB mark. And the eUSB device is capable of doing 64-bit DMA. The USBPHY uses the generic-xhci driver and when we were bringing-up we hit the issue below and the code panic’s xhci0: <Marvell Integrated USB 3.0 controller> mem 0x10243000-0x10243fff irq 15 on simplebus1 xhci0: 64 bytes context size, 32-bit DMA panic: vm_wait in early boot I modified the below function call , and the usb driver is up and it works fine. Please suggest if this change is fine and can be incorporated. #define IS_DMA_32B 1 #define IS_DMA_64B 0 err = xhci_init(sc, dev, IS_DMA_64B); Regards Faisal Juniper Business Use Only
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1A9919BF-4D07-4D71-B795-D6CFF6CD0FF1>