From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrick Wildt <patrick@blueri.se>
Date: Sat, 30 May 2020 22:14:57 +0200
Subject: [PATCH] ARM: imx: hab: panic on authentication failure
In-Reply-To: <CAOMZO5AC+TJpBrtEPxPbDzVPsvOnJu7N8w-7TTDp_uoJ2_xKDA@mail.gmail.com>
References: <20200530182900.159874-1-marex@denx.de>
 <CAOMZO5AC+TJpBrtEPxPbDzVPsvOnJu7N8w-7TTDp_uoJ2_xKDA@mail.gmail.com>
Message-ID: <20200530201457.GA8838@ryzen.blueri.se>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Sat, May 30, 2020 at 03:31:29PM -0300, Fabio Estevam wrote:
> Hi Marek,
> 
> [Adding Breno]
> 
> On Sat, May 30, 2020 at 3:29 PM Marek Vasut <marex@denx.de> wrote:
> >
> > Instead of hang()ing the system and thus disallowing any automated
> > recovery possibility from a HAB authentication failure, panic() .
> > The panic() function can be configured to hang() the system after
> > printing an error message, however the default is to reset the
> > system instead.
> >
> > This allows redundant boot to work correctly. In case the primary
> > or secondary image cannot be authenticated, the system reboots and
> > bootrom can try to start the other one.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: NXP i.MX U-Boot Team <uboot-imx@nxp.com>
> > Cc: Peng Fan <peng.fan@nxp.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> 
> This is a better behavior indeed:
> 
> Reviewed-by: Fabio Estevam <festevam@gmail.com>

What about this?  Have you ignored this patch for a reason? :/

https://marc.info/?l=u-boot&m=159069441005730&w=2