On Wed, Nov 26, 2014 at 9:48 PM, Andrew Lunn <andrew@xxxxxxx> wrote: > On Wed, Nov 26, 2014 at 09:07:33PM +0000, Grant Likely wrote: >> On Wed, Nov 26, 2014 at 6:30 PM, Andrew Lunn <andrew@xxxxxxx> wrote: >> > On Wed, Nov 26, 2014 at 05:40:40PM +0000, Leif Lindholm wrote: >> >> Support specifying console options (like with console=ttyXN,<options>) >> >> 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 <string> 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? Ah, good point. I had thought you were referring to the argument separator. Yes, the extension should be documented. The binding can actually be driver specific, but there is little to no reason for each uart driver to be unique in this regard and the b/p/b/f format is very well established, so I agree. Other drivers, say video out or netcon, could use different arguments. g. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
