From mboxrd@z Thu Jan  1 00:00:00 1970
From: York Sun <york.sun@nxp.com>
Date: Mon, 6 Jun 2016 11:40:39 -0700
Subject: [U-Boot] [PATCH v3 00/11] armv8: ls2080aqds: Enable QSPI boot
	support
In-Reply-To: <1465209816-10087-1-git-send-email-yao.yuan@freescale.com>
References: <1465209816-10087-1-git-send-email-yao.yuan@freescale.com>
Message-ID: <5755C3A7.5010505@nxp.com>
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 06/06/2016 03:53 AM, Yuan Yao wrote:
> From: Yuan Yao <yao.yuan@nxp.com>
> 
> This patch adds QSPI boot support for LS2080AQDS board.
> The QSPI boot image need to be programmed into the QSPI flash
> first. Then we can switch to booting from QSPI memory space.
> 
> Yuan Yao (11):
>   armv8: ls2080aqds: Select QSPI CLK div via SCFG
>   configs: ls2080a_common: Remove duplicate NOR configs
>   configs: ls2080aqds: disable IFC NOR & QIXIS when QSPI enable
>   configs: ls2080aqds: Enable QSPI flash support
>   dm: dts: ls2080aqds: Add QSPI dts node
>   armv8: ls2080aqds: Config QSPI pin mux via FPGA in NAND boot
>   configs: ls2080a: Increase load image len in NAND boot
>   ls2080aqds_nand_defconfig: Enable QSPI & its dependence
>   armv8: ls2080aqds: Enable QSPI boot support
> 	Rebase in v3.
>   drivers: i2c: mxc: Add early init
> 	New add in v3.
>   board: freescale: ls2080aqds: Enable early I2C access for QSPI boot
>   	New add in v3.

Yuan,

Do you think you can reorder these patches so that early i2c init can be in
front of disabling IFC? Then you don't have to use fixed clk at all. I am
thinking if we run git bisect and this set could break QSPI boot if sys clk is
other than 100MHz.

York