轉自:http://blog.csdn.net/lwj103862095/article/details/21545791
?
版權聲明:本文為博主原創文章,未經博主允許不得轉載。
MTD,Memory Technology Device即內存技術設備,在Linux內核中,引入MTD層為NOR FLASH和NAND FLASH設備提供統一接口。MTD將文件系統與底層FLASH存儲器進行了隔離。
如上圖所示,MTD設備通常可分為四層,從上到下依次是:設備節點、MTD設備層、MTD原始設備層、硬件驅動層。
Flash硬件驅動層:Flash硬件驅動層負責對Flash硬件的讀、寫和擦除操作。MTD設備的Nand Flash芯片的驅動則drivers/mtd/nand/子目錄下,Nor Flash芯片驅動位于drivers/mtd/chips/子目錄下。
MTD原始設備層:用于描述MTD原始設備的數據結構是mtd_info,它定義了大量的關于MTD的數據和操作函數。其中mtdcore.c: ?MTD原始設備接口相關實現,mtdpart.c?: ?MTD分區接口相關實現。
MTD設備層:基于MTD原始設備,linux系統可以定義出MTD的塊設備(主設備號31)和字符設備(設備號90)。其中mtdchar.c?: ?MTD字符設備接口相關實現,mtdblock.c?: MTD塊設備接口相關實現。
設備節點:通過mknod在/dev子目錄下建立MTD塊設備節點(主設備號為31)和MTD字符設備節點(主設備號為90)。通過訪問此設備節點即可訪問MTD字符設備和塊設備?
MTD數據結構:
1.Linux內核使用mtd_info結構體表示MTD原始設備,這其中定義了大量關于MTD的數據和操作函數(后面將會看到),所有的mtd_info結構體存放在mtd_table結構體數據里。在/drivers/mtd/mtdcore.c里:
?
[cpp]?view plaincopy? print?
struct?mtd_info?*mtd_table[MAX_MTD_DEVICES];?? 2.Linux內核使用mtd_part結構體表示分區,其中mtd_info結構體成員用于描述該分區,大部分成員由其主分區mtd_part->master決定,各種函數也指向主分區的相應函數。 ?
?
[cpp]?view plaincopy? print?
struct?mtd_part?{??????struct?mtd_info?mtd;??????????????struct?mtd_info?*master;??????????uint64_t?offset;??????????????????int?index;????????????????????????struct?list_head?list;????????????int?registered;??};?? mtd_info結構體主要成員,為了便于觀察,將重要的數據放在前面,不大重要的編寫在后面。 ?
?
[cpp]?view plaincopy? print?
struct?mtd_info?{??????u_char?type;???????????????uint32_t?flags;????????????uint64_t?size;?????????????uint32_t?erasesize;????????uint32_t?writesize;????????uint32_t?oobsize;??????????uint32_t?oobavail;?????????unsigned?int?erasesize_shift;?????????unsigned?int?writesize_shift;?????????unsigned?int?erasesize_mask;??????????unsigned?int?writesize_mask;??????????const?char?*name;?????????????????????int?index;????????????????????????????int?numeraseregions;??????????????????struct?mtd_erase_region_info?*eraseregions;?????????????void?*priv;???????????struct?module?*owner;?????????????????????int?(*erase)?(struct?mtd_info?*mtd,?struct?erase_info?*instr);??????????????int?(*read)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*write)?(struct?mtd_info?*mtd,?loff_t?to,?size_t?len,?size_t?*retlen,?const?u_char?*buf);??????????????int?(*read_oob)?(struct?mtd_info?*mtd,?loff_t?from,???????????????struct?mtd_oob_ops?*ops);??????int?(*write_oob)?(struct?mtd_info?*mtd,?loff_t?to,???????????????struct?mtd_oob_ops?*ops);????????int?(*get_fact_prot_info)?(struct?mtd_info?*mtd,?struct?otp_info?*buf,?size_t?len);??????int?(*read_fact_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*get_user_prot_info)?(struct?mtd_info?*mtd,?struct?otp_info?*buf,?size_t?len);??????int?(*read_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*write_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*lock_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len);????????int?(*writev)?(struct?mtd_info?*mtd,?const?struct?kvec?*vecs,?unsigned?long?count,?loff_t?to,?size_t?*retlen);??????int?(*panic_write)?(struct?mtd_info?*mtd,?loff_t?to,?size_t?len,?size_t?*retlen,?const?u_char?*buf);????????????void?(*sync)?(struct?mtd_info?*mtd);??????????????int?(*lock)?(struct?mtd_info?*mtd,?loff_t?ofs,?uint64_t?len);??????int?(*unlock)?(struct?mtd_info?*mtd,?loff_t?ofs,?uint64_t?len);??????????????int?(*suspend)?(struct?mtd_info?*mtd);??????void?(*resume)?(struct?mtd_info?*mtd);??????????????int?(*block_isbad)?(struct?mtd_info?*mtd,?loff_t?ofs);??????int?(*block_markbad)?(struct?mtd_info?*mtd,?loff_t?ofs);????????void?(*unpoint)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len);??????unsigned?long?(*get_unmapped_area)?(struct?mtd_info?*mtd,??????????????????????????unsigned?long?len,??????????????????????????unsigned?long?offset,??????????????????????????unsigned?long?flags);??????struct?backing_dev_info?*backing_dev_info;??????struct?notifier_block?reboot_notifier;????????????????struct?mtd_ecc_stats?ecc_stats;??????int?subpage_sft;??????struct?device?dev;??????int?usecount;??????int?(*get_device)?(struct?mtd_info?*mtd);??????void?(*put_device)?(struct?mtd_info?*mtd);??};?? mtd_info結構體中的read()、write()、read_oob()、write_oob()、erase()是MTD設備驅動要實現的主要函數,幸運的是Linux大牛已經幫我們實現了一套適合大部分FLASH設備的mtd_info成員函數。 ?
如果MTD設備只有一個分區,那么使用下面兩個函數注冊和注銷MTD設備。
?
[cpp]?view plaincopy? print?
int?add_mtd_device(struct?mtd_info?*mtd)??int?del_mtd_device?(struct?mtd_info?*mtd)?? 如果MTD設備存在其他分區,那么使用下面兩個函數注冊和注銷MTD設備。 [cpp]?view plaincopy? print?
int?add_mtd_partitions(struct?mtd_info?*master,const?struct?mtd_partition?*parts,int?nbparts)??int?del_mtd_partitions(struct?mtd_info?*master)?? 其中mtd_partition結構體表示分區的信息 ?
?
[cpp]?view plaincopy? print?
struct?mtd_partition?{??????char?*name;???????????????????uint64_t?size;????????????????uint64_t?offset;??????????????uint32_t?mask_flags;??????????struct?nand_ecclayout?*ecclayout;?????????struct?mtd_info?**mtdp;???????};??其中nand_ecclayout結構體:??struct?nand_ecclayout?{??????__u32?eccbytes;???????????__u32?eccpos[64];?????????__u32?oobavail;?????????????????struct?nand_oobfree?oobfree[MTD_MAX_OOBFREE_ENTRIES];??};?? 關于nand_ecclayout結構體實例,更多可參考drivers/mtd/nand/nand_base.c下的nand_oob_8、nand_oob_16、nand_oob_64實例。MTD設備層: ?
mtd字符設備接口:
/drivers/mtd/mtdchar.c文件實現了MTD字符設備接口,通過它,可以直接訪問Flash設備,與前面的字符驅動一樣,通過file_operations結構體里面的open()、read()、write()、ioctl()可以讀寫Flash,通過一系列IOCTL 命令可以獲取Flash 設備信息、擦除Flash、讀寫NAND 的OOB、獲取OOB layout 及檢查NAND 壞塊等(MEMGETINFO、MEMERASE、MEMREADOOB、MEMWRITEOOB、MEMGETBADBLOCK IOCRL)?
mtd塊設備接口:
/drivers/mtd/mtdblock.c文件實現了MTD塊設備接口,主要原理是將Flash的erase block 中的數據在內存中建立映射,然后對其進行修改,最后擦除Flash 上的block,將內存中的映射塊寫入Flash 塊。整個過程被稱為read/modify/erase/rewrite 周期。?但是,這樣做是不安全的,當下列操作序列發生時,read/modify/erase/poweroff,就會丟失這個block 塊的數據。
MTD硬件驅動層:
Linux內核再MTD層下實現了通用的NAND驅動(/driver/mtd/nand/nand_base.c),因此芯片級的NAND驅動不再需要實現mtd_info結構體中的read()、write()、read_oob()、write_oob()等成員函數。
MTD使用nand_chip來表示一個NAND FLASH芯片, 該結構體包含了關于Nand Flash的地址信息,讀寫方法,ECC模式,硬件控制等一系列底層機制。
?
[cpp]?view plaincopy? print?
struct?nand_chip?{??????void??__iomem???*IO_ADDR_R;???????????void??__iomem???*IO_ADDR_W;???????????????????uint8_t?(*read_byte)(struct?mtd_info?*mtd);?????????????????u16?????(*read_word)(struct?mtd_info?*mtd);?????????????????void????(*write_buf)(struct?mtd_info?*mtd,?const?uint8_t?*buf,?int?len);????????????????void????(*read_buf)(struct?mtd_info?*mtd,?uint8_t?*buf,?int?len);????????????int?????(*verify_buf)(struct?mtd_info?*mtd,?const?uint8_t?*buf,?int?len);????????????void????(*select_chip)(struct?mtd_info?*mtd,?int?chip);????????????int?????(*block_bad)(struct?mtd_info?*mtd,?loff_t?ofs,?int?getchip);????????????int?????(*block_markbad)(struct?mtd_info?*mtd,?loff_t?ofs);????????????void????(*cmd_ctrl)(struct?mtd_info?*mtd,?int?dat,unsigned?int?ctrl);????????????int?????(*dev_ready)(struct?mtd_info?*mtd);????????????void????(*cmdfunc)(struct?mtd_info?*mtd,?unsigned?command,?int?column,?int?page_addr);??????int?????(*waitfunc)(struct?mtd_info?*mtd,?struct?nand_chip?*this);????????????void????(*erase_cmd)(struct?mtd_info?*mtd,?int?page);????????????int?????(*scan_bbt)(struct?mtd_info?*mtd);??????int?????(*errstat)(struct?mtd_info?*mtd,?struct?nand_chip?*this,?int?state,?int?status,?int?page);????????????int?????(*write_page)(struct?mtd_info?*mtd,?struct?nand_chip?*chip,????????????????????????const?uint8_t?*buf,?int?page,?int?cached,?int?raw);????????int?????chip_delay;?????????????????????unsigned?int????options;????????????????????int??????page_shift;??????????????int??????phys_erase_shift;??????????????int??????bbt_erase_shift;????????????int??????chip_shift;????????????int??????numchips;????????????uint64_t?chipsize;??????int??????pagemask;??????int??????pagebuf;??????int??????subpagesize;??????uint8_t??cellinfo;??????int??????badblockpos;??????nand_state_t????state;??????uint8_t?????*oob_poi;??????struct?nand_hw_control??*controller;??????struct?nand_ecclayout???*ecclayout;?????????????struct?nand_ecc_ctrl?ecc;?????????struct?nand_buffers?*buffers;??????struct?nand_hw_control?hwcontrol;??????struct?mtd_oob_ops?ops;??????uint8_t?????*bbt;??????struct?nand_bbt_descr???*bbt_td;??????struct?nand_bbt_descr???*bbt_md;??????struct?nand_bbt_descr???*badblock_pattern;??????void????????*priv;??};?? 最后,我們來用圖表的形式來總結一下,MTD設備層、MTD原始設備層、FLASH硬件驅動層之間的聯系。 ?
?
?
?
版權聲明:本文為博主原創文章,未經博主允許不得轉載。
MTD,Memory Technology Device即內存技術設備,在Linux內核中,引入MTD層為NOR FLASH和NAND FLASH設備提供統一接口。MTD將文件系統與底層FLASH存儲器進行了隔離。
如上圖所示,MTD設備通常可分為四層,從上到下依次是:設備節點、MTD設備層、MTD原始設備層、硬件驅動層。
Flash硬件驅動層:Flash硬件驅動層負責對Flash硬件的讀、寫和擦除操作。MTD設備的Nand Flash芯片的驅動則drivers/mtd/nand/子目錄下,Nor Flash芯片驅動位于drivers/mtd/chips/子目錄下。
MTD原始設備層:用于描述MTD原始設備的數據結構是mtd_info,它定義了大量的關于MTD的數據和操作函數。其中mtdcore.c: ?MTD原始設備接口相關實現,mtdpart.c?: ?MTD分區接口相關實現。
MTD設備層:基于MTD原始設備,linux系統可以定義出MTD的塊設備(主設備號31)和字符設備(設備號90)。其中mtdchar.c?: ?MTD字符設備接口相關實現,mtdblock.c?: MTD塊設備接口相關實現。
設備節點:通過mknod在/dev子目錄下建立MTD塊設備節點(主設備號為31)和MTD字符設備節點(主設備號為90)。通過訪問此設備節點即可訪問MTD字符設備和塊設備?
MTD數據結構:
1.Linux內核使用mtd_info結構體表示MTD原始設備,這其中定義了大量關于MTD的數據和操作函數(后面將會看到),所有的mtd_info結構體存放在mtd_table結構體數據里。在/drivers/mtd/mtdcore.c里:
?
[cpp]?view plaincopy? print?
struct?mtd_info?*mtd_table[MAX_MTD_DEVICES];?? 2.Linux內核使用mtd_part結構體表示分區,其中mtd_info結構體成員用于描述該分區,大部分成員由其主分區mtd_part->master決定,各種函數也指向主分區的相應函數。 ?
?
[cpp]?view plaincopy? print?
struct?mtd_part?{??????struct?mtd_info?mtd;??????????????struct?mtd_info?*master;??????????uint64_t?offset;??????????????????int?index;????????????????????????struct?list_head?list;????????????int?registered;??};?? mtd_info結構體主要成員,為了便于觀察,將重要的數據放在前面,不大重要的編寫在后面。 ?
?
[cpp]?view plaincopy? print?
struct?mtd_info?{??????u_char?type;???????????????uint32_t?flags;????????????uint64_t?size;?????????????uint32_t?erasesize;????????uint32_t?writesize;????????uint32_t?oobsize;??????????uint32_t?oobavail;?????????unsigned?int?erasesize_shift;?????????unsigned?int?writesize_shift;?????????unsigned?int?erasesize_mask;??????????unsigned?int?writesize_mask;??????????const?char?*name;?????????????????????int?index;????????????????????????????int?numeraseregions;??????????????????struct?mtd_erase_region_info?*eraseregions;?????????????void?*priv;???????????struct?module?*owner;?????????????????????int?(*erase)?(struct?mtd_info?*mtd,?struct?erase_info?*instr);??????????????int?(*read)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*write)?(struct?mtd_info?*mtd,?loff_t?to,?size_t?len,?size_t?*retlen,?const?u_char?*buf);??????????????int?(*read_oob)?(struct?mtd_info?*mtd,?loff_t?from,???????????????struct?mtd_oob_ops?*ops);??????int?(*write_oob)?(struct?mtd_info?*mtd,?loff_t?to,???????????????struct?mtd_oob_ops?*ops);????????int?(*get_fact_prot_info)?(struct?mtd_info?*mtd,?struct?otp_info?*buf,?size_t?len);??????int?(*read_fact_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*get_user_prot_info)?(struct?mtd_info?*mtd,?struct?otp_info?*buf,?size_t?len);??????int?(*read_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*write_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len,?size_t?*retlen,?u_char?*buf);??????int?(*lock_user_prot_reg)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len);????????int?(*writev)?(struct?mtd_info?*mtd,?const?struct?kvec?*vecs,?unsigned?long?count,?loff_t?to,?size_t?*retlen);??????int?(*panic_write)?(struct?mtd_info?*mtd,?loff_t?to,?size_t?len,?size_t?*retlen,?const?u_char?*buf);????????????void?(*sync)?(struct?mtd_info?*mtd);??????????????int?(*lock)?(struct?mtd_info?*mtd,?loff_t?ofs,?uint64_t?len);??????int?(*unlock)?(struct?mtd_info?*mtd,?loff_t?ofs,?uint64_t?len);??????????????int?(*suspend)?(struct?mtd_info?*mtd);??????void?(*resume)?(struct?mtd_info?*mtd);??????????????int?(*block_isbad)?(struct?mtd_info?*mtd,?loff_t?ofs);??????int?(*block_markbad)?(struct?mtd_info?*mtd,?loff_t?ofs);????????void?(*unpoint)?(struct?mtd_info?*mtd,?loff_t?from,?size_t?len);??????unsigned?long?(*get_unmapped_area)?(struct?mtd_info?*mtd,??????????????????????????unsigned?long?len,??????????????????????????unsigned?long?offset,??????????????????????????unsigned?long?flags);??????struct?backing_dev_info?*backing_dev_info;??????struct?notifier_block?reboot_notifier;????????????????struct?mtd_ecc_stats?ecc_stats;??????int?subpage_sft;??????struct?device?dev;??????int?usecount;??????int?(*get_device)?(struct?mtd_info?*mtd);??????void?(*put_device)?(struct?mtd_info?*mtd);??};?? mtd_info結構體中的read()、write()、read_oob()、write_oob()、erase()是MTD設備驅動要實現的主要函數,幸運的是Linux大牛已經幫我們實現了一套適合大部分FLASH設備的mtd_info成員函數。 ?
如果MTD設備只有一個分區,那么使用下面兩個函數注冊和注銷MTD設備。
?
[cpp]?view plaincopy? print?
int?add_mtd_device(struct?mtd_info?*mtd)??int?del_mtd_device?(struct?mtd_info?*mtd)?? 如果MTD設備存在其他分區,那么使用下面兩個函數注冊和注銷MTD設備。 [cpp]?view plaincopy? print?
int?add_mtd_partitions(struct?mtd_info?*master,const?struct?mtd_partition?*parts,int?nbparts)??int?del_mtd_partitions(struct?mtd_info?*master)?? 其中mtd_partition結構體表示分區的信息 ?
?
[cpp]?view plaincopy? print?
struct?mtd_partition?{??????char?*name;???????????????????uint64_t?size;????????????????uint64_t?offset;??????????????uint32_t?mask_flags;??????????struct?nand_ecclayout?*ecclayout;?????????struct?mtd_info?**mtdp;???????};??其中nand_ecclayout結構體:??struct?nand_ecclayout?{??????__u32?eccbytes;???????????__u32?eccpos[64];?????????__u32?oobavail;?????????????????struct?nand_oobfree?oobfree[MTD_MAX_OOBFREE_ENTRIES];??};?? 關于nand_ecclayout結構體實例,更多可參考drivers/mtd/nand/nand_base.c下的nand_oob_8、nand_oob_16、nand_oob_64實例。MTD設備層: ?
mtd字符設備接口:
/drivers/mtd/mtdchar.c文件實現了MTD字符設備接口,通過它,可以直接訪問Flash設備,與前面的字符驅動一樣,通過file_operations結構體里面的open()、read()、write()、ioctl()可以讀寫Flash,通過一系列IOCTL 命令可以獲取Flash 設備信息、擦除Flash、讀寫NAND 的OOB、獲取OOB layout 及檢查NAND 壞塊等(MEMGETINFO、MEMERASE、MEMREADOOB、MEMWRITEOOB、MEMGETBADBLOCK IOCRL)?
mtd塊設備接口:
/drivers/mtd/mtdblock.c文件實現了MTD塊設備接口,主要原理是將Flash的erase block 中的數據在內存中建立映射,然后對其進行修改,最后擦除Flash 上的block,將內存中的映射塊寫入Flash 塊。整個過程被稱為read/modify/erase/rewrite 周期。?但是,這樣做是不安全的,當下列操作序列發生時,read/modify/erase/poweroff,就會丟失這個block 塊的數據。
MTD硬件驅動層:
Linux內核再MTD層下實現了通用的NAND驅動(/driver/mtd/nand/nand_base.c),因此芯片級的NAND驅動不再需要實現mtd_info結構體中的read()、write()、read_oob()、write_oob()等成員函數。
MTD使用nand_chip來表示一個NAND FLASH芯片, 該結構體包含了關于Nand Flash的地址信息,讀寫方法,ECC模式,硬件控制等一系列底層機制。
?
[cpp]?view plaincopy? print?
struct?nand_chip?{??????void??__iomem???*IO_ADDR_R;???????????void??__iomem???*IO_ADDR_W;???????????????????uint8_t?(*read_byte)(struct?mtd_info?*mtd);?????????????????u16?????(*read_word)(struct?mtd_info?*mtd);?????????????????void????(*write_buf)(struct?mtd_info?*mtd,?const?uint8_t?*buf,?int?len);????????????????void????(*read_buf)(struct?mtd_info?*mtd,?uint8_t?*buf,?int?len);????????????int?????(*verify_buf)(struct?mtd_info?*mtd,?const?uint8_t?*buf,?int?len);????????????void????(*select_chip)(struct?mtd_info?*mtd,?int?chip);????????????int?????(*block_bad)(struct?mtd_info?*mtd,?loff_t?ofs,?int?getchip);????????????int?????(*block_markbad)(struct?mtd_info?*mtd,?loff_t?ofs);????????????void????(*cmd_ctrl)(struct?mtd_info?*mtd,?int?dat,unsigned?int?ctrl);????????????int?????(*dev_ready)(struct?mtd_info?*mtd);????????????void????(*cmdfunc)(struct?mtd_info?*mtd,?unsigned?command,?int?column,?int?page_addr);??????int?????(*waitfunc)(struct?mtd_info?*mtd,?struct?nand_chip?*this);????????????void????(*erase_cmd)(struct?mtd_info?*mtd,?int?page);????????????int?????(*scan_bbt)(struct?mtd_info?*mtd);??????int?????(*errstat)(struct?mtd_info?*mtd,?struct?nand_chip?*this,?int?state,?int?status,?int?page);????????????int?????(*write_page)(struct?mtd_info?*mtd,?struct?nand_chip?*chip,????????????????????????const?uint8_t?*buf,?int?page,?int?cached,?int?raw);????????int?????chip_delay;?????????????????????unsigned?int????options;????????????????????int??????page_shift;??????????????int??????phys_erase_shift;??????????????int??????bbt_erase_shift;????????????int??????chip_shift;????????????int??????numchips;????????????uint64_t?chipsize;??????int??????pagemask;??????int??????pagebuf;??????int??????subpagesize;??????uint8_t??cellinfo;??????int??????badblockpos;??????nand_state_t????state;??????uint8_t?????*oob_poi;??????struct?nand_hw_control??*controller;??????struct?nand_ecclayout???*ecclayout;?????????????struct?nand_ecc_ctrl?ecc;?????????struct?nand_buffers?*buffers;??????struct?nand_hw_control?hwcontrol;??????struct?mtd_oob_ops?ops;??????uint8_t?????*bbt;??????struct?nand_bbt_descr???*bbt_td;??????struct?nand_bbt_descr???*bbt_md;??????struct?nand_bbt_descr???*badblock_pattern;??????void????????*priv;??};?? 最后,我們來用圖表的形式來總結一下,MTD設備層、MTD原始設備層、FLASH硬件驅動層之間的聯系。 ?
?
本文轉自張昺華-sky博客園博客,原文鏈接:http://www.cnblogs.com/sky-heaven/p/5825580.html,如需轉載請自行聯系原作者
總結
以上是生活随笔為你收集整理的Linux MTD系统剖析【转】的全部內容,希望文章能夠幫你解決所遇到的問題。
如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。