On 25 July 2017 at 11:10, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Stefan Eichenberger <eichest@xxxxxxxxx> [170725 02:04]: >> I already did an RFC [1] that tried to do the same but I think this one is >> cleaner. If a hardware module is disabled in devicetree the address range >> will still be touched by omap_hwmod.c. If the corresponding module isn't >> powered this can lead to a crash of the kernel (for example rtc): > ... > >> This patch will immediately set the disabled module to >> _HWMOD_STATE_DISABLED. > > Thanks I noticed the same issue with rng on hs omap4. I think this is a good > solution. And then the status = "incomplete" patch I posted a while back > can be used to idle devices that are safe to touch and are not wired up on > a device. Will do some testing on your patch. Perfect, thanks for testing! The patch should apply on top of linux-omap/for-next. Regards, Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
