From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Wed, 10 Jun 2015 08:55:44 +0200
Subject: [U-Boot] arm: imx: Kernel not booting when environment is in
 QSPI
In-Reply-To: <CAO8h3eFqaEQoWePOxX5yhLnGWPiddvkW4d6GOEvk_b=DDa2qHQ@mail.gmail.com>
References: <CAO8h3eFcqj-mPMv4Jf+ZSozLmCE8njmDgHyVcrWjyoLtrZBLwA@mail.gmail.com>
 <CAOMZO5Bm00m0VSB+iQAkfy6VkgK_xRwgdDRdEGHiq=+kJqtA-A@mail.gmail.com>
 <55770536.1050706@freescale.com> <20150610014519.GA5691@shlinux2>
 <CAO8h3eFqaEQoWePOxX5yhLnGWPiddvkW4d6GOEvk_b=DDa2qHQ@mail.gmail.com>
Message-ID: <5577DF70.3080904@denx.de>
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 Matthias,

On 10.06.2015 08:19, Matthias Wei?er wrote:
> With some wild guessing I found out that it must be an interrupt
> issue. If I clear FR (offset 0x160) in the QSPI module using u-boot
> command Linux boots successfully. So it seams that u-boot should clear
> the interrupt flag of the QSPI module after it was used.

Or the Linux driver should take care of clearing this before enabling 
the interrupts instead. In general Linux should make no assumption of 
the previously used/configured devices.

Thanks,
Stefan