From patchwork Sat Mar 31 17:49:58 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bryan O'Donoghue X-Patchwork-Id: 893835 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=lists.denx.de (client-ip=81.169.180.215; helo=lists.denx.de; envelope-from=u-boot-bounces@lists.denx.de; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="RR1pKYzm"; dkim-atps=neutral Received: from lists.denx.de (dione.denx.de [81.169.180.215]) by ozlabs.org (Postfix) with ESMTP id 40D5c95mpzz9s1S for ; Sun, 1 Apr 2018 03:50:16 +1000 (AEST) Received: by lists.denx.de (Postfix, from userid 105) id C7BF0C21E3B; Sat, 31 Mar 2018 17:50:06 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lists.denx.de X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.0 Received: from lists.denx.de (localhost [IPv6:::1]) by lists.denx.de (Postfix) with ESMTP id 76F43C21DAF; Sat, 31 Mar 2018 17:50:04 +0000 (UTC) Received: by lists.denx.de (Postfix, from userid 105) id B856FC21DB6; Sat, 31 Mar 2018 17:50:03 +0000 (UTC) Received: from mail-wm0-f66.google.com (mail-wm0-f66.google.com [74.125.82.66]) by lists.denx.de (Postfix) with ESMTPS id 5E2E5C21D9A for ; Sat, 31 Mar 2018 17:50:03 +0000 (UTC) Received: by mail-wm0-f66.google.com with SMTP id b127so18838374wmf.5 for ; Sat, 31 Mar 2018 10:50:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=POsspidBy8+BjRv+rboXKnWT/ZnRjPgPVYTH7hV0B/U=; b=RR1pKYzm7dG/5gv+w3kq3uU+f5XIjyIxVL/s/s1YNU0isqaWfSYgyC2FfazNBhBAIm MFHkSjBwBI7tJ4P2S+pLKu2Htk3eecYD7sgFnoDmJwRrrx9XYfd43F2kwsmqc/oHmwlY OspHLqSlWYrZjZVPthd5kMSZ3dCb9D2MR2bc8= 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; bh=POsspidBy8+BjRv+rboXKnWT/ZnRjPgPVYTH7hV0B/U=; b=HVgsQydZyrrUDCXIkvV6dRubzhPLmKqXmRyioa+9AgvLaNGbQiWamUQQeruwdjmuoP 7rtJLgDoDBsFEgF5pewXJkpBUP2RReRs0fnFHYGXMBZjKBiTp87hMsjdFgeLBGCV5CaH WgCiNcNvhUaUKpobUwVXDvvx4yBEbEmfKDUn42kj3X4cDRzQWwubDceFqXeVRwIlc1zr m3LXHvo2mV7hf3I6f9XvukxTTm0NtyUbTZ9G5p38nQogOkxU/hhAb5vrd7QuhBKIppgC fRWMEKs7CoWLVawVKDkB/YbEI0LQt2i++s8XsFz/8qlg/ec/UghpyPp7Da+PlV6CrJOv IhPg== X-Gm-Message-State: AElRT7HeU4D7O42I6PAN9rqM1AHbrQBY+nXmxkX0ZLfzoRHeGSbsPCUx lLBHFKz9KcZbv0s4qZ9fiuiSN/19A+A= X-Google-Smtp-Source: AIpwx49O4WwL66s256JfDXScc//5aRAAfI+H1eGpOXujz5qB7/9T9uOx1JuCWJW9aDeqCMwIatilDQ== X-Received: by 10.80.163.239 with SMTP id t44mr7084245edb.56.1522518602718; Sat, 31 Mar 2018 10:50:02 -0700 (PDT) Received: from localhost.localdomain ([109.255.42.2]) by smtp.gmail.com with ESMTPSA id i61sm6462800edc.53.2018.03.31.10.50.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 31 Mar 2018 10:50:01 -0700 (PDT) From: Bryan O'Donoghue To: u-boot@lists.denx.de, sbabic@denx.de, fabio.estevam@nxp.com Date: Sat, 31 Mar 2018 18:49:58 +0100 Message-Id: <1522518600-16791-1-git-send-email-bryan.odonoghue@linaro.org> X-Mailer: git-send-email 2.7.4 Cc: breno.lima@nxp.com Subject: [U-Boot] [PATCH v2 0/2] WaRP7 unify secure and non-secure defconfigs X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.18 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" Maintaining a secure and non-secure defconfig is a PITA. Having discussed an observed bug with the non-secure boot-path with Fabio and undertaken to ensure both upstream and NXP BSP kernels would work - this patchset does two things. 1. Switches on CONFIG_ARMV7_BOOT_SEC_DEFAULT for warp7_defconfig 2. Removes warp7_secure_defconfig in its entirety I have an upcoming set of patches that uses the secure defconfig which I've already verified can simply be merged into mainline WaRP7 as-is so, in this context there appears to be no justification for keeping separate configuration files. Fix the bug and zap the fat ! Bryan O'Donoghue (2): warp7: defconfig: Fix CAAM on boot with tip-of-tree warp7: secure_defconfig: Remove secure_defconfig configs/warp7_defconfig | 1 + configs/warp7_secure_defconfig | 42 ------------------------------------------ 2 files changed, 1 insertion(+), 42 deletions(-) delete mode 100644 configs/warp7_secure_defconfig