public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: serial: of-serial: fetch line number from DT
Date: Mon, 10 Nov 2014 14:38:45 -0700	[thread overview]
Message-ID: <54613065.1090300@wwwdotorg.org> (raw)
In-Reply-To: <CAOesGMjzs=dThDv6S8Xvo+ym-XECaQhTQ8NV6t46fQZ1LoJnHw@mail.gmail.com>

On 11/10/2014 02:34 PM, Olof Johansson wrote:
> Greg,
>
> This commit:
>
> commit 1bd8324535ec1ff44aef55c0e40b9e7d56b310fb
> Author: Lucas Stach <dev@lynxeye.de>
> Date:   Mon Nov 3 23:16:54 2014 +0100
>
>      serial: of-serial: fetch line number from DT
...
> Broke a whole lot of tegra boards in last night's -next here. In
> particular, I've been looking at tegra20-seaboard, which now doesn't
> boot with console any more.
>
> http://arm-soc.lixom.net/bootlogs/next/next-20141110/
>
> Unfortunately, tegra has for a long time been specifying the aliases
> as a fixed 1:1 mapping, but most environments rely on ttyS0 being the
> first _activated_ serial port. That's obviously going to break things
> here. :(
...
> Stephen: I suppose the best way to handle this on tegra is to specify
> the aliases per-board instead of in the soc dtsi today.

IIRC, there was a deliberate request to name the Tegra UARTs after the 
SoC ports rather than board ports, so that it'd be obvious to people 
which port was which. I'm not sure if we can change the aliases in the 
Tegra DTs now that people may have got used to them?

  reply	other threads:[~2014-11-10 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 21:34 serial: of-serial: fetch line number from DT Olof Johansson
2014-11-10 21:38 ` Stephen Warren [this message]
2014-11-10 21:49   ` Olof Johansson
2014-11-11 10:37   ` Lucas Stach
2014-11-11  5:24 ` Greg Kroah-Hartman
2014-11-11 16:51   ` Olof Johansson
2014-11-24 21:41     ` Lucas Stach
2014-11-24 21:57       ` Greg Kroah-Hartman
2014-11-24 21:58         ` Olof Johansson

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=54613065.1090300@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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