MTD NAND Driver Programming Interface | ||
---|---|---|
<<< Previous | Next >>> |
The function and structure docs are autogenerated. Each function and struct member has a short description which is marked with an [XXX] identifier. The following chapters explain the meaning of those identifiers.
The functions are marked with [XXX] identifiers in the short comment. The identifiers explain the usage and scope of the functions. Following identifiers are used:
[MTD Interface]
These functions provide the interface to the MTD kernel API. They are not replacable and provide functionality which is complete hardware independent.
[NAND Interface]
These functions are exported and provide the interface to the NAND kernel API.
[GENERIC]
Generic functions are not replacable and provide functionality which is complete hardware independent.
[DEFAULT]
Default functions provide hardware related functionality which is suitable for most of the implementations. These functions can be replaced by the board driver if neccecary. Those functions are called via pointers in the NAND chip description structure. The board driver can set the functions which should be replaced by board dependend functions before calling nand_scan(). If the function pointer is NULL on entry to nand_scan() then the pointer is set to the default function which is suitable for the detected chip type.
<<< Previous | Home | Next >>> |
Known Bugs And Assumptions | Struct member identifiers [XXX] |