Hi Tom, As I know, the CONFIG_BLK is not supported on some platforms' defconfig (# CONFIG_BLK is not set), such as the fsl-qoriq platform. I find when 'CONFIG_BLK=y', then 'fsl-esdhc-mmc' device can't work normally.
So, in order to make sure the NVMe driver is available on all the platforms, I support for both with and without BLK. Thank you! Best regards, Zhikang Zhang -----Original Message----- From: Tom Rini [mailto:[email protected]] Sent: Tuesday, April 11, 2017 5:49 AM To: Z.K. Zhang <[email protected]> Cc: york sun <[email protected]>; [email protected]; Wenbin Song <[email protected]> Subject: Re: [U-Boot] [RFC, 1/2] NVMe: add NVMe driver support On Thu, Apr 06, 2017 at 04:40:33PM +0800, Zhikang Zhang wrote: > Add Support of devices that follow the NVM Express standard > > basic functions: > nvme init/scan > nvme info - show the basic information of device > nvme Read/Write > > driver model: > Use block device(CONFIG_BLK)'s structure to support nvme's DM. > Use UCLASS_PCI as a parent uclass. > > The driver code heavily copy from the NVMe driver code in Linux Kernel. > > Signed-off-by: Zhikang Zhang <[email protected]> > Signed-off-by: Wenbin Song <[email protected]> Why support for both with and without BLK? Thanks! -- Tom _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
