From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jagan Teki <jteki@openedev.com>
Date: Tue, 3 Nov 2015 20:25:58 +0530
Subject: [U-Boot] [PATCH v4 1/3] dm: implement a MTD uclass
In-Reply-To: <5638C985.9060308@wytron.com.tw>
References: <1444289667-23775-1-git-send-email-thomas@wytron.com.tw>
 <1446556146-9876-1-git-send-email-thomas@wytron.com.tw>
 <CAD6G_RQMD+6Km5dJrpuE2JO6kefZmQY6P4XetQ-1kEL62u1xZg@mail.gmail.com>
 <5638C985.9060308@wytron.com.tw>
Message-ID: <CAD6G_RSXgXfhPBoeZNtmiLU5QR1zdhPdBjMtVJUZU3=+sVjdcg@mail.gmail.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 3 November 2015 at 20:19, Thomas Chou <thomas@wytron.com.tw> wrote:
> Hi Jagan,
>
> On 2015?11?03? 22:41, Jagan Teki wrote:
>>
>> Hi Thomas,
>>
>> On 3 November 2015 at 18:39, Thomas Chou <thomas@wytron.com.tw> wrote:
>>>
>>> Implement a Memory Technology Device (MTD) uclass. It should
>>> include most flash drivers in the future. Though no uclass ops
>>> are defined yet, the MTD ops could be used.
>>>
>>> The NAND flash driver is based on MTD. The CFI flash and SPI
>>> flash support MTD, too. It should make sense to convert them
>>> to MTD uclass.
>>
>>
>> Why does MTD require driver model? Should drivers like nand, cfi or
>> etc register mtd core should need to move on dm?
>
>
> The driver model combined with device tree control of u-boot offers dynamic
> binding of drivers and devices. It is expected that all drivers will be
> converted to driver model, including nand, cfi and spi flash.

So, mtd_info ops like _erase, _write and _read will also change or
something like this

struct dm_mtd_info {
    struct mtd_info *info;
    struct udevice *dev;
};


thanks!
-- 
Jagan | openedev.