Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933077AbaFLKM1 (ORCPT ); Thu, 12 Jun 2014 06:12:27 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:46483 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932878AbaFLKM0 (ORCPT ); Thu, 12 Jun 2014 06:12:26 -0400 From: Grant Likely Subject: Re: [RFC 0/5] of: Automatic console registration cleanups To: Rob Herring Cc: "devicetree@vger.kernel.org" , Christoffer Dall , "linux-kernel@vger.kernel.org" , Olof Johansson , Benjamin Herrenschmidt In-Reply-To: References: <1396022885-6102-1-git-send-email-grant.likely@linaro.org> Date: Thu, 12 Jun 2014 11:12:18 +0100 Message-Id: <20140612101218.3CCDCC42680@trevor.secretlab.ca> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 11 Jun 2014 20:28:31 -0500, Rob Herring wrote: > On Fri, Mar 28, 2014 at 11:08 AM, Grant Likely wrote: > > Hi all, > > > > This is a series that I've been playing with over the last few days to > > clean up the selection of default console devices when using the device > > tree. The device tree defines a way of specifying the console by using a > > "stdout-path" property in the /chosen node, but very few drivers > > actually attempt to use that data, and so for most platforms there needs > > to be a "console=" line in the command line if a serial port is intended > > to be used as the console. > > > > With this series, if there is a /chosen/stdout-path property, and if > > that property points to a serial port node, then when the serial driver > > registers the port, the core uart_add_one_port() function will notice > > and if no console= argument was provided then add it as a preferred > > console. > > > > I've not tested this very extensively yet, but I want to get some > > feedback before I go further. > > > > The one downside with this approach is that it doesn't do anything for > > early console setup. That still needs to be added on a per-driver basis, > > but at least it shouldn't conflict with this approach. > > Hey, what happened with this series? Ummm... I got distracted and forgot about it? I merged the first patch that adds stdout-path parsing, but the rest are still sitting in a side branch. I'll dust them off and rebase onto current mainline. g. -- 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/