From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peng Fan <b51431@freescale.com>
Date: Tue, 15 Sep 2015 08:31:03 +0800
Subject: [U-Boot] [PATCH 3/4] imx: mx7dsabresd: drop code for
 CONFIG_CMD_BMODE
In-Reply-To: <CAOMZO5Dhxr-R1i+JHJeeH3rvtxHv7yBm8pHbZQksf+hoNe0ADA@mail.gmail.com>
References: <1442221736-16377-1-git-send-email-Peng.Fan@freescale.com>
 <1442221736-16377-3-git-send-email-Peng.Fan@freescale.com>
 <CAOMZO5Dhxr-R1i+JHJeeH3rvtxHv7yBm8pHbZQksf+hoNe0ADA@mail.gmail.com>
Message-ID: <20150915003100.GA5982@shlinux2>
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

Hi Fabio,
On Mon, Sep 14, 2015 at 03:09:24PM -0300, Fabio Estevam wrote:
>Hi Peng,
>
>On Mon, Sep 14, 2015 at 6:08 AM, Peng Fan <Peng.Fan@freescale.com> wrote:
>> Since i.MX7D does not support warm reset, so boot_mode_apply
>> actually will not work. Also we use outer pmic reset and drop
>> internal reset signal, so drop boot mode code for 7dsabresd board.
>
>Booting via bmode is working fine here.

If boot from sd1, bmode sd1 work well. If boot from qspi1, bmode qspi work well.
This is expected. If boot from qspi, but we use 'bmode sd1', this will not work.
The reason that introduce bmode command is to boot from different media, but
now we use wdog signal to trigger pmic reset, which means the SoC will be
powered off and powered on. There is no reason to keep bmode. This patch
needs my previous wdog patch set.

Regards,
Peng.
>
>Regards,
>
>Fabio Estevam

--