[U-Boot] [PATCH v2] dm: implement a cfi flash uclass

Thomas Chou
2015-10-11T12:24:02Z

Hi Bin,

On 10/11/2015 05:10 PM, Bin Meng wrote:
> It's unlikely we are going to create another instance of cfi-flash
> driver, isn't it? Then it's just a single driver which does not make
> cfi-flash a "class". We can just update the cfi-flash driver to read
> its flash base address directly from device tree, without the need to
> go through driver model.

It is an on-going process to convert existing drivers to driver model.
The spi-flash has driver model now. How do you think it is unlikely that
cfi-flash should be converted to driver-model?

It is not just base address. There is device binding with compatible
ids. There will be resources allocation, too. Please don't limit your
imagination by my poor coding skill.

There are three good things to u-boot in recent years, the Kconfig,
device tree control and driver model. Together, they provide more
flexibility to processors on FPGA, like nios2. Here almost everything is
programmable, and it is difficult to hard code driver setup in the old way.

Huge thanks to all the contributors. Thank you too, Bin.

Best regards,
Thomas