From: Wolfram Sang <wsa@the-dreams.de>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
SH-Linux <linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] Serial port aliases in DT
Date: Thu, 27 Mar 2014 20:07:00 +0000 [thread overview]
Message-ID: <20140327200700.GA2585@katana> (raw)
In-Reply-To: <4966076.uASvrV0Iy2@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
> I disagree with this one: the aliases should be a board specific
> property, if not settable in the boot loader. This is how it traditionally
> work on OF, and I think it's the most sensible approach for end users:
> If the machine has multiple serial ports coming out the back, they are
> normally numbered in some way, and the numbers should match what you
> see in the OS, regardless of what the SoC calls them.
I agree with this one, makes sense. It calls for quite some cleanup,
though:
$ grep aliases arch/arm/boot/dts/*.dtsi | wc -l
79
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-27 20:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 11:59 [RFC] Serial port aliases in DT Laurent Pinchart
2014-03-10 12:38 ` Wolfram Sang
2014-03-11 11:56 ` Laurent Pinchart
2014-03-11 12:46 ` Wolfram Sang
2014-03-12 10:40 ` Laurent Pinchart
2014-03-12 10:45 ` Wolfram Sang
2014-03-10 12:57 ` Arnd Bergmann
2014-03-11 11:57 ` Laurent Pinchart
2014-03-27 12:50 ` Laurent Pinchart
2014-03-27 13:54 ` Rob Herring
2014-03-27 14:43 ` Laurent Pinchart
2014-03-27 15:18 ` Sascha Hauer
[not found] ` <20140327151829.GX17250-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-27 18:26 ` Arnd Bergmann
2014-03-27 18:34 ` Pawel Moll
2014-03-27 20:07 ` Wolfram Sang [this message]
2014-03-28 7:28 ` Sascha Hauer
[not found] ` <20140328072827.GY17250-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-28 8:09 ` Geert Uytterhoeven
2014-03-28 8:30 ` Arnd Bergmann
2014-03-28 8:39 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVYhGGt7+fR4oHzf-hDvTOWbHfhM2g92eo3RqULd6yR2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-28 10:28 ` Arnd Bergmann
2014-03-28 10:40 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVJ8Jid=bdWLb7g5MP5dFOwDkvoHEbFH4nQD5bWp-2sxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-28 11:49 ` Arnd Bergmann
2014-03-28 14:46 ` Rob Herring
2014-03-27 20:34 ` Rob Herring
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=20140327200700.GA2585@katana \
--to=wsa@the-dreams.de \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).