CONFIG_MTD_OTP: Protection Registers aka one-time programmable (OTP) bits

General informations

The Linux kernel configuration item CONFIG_MTD_OTP:

• prompt: Protection Registers aka one-time programmable (OTP) bits
• type: bool
• depends on: CONFIG_MTD_CFI_ADV_OPTIONS
• defined in drivers/mtd/chips/Kconfig
• found in Linux kernels: 2.6.13–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

This enables support for reading, writing and locking so called "Protection Registers" present on some flash chips. A subset of them are pre-programmed at the factory with a unique set of values. The rest is user-programmable.

The user-programmable Protection Registers contain one-time programmable (OTP) bits; when programmed, register bits cannot be erased. Each Protection Register can be accessed multiple times to program individual bits, as long as the register remains unlocked.

Each Protection Register has an associated Lock Register bit. When a Lock Register bit is programmed, the associated Protection Register can only be read; it can no longer be programmed. Additionally, because the Lock Register bits themselves are OTP, when programmed, Lock Register bits cannot be erased. Therefore, when a Protection Register is locked, it cannot be unlocked.

This feature should therefore be used with extreme care. Any mistake in the programming of OTP bits will waste them.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: