Hi Robin, > Robin Murphy <robin.murphy@xxxxxxx> hat am 24. Juli 2017 um 13:22 geschrieben: > > > Hi Andreas, > > On 22/07/17 13:29, Andreas Färber wrote: > > Hello, > > > > With arm64 4.13-rc1 I get no eth0 device on Pi3 (openSUSE Tumbleweed). > > The v4.13-rc1 DT works okay with a 4.12 kernel. > > > > Possibly related: > > > > [ 15.916350] OF: /soc/usb@7e980000: could not get #phy-cells for /phy > > > > [ 16.496662] usb 1-1: new high-speed USB device number 2 using dwc2 > > [ 16.502988] dwc2 3f980000.usb: Cannot do DMA to address > > 0x00000000335da400 > > This is from SWIOTLB's map_single(), which means whatever device was > passed into dma_map_single() when mapping the URB had a DMA mask smaller > than 30 bits (or none at all), which sounds wrong and is almost > certainly the root of the problem (i.e. it probably wasn't the actual > HCD device described in DT and set up by of_dma_configure()). how can i figure out what's cause this issue (bcm283x or dwc2 specific)? The dwc2 hcd already check the DMA mask on probe [1] and i never saw a warning in error case. Regards Stefan [1] - http://elixir.free-electrons.com/linux/latest/source/drivers/usb/dwc2/hcd.c#L5096 > However, > arm64's __swiotlb_map_page() still shouldn't be trying to perform cache > maintenance on the error value returned, which looks to be where the > actual splat below hails from - leave that one with me ;) > > Robin. > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
