docg3_probe(9)

🎀 NAME 🎀

docg3_probe — from the Kernel API Manual, bestie — is literally here to Probe the IO space for a DiskOnChip G3 chip 🦋✨

✨ SYNOPSIS ✨

int docg3_probe (struct platform_device *pdev );

🫶 ARGUMENTS 🫶

• pdev — platform device. That’s the whole assignment, no cap 💅

🔥 DESCRIPTION 🔥

Okay so this one probes for a G3 chip at the specified IO space in the platform data ressources. The floor 0 must be available — like, that’s non-negotiable, bestie 🚨

It returns 0 on success, and -ENOMEM / -ENXIO on error. Periodt. 💖

💜 SEE ALSO 💜

The whole squad, in order, because we are not skipping anyone 👑✨

• Kernel file: ./drivers/mtd/devices/docg3.c
• 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_set_driver_info(9)
• doc_probe_device(9)
• doc_release_device(9)
• docg3_resume(9)
• docg3_suspend(9)
• docg3_release(9)

Cute sign-off 💌: source/version ./drivers/mtd/devices, date October 2026, page docg3_probe(9) — stay iconic, probe responsibly, and protect floor 0 at all costs 💅🌈✨