From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Chou Date: Mon, 12 Oct 2015 08:07:23 +0800 Subject: [U-Boot] [PATCH v2] dm: implement a cfi flash uclass In-Reply-To: References: <1444289667-23775-1-git-send-email-thomas@wytron.com.tw> <1444548628-10119-1-git-send-email-thomas@wytron.com.tw> <561A23CE.6090900@wytron.com.tw> <561A54E2.9050803@wytron.com.tw> <561A643E.5000301@wytron.com.tw> Message-ID: <561AF9BB.4000206@wytron.com.tw> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Simon, On 10/12/2015 05:47 AM, Simon Glass wrote: > I don't see any problem with this in general, although the point with > CFI is that you are really implementing the uclass, as there will not > going to be any drivers (as I understand it). > > Looking at SPI flash, it does have an API (read, write, erase). Could > CFI use the same API? That might mean that we could unify the two and > share a uclass. > > One approach may be to use a name like UCLASS_FLASH, and add some > operations to it. Then we can say that we have a real uclass. The > operations could come in a separate flash perhaps. Great. It has been my first choice to have a unified flash uclass. Best regards, Thomas