doc_set_driver_info(9)

🌸 NAME 🌸

okay so bestie, welcome to doc_set_driver_info(9) from the Kernel API Manual 💅✨. This page is literally about doc_set_driver_info — fill the mtd_info structure and docg3 structure. periodt.

⭐ SYNOPSIS ⭐

here's the signature, exactly as it shows up, no cap:

int doc_set_driver_info (int chip_id , struct mtd_info *mtd );

🎀 ARGUMENTS 🎀

• chip_id — the chip ID of the supported chip. that's the ID, bestie 🫶
• mtd — the structure to fill. she's the one getting filled 💖

🦋 SEE ALSO 🦋

Kernel file: ./drivers/mtd/devices/docg3.c

and these are the linked besties, all of them, fr fr:

• doc_delay(9)
• doc_read_data_area(9)
• doc_write_data_area(9)
• doc_set_reliable_mode(9)
• doc_set_asic_mode(9)
• doc_set_device_id(9)
• doc_set_extra_page_mode(9)
• doc_setup_addr_sector(9)
• doc_setup_writeaddr_sector(9)
• doc_read_seek(9)
• doc_write_seek(9)
• doc_read_page_ecc_init(9)
• doc_write_page_ecc_init(9)
• doc_ecc_disable(9)
• doc_hamming_ecc_init(9)
• doc_ecc_bch_fix_data(9)
• doc_read_page_prepare(9)
• doc_read_page_getbytes(9)
• doc_write_page_putbytes(9)
• doc_get_bch_hw_ecc(9)
• doc_page_finish(9)
• doc_read_page_finish(9)
• calc_block_sector(9)
• doc_read_oob(9)
• doc_block_isbad(9)
• doc_get_erase_count(9)
• doc_get_op_status(9)
• doc_write_erase_wait_status(9)
• doc_erase_block(9)
• doc_erase(9)
• doc_write_page(9)
• doc_guess_autoecc(9)
• doc_fill_autooob(9)
• doc_backup_oob(9)
• doc_write_oob(9)
• doc_probe_device(9)
• doc_release_device(9)
• docg3_resume(9)
• docg3_suspend(9)
• docg3_probe(9)
• docg3_release(9)

okay that's the whole page! footer shoutout: source/version spot ./drivers/mtd/devices, date October 2026, and the page tag doc_set_driver_info(9). byeee bestie 💖🎀🦋