Hello Shuah, On Tue, Dec 12, 2017 at 7:26 PM, Shuah Khan <shuahkh@xxxxxxxxxxxxxxx> wrote: [snip] >>> >>> Not directly. I still didn't find time to properly add support for >>> devices, which were left in-working state (with active DMA >>> transactions) by bootloader, but due to some other changes in the >>> order of operations during boot process, power domains are >>> initialized very early and due to temporary lack of devices (which >>> are not yet added to the system), are turned off. This practically >>> stops FIMD for scanning framebuffer and "solves" this issue. >>> >>> I've checked now and Exynos Snow Chromebook boots fine with IOMMU >>> support enabled, both with v4.15-rc3 and linux-next. > > Would it make sense to enable EXYNOS_IOMMU in exynos_defconfig. I sent > a patch to do that a while back. The decision at the time to not pull > that patch is was based on systems not booting with it enabled. > > Is it time to revisit that or the recommendation is for IOMMU to be > enabled in configs manually on systems it is safe to do so? > Yes, I think it would be good to have it enabled by default if that doesn't cause boot issues anymore. Could you please resend your patch and cc Marek and me so we can test on Snow and Peach Chromebooks? > thanks, > -- Shuah Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |