| Message ID | 20200618153948.218506-3-jagan@amarulasolutions.com |
|---|---|
| State | New |
| Headers |
Return-Path: <linux-amarula+bncBD7MFH7A7EEBBY5CV33QKGQEEBKM7VY@amarulasolutions.com> X-Original-To: linux-amarula@patchwork.amarulasolutions.com Delivered-To: linux-amarula@patchwork.amarulasolutions.com Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) by ganimede.amarulasolutions.com (Postfix) with ESMTPS id 07C223F03F for <linux-amarula@patchwork.amarulasolutions.com>; Thu, 18 Jun 2020 18:08:06 +0200 (CEST) Received: by mail-pl1-f200.google.com with SMTP id d13sf4177261plr.20 for <linux-amarula@patchwork.amarulasolutions.com>; Thu, 18 Jun 2020 09:08:05 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1592496484; cv=pass; d=google.com; s=arc-20160816; b=zAr+cfwox2fUesAQsSJk/Nz6zJIS6LFjOBkYqoi7dtTfE6TmeQyFseRi1mnteQXEU0 giHMYrMMrNBZ13UsBnh9pejKzLOlUanxiRNj/ANHkM3xC7bTFim09gYhQ4T1Rb0kVBlB HY2E0q0zmR/lqhYZPGDhkWtr/Cfe1jtKhmFRVnKkPXdWnPj9VNcE10r8reTYuDPAbRWX Cmcz5FIQOiaPIKZoXkDPJav57YB5oh9tfaMaCG0rf53S4mp3UuRJrHFfmEI3bjPWjkC1 +3+yPNqleXhpe3CLCjDp1zgGOnVqd+5qWxsKcjgF/MY/k8+hICK1VlUd3N7DZCoUinL9 eR8A== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-archive:list-help:list-post:list-id :mailing-list:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=JTfDDn3SVFu+t16MUBw8E9t96K/Y8EejwuHO+gOHCp0=; b=mrbSC0XTFF28skk8MPSCYRtPWsf+j1ZWj9TxiL2ftDL19cqJDPzxhFz0EyNNQZheb1 cHUa2OTdg0L3ICJEjNrqK1fPoA5vIPv7LSOIWydeCUupIkgEbSka7v1sZrVUKtZJGMM/ DtDz73fWNRMl/1d/J56f5MlcoNXdjFeoausYzDwahqzUOwI6bV8GNNbomPpteuKS/O2R 1ZDM23gGRfRwCv2/Xex2pxe3XZ93e5X1HG8b1QKhgDmEbowAexj9xhIgfWaBX1wxD9Tg XVy0RBOKCGy6kgEMTYy6tFZzlyD7YQQpIFSf93j02XQo25agnvQIiMPeHcTHNFBTKZVX YvoA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=CLJW58wU; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-unsubscribe; bh=JTfDDn3SVFu+t16MUBw8E9t96K/Y8EejwuHO+gOHCp0=; b=Lf3t4R27d0l/HfnLx46DgxcG4RtkBB1VaXtKszO1R0hleu/EnF99WqybF30QJC25y2 TM11NmTcEvjRlT3dPV50cEXIACizyvBYP0FdD8NujA5dVxWw1ADmE8oeXOh6013gxuRo fpHkV/FZwtPa0wX8cWy+iKyExu9Srofo1rYjU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-unsubscribe; bh=JTfDDn3SVFu+t16MUBw8E9t96K/Y8EejwuHO+gOHCp0=; b=tK+8sT1ZzXoiB7wOULkIKGS2++AsmplJs3gEL4yzbEi4Nb/6UL7/DJLjurDqe1Wbmh EZTSAgYrPli9299qF0hkuK3ataKkf70th5z5zRRee2d6XOkYYywZqEXzcYM0F3F4l5CW 33K6btVVtPQMvrMl7AcP+kTp2RySEjotUdfrv+feP1VUFPzoOwNf6kPhOFjb+E+6yoW5 mjIMEGPQZhaJXuRaOAA/efZjlyUgvJ+R3SVlOC1JbXJZDDksOvXmxcTXqYLzNfbAIpdc ZdSZ8RhIqjIF3WlSQcMGC0/RqyoM6GrFSbmMt3qz+tPFyfcT16GPw450Cg/35fKbxsQq Y1bQ== X-Gm-Message-State: AOAM5300EXSPjf3YULg45zlq6Suhim7ank0DyzVbGje3q27Qi4DUbL8H BCuinn9WBpYJzPaLuFB1bt5Z/9V5 X-Google-Smtp-Source: ABdhPJyXKjVjWyqJ2cHVA0bvVIq38qvD4RNBtJSxrx/Kf222YAhr3UlB/00zI7XKmISVHlfj1YXCqw== X-Received: by 2002:a17:902:b942:: with SMTP id h2mr4199108pls.163.1592496483976; Thu, 18 Jun 2020 09:08:03 -0700 (PDT) X-BeenThere: linux-amarula@amarulasolutions.com Received: by 2002:a62:7a0c:: with SMTP id v12ls2001518pfc.1.gmail; Thu, 18 Jun 2020 09:08:03 -0700 (PDT) X-Received: by 2002:a63:371c:: with SMTP id e28mr3831434pga.114.1592496483521; Thu, 18 Jun 2020 09:08:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592496483; cv=none; d=google.com; s=arc-20160816; b=0A9+f/ryH9DlS7ugF95R5BGpSuivZn5b3MwbSlp0r+YX3Teb9hKkohZ0nNDBCxb8th beGjRpRhCdRPeLIoCaO+VdeCwemd2p6SDS1A0uXTEKJgWYF/ozHDJS07oBeGbZHoSYUi wyfCEcVdHTkja7Rno/9zo+pYOJJVJIQG9tafQNTeQFslgGon2G/d1noibiibuiUcez/O Im/HFTIayUQ0Mzey5fZi941BjgUTsbeOc4Mg7zhQRmx2BFX8IfMKIXRrmMlPBU4hRW8u yppjcg5amqOe6LP8itIQNDUv9BxOR8Znn8ey7z3BhGtjOMC3DpuwC4hTfVrg5nWfu5Uz 8OfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=8sFgYtAh2b0Wohv3uaF5Qyt69kdsVZxcLGheuYLU8jY=; b=ik5cg9W51JpiVzL4JIYy+NmYTOtT8fCsYW1pfEsshVHRu64FCvGyvHiyizrpa6VA9/ v2NXbw58uGbdWsPtgZS0PursZW3GbUn1Cmy5WlcRV2EHvI+TNFMc5yaKoIlzQA8a7L0N UiisZCbCkLvGXhoho8CSwYorwUVePBqlYmra93iLQEs4AGqTeKjlCl6NWAxP71KYBLZE 9w0VyNS7GXrWA+eL6jSNk7TWCIJdHB1vMi44SrI6bQHFdrCXwmecQl0DyFckKR2fcKsr mC7sZSil38snWCZwLv31pO9rNEdzGZzkvTKKQa6zjzfqx7rTCeheHnval0GAqW2apoOr j3PQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=CLJW58wU; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id a8sor4710443plp.19.2020.06.18.09.08.03 for <linux-amarula@amarulasolutions.com> (Google Transport Security); Thu, 18 Jun 2020 09:08:03 -0700 (PDT) Received-SPF: pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) client-ip=209.85.220.65; X-Received: by 2002:a17:902:ea8a:: with SMTP id x10mr4325689plb.330.1592496483193; Thu, 18 Jun 2020 09:08:03 -0700 (PDT) Received: from localhost.localdomain ([2405:201:c809:c7d5:b0c7:f192:869b:df87]) by smtp.gmail.com with ESMTPSA id u4sm3264943pfl.102.2020.06.18.09.07.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 09:08:02 -0700 (PDT) From: Jagan Teki <jagan@amarulasolutions.com> To: Kever Yang <kever.yang@rock-chips.com>, Philipp Tomsich <philipp.tomsich@theobroma-systems.com>, Simon Glass <sjg@chromium.org> Cc: Suniel Mahesh <sunil@amarulasolutions.com>, U-Boot-Denx <u-boot@lists.denx.de>, linux-rockchip@lists.infradead.org, linux-amarula <linux-amarula@amarulasolutions.com>, Jagan Teki <jagan@amarulasolutions.com> Subject: [PATCH v4 2/5] rk3399: spl: Print SPL banner after relocation Date: Thu, 18 Jun 2020 21:09:45 +0530 Message-Id: <20200618153948.218506-3-jagan@amarulasolutions.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200618153948.218506-1-jagan@amarulasolutions.com> References: <20200618153948.218506-1-jagan@amarulasolutions.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Original-Sender: jagan@amarulasolutions.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=CLJW58wU; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com Precedence: list Mailing-list: list linux-amarula@amarulasolutions.com; contact linux-amarula+owners@amarulasolutions.com List-ID: <linux-amarula.amarulasolutions.com> X-Spam-Checked-In-Group: linux-amarula@amarulasolutions.com X-Google-Group-Id: 476853432473 List-Post: <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/post>, <mailto:linux-amarula@amarulasolutions.com> List-Help: <https://support.google.com/a/amarulasolutions.com/bin/topic.py?topic=25838>, <mailto:linux-amarula+help@amarulasolutions.com> List-Archive: <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/> List-Unsubscribe: <mailto:googlegroups-manage+476853432473+unsubscribe@googlegroups.com>, <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/subscribe> |
| Series |
roc-rk3399-pc: Custom SPL init
|
|
Commit Message
Jagan Teki
June 18, 2020, 3:39 p.m. UTC
Usually printing the SPL banner varies between architecture or board codes. - Some would print before relocation at the end board_init_f for making sure all initialization prior to this would happen properly. if at all there is a requirement for serial init, that happens properly since it prints all after that. - Some would print after relocation at the spl_board_init for making sure all initialization prior to relocation would happen properly. Also debug uart on these cases would be available before relocation. So debug support is available in before and after relocation. Rockchip SPL is following formar step to print the banner at the end of board_init_f. To support various custom use cases in SPL like leds, environment, board detections later options like printing the banner after relocation would be a better option. Printing banner would also help to support debugging availability between relocation codes, like debug uart available before relocation and banner availability after relation. By demonstrating all the above use cases, this patch is trying to print the SPL banner after relocation. Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> Tested-by: Suniel Mahesh <sunil@amarulasolutions.com> --- Changes for v4: - none arch/arm/mach-rockchip/spl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Comments
Hi Jagan, On 2020/6/18 下午11:39, Jagan Teki wrote: > Usually printing the SPL banner varies between architecture > or board codes. > - Some would print before relocation at the end board_init_f > for making sure all initialization prior to this would happen > properly. if at all there is a requirement for serial init, > that happens properly since it prints all after that. > - Some would print after relocation at the spl_board_init for > making sure all initialization prior to relocation would > happen properly. Also debug uart on these cases would be > available before relocation. So debug support is available > in before and after relocation. > > Rockchip SPL is following formar step to print the banner at > the end of board_init_f. > > To support various custom use cases in SPL like leds, environment, > board detections later options like printing the banner after > relocation would be a better option. I don't agree, the banner is tell people we are in SPL now, we should print it as soon as possible, if any of step like led, env, relocate and etc fails, then user can not see anything, they don't event know if we have get into SPL. The update of leds and env does not depends on banner print. Thanks, - Kever > Printing banner would also > help to support debugging availability between relocation codes, > like debug uart available before relocation and banner availability > after relation. > > By demonstrating all the above use cases, this patch is trying > to print the SPL banner after relocation. > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > Tested-by: Suniel Mahesh <sunil@amarulasolutions.com> > --- > Changes for v4: > - none > > arch/arm/mach-rockchip/spl.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/mach-rockchip/spl.c b/arch/arm/mach-rockchip/spl.c > index d4c83a1119..6d5c058548 100644 > --- a/arch/arm/mach-rockchip/spl.c > +++ b/arch/arm/mach-rockchip/spl.c > @@ -147,7 +147,6 @@ void board_init_f(ulong dummy) > gd->ram_top = gd->ram_base + get_effective_memsize(); > gd->ram_top = board_get_usable_ram_top(gd->ram_size); > #endif > - preloader_console_init(); > } > > __weak void rk_spl_board_init(void) > @@ -158,6 +157,8 @@ void spl_board_init(void) > { > /* board specific spl init */ > rk_spl_board_init(); > + > + preloader_console_init(); > } > > #ifdef CONFIG_SPL_LOAD_FIT
Hi Kever, On Sun, Jun 28, 2020 at 8:26 AM Kever Yang <kever.yang@rock-chips.com> wrote: > > Hi Jagan, > > On 2020/6/18 下午11:39, Jagan Teki wrote: > > Usually printing the SPL banner varies between architecture > > or board codes. > > - Some would print before relocation at the end board_init_f > > for making sure all initialization prior to this would happen > > properly. if at all there is a requirement for serial init, > > that happens properly since it prints all after that. > > - Some would print after relocation at the spl_board_init for > > making sure all initialization prior to relocation would > > happen properly. Also debug uart on these cases would be > > available before relocation. So debug support is available > > in before and after relocation. > > > > Rockchip SPL is following formar step to print the banner at > > the end of board_init_f. > > > > To support various custom use cases in SPL like leds, environment, > > board detections later options like printing the banner after > > relocation would be a better option. > > I don't agree, the banner is tell people we are in SPL now, we should > print it as soon as > > possible, if any of step like led, env, relocate and etc fails, then > user can not see anything, > > they don't event know if we have get into SPL. The update of leds and > env does not depends > > on banner print. It is unsafe or sometimes won't work if we do leds, env at _f due to memory availability. Since we have debug uart at _f and moving spl banner to relocation will make the debug available possible in relocation code. Jagan.
diff --git a/arch/arm/mach-rockchip/spl.c b/arch/arm/mach-rockchip/spl.c index d4c83a1119..6d5c058548 100644 --- a/arch/arm/mach-rockchip/spl.c +++ b/arch/arm/mach-rockchip/spl.c @@ -147,7 +147,6 @@ void board_init_f(ulong dummy) gd->ram_top = gd->ram_base + get_effective_memsize(); gd->ram_top = board_get_usable_ram_top(gd->ram_size); #endif - preloader_console_init(); } __weak void rk_spl_board_init(void) @@ -158,6 +157,8 @@ void spl_board_init(void) { /* board specific spl init */ rk_spl_board_init(); + + preloader_console_init(); } #ifdef CONFIG_SPL_LOAD_FIT