Hi Ye Li,
On Wed, Jun 27, 2018 at 3:48 AM, Ye Li ye.li@nxp.com wrote:
To support DM QSPI driver
- Add spi0 and spi1 alias for qspi1 and qspi2.
- Modify n25q256a@0 and n25q256a@1 compatible string to "spi-flash"
- Enable DM SPI/QSPI relavent configurations
- Remove iomux settings of qspi2 in board codes which is not needed for DM driver.
- Add sf default settings. So running "sf probe" can detect the flash
Signed-off-by: Ye Li ye.li@nxp.com
arch/arm/dts/imx6sx-sdb.dts | 4 ++-- arch/arm/dts/imx6sx.dtsi | 12 +++++++----- board/freescale/mx6sxsabresd/mx6sxsabresd.c | 25 ------------------------- configs/mx6sxsabresd_defconfig | 7 +++++++ include/configs/mx6sxsabresd.h | 4 ++++ 5 files changed, 20 insertions(+), 32 deletions(-)
diff --git a/arch/arm/dts/imx6sx-sdb.dts b/arch/arm/dts/imx6sx-sdb.dts index 6dd9beb..a04b00d 100644 --- a/arch/arm/dts/imx6sx-sdb.dts +++ b/arch/arm/dts/imx6sx-sdb.dts @@ -115,7 +115,7 @@ flash0: n25q256a@0 { #address-cells = <1>; #size-cells = <1>;
compatible = "micron,n25q256a", "jedec,spi-nor";
compatible = "spi-flash";
I don't see "spi-flash" compatible documented in the kernel bindings.
Please clarify why we are deviating from Linux here.
Thanks