[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3363597.IVJfReRkL0@wuerfel>
Date: Fri, 06 Jan 2017 20:21:34 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Rob Herring <robh@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marcel Holtmann <marcel@...tmann.org>,
Jiri Slaby <jslaby@...e.com>,
Sebastian Reichel <sre@...nel.org>,
"Dr . H . Nikolaus Schaller" <hns@...delico.com>,
Peter Hurley <peter@...leysoftware.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Loic Poulain <loic.poulain@...el.com>,
Pavel Machek <pavel@....cz>, NeilBrown <neil@...wn.name>,
Linus Walleij <linus.walleij@...aro.org>,
linux-bluetooth@...r.kernel.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org
Subject: Re: [PATCH 6/9] dt/bindings: Add a serial/UART attached device binding
On Friday, January 6, 2017 10:26:32 AM CET Rob Herring wrote:
> +Optional Properties:
> +
> +- reg : A single cell representing the port/line number of the
> + host UART. Only used if the host UART is a single node
> + with multiple ports.
> +
If there is a 'reg' property in the child, I guess we should also
document a #address-cells/#size-cells value for the parent.
Can you give an example of a multi-port serial device we support?
I was expecting that we already need a device node per port anyway,
to make the console work.
Arnd
Powered by blists - more mailing lists