linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: Define stdout-path property for Spring board
Date: Wed, 18 Mar 2015 00:29:12 +0900	[thread overview]
Message-ID: <55084848.1000207@kernel.org> (raw)
In-Reply-To: <CABxcv=mmr-WWXY7-KUJe-3EP8FHRBzv-SabJma9VwGRPiHio3Q@mail.gmail.com>

On 03/16/15 20:28, Javier Martinez Canillas wrote:
> Hello Andreas,
> 
Hi,

>>> index f02775487cd4..b9ec763a5602 100644
>>> --- a/arch/arm/boot/dts/exynos5250-spring.dts
>>> +++ b/arch/arm/boot/dts/exynos5250-spring.dts
>>> @@ -25,6 +25,7 @@
>>>
>>>       chosen {
>>>               bootargs = "console=tty1";
>>> +             stdout-path = "serial3:115200n8";
>>
>> Is this a guess or did you verify that against some schematics?
>>
> 
> I don't have access to the Spring schematics but it is based on what
> is defined in the vendor u-boot for Spring [0].
> 
> There isn't a Spring specific configuration file but only a
> chromeos_daisy.h which is shared by Snow, Spring and Kate (not yet in
> mainline):
> 
> #define CONFIG_DIRECT_BOOTARGS \
> "console=ttySAC3," STRINGIFY(CONFIG_BAUDRATE) " debug earlyprintk"
> 
> So I assumed that all daisy-based Chromebooks use the same UART for debug.
> 
>>>       };
>>>
>>>       gpio-keys {
>>
>> Assuming that bootargs still work,
>>
> 
> Yes, the semantics are not changed. The std-out property is only used
> as a default if no console= parameter is passed so if you already are
> passing one in your bootloader or using the one defined in the /chosen
> bootargs by enabling CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND, that
> will be used instead of std-out.
> 
>> Reviewed-by: Andreas F?rber <afaerber@suse.de>
>>
>> I do wonder why this mechanism could not point to the same location as
>> bootargs? ("dp-controller"?) The device does not even have screws for
> 
> I did wonder the same indeed but I don't know if you can use a display
> as std-out or only works for serial consoles.
> 
>> opening it, so accessing the serial port is highly theoretical.
>>
> 
> I see, in that case I think we could just drop this patch if is not
> possible to have a serial console even with some soldering like is the
> case in Snow, Peach Pit and Peach Pi.
> 
I've applied this whole series so if you guys find any problem on this,
please let me know ;)

Thanks,
Kukjin

  reply	other threads:[~2015-03-17 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 10:28 [PATCH 0/3] ARM: dts: Define stdout-patch for Exynos Chromebooks Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 1/3] ARM: dts: Define stdout-path property for Peach boards Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 2/3] ARM: dts: Define stdout-path property for Snow board Javier Martinez Canillas
2015-03-16 10:28 ` [PATCH 3/3] ARM: dts: Define stdout-path property for Spring board Javier Martinez Canillas
2015-03-16 11:05   ` Andreas Färber
2015-03-16 11:28     ` Javier Martinez Canillas
2015-03-17 15:29       ` Kukjin Kim [this message]
2015-03-17  1:51 ` [PATCH 0/3] ARM: dts: Define stdout-patch for Exynos Chromebooks Kukjin Kim
2015-03-17  5:27   ` Arnd Bergmann
2015-03-17 15:28     ` Kukjin Kim

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=55084848.1000207@kernel.org \
    --to=kgene@kernel.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;
as well as URLs for NNTP newsgroup(s).