public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Chen-Yu Tsai <wens@csie.org>,
	Russell King <linux@armlinux.org.uk>,
	Hans de Goede <hdegoede@redhat.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board
Date: Thu, 25 Aug 2016 22:47:26 +0200	[thread overview]
Message-ID: <20160825204726.GH32598@lukather> (raw)
In-Reply-To: <116041472134355@web12g.yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

On Thu, Aug 25, 2016 at 10:12:35PM +0800, Icenowy Zheng wrote:
> >>  But many codes will require a ttyS0 as console... So I think the
> >>  bluetooth should be located at ttyS1...
> >
> > Most of them would use /dev/console anyway. What do you have in mind?
> 
> As a general configuration, /dev/ttyS0 will be indicated as the default console=
> value... (Otherwise more boards will fail)

There's no reason to make that assumption. The console might be on
another UART entirely (ttyS3, for the sake of the argument), on a
different UART "class" (ttyUSB?, framebuffer console?), or not present
at all.

If you want to use the console, use /dev/console.

I don't what's so special about the UART here. Every single device in
Linux behaves that way.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-08-25 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160823064451.25997-1-icenowy@aosc.xyz>
     [not found] ` <20160823064451.25997-2-icenowy@aosc.xyz>
2016-08-24 19:32   ` [PATCH 1/2] ARM: dts: sun8i: Add dts file for inet-d978_rev2 tablets Maxime Ripard
     [not found]     ` <43601472083053@web23m.yandex.ru>
2016-08-25  7:35       ` Maxime Ripard
     [not found] ` <20160823064451.25997-3-icenowy@aosc.xyz>
2016-08-24 19:36   ` [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board Maxime Ripard
     [not found]     ` <43951472083107@web23m.yandex.ru>
2016-08-25  4:40       ` Chen-Yu Tsai
     [not found]         ` <97321472108244@web8m.yandex.ru>
2016-08-25  8:03           ` Maxime Ripard
     [not found]             ` <116041472134355@web12g.yandex.ru>
2016-08-25 14:17               ` Hans de Goede
     [not found]                 ` <438381472136802@web24g.yandex.ru>
2016-08-25 15:13                   ` Hans de Goede
2016-08-25 20:47               ` Maxime Ripard [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=20160825204726.GH32598@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=icenowy@aosc.xyz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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