Re: [PATCH] ARM: samsung: avoid racy early printk at bootup

2013-06-05 Thread Doug Anderson
Olof, On Tue, Jun 4, 2013 at 8:15 PM, Olof Johansson wrote: > This seems to be caused by not calling iotable_ini() in exynos_init_io() > when a device tree is passed into the kernel, thus not setting up the > mapping for the UART in that case. > > I think the solution is instead to map the uart e

Re: [PATCH] ARM: samsung: avoid racy early printk at bootup

2013-06-04 Thread Olof Johansson
Hi, On Tue, Jun 04, 2013 at 06:58:59PM -0700, Doug Anderson wrote: > At boot, we've got a stack trace that looks something like this > (exynos5 as example) > * exynos5_map_io > * s3c_init_cpu > * exynos_init_io > * exynos5_dt_map_io > * paging_init > * setup_arch > > When paging_init() runs we'll

[PATCH] ARM: samsung: avoid racy early printk at bootup

2013-06-04 Thread Doug Anderson
At boot, we've got a stack trace that looks something like this (exynos5 as example) * exynos5_map_io * s3c_init_cpu * exynos_init_io * exynos5_dt_map_io * paging_init * setup_arch When paging_init() runs we'll lose any early MMU mappings that we might have had to allow us access to S3C_VA_UART.