Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753395AbaKZVt3 (ORCPT ); Wed, 26 Nov 2014 16:49:29 -0500 Received: from vps0.lunn.ch ([178.209.37.122]:40054 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753311AbaKZVt1 (ORCPT ); Wed, 26 Nov 2014 16:49:27 -0500 Date: Wed, 26 Nov 2014 22:48:47 +0100 From: Andrew Lunn To: Grant Likely Cc: Andrew Lunn , Leif Lindholm , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , Mark Rutland , Rob Herring , Jean-Christophe PLAGNIOL-VILLARD , Ian Campbell , "s.hauer@pengutronix.de" Subject: Re: [PATCH v2 2/2] of: support passing console options with stdout-path Message-ID: <20141126214847.GJ3443@lunn.ch> References: <1417023640-23464-1-git-send-email-leif.lindholm@linaro.org> <1417023640-23464-3-git-send-email-leif.lindholm@linaro.org> <20141126183052.GH3443@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 26, 2014 at 09:07:33PM +0000, Grant Likely wrote: > On Wed, Nov 26, 2014 at 6:30 PM, Andrew Lunn wrote: > > On Wed, Nov 26, 2014 at 05:40:40PM +0000, Leif Lindholm wrote: > >> Support specifying console options (like with console=ttyXN,) > >> by appending them to the stdout-path property after a separating ':'. > >> > >> Example: > >> stdout-path = "uart0:115200"; > > > > Hi Leif > > > > This should be documented somewhere under > > Documentation/devicetree/bindings/ > > > > Not sure where thought. Maybe a top level chosen.txt? > > Actually, this one doesn't. It is already documented in ePAPR Hi Grant Humm, do i have an old version of ePAPR? All i see is that in Table 3-4 It says: stdout-path O A string that specifies the full path to the node representing the device to be used for boot console output. If the character ":" is present in the value it terminates the path. The value may be an alias. If the stdin-path property is not specified, stdout-path should be assumed to define the input device. So what is before the : is defined. What comes afterwards, baudrate/parity/bits/flow control does not appear to the defined in ePAPR. Should we not document the extension being added here? Andrew -- 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/