From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Mon, 6 Apr 2020 13:03:11 +0200 Subject: [PATCH] ARM: zynq: Do not print message about boot device In-Reply-To: <2ac20583ad3d670cf7ea0d8eb5a4a0252fe6cfc0.1583403200.git.michal.simek@xilinx.com> References: <2ac20583ad3d670cf7ea0d8eb5a4a0252fe6cfc0.1583403200.git.michal.simek@xilinx.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de ?t 5. 3. 2020 v 11:13 odes?latel Michal Simek napsal: > > This information is shown already that's why there is no reason to print it > again via custom prints. > > U-Boot SPL 2020.01-03080-ga6214d033bd0 (Mar 05 2020 - 09:59:05 +0100) > mmc boot > Trying to boot from MMC1 > > or > > U-Boot SPL 2020.01-03080-ga6214d033bd0 (Mar 05 2020 - 10:49:46 +0100) > qspi boot > Trying to boot from SPI > > Signed-off-by: Michal Simek > --- > > arch/arm/mach-zynq/spl.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/arch/arm/mach-zynq/spl.c b/arch/arm/mach-zynq/spl.c > index e89e46c1038d..02a7dc985475 100644 > --- a/arch/arm/mach-zynq/spl.c > +++ b/arch/arm/mach-zynq/spl.c > @@ -45,7 +45,6 @@ u32 spl_boot_device(void) > switch ((zynq_slcr_get_boot_mode()) & ZYNQ_BM_MASK) { > #ifdef CONFIG_SPL_SPI_SUPPORT > case ZYNQ_BM_QSPI: > - puts("qspi boot\n"); > mode = BOOT_DEVICE_SPI; > break; > #endif > @@ -57,7 +56,6 @@ u32 spl_boot_device(void) > break; > #ifdef CONFIG_SPL_MMC_SUPPORT > case ZYNQ_BM_SD: > - puts("mmc boot\n"); > mode = BOOT_DEVICE_MMC1; > break; > #endif > -- > 2.25.1 > Applied. M -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs