From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: ux500: define serial port aliases
Date: Fri, 17 Jul 2015 14:23:19 +0200 [thread overview]
Message-ID: <3466799.BCvMeL6TVk@wuerfel> (raw)
In-Reply-To: <CACRpkdb3k+s65tOR13iKNLqJ+CWvxSH6d3Z2Ra4OJ9rw+t2Q3w@mail.gmail.com>
On Thursday 16 July 2015 21:57:35 Linus Walleij wrote:
> On Thu, Jul 16, 2015 at 4:09 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 16 July 2015 16:03:18 Linus Walleij wrote:
>
> >> The aliases are set also to disabled ports to ensure enumeration
> >> for the cases where a board file enabled a previously disabled
> >> UART.
> >>
> >
> > Well, both really. The status property tells the kernel to not
> > ever touch a device, while the alias is what traditionally gets
> > used to assign an OS visible device name to a device in the tree.
> > This is more true for MacOS and AIX than Linux, which sometimes
> > does its own naming, but we really should not have an alias pointing
> > at a disabled device node.
>
> OK ... I will make a patch that remove the aliases for the disabled
> nodes.
>
> But this makes me think of whether the DT compiler should allow
> it or at least warn about it?
We don't get a lot of warnings from dtc at the moment, but
we could start adding them for stuff like this. It probably
requires looking at the whole dtb a bit deeper than dtc
does at the moment.
Arnd
next prev parent reply other threads:[~2015-07-17 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 9:32 [PATCH 1/2] ARM: ux500: define serial port aliases Linus Walleij
2015-07-12 21:02 ` Arnd Bergmann
2015-07-13 8:16 ` Linus Walleij
2015-07-13 8:21 ` Linus Walleij
2015-07-14 20:53 ` Arnd Bergmann
2015-07-16 14:03 ` Linus Walleij
2015-07-16 14:09 ` Arnd Bergmann
2015-07-16 19:57 ` Linus Walleij
2015-07-17 12:23 ` Arnd Bergmann [this message]
2015-07-14 9:15 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 13:15 Linus Walleij
2015-07-08 14:44 ` Arnd Bergmann
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=3466799.BCvMeL6TVk@wuerfel \
--to=arnd@arndb.de \
--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