Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932316Ab3FEU46 (ORCPT ); Wed, 5 Jun 2013 16:56:58 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:53077 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932194Ab3FEU4x (ORCPT ); Wed, 5 Jun 2013 16:56:53 -0400 MIME-Version: 1.0 In-Reply-To: <20130605031536.GA24910@quad.lixom.net> References: <1370397539-21653-1-git-send-email-dianders@chromium.org> <20130605031536.GA24910@quad.lixom.net> Date: Wed, 5 Jun 2013 13:56:52 -0700 X-Google-Sender-Auth: hzkYs4LTwr58py4erRleEQQCB3E Message-ID: Subject: Re: [PATCH] ARM: samsung: avoid racy early printk at bootup From: Doug Anderson To: Olof Johansson Cc: Kukjin Kim , Thomas Abraham , Simon Glass , linux-samsung-soc , Tomasz Figa , Russell King , Ben Dooks , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 26 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 earlier. The window of > exposure is still there, but much smaller (and similar to how it always > has been). > > In current upstream, if there is no map_io mach_desc entry at all, > debug_ll_io_init() will be called on all platforms. Seems appropriate > to call that explicitly before of_scan_flat_dt() in exynos_init_io() > in this case. Oh. Ummm, right. Yes, debug_ll_io_init() is exactly what's needed here instead of all the complexity of what I proposed. New patch coming shortly. Thanks! :) -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/