cc'ing Aaro On Mon, 4 Jul 2011, Tony Lindgren wrote:
> Also related is the gptimer12 on secure omaps as reported by Aaro. This problem is actually worse. In this case it's not just preventing reset; we must prevent the kernel from using the device at all. My understanding is also that it's the X-Loader or bootloader -- or more broadly, secure mode code -- that actually chooses which devices are protected in this way. In other words, we can't make any automatic decisions that are based on knowing that a chip is a high-security chip -- it will need to be defined by the board file :-( For this case, we probably need some board file function to tell the hwmod code to disregard a device completely, to tell the kernel to pretend that the device does not exist. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
