From: Maarten Brock <m.brock@vanmierlo.com>
To: Rob Herring <robh@kernel.org>
Cc: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, shubhrajyoti.datta@gmail.com,
linux-serial-owner@vger.kernel.org
Subject: Re: [PATCH 3/4] doc: uartlite: Add binding for the driver
Date: Mon, 09 Jul 2018 15:44:41 +0200 [thread overview]
Message-ID: <cbcc75219d9c9721341f237f31f44549@vanmierlo.com> (raw)
In-Reply-To: <20180703224239.GA6756@rob-hp-laptop>
On 2018-07-04 00:42, Rob Herring wrote:
> On Wed, Jun 27, 2018 at 05:53:44PM +0530, Shubhrajyoti Datta wrote:
>> +
>> +Optional properties:
>> +- port-number : Set Uart port number
>
> Nope. Use aliases.
You may not like the current implementation, but that is no reason to
deny
this documentation of the current state.
Personally I don't get this preference for aliases. It is a one way
mapping
in the wrong direction if you ask me. If e.g. you have serial0 pointing
to
a 16550 it will give /dev/ttyS0. This prevents you to create
/dev/ttyUL0,
because serial0 is already taken. Note that ttySx and ttyULx are in
different namespaces. It would only make sense if ttyULx was an illegal
name for a UART.
Maarten
next prev parent reply other threads:[~2018-07-09 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 12:23 [PATCH 1/4] tty: serial: uartlite: Add structure for private data Shubhrajyoti Datta
2018-06-27 12:23 ` [PATCH 2/4] tty: serial: uartlite: Add clock adaptation Shubhrajyoti Datta
2018-06-28 12:12 ` Greg KH
2018-06-27 12:23 ` [PATCH 3/4] doc: uartlite: Add binding for the driver Shubhrajyoti Datta
2018-07-03 22:42 ` Rob Herring
2018-07-09 13:44 ` Maarten Brock [this message]
2018-07-09 14:36 ` Rob Herring
2018-07-03 22:43 ` Rob Herring
2018-06-27 12:23 ` [PATCH 4/4] Documentation: uartlite: Add clock to the binding Shubhrajyoti Datta
2018-07-03 22:45 ` Rob Herring
2018-06-28 12:14 ` [PATCH 1/4] tty: serial: uartlite: Add structure for private data Greg KH
2018-07-02 4:29 ` Shubhrajyoti Datta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cbcc75219d9c9721341f237f31f44549@vanmierlo.com \
--to=m.brock@vanmierlo.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial-owner@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shubhrajyoti.datta@gmail.com \
--cc=shubhrajyoti.datta@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox