On Tue, Aug 21, 2018 at 05:45:43PM +0200, Geert Uytterhoeven wrote: > Hi Robin, > > CC Lee (mfd), Wolfram (i2c), Marek (bd9571wmv + recent da9063 hacking) > > On Fri, Jul 27, 2018 at 6:28 PM Robin Murphy <[email protected]> wrote: > > On 27/07/18 17:17, Stefan Wahren wrote: > > > i was noticed that recent linux-next on Raspberry Pi 3 (32 bit) doesn't > > > boot anymore. So i tested todays linux-next with multi_v7_defconfig and > > > i'm getting a lot of DMA mask not set warnings. At least USB dwc2 is > > > broken. > > > > > > Any suggestions before i start to bisect? > > > > https://patchwork.kernel.org/patch/10547231/ > > > > Although the upside of this hiccup is that it should give us a fair view > > of how many active drivers are still relying on implicit default DMA > > masks - I'm now waiting for kernelci's boot chart to catch up with > > today's -next to see the full fallout... > > I'm still seeing the following on r8a7791/koelsch with a DA9063 PMIC, which > is an MFD device: > > da9063-watchdog da9063-watchdog: DMA mask not set > da9063-rtc da9063-rtc: DMA mask not set > > The dma masks (both normal and coherent) are NULL, and inherited from the > i2c parent device (6-0058):
I think the larger question is: why is the kernel complaining about an unset DMA mask for a device that does not have any capability to perform DMA? Surely the warning is wrong. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up According to speedtest.net: 13Mbps down 490kbps up
