From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5A65BC433DF for ; Sun, 5 Jul 2020 18:11:20 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2925A20720 for ; Sun, 5 Jul 2020 18:11:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="T5+Vhzh5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2925A20720 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=TORHfHNnRnvOaNQVY3/1zCFxDKVINYct3htsJ+Tu62A=; b=T5+Vhzh5MdTp/sC8wZqMomsZ+ xqdQCdMMCQ5lFIkp7MbL4JBhM62iOMu4NfGbZULppKaHGdd9zKMKlOkzPT8I40YuwI5aZxajtnNdL ywiulJbgaQLXqTyXkO+2Xd/ChPKAJrcdobrGP6ymeUbDOqRCe9innvIpNQYTtPzyKp0YI9R9rmB6G 1og5L1MuFeVV6N7fnjssAZHvod/7XhZF33KcX6uuVx0UTK//Bgd2yw8Rh4Ezt2DJ/iVZUWUCEhYkb FFSsSo851KsqZPhfqsealZrNEPRdkEjOdtLCkuQFI9a+7TUD165T7f3MKmJ2Z/jBnG8L4ChO2QaMU NAEkw3WIQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1js95M-0002A6-KU; Sun, 05 Jul 2020 18:09:52 +0000 Received: from mail-wm1-f67.google.com ([209.85.128.67]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1js95J-00029U-HP for linux-arm-kernel@lists.infradead.org; Sun, 05 Jul 2020 18:09:50 +0000 Received: by mail-wm1-f67.google.com with SMTP id f139so39290680wmf.5 for ; Sun, 05 Jul 2020 11:09:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=WFXUuYLx9z7kdQD8cxQDN+qE9M0mmvVhR4YuFlGCggU=; b=ErA4IBaDSpu3CpUyyOxpHVuTgbL0fgLa4KLceGOvsKASmIZrzxya+iE7iJLa5IVEeA R+DhhR37rlb1ekAgKAz1nbPQZlja96hGY/SnNqNtrFcWedXbGMIdCWfWslnRU6nntarG K9HjTirVi628/jHB+AkR5F4lprUiFr8poGPJqAqZ5Y22LS1jqffTs7Vpu+mHpNzHkamI E6ZQkKyVaMx3cPiZrNNsfaLk/87Yxyl13RLq95EdBKEzmbF2kKQiFvnxGndM1PDYer8E ordb/728QPevCZ0FdIjwk9pJoKMkZcwqfW53wE+h70FVR5VOE79qKJlczmshSRO9BZmw fp7Q== X-Gm-Message-State: AOAM5301+2lS0ZC4XvwVdaKMLD6QC1ZqQtP4EXiJ8WgFHigXkQc+wF84 +uxz3G5xlJ2Qeq9MjNlPb2w= X-Google-Smtp-Source: ABdhPJxjI4yFt1EotH4VAiKnZjhxmDAOFtIsBKxuNGU1hyL2uOKUIKD6daN9NG2yCKPfXkNal/526Q== X-Received: by 2002:a1c:cc0c:: with SMTP id h12mr3373057wmb.140.1593972588223; Sun, 05 Jul 2020 11:09:48 -0700 (PDT) Received: from kozik-lap ([194.230.155.195]) by smtp.googlemail.com with ESMTPSA id 138sm15606042wmb.1.2020.07.05.11.09.46 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Sun, 05 Jul 2020 11:09:46 -0700 (PDT) Date: Sun, 5 Jul 2020 20:09:44 +0200 From: 'Krzysztof Kozlowski' To: Alim Akhtar Subject: Re: [PATCH] arm64: dts: exynos: Add minimal bootargs Message-ID: <20200705180944.GB2765@kozik-lap> References: <20200703182536.9190-1-alim.akhtar@samsung.com> <000801d6516a$b6efcb40$24cf61c0$@samsung.com> <20200704102246.GA5975@kozik-lap> <004c01d6526d$18c365e0$4a4a31a0$@samsung.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <004c01d6526d$18c365e0$4a4a31a0$@samsung.com> User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200705_140949_614617_DC0FC058 X-CRM114-Status: GOOD ( 17.20 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: robh+dt@kernel.org, devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sun, Jul 05, 2020 at 07:09:14AM +0530, Alim Akhtar wrote: > Hi Krzysztof, > > Also, why did you use different serial for console? > > > Once UART driver gets probed then console changes to ttySAC0. In case I am using stdout-path only, > after bootconsole is disabled, kernel logs re-start printing from beginning (which might be expected behaviour?) > > [ 0.012416] printk: console [tty0] enabled > [ 0.016491] printk: bootconsole [exynos4210] disabled > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd032] > [ 0.000000] Linux version 5.8.0-rc3-next-20200703-00008-g4af626444f4a-dirty (alim@alim) (aarch64-linux-gnu-gcc (Linaro GCC 7.4-2019.02) 7.4.1 20181213 [l0 > [ 0.000000] Machine model: Samsung Exynos7 Espresso board based on Exynos7 > No, this is not desired. The fix for it should not be redefining the console to wrong argument. For example on Odroid MC1 this problem does not exist: [ 0.000000] earlycon: exynos4210 at MMIO 0x12c20000 (options '115200n8') [ 0.000000] printk: bootconsole [exynos4210] enabled [ 3.111883] printk: console [ttySAC2] enabled [ 3.111883] printk: console [ttySAC2] enabled [ 3.120102] printk: bootconsole [exynos4210] disabled [ 3.120102] printk: bootconsole [exynos4210] disabled but your console for some reason is tty0... why? Is your console ttySAC2? Maybe it is the effect of alias: serial0 = &serial_2; > > However the question is, are you sure you want earlycon on every, including > > successful boot? On most of the boards we do not enable by default. If > > developer needs, he can choose it for example via U-Boot "setenv opts > > earlycon". > > > Using U-Boot is not the case always, any bootload can be used to boot the Linux, currently I am Coreboot. > And 'earlycon' is not setup by default. > As Espresson board is development board, IMO it is ok to keep it enable all the time, this helps in quickly knowing what going on incase boot fails early. > Let me know if it is ok to keep " console=ttySAC0,115200n8" or shell I just re-spin with only 'earlycon'? or any other suggestion? It should be just earlycon. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel