From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: How do /dev/ttyS* devices get assigned from the device tree?
Date: Sat, 9 Jul 2016 22:37:31 +0300 [thread overview]
Message-ID: <20160709193731.GA3870@tarshish> (raw)
In-Reply-To: <CAF_dkJBmgxyQLNtJqXWyQtzsmcK3QCqjYugsMG7MXGUdjL6nvA@mail.gmail.com>
Hi Patrick,
On Fri, Jul 08, 2016 at 12:58:06PM -0400, Patrick Doyle wrote:
> Do they show up numerically in the sequence in which they appear in
> the device tree?
>
> Where could I learn more?
Adding devicetree ML to Cc.
You may use an "aliases" node for that, if your UART driver supports that. The
8250/16550 driver does. See arch/arm/boot/dts/aspeed-ast2500-evb.dts, for
example. Note though that the use of aliases for this purpose is contentious.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2016-07-09 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 16:58 How do /dev/ttyS* devices get assigned from the device tree? Patrick Doyle
2016-07-09 19:37 ` Baruch Siach [this message]
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=20160709193731.GA3870@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).