summaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing/sysfs-devices-platform-docg3
blob: 8aa36716882f87179aa8d025b2f1696d6aa1ac3b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
What:		/sys/devices/platform/docg3/f[0-3]_dps[01]_is_keylocked
Date:		November 2011
KernelVersion:	3.3
Contact:	Robert Jarzmik <robert.jarzmik@free.fr>
Description:
		Show whether the floor (0 to 4), protection area (0 or 1) is
		keylocked. Each docg3 chip (or floor) has 2 protection areas,
		which can cover any part of it, block aligned, called DPS.
		The protection has information embedded whether it blocks reads,
		writes or both.
		The result is:
		0 -> the DPS is not keylocked
		1 -> the DPS is keylocked
Users:		None identified so far.

What:		/sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key
Date:		November 2011
KernelVersion:	3.3
Contact:	Robert Jarzmik <robert.jarzmik@free.fr>
Description:
		Enter the protection key for the floor (0 to 4), protection area
		(0 or 1). Each docg3 chip (or floor) has 2 protection areas,
		which can cover any part of it, block aligned, called DPS.
		The protection has information embedded whether it blocks reads,
		writes or both.
		The protection key is a string of 8 bytes (value 0-255).
		Entering the correct value toggle the lock, and can be observed
		through f[0-3]_dps[01]_is_keylocked.
		Possible values are:
			- 8 bytes
		Typical values are:
			- "00000000"
			- "12345678"
Users:		None identified so far.
OpenPOWER on IntegriCloud