diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-01-10 16:45:22 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-01-10 16:45:22 -0500 |
commit | 7b3480f8b701170c046e1ed362946f5f0d005e13 (patch) | |
tree | bd25e05b4f35699689b485480dddf24f840f80af /Documentation/ABI | |
parent | 1c8106528aa6bf16b3f457de80df1cf7462a49a4 (diff) | |
parent | b60ef99c1164a8ad346cf41f9e71acfffb6d25a6 (diff) |
Merge tag 'for-linus-3.3' of git://git.infradead.org/mtd-2.6
MTD pull for 3.3
* tag 'for-linus-3.3' of git://git.infradead.org/mtd-2.6: (113 commits)
mtd: Fix dependency for MTD_DOC200x
mtd: do not use mtd->block_markbad directly
logfs: do not use 'mtd->block_isbad' directly
mtd: introduce mtd_can_have_bb helper
mtd: do not use mtd->suspend and mtd->resume directly
mtd: do not use mtd->lock, unlock and is_locked directly
mtd: do not use mtd->sync directly
mtd: harmonize mtd_writev usage
mtd: do not use mtd->lock_user_prot_reg directly
mtd: mtd->write_user_prot_reg directly
mtd: do not use mtd->read_*_prot_reg directly
mtd: do not use mtd->get_*_prot_info directly
mtd: do not use mtd->read_oob directly
mtd: mtdoops: do not use mtd->panic_write directly
romfs: do not use mtd->get_unmapped_area directly
mtd: do not use mtd->get_unmapped_area directly
mtd: do use mtd->point directly
mtd: introduce mtd_has_oob helper
mtd: mtdcore: export symbols cleanup
mtd: clean-up the default_mtd_writev function
...
Fix up trivial edit/remove conflict in drivers/staging/spectra/lld_mtd.c
Diffstat (limited to 'Documentation/ABI')
-rw-r--r-- | Documentation/ABI/testing/sysfs-devices-platform-docg3 | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-devices-platform-docg3 b/Documentation/ABI/testing/sysfs-devices-platform-docg3 new file mode 100644 index 000000000000..8aa36716882f --- /dev/null +++ b/Documentation/ABI/testing/sysfs-devices-platform-docg3 | |||
@@ -0,0 +1,34 @@ | |||
1 | What: /sys/devices/platform/docg3/f[0-3]_dps[01]_is_keylocked | ||
2 | Date: November 2011 | ||
3 | KernelVersion: 3.3 | ||
4 | Contact: Robert Jarzmik <robert.jarzmik@free.fr> | ||
5 | Description: | ||
6 | Show whether the floor (0 to 4), protection area (0 or 1) is | ||
7 | keylocked. Each docg3 chip (or floor) has 2 protection areas, | ||
8 | which can cover any part of it, block aligned, called DPS. | ||
9 | The protection has information embedded whether it blocks reads, | ||
10 | writes or both. | ||
11 | The result is: | ||
12 | 0 -> the DPS is not keylocked | ||
13 | 1 -> the DPS is keylocked | ||
14 | Users: None identified so far. | ||
15 | |||
16 | What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key | ||
17 | Date: November 2011 | ||
18 | KernelVersion: 3.3 | ||
19 | Contact: Robert Jarzmik <robert.jarzmik@free.fr> | ||
20 | Description: | ||
21 | Enter the protection key for the floor (0 to 4), protection area | ||
22 | (0 or 1). Each docg3 chip (or floor) has 2 protection areas, | ||
23 | which can cover any part of it, block aligned, called DPS. | ||
24 | The protection has information embedded whether it blocks reads, | ||
25 | writes or both. | ||
26 | The protection key is a string of 8 bytes (value 0-255). | ||
27 | Entering the correct value toggle the lock, and can be observed | ||
28 | through f[0-3]_dps[01]_is_keylocked. | ||
29 | Possible values are: | ||
30 | - 8 bytes | ||
31 | Typical values are: | ||
32 | - "00000000" | ||
33 | - "12345678" | ||
34 | Users: None identified so far. | ||