public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: serial: of-serial: fetch line number from DT
Date: Mon, 24 Nov 2014 22:41:39 +0100	[thread overview]
Message-ID: <1416865299.2180.1.camel@lynxeye.de> (raw)
In-Reply-To: <CAOesGMhe8orqL6wSiouQvdM8y4N44p12n7M1opraSkAP=3ZB+A@mail.gmail.com>

Hi Greg,

Am Dienstag, den 11.11.2014, 08:51 -0800 schrieb Olof Johansson:
> On Mon, Nov 10, 2014 at 9:24 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Nov 10, 2014 at 01:34:19PM -0800, 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
> >>
> >>     The general agreed way to specify a fixed line number
> >>     for a serial console is to provide a "serial" alias
> >>     in the devicetree. Start parsing this property in
> >>     of_serial.
> >>
> >>     Signed-off-by: Lucas Stach <dev@lynxeye.de>
> >>     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>
> >>
> >> 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. :(
> >>
> >> Greg, can you please revert until we get the tegra-side fixes in for
> >> this, or we're in for a pretty lousy time w.r.t. bisecting problems
> >> across the two mergepoints?
> >>
> >> 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.
> >>
> >> Apologies for not replying to the patch directly -- it was only ever
> >> posted to linux-serial and I don't seem to be subscribed.
> >
> > Now reverted, sorry for the problems.
> 
> No worries, it's what linux-next is for. Thanks for the revert!
> 
As 3.18-rc6 now landed the fix to avoid the regression on Tegra would
you please consider reapplying this patch?

Regards,
Lucas

  reply	other threads:[~2014-11-24 21:41 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
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 [this message]
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=1416865299.2180.1.camel@lynxeye.de \
    --to=dev@lynxeye.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