Merge branch 'topic/usb-audio-refactoring' into for-next
Pull the USB audio improvement Signed-off-by: Takashi Iwai <tiwai@suse.de>
This commit is contained in:
Takashi Iwai
Коммит
4390628738
5
.mailmap
5
.mailmap
|
|
@ -82,7 +82,10 @@ Dengcheng Zhu <dzhu@wavecomp.com> <dengcheng.zhu@gmail.com>
|
|||
Dengcheng Zhu <dzhu@wavecomp.com> <dengcheng.zhu@imgtec.com>
|
||||
Dengcheng Zhu <dzhu@wavecomp.com> <dengcheng.zhu@mips.com>
|
||||
<dev.kurt@vandijck-laurijssen.be> <kurt.van.dijck@eia.be>
|
||||
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
||||
Dmitry Baryshkov <dbaryshkov@gmail.com>
|
||||
Dmitry Baryshkov <dbaryshkov@gmail.com> <[dbaryshkov@gmail.com]>
|
||||
Dmitry Baryshkov <dbaryshkov@gmail.com> <dmitry_baryshkov@mentor.com>
|
||||
Dmitry Baryshkov <dbaryshkov@gmail.com> <dmitry_eremin@mentor.com>
|
||||
Dmitry Safonov <0x7f454c46@gmail.com> <dima@arista.com>
|
||||
Dmitry Safonov <0x7f454c46@gmail.com> <d.safonov@partner.samsung.com>
|
||||
Dmitry Safonov <0x7f454c46@gmail.com> <dsafonov@virtuozzo.com>
|
||||
|
|
|
|||
71
CREDITS
71
CREDITS
|
|
@ -98,7 +98,7 @@ N: Erik Andersen
|
|||
E: andersen@codepoet.org
|
||||
W: https://www.codepoet.org/
|
||||
P: 1024D/30D39057 1BC4 2742 E885 E4DE 9301 0C82 5F9B 643E 30D3 9057
|
||||
D: Maintainer of ide-cd and Uniform CD-ROM driver,
|
||||
D: Maintainer of ide-cd and Uniform CD-ROM driver,
|
||||
D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update.
|
||||
S: 352 North 525 East
|
||||
S: Springville, Utah 84663
|
||||
|
|
@ -263,7 +263,7 @@ N: Paul Barton-Davis
|
|||
E: pbd@op.net
|
||||
D: Driver for WaveFront soundcards (Turtle Beach Maui, Tropez, Tropez+)
|
||||
D: Various bugfixes and changes to sound drivers
|
||||
S: USA
|
||||
S: USA
|
||||
|
||||
N: Carlos Henrique Bauer
|
||||
E: chbauer@acm.org
|
||||
|
|
@ -849,6 +849,12 @@ D: trivial hack to add variable address length routing to Rose.
|
|||
D: AX25-HOWTO, HAM-HOWTO, IPX-HOWTO, NET-2-HOWTO
|
||||
D: ax25-utils maintainer.
|
||||
|
||||
N: Kamil Debski
|
||||
E: kamil@wypas.org
|
||||
D: Samsung S5P 2D graphics acceleration and Multi Format Codec drivers
|
||||
D: Samsung USB2 phy drivers
|
||||
D: PWM fan driver
|
||||
|
||||
N: Helge Deller
|
||||
E: deller@gmx.de
|
||||
W: http://www.parisc-linux.org/
|
||||
|
|
@ -1199,7 +1205,7 @@ N: Daniel J. Frasnelli
|
|||
E: dfrasnel@alphalinux.org
|
||||
W: http://www.alphalinux.org/
|
||||
P: 1024/3EF87611 B9 F1 44 50 D3 E8 C2 80 DA E5 55 AA 56 7C 42 DA
|
||||
D: DEC Alpha hacker
|
||||
D: DEC Alpha hacker
|
||||
D: Miscellaneous bug squisher
|
||||
|
||||
N: Jim Freeman
|
||||
|
|
@ -1299,7 +1305,7 @@ S: P.O. Box 76, Epping
|
|||
S: New South Wales, 2121
|
||||
S: Australia
|
||||
|
||||
N: Carlos E. Gorges
|
||||
N: Carlos E. Gorges
|
||||
E: carlos@techlinux.com.br
|
||||
D: fix smp support on cmpci driver
|
||||
P: 2048G/EA3C4B19 FF31 33A6 0362 4915 B7EB E541 17D0 0379 EA3C 4B19
|
||||
|
|
@ -1340,7 +1346,7 @@ E: wgreathouse@smva.com
|
|||
E: wgreathouse@myfavoritei.com
|
||||
D: Current Belkin USB Serial Adapter F5U103 hacker
|
||||
D: Kernel hacker, embedded systems
|
||||
S: 7802 Fitzwater Road
|
||||
S: 7802 Fitzwater Road
|
||||
S: Brecksville, OH 44141-1334
|
||||
S: USA
|
||||
|
||||
|
|
@ -1381,7 +1387,7 @@ N: Grant Guenther
|
|||
E: grant@torque.net
|
||||
W: http://www.torque.net/linux-pp.html
|
||||
D: original author of ppa driver for parallel port ZIP drive
|
||||
D: original architect of the parallel-port sharing scheme
|
||||
D: original architect of the parallel-port sharing scheme
|
||||
D: PARIDE subsystem: drivers for parallel port IDE & ATAPI devices
|
||||
S: 44 St. Joseph Street, Suite 506
|
||||
S: Toronto, Ontario, M4Y 2W4
|
||||
|
|
@ -1523,7 +1529,7 @@ N: Benjamin Herrenschmidt
|
|||
E: benh@kernel.crashing.org
|
||||
D: Various parts of PPC/PPC64 & PowerMac
|
||||
S: 312/107 Canberra Avenue
|
||||
S: Griffith, ACT 2603
|
||||
S: Griffith, ACT 2603
|
||||
S: Australia
|
||||
|
||||
N: Andreas Herrmann
|
||||
|
|
@ -1825,7 +1831,7 @@ S: Hungary
|
|||
N: Bernhard Kaindl
|
||||
E: bkaindl@netway.at
|
||||
E: edv@bartelt.via.at
|
||||
D: Author of a menu based configuration tool, kmenu, which
|
||||
D: Author of a menu based configuration tool, kmenu, which
|
||||
D: is the predecessor of 'make menuconfig' and 'make xconfig'.
|
||||
D: digiboard driver update(modularisation work and 2.1.x upd)
|
||||
S: Tallak 95
|
||||
|
|
@ -1910,6 +1916,15 @@ S: 660 Harvard Ave. #7
|
|||
S: Santa Clara, CA 95051
|
||||
S: USA
|
||||
|
||||
N: Kukjin Kim
|
||||
E: kgene@kernel.org
|
||||
D: Samsung S3C, S5P and Exynos ARM architectures
|
||||
|
||||
N: Sangbeom Kim
|
||||
E: sbkim73@samsung.com
|
||||
D: Samsung SoC Audio (ASoC) drivers
|
||||
D: Samsung PMIC (RTC, regulators, MFD) drivers
|
||||
|
||||
N: Russell King
|
||||
E: rmk@arm.linux.org.uk
|
||||
D: Linux/arm integrator, maintainer & hacker
|
||||
|
|
@ -2007,7 +2022,7 @@ W: http://www.xos.nl/
|
|||
D: IP transparent proxy support
|
||||
S: X/OS Experts in Open Systems BV
|
||||
S: Kruislaan 419
|
||||
S: 1098 VA Amsterdam
|
||||
S: 1098 VA Amsterdam
|
||||
S: The Netherlands
|
||||
|
||||
N: Goran Koruga
|
||||
|
|
@ -2079,7 +2094,7 @@ S: Germany
|
|||
|
||||
N: Andrzej M. Krzysztofowicz
|
||||
E: ankry@mif.pg.gda.pl
|
||||
D: Some 8-bit XT disk driver and devfs hacking
|
||||
D: Some 8-bit XT disk driver and devfs hacking
|
||||
D: Aladdin 1533/1543(C) chipset IDE
|
||||
D: PIIX chipset IDE
|
||||
S: ul. Matemblewska 1B/10
|
||||
|
|
@ -2454,7 +2469,7 @@ E: mge@EZ-Darmstadt.Telekom.de
|
|||
D: Logical Volume Manager
|
||||
S: Bartningstr. 12
|
||||
S: 64289 Darmstadt
|
||||
S: Germany
|
||||
S: Germany
|
||||
|
||||
N: Mark W. McClelland
|
||||
E: mmcclell@bigfoot.com
|
||||
|
|
@ -2538,7 +2553,7 @@ E: meskes@debian.org
|
|||
P: 1024/04B6E8F5 6C 77 33 CA CC D6 22 03 AB AB 15 A3 AE AD 39 7D
|
||||
D: Kernel hacker. PostgreSQL hacker. Software watchdog daemon.
|
||||
D: Maintainer of several Debian packages
|
||||
S: Th.-Heuss-Str. 61
|
||||
S: Th.-Heuss-Str. 61
|
||||
S: D-41812 Erkelenz
|
||||
S: Germany
|
||||
|
||||
|
|
@ -2776,7 +2791,7 @@ E: neuffer@goofy.zdv.uni-mainz.de
|
|||
W: http://www.i-Connect.Net/~mike/
|
||||
D: Developer and maintainer of the EATA-DMA SCSI driver
|
||||
D: Co-developer EATA-PIO SCSI driver
|
||||
D: /proc/scsi and assorted other snippets
|
||||
D: /proc/scsi and assorted other snippets
|
||||
S: Zum Schiersteiner Grund 2
|
||||
S: 55127 Mainz
|
||||
S: Germany
|
||||
|
|
@ -2843,6 +2858,10 @@ D: IPX development and support
|
|||
N: Venkatesh Pallipadi (Venki)
|
||||
D: x86/HPET
|
||||
|
||||
N: Kyungmin Park
|
||||
E: kyungmin.park@samsung.com
|
||||
D: Samsung S5Pv210 and Exynos4210 mobile platforms
|
||||
|
||||
N: David Parsons
|
||||
E: orc@pell.chi.il.us
|
||||
D: improved memory detection code.
|
||||
|
|
@ -3010,7 +3029,7 @@ D: Embedded PowerPC 4xx/6xx/7xx/74xx support
|
|||
S: Chandler, Arizona 85249
|
||||
S: USA
|
||||
|
||||
N: Frederic Potter
|
||||
N: Frederic Potter
|
||||
E: fpotter@cirpack.com
|
||||
D: Some PCI kernel support
|
||||
|
||||
|
|
@ -3443,21 +3462,21 @@ S: Klosterweg 28 / i309
|
|||
S: 76131 Karlsruhe
|
||||
S: Germany
|
||||
|
||||
N: James Simmons
|
||||
N: James Simmons
|
||||
E: jsimmons@infradead.org
|
||||
E: jsimmons@users.sf.net
|
||||
E: jsimmons@users.sf.net
|
||||
D: Frame buffer device maintainer
|
||||
D: input layer development
|
||||
D: tty/console layer
|
||||
D: various mipsel devices
|
||||
S: 115 Carmel Avenue
|
||||
D: various mipsel devices
|
||||
S: 115 Carmel Avenue
|
||||
S: El Cerrito CA 94530
|
||||
S: USA
|
||||
S: USA
|
||||
|
||||
N: Jaspreet Singh
|
||||
E: jaspreet@sangoma.com
|
||||
W: www.sangoma.com
|
||||
D: WANPIPE drivers & API Support for Sangoma S508/FT1 cards
|
||||
D: WANPIPE drivers & API Support for Sangoma S508/FT1 cards
|
||||
S: Sangoma Technologies Inc.,
|
||||
S: 1001 Denison Street
|
||||
S: Suite 101
|
||||
|
|
@ -3481,7 +3500,7 @@ N: Craig Small
|
|||
E: csmall@triode.apana.org.au
|
||||
E: vk2xlz@gonzo.vk2xlz.ampr.org (packet radio)
|
||||
D: Gracilis PackeTwin device driver
|
||||
D: RSPF daemon
|
||||
D: RSPF daemon
|
||||
S: 10 Stockalls Place
|
||||
S: Minto, NSW, 2566
|
||||
S: Australia
|
||||
|
|
@ -3691,7 +3710,7 @@ N: Tsu-Sheng Tsao
|
|||
E: tsusheng@scf.usc.edu
|
||||
D: IGMP(Internet Group Management Protocol) version 2
|
||||
S: 2F 14 ALY 31 LN 166 SEC 1 SHIH-PEI RD
|
||||
S: Taipei
|
||||
S: Taipei
|
||||
S: Taiwan 112
|
||||
S: Republic of China
|
||||
S: 24335 Delta Drive
|
||||
|
|
@ -3852,7 +3871,7 @@ D: Produced the Slackware distribution, updated the SVGAlib
|
|||
D: patches for ghostscript, worked on color 'ls', etc.
|
||||
S: 301 15th Street S.
|
||||
S: Moorhead, Minnesota 56560
|
||||
S: USA
|
||||
S: USA
|
||||
|
||||
N: Jos Vos
|
||||
E: jos@xos.nl
|
||||
|
|
@ -3860,7 +3879,7 @@ W: http://www.xos.nl/
|
|||
D: Various IP firewall updates, ipfwadm
|
||||
S: X/OS Experts in Open Systems BV
|
||||
S: Kruislaan 419
|
||||
S: 1098 VA Amsterdam
|
||||
S: 1098 VA Amsterdam
|
||||
S: The Netherlands
|
||||
|
||||
N: Jeroen Vreeken
|
||||
|
|
@ -4098,7 +4117,7 @@ S: People's Repulic of China
|
|||
N: Victor Yodaiken
|
||||
E: yodaiken@fsmlabs.com
|
||||
D: RTLinux (RealTime Linux)
|
||||
S: POB 1822
|
||||
S: POB 1822
|
||||
S: Socorro NM, 87801
|
||||
S: USA
|
||||
|
||||
|
|
@ -4196,7 +4215,7 @@ D: EISA/sysfs subsystem
|
|||
S: France
|
||||
|
||||
# Don't add your name here, unless you really _are_ after Marc
|
||||
# alphabetically. Leonard used to be very proud of being the
|
||||
# alphabetically. Leonard used to be very proud of being the
|
||||
# last entry, and he'll get positively pissed if he can't even
|
||||
# be second-to-last. (and this file really _is_ supposed to be
|
||||
# in alphabetic order)
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ The different levels of stability are:
|
|||
layout of the files below for details on how to do this.)
|
||||
|
||||
obsolete/
|
||||
This directory documents interfaces that are still remaining in
|
||||
This directory documents interfaces that are still remaining in
|
||||
the kernel, but are marked to be removed at some later point in
|
||||
time. The description of the interface will document the reason
|
||||
why it is obsolete and when it can be expected to be removed.
|
||||
|
|
@ -58,6 +58,14 @@ Users: All users of this interface who wish to be notified when
|
|||
be changed further.
|
||||
|
||||
|
||||
Note:
|
||||
The fields should be use a simple notation, compatible with ReST markup.
|
||||
Also, the file **should not** have a top-level index, like::
|
||||
|
||||
===
|
||||
foo
|
||||
===
|
||||
|
||||
How things move between levels:
|
||||
|
||||
Interfaces in stable may move to obsolete, as long as the proper
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ Description: Device DAX is the device-centric analogue of Filesystem
|
|||
system. Device DAX is strict, precise and predictable.
|
||||
Specifically this interface:
|
||||
|
||||
1/ Guarantees fault granularity with respect to a given
|
||||
page size (pte, pmd, or pud) set at configuration time.
|
||||
1. Guarantees fault granularity with respect to a given
|
||||
page size (pte, pmd, or pud) set at configuration time.
|
||||
|
||||
2/ Enforces deterministic behavior by being strict about
|
||||
what fault scenarios are supported.
|
||||
2. Enforces deterministic behavior by being strict about
|
||||
what fault scenarios are supported.
|
||||
|
||||
The /sys/class/dax/ interface enumerates all the
|
||||
device-dax instances in the system. The ABI is
|
||||
|
|
|
|||
|
|
@ -7,10 +7,13 @@ Description: It is possible to switch the cpi setting of the mouse with the
|
|||
setting reported by the mouse. This number has to be further
|
||||
processed to receive the real dpi value:
|
||||
|
||||
===== ====
|
||||
VALUE DPI
|
||||
===== ====
|
||||
1 400
|
||||
2 800
|
||||
4 1600
|
||||
===== ====
|
||||
|
||||
This file is readonly.
|
||||
Has never been used. If bookkeeping is done, it's done in userland tools.
|
||||
|
|
|
|||
|
|
@ -13,6 +13,8 @@ Description:
|
|||
GPIOs are identified as they are inside the kernel, using integers in
|
||||
the range 0..INT_MAX. See Documentation/admin-guide/gpio for more information.
|
||||
|
||||
::
|
||||
|
||||
/sys/class/gpio
|
||||
/export ... asks the kernel to export a GPIO to userspace
|
||||
/unexport ... to return a GPIO to the kernel
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ Description:
|
|||
devfs has been unmaintained for a number of years, has unfixable
|
||||
races, contains a naming policy within the kernel that is
|
||||
against the LSB, and can be replaced by using udev.
|
||||
|
||||
The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
|
||||
along with the assorted devfs function calls throughout the
|
||||
kernel tree.
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ Description:
|
|||
to implement sensible device security policies, and its low level
|
||||
of abstraction that required userspace clients to duplicate much
|
||||
of the kernel's ieee1394 core functionality.
|
||||
|
||||
Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
|
||||
firewire-core.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@ Description: This file was deprecated because there no longer was a way to
|
|||
claim just control over a single rfkill instance.
|
||||
This file was scheduled to be removed in 2012, and was removed
|
||||
in 2016.
|
||||
Values: 0: Kernel handles events
|
||||
Values: 0: Kernel handles events
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ Description:
|
|||
performance issues in its first generation. Any video1394 user had
|
||||
to use raw1394 + libraw1394 too because video1394 did not provide
|
||||
asynchronous I/O for device discovery and configuration.
|
||||
|
||||
Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
|
||||
firewire-core.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,13 +14,17 @@ Description:
|
|||
Each /dev/fw* is associated with one IEEE 1394 node, which can
|
||||
be remote or local nodes. Operations on a /dev/fw* file have
|
||||
different scope:
|
||||
|
||||
- The 1394 node which is associated with the file:
|
||||
|
||||
- Asynchronous request transmission
|
||||
- Get the Configuration ROM
|
||||
- Query node ID
|
||||
- Query maximum speed of the path between this node
|
||||
and local node
|
||||
|
||||
- The 1394 bus (i.e. "card") to which the node is attached to:
|
||||
|
||||
- Isochronous stream transmission and reception
|
||||
- Asynchronous stream transmission and reception
|
||||
- Asynchronous broadcast request transmission
|
||||
|
|
@ -31,7 +35,9 @@ Description:
|
|||
manager
|
||||
- Query cycle time
|
||||
- Bus reset initiation, bus reset event reception
|
||||
|
||||
- All 1394 buses:
|
||||
|
||||
- Allocation of IEEE 1212 address ranges on the local
|
||||
link layers, reception of inbound requests to such
|
||||
an address range, asynchronous response transmission
|
||||
|
|
@ -43,6 +49,7 @@ Description:
|
|||
userland implement different access permission models, some
|
||||
operations are restricted to /dev/fw* files that are associated
|
||||
with a local node:
|
||||
|
||||
- Addition of descriptors or directories to the local
|
||||
nodes' Configuration ROM
|
||||
- PHY packet transmission and reception
|
||||
|
|
@ -55,50 +62,50 @@ Description:
|
|||
The following file operations are supported:
|
||||
|
||||
open(2)
|
||||
Currently the only useful flags are O_RDWR.
|
||||
Currently the only useful flags are O_RDWR.
|
||||
|
||||
ioctl(2)
|
||||
Initiate various actions. Some take immediate effect, others
|
||||
are performed asynchronously while or after the ioctl returns.
|
||||
See the inline documentation in <linux/firewire-cdev.h> for
|
||||
descriptions of all ioctls.
|
||||
Initiate various actions. Some take immediate effect, others
|
||||
are performed asynchronously while or after the ioctl returns.
|
||||
See the inline documentation in <linux/firewire-cdev.h> for
|
||||
descriptions of all ioctls.
|
||||
|
||||
poll(2), select(2), epoll_wait(2) etc.
|
||||
Watch for events to become available to be read.
|
||||
Watch for events to become available to be read.
|
||||
|
||||
read(2)
|
||||
Receive various events. There are solicited events like
|
||||
outbound asynchronous transaction completion or isochronous
|
||||
buffer completion, and unsolicited events such as bus resets,
|
||||
request reception, or PHY packet reception. Always use a read
|
||||
buffer which is large enough to receive the largest event that
|
||||
could ever arrive. See <linux/firewire-cdev.h> for descriptions
|
||||
of all event types and for which ioctls affect reception of
|
||||
events.
|
||||
Receive various events. There are solicited events like
|
||||
outbound asynchronous transaction completion or isochronous
|
||||
buffer completion, and unsolicited events such as bus resets,
|
||||
request reception, or PHY packet reception. Always use a read
|
||||
buffer which is large enough to receive the largest event that
|
||||
could ever arrive. See <linux/firewire-cdev.h> for descriptions
|
||||
of all event types and for which ioctls affect reception of
|
||||
events.
|
||||
|
||||
mmap(2)
|
||||
Allocate a DMA buffer for isochronous reception or transmission
|
||||
and map it into the process address space. The arguments should
|
||||
be used as follows: addr = NULL, length = the desired buffer
|
||||
size, i.e. number of packets times size of largest packet,
|
||||
prot = at least PROT_READ for reception and at least PROT_WRITE
|
||||
for transmission, flags = MAP_SHARED, fd = the handle to the
|
||||
/dev/fw*, offset = 0.
|
||||
Allocate a DMA buffer for isochronous reception or transmission
|
||||
and map it into the process address space. The arguments should
|
||||
be used as follows: addr = NULL, length = the desired buffer
|
||||
size, i.e. number of packets times size of largest packet,
|
||||
prot = at least PROT_READ for reception and at least PROT_WRITE
|
||||
for transmission, flags = MAP_SHARED, fd = the handle to the
|
||||
/dev/fw*, offset = 0.
|
||||
|
||||
Isochronous reception works in packet-per-buffer fashion except
|
||||
for multichannel reception which works in buffer-fill mode.
|
||||
|
||||
munmap(2)
|
||||
Unmap the isochronous I/O buffer from the process address space.
|
||||
Unmap the isochronous I/O buffer from the process address space.
|
||||
|
||||
close(2)
|
||||
Besides stopping and freeing I/O contexts that were associated
|
||||
with the file descriptor, back out any changes to the local
|
||||
nodes' Configuration ROM. Deallocate isochronous channels and
|
||||
bandwidth at the IRM that were marked for kernel-assisted
|
||||
re- and deallocation.
|
||||
Besides stopping and freeing I/O contexts that were associated
|
||||
with the file descriptor, back out any changes to the local
|
||||
nodes' Configuration ROM. Deallocate isochronous channels and
|
||||
bandwidth at the IRM that were marked for kernel-assisted
|
||||
re- and deallocation.
|
||||
|
||||
Users: libraw1394
|
||||
libdc1394
|
||||
libhinawa
|
||||
Users: libraw1394;
|
||||
libdc1394;
|
||||
libhinawa;
|
||||
tools like linux-firewire-utils, fwhack, ...
|
||||
|
|
|
|||
|
|
@ -1,22 +1,26 @@
|
|||
What: /sys/firmware/acpi/pm_profile
|
||||
What: /sys/firmware/acpi/pm_profile
|
||||
Date: 03-Nov-2011
|
||||
KernelVersion: v3.2
|
||||
Contact: linux-acpi@vger.kernel.org
|
||||
Description: The ACPI pm_profile sysfs interface exports the platform
|
||||
Description: The ACPI pm_profile sysfs interface exports the platform
|
||||
power management (and performance) requirement expectations
|
||||
as provided by BIOS. The integer value is directly passed as
|
||||
retrieved from the FADT ACPI table.
|
||||
Values: For possible values see ACPI specification:
|
||||
|
||||
Values: For possible values see ACPI specification:
|
||||
5.2.9 Fixed ACPI Description Table (FADT)
|
||||
Field: Preferred_PM_Profile
|
||||
|
||||
Currently these values are defined by spec:
|
||||
0 Unspecified
|
||||
1 Desktop
|
||||
2 Mobile
|
||||
3 Workstation
|
||||
4 Enterprise Server
|
||||
5 SOHO Server
|
||||
6 Appliance PC
|
||||
7 Performance Server
|
||||
|
||||
== =================
|
||||
0 Unspecified
|
||||
1 Desktop
|
||||
2 Mobile
|
||||
3 Workstation
|
||||
4 Enterprise Server
|
||||
5 SOHO Server
|
||||
6 Appliance PC
|
||||
7 Performance Server
|
||||
>7 Reserved
|
||||
== =================
|
||||
|
|
|
|||
|
|
@ -47,6 +47,7 @@ Description:
|
|||
IEEE 1394 node device attribute.
|
||||
Read-only and immutable.
|
||||
Values: 1: The sysfs entry represents a local node (a controller card).
|
||||
|
||||
0: The sysfs entry represents a remote node.
|
||||
|
||||
|
||||
|
|
@ -125,7 +126,9 @@ Description:
|
|||
Read-only attribute, immutable during the target's lifetime.
|
||||
Format, as exposed by firewire-sbp2 since 2.6.22, May 2007:
|
||||
Colon-separated hexadecimal string representations of
|
||||
|
||||
u64 EUI-64 : u24 directory_ID : u16 LUN
|
||||
|
||||
without 0x prefixes, without whitespace. The former sbp2 driver
|
||||
(removed in 2.6.37 after being superseded by firewire-sbp2) used
|
||||
a somewhat shorter format which was not as close to SAM.
|
||||
|
|
|
|||
|
|
@ -9,13 +9,14 @@ Description:
|
|||
Note: This file is only present if CONFIG_NVMEM_SYSFS
|
||||
is enabled
|
||||
|
||||
ex:
|
||||
hexdump /sys/bus/nvmem/devices/qfprom0/nvmem
|
||||
ex::
|
||||
|
||||
0000000 0000 0000 0000 0000 0000 0000 0000 0000
|
||||
*
|
||||
00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00
|
||||
0000000 0000 0000 0000 0000 0000 0000 0000 0000
|
||||
...
|
||||
*
|
||||
0001000
|
||||
hexdump /sys/bus/nvmem/devices/qfprom0/nvmem
|
||||
|
||||
0000000 0000 0000 0000 0000 0000 0000 0000 0000
|
||||
*
|
||||
00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00
|
||||
0000000 0000 0000 0000 0000 0000 0000 0000 0000
|
||||
...
|
||||
*
|
||||
0001000
|
||||
|
|
|
|||
|
|
@ -50,8 +50,10 @@ Description:
|
|||
|
||||
Tools can use this file and the connected_duration file to
|
||||
compute the percentage of time that a device has been active.
|
||||
For example,
|
||||
echo $((100 * `cat active_duration` / `cat connected_duration`))
|
||||
For example::
|
||||
|
||||
echo $((100 * `cat active_duration` / `cat connected_duration`))
|
||||
|
||||
will give an integer percentage. Note that this does not
|
||||
account for counter wrap.
|
||||
Users:
|
||||
|
|
|
|||
|
|
@ -63,13 +63,6 @@ Contact: Stephen Hemminger <sthemmin@microsoft.com>
|
|||
Description: VCPU (sub)channel is affinitized to
|
||||
Users: tools/hv/lsvmbus and other debugging tools
|
||||
|
||||
What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu
|
||||
Date: September. 2017
|
||||
KernelVersion: 4.14
|
||||
Contact: Stephen Hemminger <sthemmin@microsoft.com>
|
||||
Description: VCPU (sub)channel is affinitized to
|
||||
Users: tools/hv/lsvmbus and other debugging tools
|
||||
|
||||
What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask
|
||||
Date: September. 2017
|
||||
KernelVersion: 4.14
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ Description: Bus scanning interval, microseconds component.
|
|||
control systems are attached/generate presence for as short as
|
||||
100 ms - hence the tens-to-hundreds milliseconds scan intervals
|
||||
are required.
|
||||
|
||||
see Documentation/w1/w1-generic.rst for detailed information.
|
||||
Users: any user space application which wants to know bus scanning
|
||||
interval
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ KernelVersion: 2.6.12
|
|||
Contact: Richard Purdie <rpurdie@rpsys.net>
|
||||
Description:
|
||||
Control BACKLIGHT power, values are FB_BLANK_* from fb.h
|
||||
|
||||
- FB_BLANK_UNBLANK (0) : power on.
|
||||
- FB_BLANK_POWERDOWN (4) : power off
|
||||
Users: HAL
|
||||
|
|
|
|||
|
|
@ -8,12 +8,14 @@ Date: Apr, 2005
|
|||
KernelVersion: v2.6.12
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ===========================================
|
||||
node_type: (RO) Node type (CA, RNIC, usNIC, usNIC UDP,
|
||||
switch or router)
|
||||
|
||||
node_guid: (RO) Node GUID
|
||||
|
||||
sys_image_guid: (RO) System image GUID
|
||||
=============== ===========================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/<device>/node_desc
|
||||
|
|
@ -47,6 +49,7 @@ KernelVersion: v2.6.12
|
|||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
|
||||
=============== ===============================================
|
||||
lid: (RO) Port LID
|
||||
|
||||
rate: (RO) Port data rate (active width * active
|
||||
|
|
@ -66,8 +69,9 @@ Description:
|
|||
|
||||
cap_mask: (RO) Port capability mask. 2 bits here are
|
||||
settable- IsCommunicationManagementSupported
|
||||
(set when CM module is loaded) and IsSM (set via
|
||||
open of issmN file).
|
||||
(set when CM module is loaded) and IsSM (set
|
||||
via open of issmN file).
|
||||
=============== ===============================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/<device>/ports/<port-num>/link_layer
|
||||
|
|
@ -103,8 +107,7 @@ Date: Apr, 2005
|
|||
KernelVersion: v2.6.12
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
Errors info:
|
||||
-----------
|
||||
**Errors info**:
|
||||
|
||||
symbol_error: (RO) Total number of minor link errors detected on
|
||||
one or more physical lanes.
|
||||
|
|
@ -142,8 +145,7 @@ Description:
|
|||
intervention. It can also indicate hardware issues or extremely
|
||||
poor link signal integrity
|
||||
|
||||
Data info:
|
||||
---------
|
||||
**Data info**:
|
||||
|
||||
port_xmit_data: (RO) Total number of data octets, divided by 4
|
||||
(lanes), transmitted on all VLs. This is 64 bit counter
|
||||
|
|
@ -176,8 +178,7 @@ Description:
|
|||
transmitted on all VLs from the port. This may include multicast
|
||||
packets with errors.
|
||||
|
||||
Misc info:
|
||||
---------
|
||||
**Misc info**:
|
||||
|
||||
port_xmit_discards: (RO) Total number of outbound packets
|
||||
discarded by the port because the port is down or congested.
|
||||
|
|
@ -244,9 +245,11 @@ Description:
|
|||
two umad devices and two issm devices, while a switch will have
|
||||
one device of each type (for switch port 0).
|
||||
|
||||
======= =====================================
|
||||
ibdev: (RO) Show Infiniband (IB) device name
|
||||
|
||||
port: (RO) Display port number
|
||||
======= =====================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband_mad/abi_version
|
||||
|
|
@ -264,10 +267,12 @@ Date: Sept, 2005
|
|||
KernelVersion: v2.6.14
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ===========================================
|
||||
ibdev: (RO) Display Infiniband (IB) device name
|
||||
|
||||
abi_version: (RO) Show ABI version of IB device specific
|
||||
interfaces.
|
||||
=============== ===========================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband_verbs/abi_version
|
||||
|
|
@ -289,12 +294,14 @@ Date: Apr, 2005
|
|||
KernelVersion: v2.6.12
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ================================================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Host Channel Adapter type: MT23108, MT25208
|
||||
(MT23108 compat mode), MT25208 or MT25204
|
||||
|
||||
board_id: (RO) Manufacturing board ID
|
||||
=============== ================================================
|
||||
|
||||
|
||||
sysfs interface for Mellanox ConnectX HCA IB driver (mlx4)
|
||||
|
|
@ -307,11 +314,13 @@ Date: Sep, 2007
|
|||
KernelVersion: v2.6.24
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ===============================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Host channel adapter type
|
||||
|
||||
board_id: (RO) Manufacturing board ID
|
||||
=============== ===============================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/mlx4_X/iov/ports/<port-num>/gids/<n>
|
||||
|
|
@ -337,6 +346,7 @@ Description:
|
|||
example, ports/1/pkeys/10 contains the value at index 10 in port
|
||||
1's P_Key table.
|
||||
|
||||
======================= ==========================================
|
||||
gids/<n>: (RO) The physical port gids n = 0..127
|
||||
|
||||
admin_guids/<n>: (RW) Allows examining or changing the
|
||||
|
|
@ -365,6 +375,7 @@ Description:
|
|||
guest, whenever it uses its pkey index
|
||||
1, will actually be using the real pkey
|
||||
index 10.
|
||||
======================= ==========================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/mlx4_X/iov/<pci-slot-num>/ports/<m>/smi_enabled
|
||||
|
|
@ -376,12 +387,14 @@ Description:
|
|||
Enabling QP0 on VFs for selected VF/port. By default, no VFs are
|
||||
enabled for QP0 operation.
|
||||
|
||||
smi_enabled: (RO) Indicates whether smi is currently enabled
|
||||
for the indicated VF/port
|
||||
================= ==== ===========================================
|
||||
smi_enabled: (RO) Indicates whether smi is currently enabled
|
||||
for the indicated VF/port
|
||||
|
||||
enable_smi_admin:(RW) Used by the admin to request that smi
|
||||
capability be enabled or disabled for the
|
||||
indicated VF/port. 0 = disable, 1 = enable.
|
||||
enable_smi_admin: (RW) Used by the admin to request that smi
|
||||
capability be enabled or disabled for the
|
||||
indicated VF/port. 0 = disable, 1 = enable.
|
||||
================= ==== ===========================================
|
||||
|
||||
The requested enablement will occur at the next reset of the VF
|
||||
(e.g. driver restart on the VM which owns the VF).
|
||||
|
|
@ -398,6 +411,7 @@ KernelVersion: v2.6.35
|
|||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
|
||||
=============== =============================================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Driver short name. Should normally match
|
||||
|
|
@ -406,6 +420,7 @@ Description:
|
|||
|
||||
board_id: (RO) Manufacturing board id. (Vendor + device
|
||||
information)
|
||||
=============== =============================================
|
||||
|
||||
|
||||
sysfs interface for Intel IB driver qib
|
||||
|
|
@ -426,6 +441,7 @@ Date: May, 2010
|
|||
KernelVersion: v2.6.35
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ======================================================
|
||||
version: (RO) Display version information of installed software
|
||||
and drivers.
|
||||
|
||||
|
|
@ -452,6 +468,7 @@ Description:
|
|||
chip_reset: (WO) Reset the chip if possible by writing
|
||||
"reset" to this file. Only allowed if no user
|
||||
contexts are open that use chip resources.
|
||||
=============== ======================================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/qibX/ports/N/sl2vl/[0-15]
|
||||
|
|
@ -471,14 +488,16 @@ Contact: linux-rdma@vger.kernel.org
|
|||
Description:
|
||||
Per-port congestion control. Both are binary attributes.
|
||||
|
||||
cc_table_bin: (RO) Congestion control table size followed by
|
||||
=============== ================================================
|
||||
cc_table_bin (RO) Congestion control table size followed by
|
||||
table entries.
|
||||
|
||||
cc_settings_bin:(RO) Congestion settings: port control, control
|
||||
cc_settings_bin (RO) Congestion settings: port control, control
|
||||
map and an array of 16 entries for the
|
||||
congestion entries - increase, timer, event log
|
||||
trigger threshold and the minimum injection rate
|
||||
delay.
|
||||
=============== ================================================
|
||||
|
||||
What: /sys/class/infiniband/qibX/ports/N/linkstate/loopback
|
||||
What: /sys/class/infiniband/qibX/ports/N/linkstate/led_override
|
||||
|
|
@ -491,6 +510,7 @@ Contact: linux-rdma@vger.kernel.org
|
|||
Description:
|
||||
[to be documented]
|
||||
|
||||
=============== ===============================================
|
||||
loopback: (WO)
|
||||
led_override: (WO)
|
||||
hrtbt_enable: (RW)
|
||||
|
|
@ -501,6 +521,7 @@ Description:
|
|||
errors. Possible states are- "Initted",
|
||||
"Present", "IB_link_up", "IB_configured" or
|
||||
"Fatal_Hardware_Error".
|
||||
=============== ===============================================
|
||||
|
||||
What: /sys/class/infiniband/qibX/ports/N/diag_counters/rc_resends
|
||||
What: /sys/class/infiniband/qibX/ports/N/diag_counters/seq_naks
|
||||
|
|
@ -549,6 +570,7 @@ Contact: Christian Benvenuti <benve@cisco.com>,
|
|||
linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
|
||||
=============== ===============================================
|
||||
board_id: (RO) Manufacturing board id
|
||||
|
||||
config: (RO) Report the configuration for this PF
|
||||
|
|
@ -561,6 +583,7 @@ Description:
|
|||
|
||||
iface: (RO) Shows which network interface this usNIC
|
||||
entry is associated to (visible with ifconfig).
|
||||
=============== ===============================================
|
||||
|
||||
What: /sys/class/infiniband/usnic_X/qpn/summary
|
||||
What: /sys/class/infiniband/usnic_X/qpn/context
|
||||
|
|
@ -605,6 +628,7 @@ Date: May, 2016
|
|||
KernelVersion: v4.6
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== =============================================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
board_id: (RO) Manufacturing board id
|
||||
|
|
@ -623,6 +647,7 @@ Description:
|
|||
available.
|
||||
|
||||
tempsense: (RO) Thermal sense information
|
||||
=============== =============================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/hfi1_X/ports/N/CCMgtA/cc_settings_bin
|
||||
|
|
@ -634,19 +659,21 @@ Contact: linux-rdma@vger.kernel.org
|
|||
Description:
|
||||
Per-port congestion control.
|
||||
|
||||
cc_table_bin: (RO) CCA tables used by PSM2 Congestion control
|
||||
=============== ================================================
|
||||
cc_table_bin (RO) CCA tables used by PSM2 Congestion control
|
||||
table size followed by table entries. Binary
|
||||
attribute.
|
||||
|
||||
cc_settings_bin:(RO) Congestion settings: port control, control
|
||||
cc_settings_bin (RO) Congestion settings: port control, control
|
||||
map and an array of 16 entries for the
|
||||
congestion entries - increase, timer, event log
|
||||
trigger threshold and the minimum injection rate
|
||||
delay. Binary attribute.
|
||||
|
||||
cc_prescan: (RW) enable prescanning for faster BECN
|
||||
cc_prescan (RW) enable prescanning for faster BECN
|
||||
response. Write "on" to enable and "off" to
|
||||
disable.
|
||||
=============== ================================================
|
||||
|
||||
What: /sys/class/infiniband/hfi1_X/ports/N/sc2vl/[0-31]
|
||||
What: /sys/class/infiniband/hfi1_X/ports/N/sl2sc/[0-31]
|
||||
|
|
@ -655,11 +682,13 @@ Date: May, 2016
|
|||
KernelVersion: v4.6
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ===================================================
|
||||
sc2vl/: (RO) 32 files (0 - 31) used to translate sl->vl
|
||||
|
||||
sl2sc/: (RO) 32 files (0 - 31) used to translate sl->sc
|
||||
|
||||
vl2mtu/: (RO) 16 files (0 - 15) used to determine MTU for vl
|
||||
=============== ===================================================
|
||||
|
||||
|
||||
What: /sys/class/infiniband/hfi1_X/sdma_N/cpu_list
|
||||
|
|
@ -670,26 +699,28 @@ Contact: linux-rdma@vger.kernel.org
|
|||
Description:
|
||||
sdma<N>/ contains one directory per sdma engine (0 - 15)
|
||||
|
||||
=============== ==============================================
|
||||
cpu_list: (RW) List of cpus for user-process to sdma
|
||||
engine assignment.
|
||||
|
||||
vl: (RO) Displays the virtual lane (vl) the sdma
|
||||
engine maps to.
|
||||
=============== ==============================================
|
||||
|
||||
This interface gives the user control on the affinity settings
|
||||
for the device. As an example, to set an sdma engine irq
|
||||
affinity and thread affinity of a user processes to use the
|
||||
sdma engine, which is "near" in terms of NUMA configuration, or
|
||||
physical cpu location, the user will do:
|
||||
physical cpu location, the user will do::
|
||||
|
||||
echo "3" > /proc/irq/<N>/smp_affinity_list
|
||||
echo "4-7" > /sys/devices/.../sdma3/cpu_list
|
||||
cat /sys/devices/.../sdma3/vl
|
||||
0
|
||||
echo "8" > /proc/irq/<M>/smp_affinity_list
|
||||
echo "9-12" > /sys/devices/.../sdma4/cpu_list
|
||||
cat /sys/devices/.../sdma4/vl
|
||||
1
|
||||
echo "3" > /proc/irq/<N>/smp_affinity_list
|
||||
echo "4-7" > /sys/devices/.../sdma3/cpu_list
|
||||
cat /sys/devices/.../sdma3/vl
|
||||
0
|
||||
echo "8" > /proc/irq/<M>/smp_affinity_list
|
||||
echo "9-12" > /sys/devices/.../sdma4/cpu_list
|
||||
cat /sys/devices/.../sdma4/vl
|
||||
1
|
||||
|
||||
to make sure that when a process runs on cpus 4,5,6, or 7, and
|
||||
uses vl=0, then sdma engine 3 is selected by the driver, and
|
||||
|
|
@ -711,11 +742,13 @@ Date: Jan, 2016
|
|||
KernelVersion: v4.10
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ==== ========================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Show HCA type (I40IW)
|
||||
|
||||
board_id: (RO) I40IW board ID
|
||||
=============== ==== ========================
|
||||
|
||||
|
||||
sysfs interface for QLogic qedr NIC Driver
|
||||
|
|
@ -728,9 +761,11 @@ KernelVersion: v4.10
|
|||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
|
||||
=============== ==== ========================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Display HCA type
|
||||
=============== ==== ========================
|
||||
|
||||
|
||||
sysfs interface for VMware Paravirtual RDMA driver
|
||||
|
|
@ -744,11 +779,13 @@ KernelVersion: v4.10
|
|||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
|
||||
=============== ==== =====================================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Host channel adapter type
|
||||
|
||||
board_id: (RO) Display PVRDMA manufacturing board ID
|
||||
=============== ==== =====================================
|
||||
|
||||
|
||||
sysfs interface for Broadcom NetXtreme-E RoCE driver
|
||||
|
|
@ -760,6 +797,8 @@ Date: Feb, 2017
|
|||
KernelVersion: v4.11
|
||||
Contact: linux-rdma@vger.kernel.org
|
||||
Description:
|
||||
=============== ==== =========================
|
||||
hw_rev: (RO) Hardware revision number
|
||||
|
||||
hca_type: (RO) Host channel adapter type
|
||||
=============== ==== =========================
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ rfkill - radio frequency (RF) connector kill switch support
|
|||
|
||||
For details to this subsystem look at Documentation/driver-api/rfkill.rst.
|
||||
|
||||
For the deprecated /sys/class/rfkill/*/claim knobs of this interface look in
|
||||
For the deprecated ``/sys/class/rfkill/*/claim`` knobs of this interface look in
|
||||
Documentation/ABI/removed/sysfs-class-rfkill.
|
||||
|
||||
What: /sys/class/rfkill
|
||||
|
|
@ -36,9 +36,10 @@ KernelVersion v2.6.22
|
|||
Contact: linux-wireless@vger.kernel.org
|
||||
Description: Whether the soft blocked state is initialised from non-volatile
|
||||
storage at startup.
|
||||
Values: A numeric value.
|
||||
0: false
|
||||
1: true
|
||||
Values: A numeric value:
|
||||
|
||||
- 0: false
|
||||
- 1: true
|
||||
|
||||
|
||||
What: /sys/class/rfkill/rfkill[0-9]+/state
|
||||
|
|
@ -54,6 +55,7 @@ Description: Current state of the transmitter.
|
|||
through this interface. There will likely be another attempt to
|
||||
remove it in the future.
|
||||
Values: A numeric value.
|
||||
|
||||
0: RFKILL_STATE_SOFT_BLOCKED
|
||||
transmitter is turned off by software
|
||||
1: RFKILL_STATE_UNBLOCKED
|
||||
|
|
@ -69,6 +71,7 @@ KernelVersion v2.6.34
|
|||
Contact: linux-wireless@vger.kernel.org
|
||||
Description: Current hardblock state. This file is read only.
|
||||
Values: A numeric value.
|
||||
|
||||
0: inactive
|
||||
The transmitter is (potentially) active.
|
||||
1: active
|
||||
|
|
@ -82,7 +85,9 @@ KernelVersion v2.6.34
|
|||
Contact: linux-wireless@vger.kernel.org
|
||||
Description: Current softblock state. This file is read and write.
|
||||
Values: A numeric value.
|
||||
|
||||
0: inactive
|
||||
The transmitter is (potentially) active.
|
||||
|
||||
1: active
|
||||
The transmitter is turned off by software.
|
||||
|
|
|
|||
|
|
@ -32,11 +32,11 @@ KernelVersion: 2.6.12
|
|||
Contact: linux-integrity@vger.kernel.org
|
||||
Description: The "caps" property contains TPM manufacturer and version info.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
Manufacturer: 0x53544d20
|
||||
TCG version: 1.2
|
||||
Firmware version: 8.16
|
||||
Manufacturer: 0x53544d20
|
||||
TCG version: 1.2
|
||||
Firmware version: 8.16
|
||||
|
||||
Manufacturer is a hex dump of the 4 byte manufacturer info
|
||||
space in a TPM. TCG version shows the TCG TPM spec level that
|
||||
|
|
@ -54,9 +54,9 @@ Description: The "durations" property shows the 3 vendor-specific values
|
|||
any longer than necessary before starting to poll for a
|
||||
result.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
3015000 4508000 180995000 [original]
|
||||
3015000 4508000 180995000 [original]
|
||||
|
||||
Here the short, medium and long durations are displayed in
|
||||
usecs. "[original]" indicates that the values are displayed
|
||||
|
|
@ -92,14 +92,14 @@ Description: The "pcrs" property will dump the current value of all Platform
|
|||
values may be constantly changing, the output is only valid
|
||||
for a snapshot in time.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
...
|
||||
PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
|
||||
...
|
||||
|
||||
The number of PCRs and hex bytes needed to represent a PCR
|
||||
value will vary depending on TPM chip version. For TPM 1.1 and
|
||||
|
|
@ -119,44 +119,44 @@ Description: The "pubek" property will return the TPM's public endorsement
|
|||
ated at TPM manufacture time and exists for the life of the
|
||||
chip.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
Algorithm: 00 00 00 01
|
||||
Encscheme: 00 03
|
||||
Sigscheme: 00 01
|
||||
Parameters: 00 00 08 00 00 00 00 02 00 00 00 00
|
||||
Modulus length: 256
|
||||
Modulus:
|
||||
B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C
|
||||
3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6
|
||||
1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB
|
||||
86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3
|
||||
D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B
|
||||
82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26
|
||||
0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E
|
||||
1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D
|
||||
6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0
|
||||
A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6
|
||||
47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6
|
||||
10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70
|
||||
E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A
|
||||
F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6
|
||||
F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B
|
||||
C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B
|
||||
Algorithm: 00 00 00 01
|
||||
Encscheme: 00 03
|
||||
Sigscheme: 00 01
|
||||
Parameters: 00 00 08 00 00 00 00 02 00 00 00 00
|
||||
Modulus length: 256
|
||||
Modulus:
|
||||
B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C
|
||||
3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6
|
||||
1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB
|
||||
86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3
|
||||
D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B
|
||||
82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26
|
||||
0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E
|
||||
1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D
|
||||
6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0
|
||||
A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6
|
||||
47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6
|
||||
10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70
|
||||
E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A
|
||||
F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6
|
||||
F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B
|
||||
C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B
|
||||
|
||||
Possible values:
|
||||
Possible values::
|
||||
|
||||
Algorithm: TPM_ALG_RSA (1)
|
||||
Encscheme: TPM_ES_RSAESPKCSv15 (2)
|
||||
Algorithm: TPM_ALG_RSA (1)
|
||||
Encscheme: TPM_ES_RSAESPKCSv15 (2)
|
||||
TPM_ES_RSAESOAEP_SHA1_MGF1 (3)
|
||||
Sigscheme: TPM_SS_NONE (1)
|
||||
Parameters, a byte string of 3 u32 values:
|
||||
Sigscheme: TPM_SS_NONE (1)
|
||||
Parameters, a byte string of 3 u32 values:
|
||||
Key Length (bits): 00 00 08 00 (2048)
|
||||
Num primes: 00 00 00 02 (2)
|
||||
Exponent Size: 00 00 00 00 (0 means the
|
||||
default exp)
|
||||
Modulus Length: 256 (bytes)
|
||||
Modulus: The 256 byte Endorsement Key modulus
|
||||
Modulus Length: 256 (bytes)
|
||||
Modulus: The 256 byte Endorsement Key modulus
|
||||
|
||||
What: /sys/class/tpm/tpmX/device/temp_deactivated
|
||||
Date: April 2006
|
||||
|
|
@ -176,9 +176,9 @@ Description: The "timeouts" property shows the 4 vendor-specific values
|
|||
timeouts is defined by the TPM interface spec that the chip
|
||||
conforms to.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
750000 750000 750000 750000 [original]
|
||||
750000 750000 750000 750000 [original]
|
||||
|
||||
The four timeout values are shown in usecs, with a trailing
|
||||
"[original]" or "[adjusted]" depending on whether the values
|
||||
|
|
@ -191,6 +191,6 @@ Contact: linux-integrity@vger.kernel.org
|
|||
Description: The "tpm_version_major" property shows the TCG spec major version
|
||||
implemented by the TPM device.
|
||||
|
||||
Example output:
|
||||
Example output::
|
||||
|
||||
2
|
||||
2
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
# Note: This documents additional properties of any device beyond what
|
||||
# is documented in Documentation/admin-guide/sysfs-rules.rst
|
||||
Note:
|
||||
This documents additional properties of any device beyond what
|
||||
is documented in Documentation/admin-guide/sysfs-rules.rst
|
||||
|
||||
What: /sys/devices/*/of_node
|
||||
Date: February 2015
|
||||
|
|
|
|||
|
|
@ -1,29 +1,29 @@
|
|||
What: sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/cap
|
||||
What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/cap
|
||||
Date: December 3, 2009
|
||||
KernelVersion: 2.6.32
|
||||
Contact: dmaengine@vger.kernel.org
|
||||
Description: Capabilities the DMA supports.Currently there are DMA_PQ, DMA_PQ_VAL,
|
||||
DMA_XOR,DMA_XOR_VAL,DMA_INTERRUPT.
|
||||
|
||||
What: sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_active
|
||||
What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_active
|
||||
Date: December 3, 2009
|
||||
KernelVersion: 2.6.32
|
||||
Contact: dmaengine@vger.kernel.org
|
||||
Description: The number of descriptors active in the ring.
|
||||
|
||||
What: sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_size
|
||||
What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_size
|
||||
Date: December 3, 2009
|
||||
KernelVersion: 2.6.32
|
||||
Contact: dmaengine@vger.kernel.org
|
||||
Description: Descriptor ring size, total number of descriptors available.
|
||||
|
||||
What: sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/version
|
||||
What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/version
|
||||
Date: December 3, 2009
|
||||
KernelVersion: 2.6.32
|
||||
Contact: dmaengine@vger.kernel.org
|
||||
Description: Version of ioatdma device.
|
||||
|
||||
What: sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/intr_coalesce
|
||||
What: /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/intr_coalesce
|
||||
Date: August 8, 2017
|
||||
KernelVersion: 4.14
|
||||
Contact: dmaengine@vger.kernel.org
|
||||
|
|
|
|||
|
|
@ -12,13 +12,15 @@ Description:
|
|||
resets. Three registers are used by the FSBL and
|
||||
other Xilinx software products: GLOBAL_GEN_STORAGE{4:6}.
|
||||
|
||||
Usage:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
Usage::
|
||||
|
||||
Example:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
|
||||
Example::
|
||||
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
|
||||
|
||||
Users: Xilinx
|
||||
|
||||
|
|
@ -39,13 +41,15 @@ Description:
|
|||
software products: PERS_GLOB_GEN_STORAGE{4:7}.
|
||||
Register is reset only by a POR reset.
|
||||
|
||||
Usage:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
Usage::
|
||||
|
||||
Example:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
|
||||
Example::
|
||||
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
|
||||
|
||||
Users: Xilinx
|
||||
|
||||
|
|
@ -61,23 +65,28 @@ Description:
|
|||
|
||||
Following are available shutdown scopes(subtypes):
|
||||
|
||||
subsystem: Only the APU along with all of its peripherals
|
||||
subsystem:
|
||||
Only the APU along with all of its peripherals
|
||||
not used by other processing units will be
|
||||
shut down. This may result in the FPD power
|
||||
domain being shut down provided that no other
|
||||
processing unit uses FPD peripherals or DRAM.
|
||||
ps_only: The complete PS will be shut down, including the
|
||||
ps_only:
|
||||
The complete PS will be shut down, including the
|
||||
RPU, PMU, etc. Only the PL domain (FPGA)
|
||||
remains untouched.
|
||||
system: The complete system/device is shut down.
|
||||
system:
|
||||
The complete system/device is shut down.
|
||||
|
||||
Usage:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
# echo <scope> > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
Usage::
|
||||
|
||||
Example:
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
# echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
# echo <scope> > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
|
||||
Example::
|
||||
|
||||
# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
# echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
|
||||
|
||||
Users: Xilinx
|
||||
|
||||
|
|
@ -94,10 +103,13 @@ Description:
|
|||
system restart.
|
||||
|
||||
Usage:
|
||||
Set healthy bit
|
||||
# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
|
||||
|
||||
Unset healthy bit
|
||||
# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
|
||||
Set healthy bit::
|
||||
|
||||
# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
|
||||
|
||||
Unset healthy bit::
|
||||
|
||||
# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
|
||||
|
||||
Users: Xilinx
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ Description: Interface for making ib_srp connect to a new target.
|
|||
One can request ib_srp to connect to a new target by writing
|
||||
a comma-separated list of login parameters to this sysfs
|
||||
attribute. The supported parameters are:
|
||||
|
||||
* id_ext, a 16-digit hexadecimal number specifying the eight
|
||||
byte identifier extension in the 16-byte SRP target port
|
||||
identifier. The target port identifier is sent by ib_srp
|
||||
|
|
|
|||
|
|
@ -69,6 +69,7 @@ Description: Controls if typing interrupts output from speakup. With
|
|||
speakup if for example
|
||||
the say screen command is used before the
|
||||
entire screen is read.
|
||||
|
||||
With no_interrupt set to one, if the say
|
||||
screen command is used, and one then types on the keyboard,
|
||||
speakup will continue to say the whole screen regardless until
|
||||
|
|
@ -215,8 +216,10 @@ Description: This file contains names for key states.
|
|||
Again, these are part of the help system. For instance, if you
|
||||
had pressed speakup + keypad 3, you would hear:
|
||||
"speakup keypad 3 is go to bottom edge."
|
||||
|
||||
The speakup key is depressed, so the name of the key state is
|
||||
speakup.
|
||||
|
||||
This part of the message comes from the states collection.
|
||||
|
||||
What: /sys/accessibility/speakup/i18n/characters
|
||||
|
|
@ -297,6 +300,7 @@ KernelVersion: 2.6
|
|||
Contact: speakup@linux-speakup.org
|
||||
Description: Controls if punctuation is spoken by speakup, or by the
|
||||
synthesizer.
|
||||
|
||||
For example, speakup speaks ">" as "greater", while
|
||||
the espeak synthesizer used by the soft driver speaks "greater
|
||||
than". Zero lets speakup speak the punctuation. One lets the
|
||||
|
|
|
|||
|
|
@ -17,6 +17,7 @@ Description:
|
|||
directory has a name of the form "<key>-<vendor guid>"
|
||||
and contains the following files:
|
||||
|
||||
=============== ========================================
|
||||
attributes: A read-only text file enumerating the
|
||||
EFI variable flags. Potential values
|
||||
include:
|
||||
|
|
@ -59,12 +60,14 @@ Description:
|
|||
|
||||
size: As ASCII representation of the size of
|
||||
the variable's value.
|
||||
=============== ========================================
|
||||
|
||||
|
||||
In addition, two other magic binary files are provided
|
||||
in the top-level directory and are used for adding and
|
||||
removing variables:
|
||||
|
||||
=============== ========================================
|
||||
new_var: Takes a "struct efi_variable" and
|
||||
instructs the EFI firmware to create a
|
||||
new variable.
|
||||
|
|
@ -73,3 +76,4 @@ Description:
|
|||
instructs the EFI firmware to remove any
|
||||
variable that has a matching vendor GUID
|
||||
and variable key name.
|
||||
=============== ========================================
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ Description:
|
|||
|
||||
This is only for the powerpc/powernv platform.
|
||||
|
||||
=============== ===============================================
|
||||
initiate_dump: When '1' is written to it,
|
||||
we will initiate a dump.
|
||||
Read this file for supported commands.
|
||||
|
|
@ -19,8 +20,11 @@ Description:
|
|||
and ID of the dump, use the id and type files.
|
||||
Do not rely on any particular size of dump
|
||||
type or dump id.
|
||||
=============== ===============================================
|
||||
|
||||
Each dump has the following files:
|
||||
|
||||
=============== ===============================================
|
||||
id: An ASCII representation of the dump ID
|
||||
in hex (e.g. '0x01')
|
||||
type: An ASCII representation of the type of
|
||||
|
|
@ -39,3 +43,4 @@ Description:
|
|||
inaccessible.
|
||||
Reading this file will get a list of
|
||||
supported actions.
|
||||
=============== ===============================================
|
||||
|
|
|
|||
|
|
@ -38,6 +38,7 @@ Description:
|
|||
For each log entry (directory), there are the following
|
||||
files:
|
||||
|
||||
============== ================================================
|
||||
id: An ASCII representation of the ID of the
|
||||
error log, in hex - e.g. "0x01".
|
||||
|
||||
|
|
@ -58,3 +59,4 @@ Description:
|
|||
entry will be removed from sysfs.
|
||||
Reading this file will list the supported
|
||||
operations (currently just acknowledge).
|
||||
============== ================================================
|
||||
|
|
|
|||
|
|
@ -33,6 +33,8 @@ Description: If running under Xen:
|
|||
Space separated list of supported guest system types. Each type
|
||||
is in the format: <class>-<major>.<minor>-<arch>
|
||||
With:
|
||||
|
||||
======== ============================================
|
||||
<class>: "xen" -- x86: paravirtualized, arm: standard
|
||||
"hvm" -- x86 only: fully virtualized
|
||||
<major>: major guest interface version
|
||||
|
|
@ -43,6 +45,7 @@ Description: If running under Xen:
|
|||
"x86_64": 64 bit x86 guest
|
||||
"armv7l": 32 bit arm guest
|
||||
"aarch64": 64 bit arm guest
|
||||
======== ============================================
|
||||
|
||||
What: /sys/hypervisor/properties/changeset
|
||||
Date: March 2009
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
What: vDSO
|
||||
Date: July 2011
|
||||
KernelVersion: 3.0
|
||||
Contact: Andy Lutomirski <luto@kernel.org>
|
||||
Description:
|
||||
|
||||
On some architectures, when the kernel loads any userspace program it
|
||||
maps an ELF DSO into that program's address space. This DSO is called
|
||||
the vDSO and it often contains useful and highly-optimized alternatives
|
||||
|
|
@ -23,6 +29,7 @@ Unless otherwise noted, the set of symbols with any given version and the
|
|||
ABI of those symbols is considered stable. It may vary across architectures,
|
||||
though.
|
||||
|
||||
(As of this writing, this ABI documentation as been confirmed for x86_64.
|
||||
Note:
|
||||
As of this writing, this ABI documentation as been confirmed for x86_64.
|
||||
The maintainers of the other vDSO-using architectures should confirm
|
||||
that it is correct for their architecture.)
|
||||
that it is correct for their architecture.
|
||||
|
|
|
|||
|
|
@ -14,7 +14,8 @@ Description:
|
|||
This group contains the configuration for user defined ACPI
|
||||
tables. The attributes of a user define table are:
|
||||
|
||||
aml - a binary attribute that the user can use to
|
||||
aml
|
||||
- a binary attribute that the user can use to
|
||||
fill in the ACPI aml definitions. Once the aml
|
||||
data is written to this file and the file is
|
||||
closed the table will be loaded and ACPI devices
|
||||
|
|
@ -26,11 +27,26 @@ Description:
|
|||
The rest of the attributes are read-only and are valid only
|
||||
after the table has been loaded by filling the aml entry:
|
||||
|
||||
signature - ASCII table signature
|
||||
length - length of table in bytes, including the header
|
||||
revision - ACPI Specification minor version number
|
||||
oem_id - ASCII OEM identification
|
||||
oem_table_id - ASCII OEM table identification
|
||||
oem_revision - OEM revision number
|
||||
asl_compiler_id - ASCII ASL compiler vendor ID
|
||||
asl_compiler_revision - ASL compiler version
|
||||
signature
|
||||
- ASCII table signature
|
||||
|
||||
length
|
||||
- length of table in bytes, including the header
|
||||
|
||||
revision
|
||||
- ACPI Specification minor version number
|
||||
|
||||
oem_id
|
||||
- ASCII OEM identification
|
||||
|
||||
oem_table_id
|
||||
- ASCII OEM table identification
|
||||
|
||||
oem_revision
|
||||
- OEM revision number
|
||||
|
||||
asl_compiler_id
|
||||
- ASCII ASL compiler vendor ID
|
||||
|
||||
asl_compiler_revision
|
||||
- ASL compiler version
|
||||
|
|
|
|||
|
|
@ -15,22 +15,28 @@ KernelVersion: 5.2
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
buffer_size configure the buffer size for this channel
|
||||
buffer_size
|
||||
configure the buffer size for this channel
|
||||
|
||||
subbuffer_size configure the sub-buffer size for this channel
|
||||
subbuffer_size
|
||||
configure the sub-buffer size for this channel
|
||||
(needed for synchronous and isochrnous data)
|
||||
|
||||
|
||||
num_buffers configure number of buffers used for this
|
||||
num_buffers
|
||||
configure number of buffers used for this
|
||||
channel
|
||||
|
||||
datatype configure type of data that will travel over
|
||||
datatype
|
||||
configure type of data that will travel over
|
||||
this channel
|
||||
|
||||
direction configure whether this link will be an input
|
||||
direction
|
||||
configure whether this link will be an input
|
||||
or output
|
||||
|
||||
dbr_size configure DBR data buffer size (this is used
|
||||
dbr_size
|
||||
configure DBR data buffer size (this is used
|
||||
for MediaLB communication only)
|
||||
|
||||
packets_per_xact
|
||||
|
|
@ -39,18 +45,23 @@ Description:
|
|||
transmitted via USB (this is used for USB
|
||||
communication only)
|
||||
|
||||
device name of the device the link is to be attached to
|
||||
device
|
||||
name of the device the link is to be attached to
|
||||
|
||||
channel name of the channel the link is to be attached to
|
||||
channel
|
||||
name of the channel the link is to be attached to
|
||||
|
||||
comp_params pass parameters needed by some components
|
||||
comp_params
|
||||
pass parameters needed by some components
|
||||
|
||||
create_link write '1' to this attribute to trigger the
|
||||
create_link
|
||||
write '1' to this attribute to trigger the
|
||||
creation of the link. In case of speculative
|
||||
configuration, the creation is post-poned until
|
||||
a physical device is being attached to the bus.
|
||||
|
||||
destroy_link write '1' to this attribute to destroy an
|
||||
destroy_link
|
||||
write '1' to this attribute to destroy an
|
||||
active link
|
||||
|
||||
What: /sys/kernel/config/most_video/<link>
|
||||
|
|
@ -59,22 +70,28 @@ KernelVersion: 5.2
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
buffer_size configure the buffer size for this channel
|
||||
buffer_size
|
||||
configure the buffer size for this channel
|
||||
|
||||
subbuffer_size configure the sub-buffer size for this channel
|
||||
subbuffer_size
|
||||
configure the sub-buffer size for this channel
|
||||
(needed for synchronous and isochrnous data)
|
||||
|
||||
|
||||
num_buffers configure number of buffers used for this
|
||||
num_buffers
|
||||
configure number of buffers used for this
|
||||
channel
|
||||
|
||||
datatype configure type of data that will travel over
|
||||
datatype
|
||||
configure type of data that will travel over
|
||||
this channel
|
||||
|
||||
direction configure whether this link will be an input
|
||||
direction
|
||||
configure whether this link will be an input
|
||||
or output
|
||||
|
||||
dbr_size configure DBR data buffer size (this is used
|
||||
dbr_size
|
||||
configure DBR data buffer size (this is used
|
||||
for MediaLB communication only)
|
||||
|
||||
packets_per_xact
|
||||
|
|
@ -83,18 +100,23 @@ Description:
|
|||
transmitted via USB (this is used for USB
|
||||
communication only)
|
||||
|
||||
device name of the device the link is to be attached to
|
||||
device
|
||||
name of the device the link is to be attached to
|
||||
|
||||
channel name of the channel the link is to be attached to
|
||||
channel
|
||||
name of the channel the link is to be attached to
|
||||
|
||||
comp_params pass parameters needed by some components
|
||||
comp_params
|
||||
pass parameters needed by some components
|
||||
|
||||
create_link write '1' to this attribute to trigger the
|
||||
create_link
|
||||
write '1' to this attribute to trigger the
|
||||
creation of the link. In case of speculative
|
||||
configuration, the creation is post-poned until
|
||||
a physical device is being attached to the bus.
|
||||
|
||||
destroy_link write '1' to this attribute to destroy an
|
||||
destroy_link
|
||||
write '1' to this attribute to destroy an
|
||||
active link
|
||||
|
||||
What: /sys/kernel/config/most_net/<link>
|
||||
|
|
@ -103,22 +125,28 @@ KernelVersion: 5.2
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
buffer_size configure the buffer size for this channel
|
||||
buffer_size
|
||||
configure the buffer size for this channel
|
||||
|
||||
subbuffer_size configure the sub-buffer size for this channel
|
||||
subbuffer_size
|
||||
configure the sub-buffer size for this channel
|
||||
(needed for synchronous and isochrnous data)
|
||||
|
||||
|
||||
num_buffers configure number of buffers used for this
|
||||
num_buffers
|
||||
configure number of buffers used for this
|
||||
channel
|
||||
|
||||
datatype configure type of data that will travel over
|
||||
datatype
|
||||
configure type of data that will travel over
|
||||
this channel
|
||||
|
||||
direction configure whether this link will be an input
|
||||
direction
|
||||
configure whether this link will be an input
|
||||
or output
|
||||
|
||||
dbr_size configure DBR data buffer size (this is used
|
||||
dbr_size
|
||||
configure DBR data buffer size (this is used
|
||||
for MediaLB communication only)
|
||||
|
||||
packets_per_xact
|
||||
|
|
@ -127,18 +155,23 @@ Description:
|
|||
transmitted via USB (this is used for USB
|
||||
communication only)
|
||||
|
||||
device name of the device the link is to be attached to
|
||||
device
|
||||
name of the device the link is to be attached to
|
||||
|
||||
channel name of the channel the link is to be attached to
|
||||
channel
|
||||
name of the channel the link is to be attached to
|
||||
|
||||
comp_params pass parameters needed by some components
|
||||
comp_params
|
||||
pass parameters needed by some components
|
||||
|
||||
create_link write '1' to this attribute to trigger the
|
||||
create_link
|
||||
write '1' to this attribute to trigger the
|
||||
creation of the link. In case of speculative
|
||||
configuration, the creation is post-poned until
|
||||
a physical device is being attached to the bus.
|
||||
|
||||
destroy_link write '1' to this attribute to destroy an
|
||||
destroy_link
|
||||
write '1' to this attribute to destroy an
|
||||
active link
|
||||
|
||||
What: /sys/kernel/config/most_sound/<card>
|
||||
|
|
@ -147,7 +180,8 @@ KernelVersion: 5.2
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
create_card write '1' to this attribute to trigger the
|
||||
create_card
|
||||
write '1' to this attribute to trigger the
|
||||
registration of the sound card with the ALSA
|
||||
subsystem.
|
||||
|
||||
|
|
@ -157,22 +191,28 @@ KernelVersion: 5.2
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
buffer_size configure the buffer size for this channel
|
||||
buffer_size
|
||||
configure the buffer size for this channel
|
||||
|
||||
subbuffer_size configure the sub-buffer size for this channel
|
||||
subbuffer_size
|
||||
configure the sub-buffer size for this channel
|
||||
(needed for synchronous and isochrnous data)
|
||||
|
||||
|
||||
num_buffers configure number of buffers used for this
|
||||
num_buffers
|
||||
configure number of buffers used for this
|
||||
channel
|
||||
|
||||
datatype configure type of data that will travel over
|
||||
datatype
|
||||
configure type of data that will travel over
|
||||
this channel
|
||||
|
||||
direction configure whether this link will be an input
|
||||
direction
|
||||
configure whether this link will be an input
|
||||
or output
|
||||
|
||||
dbr_size configure DBR data buffer size (this is used
|
||||
dbr_size
|
||||
configure DBR data buffer size (this is used
|
||||
for MediaLB communication only)
|
||||
|
||||
packets_per_xact
|
||||
|
|
@ -181,16 +221,21 @@ Description:
|
|||
transmitted via USB (this is used for USB
|
||||
communication only)
|
||||
|
||||
device name of the device the link is to be attached to
|
||||
device
|
||||
name of the device the link is to be attached to
|
||||
|
||||
channel name of the channel the link is to be attached to
|
||||
channel
|
||||
name of the channel the link is to be attached to
|
||||
|
||||
comp_params pass parameters needed by some components
|
||||
comp_params
|
||||
pass parameters needed by some components
|
||||
|
||||
create_link write '1' to this attribute to trigger the
|
||||
create_link
|
||||
write '1' to this attribute to trigger the
|
||||
creation of the link. In case of speculative
|
||||
configuration, the creation is post-poned until
|
||||
a physical device is being attached to the bus.
|
||||
|
||||
destroy_link write '1' to this attribute to destroy an
|
||||
destroy_link
|
||||
write '1' to this attribute to destroy an
|
||||
active link
|
||||
|
|
|
|||
|
|
@ -10,22 +10,24 @@ Description:
|
|||
This interfaces can be used to show spear's PCIe device capability.
|
||||
|
||||
Nodes are only visible when configfs is mounted. To mount configfs
|
||||
in /config directory use:
|
||||
# mount -t configfs none /config/
|
||||
in /config directory use::
|
||||
|
||||
For nth PCIe Device Controller
|
||||
/config/pcie-gadget.n/
|
||||
link ... used to enable ltssm and read its status.
|
||||
int_type ...used to configure and read type of supported
|
||||
interrupt
|
||||
no_of_msi ... used to configure number of MSI vector needed and
|
||||
# mount -t configfs none /config/
|
||||
|
||||
For nth PCIe Device Controller /config/pcie-gadget.n/:
|
||||
|
||||
=============== ======================================================
|
||||
link used to enable ltssm and read its status.
|
||||
int_type used to configure and read type of supported interrupt
|
||||
no_of_msi used to configure number of MSI vector needed and
|
||||
to read no of MSI granted.
|
||||
inta ... write 1 to assert INTA and 0 to de-assert.
|
||||
send_msi ... write MSI vector to be sent.
|
||||
vendor_id ... used to write and read vendor id (hex)
|
||||
device_id ... used to write and read device id (hex)
|
||||
bar0_size ... used to write and read bar0_size
|
||||
bar0_address ... used to write and read bar0 mapped area in hex.
|
||||
bar0_rw_offset ... used to write and read offset of bar0 where
|
||||
bar0_data will be written or read.
|
||||
bar0_data ... used to write and read data at bar0_rw_offset.
|
||||
inta write 1 to assert INTA and 0 to de-assert.
|
||||
send_msi write MSI vector to be sent.
|
||||
vendor_id used to write and read vendor id (hex)
|
||||
device_id used to write and read device id (hex)
|
||||
bar0_size used to write and read bar0_size
|
||||
bar0_address used to write and read bar0 mapped area in hex.
|
||||
bar0_rw_offset used to write and read offset of bar0 where bar0_data
|
||||
will be written or read.
|
||||
bar0_data used to write and read data at bar0_rw_offset.
|
||||
=============== ======================================================
|
||||
|
|
|
|||
|
|
@ -12,22 +12,24 @@ Description:
|
|||
|
||||
The attributes of a gadget:
|
||||
|
||||
UDC - bind a gadget to UDC/unbind a gadget;
|
||||
write UDC's name found in /sys/class/udc/*
|
||||
to bind a gadget, empty string "" to unbind.
|
||||
================ ============================================
|
||||
UDC bind a gadget to UDC/unbind a gadget;
|
||||
write UDC's name found in /sys/class/udc/*
|
||||
to bind a gadget, empty string "" to unbind.
|
||||
|
||||
max_speed - maximum speed the driver supports. Valid
|
||||
names are super-speed-plus, super-speed,
|
||||
high-speed, full-speed, and low-speed.
|
||||
max_speed maximum speed the driver supports. Valid
|
||||
names are super-speed-plus, super-speed,
|
||||
high-speed, full-speed, and low-speed.
|
||||
|
||||
bDeviceClass - USB device class code
|
||||
bDeviceSubClass - USB device subclass code
|
||||
bDeviceProtocol - USB device protocol code
|
||||
bMaxPacketSize0 - maximum endpoint 0 packet size
|
||||
bcdDevice - bcd device release number
|
||||
bcdUSB - bcd USB specification version number
|
||||
idProduct - product ID
|
||||
idVendor - vendor ID
|
||||
bDeviceClass USB device class code
|
||||
bDeviceSubClass USB device subclass code
|
||||
bDeviceProtocol USB device protocol code
|
||||
bMaxPacketSize0 maximum endpoint 0 packet size
|
||||
bcdDevice bcd device release number
|
||||
bcdUSB bcd USB specification version number
|
||||
idProduct product ID
|
||||
idVendor vendor ID
|
||||
================ ============================================
|
||||
|
||||
What: /config/usb-gadget/gadget/configs
|
||||
Date: Jun 2013
|
||||
|
|
@ -41,8 +43,10 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes of a configuration:
|
||||
|
||||
bmAttributes - configuration characteristics
|
||||
MaxPower - maximum power consumption from the bus
|
||||
================ ======================================
|
||||
bmAttributes configuration characteristics
|
||||
MaxPower maximum power consumption from the bus
|
||||
================ ======================================
|
||||
|
||||
What: /config/usb-gadget/gadget/configs/config/strings
|
||||
Date: Jun 2013
|
||||
|
|
@ -57,7 +61,9 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
configuration - configuration description
|
||||
================ =========================
|
||||
configuration configuration description
|
||||
================ =========================
|
||||
|
||||
|
||||
What: /config/usb-gadget/gadget/functions
|
||||
|
|
@ -76,8 +82,10 @@ Description:
|
|||
|
||||
The attributes:
|
||||
|
||||
compatible_id - 8-byte string for "Compatible ID"
|
||||
sub_compatible_id - 8-byte string for "Sub Compatible ID"
|
||||
================= =====================================
|
||||
compatible_id 8-byte string for "Compatible ID"
|
||||
sub_compatible_id 8-byte string for "Sub Compatible ID"
|
||||
================= =====================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>
|
||||
Date: May 2014
|
||||
|
|
@ -89,16 +97,19 @@ Description:
|
|||
|
||||
The attributes:
|
||||
|
||||
type - value 1..7 for interpreting the data
|
||||
1: unicode string
|
||||
2: unicode string with environment variable
|
||||
3: binary
|
||||
4: little-endian 32-bit
|
||||
5: big-endian 32-bit
|
||||
6: unicode string with a symbolic link
|
||||
7: multiple unicode strings
|
||||
data - blob of data to be interpreted depending on
|
||||
===== ===============================================
|
||||
type value 1..7 for interpreting the data
|
||||
|
||||
- 1: unicode string
|
||||
- 2: unicode string with environment variable
|
||||
- 3: binary
|
||||
- 4: little-endian 32-bit
|
||||
- 5: big-endian 32-bit
|
||||
- 6: unicode string with a symbolic link
|
||||
- 7: multiple unicode strings
|
||||
data blob of data to be interpreted depending on
|
||||
type
|
||||
===== ===============================================
|
||||
|
||||
What: /config/usb-gadget/gadget/strings
|
||||
Date: Jun 2013
|
||||
|
|
@ -113,9 +124,11 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
serialnumber - gadget's serial number (string)
|
||||
product - gadget's product description
|
||||
manufacturer - gadget's manufacturer description
|
||||
============ =================================
|
||||
serialnumber gadget's serial number (string)
|
||||
product gadget's product description
|
||||
manufacturer gadget's manufacturer description
|
||||
============ =================================
|
||||
|
||||
What: /config/usb-gadget/gadget/os_desc
|
||||
Date: May 2014
|
||||
|
|
@ -123,8 +136,10 @@ KernelVersion: 3.16
|
|||
Description:
|
||||
This group contains "OS String" extension handling attributes.
|
||||
|
||||
use - flag turning "OS Desctiptors" support on/off
|
||||
b_vendor_code - one-byte value used for custom per-device and
|
||||
============= ===============================================
|
||||
use flag turning "OS Desctiptors" support on/off
|
||||
b_vendor_code one-byte value used for custom per-device and
|
||||
per-interface requests
|
||||
qw_sign - an identifier to be reported as "OS String"
|
||||
qw_sign an identifier to be reported as "OS String"
|
||||
proper
|
||||
============= ===============================================
|
||||
|
|
|
|||
|
|
@ -4,13 +4,17 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
ifname - network device interface name associated with
|
||||
ifname
|
||||
- network device interface name associated with
|
||||
this function instance
|
||||
qmult - queue length multiplier for high and
|
||||
qmult
|
||||
- queue length multiplier for high and
|
||||
super speed
|
||||
host_addr - MAC address of host's end of this
|
||||
host_addr
|
||||
- MAC address of host's end of this
|
||||
Ethernet over USB link
|
||||
dev_addr - MAC address of device's end of this
|
||||
dev_addr
|
||||
- MAC address of device's end of this
|
||||
Ethernet over USB link
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -4,11 +4,13 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
ifname - network device interface name associated with
|
||||
========== =============================================
|
||||
ifname network device interface name associated with
|
||||
this function instance
|
||||
qmult - queue length multiplier for high and
|
||||
qmult queue length multiplier for high and
|
||||
super speed
|
||||
host_addr - MAC address of host's end of this
|
||||
host_addr MAC address of host's end of this
|
||||
Ethernet over USB link
|
||||
dev_addr - MAC address of device's end of this
|
||||
dev_addr MAC address of device's end of this
|
||||
Ethernet over USB link
|
||||
========== =============================================
|
||||
|
|
|
|||
|
|
@ -4,8 +4,10 @@ KernelVersion: 3.19
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
protocol - HID protocol to use
|
||||
report_desc - blob corresponding to HID report descriptors
|
||||
============= ============================================
|
||||
protocol HID protocol to use
|
||||
report_desc blob corresponding to HID report descriptors
|
||||
except the data passed through /dev/hidg<N>
|
||||
report_length - HID report length
|
||||
subclass - HID device subclass to use
|
||||
report_length HID report length
|
||||
subclass HID device subclass to use
|
||||
============= ============================================
|
||||
|
|
|
|||
|
|
@ -4,5 +4,7 @@ KernelVersion: 3.13
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
qlen - depth of loopback queue
|
||||
buflen - buffer length
|
||||
======= =======================
|
||||
qlen depth of loopback queue
|
||||
buflen buffer length
|
||||
======= =======================
|
||||
|
|
|
|||
|
|
@ -4,12 +4,14 @@ KernelVersion: 3.13
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
stall - Set to permit function to halt bulk endpoints.
|
||||
=========== ==============================================
|
||||
stall Set to permit function to halt bulk endpoints.
|
||||
Disabled on some USB devices known not to work
|
||||
correctly. You should set it to true.
|
||||
num_buffers - Number of pipeline buffers. Valid numbers
|
||||
num_buffers Number of pipeline buffers. Valid numbers
|
||||
are 2..4. Available only if
|
||||
CONFIG_USB_GADGET_DEBUG_FILES is set.
|
||||
=========== ==============================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/mass_storage.name/lun.name
|
||||
Date: Oct 2013
|
||||
|
|
@ -17,15 +19,17 @@ KernelVersion: 3.13
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
file - The path to the backing file for the LUN.
|
||||
=========== ==============================================
|
||||
file The path to the backing file for the LUN.
|
||||
Required if LUN is not marked as removable.
|
||||
ro - Flag specifying access to the LUN shall be
|
||||
ro Flag specifying access to the LUN shall be
|
||||
read-only. This is implied if CD-ROM emulation
|
||||
is enabled as well as when it was impossible
|
||||
to open "filename" in R/W mode.
|
||||
removable - Flag specifying that LUN shall be indicated as
|
||||
removable Flag specifying that LUN shall be indicated as
|
||||
being removable.
|
||||
cdrom - Flag specifying that LUN shall be reported as
|
||||
cdrom Flag specifying that LUN shall be reported as
|
||||
being a CD-ROM.
|
||||
nofua - Flag specifying that FUA flag
|
||||
nofua Flag specifying that FUA flag
|
||||
in SCSI WRITE(10,12)
|
||||
=========== ==============================================
|
||||
|
|
|
|||
|
|
@ -4,9 +4,11 @@ KernelVersion: 3.19
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
index - index value for the USB MIDI adapter
|
||||
id - ID string for the USB MIDI adapter
|
||||
buflen - MIDI buffer length
|
||||
qlen - USB read request queue length
|
||||
in_ports - number of MIDI input ports
|
||||
out_ports - number of MIDI output ports
|
||||
========== ====================================
|
||||
index index value for the USB MIDI adapter
|
||||
id ID string for the USB MIDI adapter
|
||||
buflen MIDI buffer length
|
||||
qlen USB read request queue length
|
||||
in_ports number of MIDI input ports
|
||||
out_ports number of MIDI output ports
|
||||
========== ====================================
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ KernelVersion: 4.1
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
pnp_string - Data to be passed to the host in pnp string
|
||||
q_len - Number of requests per endpoint
|
||||
========== ===========================================
|
||||
pnp_string Data to be passed to the host in pnp string
|
||||
q_len Number of requests per endpoint
|
||||
========== ===========================================
|
||||
|
||||
|
|
|
|||
|
|
@ -4,14 +4,16 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
ifname - network device interface name associated with
|
||||
========= =============================================
|
||||
ifname network device interface name associated with
|
||||
this function instance
|
||||
qmult - queue length multiplier for high and
|
||||
qmult queue length multiplier for high and
|
||||
super speed
|
||||
host_addr - MAC address of host's end of this
|
||||
host_addr MAC address of host's end of this
|
||||
Ethernet over USB link
|
||||
dev_addr - MAC address of device's end of this
|
||||
dev_addr MAC address of device's end of this
|
||||
Ethernet over USB link
|
||||
class - USB interface class, default is 02 (hex)
|
||||
subclass - USB interface subclass, default is 06 (hex)
|
||||
protocol - USB interface protocol, default is 00 (hex)
|
||||
class USB interface class, default is 02 (hex)
|
||||
subclass USB interface subclass, default is 06 (hex)
|
||||
protocol USB interface protocol, default is 00 (hex)
|
||||
========= =============================================
|
||||
|
|
|
|||
|
|
@ -4,11 +4,13 @@ KernelVersion: 3.13
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
pattern - 0 (all zeros), 1 (mod63), 2 (none)
|
||||
isoc_interval - 1..16
|
||||
isoc_maxpacket - 0 - 1023 (fs), 0 - 1024 (hs/ss)
|
||||
isoc_mult - 0..2 (hs/ss only)
|
||||
isoc_maxburst - 0..15 (ss only)
|
||||
buflen - buffer length
|
||||
bulk_qlen - depth of queue for bulk
|
||||
iso_qlen - depth of queue for iso
|
||||
============== ==================================
|
||||
pattern 0 (all zeros), 1 (mod63), 2 (none)
|
||||
isoc_interval 1..16
|
||||
isoc_maxpacket 0 - 1023 (fs), 0 - 1024 (hs/ss)
|
||||
isoc_mult 0..2 (hs/ss only)
|
||||
isoc_maxburst 0..15 (ss only)
|
||||
buflen buffer length
|
||||
bulk_qlen depth of queue for bulk
|
||||
iso_qlen depth of queue for iso
|
||||
============== ==================================
|
||||
|
|
|
|||
|
|
@ -4,11 +4,13 @@ KernelVersion: 3.11
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
ifname - network device interface name associated with
|
||||
========== =============================================
|
||||
ifname network device interface name associated with
|
||||
this function instance
|
||||
qmult - queue length multiplier for high and
|
||||
qmult queue length multiplier for high and
|
||||
super speed
|
||||
host_addr - MAC address of host's end of this
|
||||
host_addr MAC address of host's end of this
|
||||
Ethernet over USB link
|
||||
dev_addr - MAC address of device's end of this
|
||||
dev_addr MAC address of device's end of this
|
||||
Ethernet over USB link
|
||||
========== =============================================
|
||||
|
|
|
|||
|
|
@ -4,11 +4,13 @@ KernelVersion: 4.14
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
c_chmask - capture channel mask
|
||||
c_srate - capture sampling rate
|
||||
c_ssize - capture sample size (bytes)
|
||||
p_chmask - playback channel mask
|
||||
p_srate - playback sampling rate
|
||||
p_ssize - playback sample size (bytes)
|
||||
req_number - the number of pre-allocated request
|
||||
for both capture and playback
|
||||
========== ===================================
|
||||
c_chmask capture channel mask
|
||||
c_srate capture sampling rate
|
||||
c_ssize capture sample size (bytes)
|
||||
p_chmask playback channel mask
|
||||
p_srate playback sampling rate
|
||||
p_ssize playback sample size (bytes)
|
||||
req_number the number of pre-allocated request
|
||||
for both capture and playback
|
||||
========== ===================================
|
||||
|
|
|
|||
|
|
@ -4,9 +4,11 @@ KernelVersion: 3.18
|
|||
Description:
|
||||
The attributes:
|
||||
|
||||
c_chmask - capture channel mask
|
||||
c_srate - capture sampling rate
|
||||
c_ssize - capture sample size (bytes)
|
||||
p_chmask - playback channel mask
|
||||
p_srate - playback sampling rate
|
||||
p_ssize - playback sample size (bytes)
|
||||
========= ============================
|
||||
c_chmask capture channel mask
|
||||
c_srate capture sampling rate
|
||||
c_ssize capture sample size (bytes)
|
||||
p_chmask playback channel mask
|
||||
p_srate playback sampling rate
|
||||
p_ssize playback sample size (bytes)
|
||||
========= ============================
|
||||
|
|
|
|||
|
|
@ -3,9 +3,11 @@ Date: Dec 2014
|
|||
KernelVersion: 4.0
|
||||
Description: UVC function directory
|
||||
|
||||
streaming_maxburst - 0..15 (ss only)
|
||||
streaming_maxpacket - 1..1023 (fs), 1..3072 (hs/ss)
|
||||
streaming_interval - 1..16
|
||||
=================== =============================
|
||||
streaming_maxburst 0..15 (ss only)
|
||||
streaming_maxpacket 1..1023 (fs), 1..3072 (hs/ss)
|
||||
streaming_interval 1..16
|
||||
=================== =============================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/control
|
||||
Date: Dec 2014
|
||||
|
|
@ -13,8 +15,11 @@ KernelVersion: 4.0
|
|||
Description: Control descriptors
|
||||
|
||||
All attributes read only:
|
||||
bInterfaceNumber - USB interface number for this
|
||||
streaming interface
|
||||
|
||||
================ =============================
|
||||
bInterfaceNumber USB interface number for this
|
||||
streaming interface
|
||||
================ =============================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/control/class
|
||||
Date: Dec 2014
|
||||
|
|
@ -47,13 +52,16 @@ KernelVersion: 4.0
|
|||
Description: Default output terminal descriptors
|
||||
|
||||
All attributes read only:
|
||||
iTerminal - index of string descriptor
|
||||
bSourceID - id of the terminal to which this terminal
|
||||
|
||||
============== =============================================
|
||||
iTerminal index of string descriptor
|
||||
bSourceID id of the terminal to which this terminal
|
||||
is connected
|
||||
bAssocTerminal - id of the input terminal to which this output
|
||||
bAssocTerminal id of the input terminal to which this output
|
||||
terminal is associated
|
||||
wTerminalType - terminal type
|
||||
bTerminalID - a non-zero id of this terminal
|
||||
wTerminalType terminal type
|
||||
bTerminalID a non-zero id of this terminal
|
||||
============== =============================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
|
||||
Date: Dec 2014
|
||||
|
|
@ -66,16 +74,19 @@ KernelVersion: 4.0
|
|||
Description: Default camera terminal descriptors
|
||||
|
||||
All attributes read only:
|
||||
bmControls - bitmap specifying which controls are
|
||||
supported for the video stream
|
||||
wOcularFocalLength - the value of Locular
|
||||
wObjectiveFocalLengthMax- the value of Lmin
|
||||
wObjectiveFocalLengthMin- the value of Lmax
|
||||
iTerminal - index of string descriptor
|
||||
bAssocTerminal - id of the output terminal to which
|
||||
this terminal is connected
|
||||
wTerminalType - terminal type
|
||||
bTerminalID - a non-zero id of this terminal
|
||||
|
||||
======================== ====================================
|
||||
bmControls bitmap specifying which controls are
|
||||
supported for the video stream
|
||||
wOcularFocalLength the value of Locular
|
||||
wObjectiveFocalLengthMax the value of Lmin
|
||||
wObjectiveFocalLengthMin the value of Lmax
|
||||
iTerminal index of string descriptor
|
||||
bAssocTerminal id of the output terminal to which
|
||||
this terminal is connected
|
||||
wTerminalType terminal type
|
||||
bTerminalID a non-zero id of this terminal
|
||||
======================== ====================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/control/processing
|
||||
Date: Dec 2014
|
||||
|
|
@ -88,13 +99,16 @@ KernelVersion: 4.0
|
|||
Description: Default processing unit descriptors
|
||||
|
||||
All attributes read only:
|
||||
iProcessing - index of string descriptor
|
||||
bmControls - bitmap specifying which controls are
|
||||
|
||||
=============== ========================================
|
||||
iProcessing index of string descriptor
|
||||
bmControls bitmap specifying which controls are
|
||||
supported for the video stream
|
||||
wMaxMultiplier - maximum digital magnification x100
|
||||
bSourceID - id of the terminal to which this unit is
|
||||
wMaxMultiplier maximum digital magnification x100
|
||||
bSourceID id of the terminal to which this unit is
|
||||
connected
|
||||
bUnitID - a non-zero id of this unit
|
||||
bUnitID a non-zero id of this unit
|
||||
=============== ========================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/control/header
|
||||
Date: Dec 2014
|
||||
|
|
@ -114,8 +128,11 @@ KernelVersion: 4.0
|
|||
Description: Streaming descriptors
|
||||
|
||||
All attributes read only:
|
||||
bInterfaceNumber - USB interface number for this
|
||||
streaming interface
|
||||
|
||||
================ =============================
|
||||
bInterfaceNumber USB interface number for this
|
||||
streaming interface
|
||||
================ =============================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class
|
||||
Date: Dec 2014
|
||||
|
|
@ -148,13 +165,16 @@ KernelVersion: 4.0
|
|||
Description: Default color matching descriptors
|
||||
|
||||
All attributes read only:
|
||||
bMatrixCoefficients - matrix used to compute luma and
|
||||
chroma values from the color primaries
|
||||
bTransferCharacteristics- optoelectronic transfer
|
||||
characteristic of the source picutre,
|
||||
also called the gamma function
|
||||
bColorPrimaries - color primaries and the reference
|
||||
white
|
||||
|
||||
======================== ======================================
|
||||
bMatrixCoefficients matrix used to compute luma and
|
||||
chroma values from the color primaries
|
||||
bTransferCharacteristics optoelectronic transfer
|
||||
characteristic of the source picutre,
|
||||
also called the gamma function
|
||||
bColorPrimaries color primaries and the reference
|
||||
white
|
||||
======================== ======================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg
|
||||
Date: Dec 2014
|
||||
|
|
@ -168,47 +188,52 @@ Description: Specific MJPEG format descriptors
|
|||
|
||||
All attributes read only,
|
||||
except bmaControls and bDefaultFrameIndex:
|
||||
bFormatIndex - unique id for this format descriptor;
|
||||
|
||||
=================== =====================================
|
||||
bFormatIndex unique id for this format descriptor;
|
||||
only defined after parent header is
|
||||
linked into the streaming class;
|
||||
read-only
|
||||
bmaControls - this format's data for bmaControls in
|
||||
bmaControls this format's data for bmaControls in
|
||||
the streaming header
|
||||
bmInterfaceFlags - specifies interlace information,
|
||||
bmInterfaceFlags specifies interlace information,
|
||||
read-only
|
||||
bAspectRatioY - the X dimension of the picture aspect
|
||||
bAspectRatioY the X dimension of the picture aspect
|
||||
ratio, read-only
|
||||
bAspectRatioX - the Y dimension of the picture aspect
|
||||
bAspectRatioX the Y dimension of the picture aspect
|
||||
ratio, read-only
|
||||
bmFlags - characteristics of this format,
|
||||
bmFlags characteristics of this format,
|
||||
read-only
|
||||
bDefaultFrameIndex - optimum frame index for this stream
|
||||
bDefaultFrameIndex optimum frame index for this stream
|
||||
=================== =====================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name/name
|
||||
Date: Dec 2014
|
||||
KernelVersion: 4.0
|
||||
Description: Specific MJPEG frame descriptors
|
||||
|
||||
bFrameIndex - unique id for this framedescriptor;
|
||||
only defined after parent format is
|
||||
linked into the streaming header;
|
||||
read-only
|
||||
dwFrameInterval - indicates how frame interval can be
|
||||
programmed; a number of values
|
||||
separated by newline can be specified
|
||||
dwDefaultFrameInterval - the frame interval the device would
|
||||
like to use as default
|
||||
dwMaxVideoFrameBufferSize- the maximum number of bytes the
|
||||
compressor will produce for a video
|
||||
frame or still image
|
||||
dwMaxBitRate - the maximum bit rate at the shortest
|
||||
frame interval in bps
|
||||
dwMinBitRate - the minimum bit rate at the longest
|
||||
frame interval in bps
|
||||
wHeight - height of decoded bitmap frame in px
|
||||
wWidth - width of decoded bitmam frame in px
|
||||
bmCapabilities - still image support, fixed frame-rate
|
||||
support
|
||||
========================= =====================================
|
||||
bFrameIndex unique id for this framedescriptor;
|
||||
only defined after parent format is
|
||||
linked into the streaming header;
|
||||
read-only
|
||||
dwFrameInterval indicates how frame interval can be
|
||||
programmed; a number of values
|
||||
separated by newline can be specified
|
||||
dwDefaultFrameInterval the frame interval the device would
|
||||
like to use as default
|
||||
dwMaxVideoFrameBufferSize the maximum number of bytes the
|
||||
compressor will produce for a video
|
||||
frame or still image
|
||||
dwMaxBitRate the maximum bit rate at the shortest
|
||||
frame interval in bps
|
||||
dwMinBitRate the minimum bit rate at the longest
|
||||
frame interval in bps
|
||||
wHeight height of decoded bitmap frame in px
|
||||
wWidth width of decoded bitmam frame in px
|
||||
bmCapabilities still image support, fixed frame-rate
|
||||
support
|
||||
========================= =====================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed
|
||||
Date: Dec 2014
|
||||
|
|
@ -220,50 +245,54 @@ Date: Dec 2014
|
|||
KernelVersion: 4.0
|
||||
Description: Specific uncompressed format descriptors
|
||||
|
||||
bFormatIndex - unique id for this format descriptor;
|
||||
================== =======================================
|
||||
bFormatIndex unique id for this format descriptor;
|
||||
only defined after parent header is
|
||||
linked into the streaming class;
|
||||
read-only
|
||||
bmaControls - this format's data for bmaControls in
|
||||
bmaControls this format's data for bmaControls in
|
||||
the streaming header
|
||||
bmInterfaceFlags - specifies interlace information,
|
||||
bmInterfaceFlags specifies interlace information,
|
||||
read-only
|
||||
bAspectRatioY - the X dimension of the picture aspect
|
||||
bAspectRatioY the X dimension of the picture aspect
|
||||
ratio, read-only
|
||||
bAspectRatioX - the Y dimension of the picture aspect
|
||||
bAspectRatioX the Y dimension of the picture aspect
|
||||
ratio, read-only
|
||||
bDefaultFrameIndex - optimum frame index for this stream
|
||||
bBitsPerPixel - number of bits per pixel used to
|
||||
bDefaultFrameIndex optimum frame index for this stream
|
||||
bBitsPerPixel number of bits per pixel used to
|
||||
specify color in the decoded video
|
||||
frame
|
||||
guidFormat - globally unique id used to identify
|
||||
guidFormat globally unique id used to identify
|
||||
stream-encoding format
|
||||
================== =======================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name/name
|
||||
Date: Dec 2014
|
||||
KernelVersion: 4.0
|
||||
Description: Specific uncompressed frame descriptors
|
||||
|
||||
bFrameIndex - unique id for this framedescriptor;
|
||||
only defined after parent format is
|
||||
linked into the streaming header;
|
||||
read-only
|
||||
dwFrameInterval - indicates how frame interval can be
|
||||
programmed; a number of values
|
||||
separated by newline can be specified
|
||||
dwDefaultFrameInterval - the frame interval the device would
|
||||
like to use as default
|
||||
dwMaxVideoFrameBufferSize- the maximum number of bytes the
|
||||
compressor will produce for a video
|
||||
frame or still image
|
||||
dwMaxBitRate - the maximum bit rate at the shortest
|
||||
frame interval in bps
|
||||
dwMinBitRate - the minimum bit rate at the longest
|
||||
frame interval in bps
|
||||
wHeight - height of decoded bitmap frame in px
|
||||
wWidth - width of decoded bitmam frame in px
|
||||
bmCapabilities - still image support, fixed frame-rate
|
||||
support
|
||||
========================= =====================================
|
||||
bFrameIndex unique id for this framedescriptor;
|
||||
only defined after parent format is
|
||||
linked into the streaming header;
|
||||
read-only
|
||||
dwFrameInterval indicates how frame interval can be
|
||||
programmed; a number of values
|
||||
separated by newline can be specified
|
||||
dwDefaultFrameInterval the frame interval the device would
|
||||
like to use as default
|
||||
dwMaxVideoFrameBufferSize the maximum number of bytes the
|
||||
compressor will produce for a video
|
||||
frame or still image
|
||||
dwMaxBitRate the maximum bit rate at the shortest
|
||||
frame interval in bps
|
||||
dwMinBitRate the minimum bit rate at the longest
|
||||
frame interval in bps
|
||||
wHeight height of decoded bitmap frame in px
|
||||
wWidth width of decoded bitmam frame in px
|
||||
bmCapabilities still image support, fixed frame-rate
|
||||
support
|
||||
========================= =====================================
|
||||
|
||||
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header
|
||||
Date: Dec 2014
|
||||
|
|
@ -276,17 +305,20 @@ KernelVersion: 4.0
|
|||
Description: Specific streaming header descriptors
|
||||
|
||||
All attributes read only:
|
||||
bTriggerUsage - how the host software will respond to
|
||||
|
||||
==================== =====================================
|
||||
bTriggerUsage how the host software will respond to
|
||||
a hardware trigger interrupt event
|
||||
bTriggerSupport - flag specifying if hardware
|
||||
bTriggerSupport flag specifying if hardware
|
||||
triggering is supported
|
||||
bStillCaptureMethod - method of still image caputre
|
||||
bStillCaptureMethod method of still image caputre
|
||||
supported
|
||||
bTerminalLink - id of the output terminal to which
|
||||
bTerminalLink id of the output terminal to which
|
||||
the video endpoint of this interface
|
||||
is connected
|
||||
bmInfo - capabilities of this video streaming
|
||||
bmInfo capabilities of this video streaming
|
||||
interface
|
||||
==================== =====================================
|
||||
|
||||
What: /sys/class/udc/udc.name/device/gadget/video4linux/video.name/function_name
|
||||
Date: May 2018
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ error injections without having to know the details of the driver-specific
|
|||
commands.
|
||||
|
||||
Note that the output of 'error-inj' shall be valid as input to 'error-inj'.
|
||||
So this must work:
|
||||
So this must work::
|
||||
|
||||
$ cat error-inj >einj.txt
|
||||
$ cat einj.txt >error-inj
|
||||
|
|
|
|||
|
|
@ -20,9 +20,13 @@ Description: Allow the root user to disable/enable in runtime the clock
|
|||
The user can supply a bitmask value, each bit represents
|
||||
a different engine to disable/enable its clock gating feature.
|
||||
The bitmask is composed of 20 bits:
|
||||
0 - 7 : DMA channels
|
||||
8 - 11 : MME engines
|
||||
12 - 19 : TPC engines
|
||||
|
||||
======= ============
|
||||
0 - 7 DMA channels
|
||||
8 - 11 MME engines
|
||||
12 - 19 TPC engines
|
||||
======= ============
|
||||
|
||||
The bit's location of a specific engine can be determined
|
||||
using (1 << GAUDI_ENGINE_ID_*). GAUDI_ENGINE_ID_* values
|
||||
are defined in uapi habanalabs.h file in enum gaudi_engine_id
|
||||
|
|
@ -59,6 +63,7 @@ Description: Allows the root user to read or write directly through the
|
|||
the generic Linux user-space PCI mapping) because the DDR bar
|
||||
is very small compared to the DDR memory and only the driver can
|
||||
move the bar before and after the transaction.
|
||||
|
||||
If the IOMMU is disabled, it also allows the root user to read
|
||||
or write from the host a device VA of a host mapped memory
|
||||
|
||||
|
|
@ -73,6 +78,7 @@ Description: Allows the root user to read or write 64 bit data directly
|
|||
the generic Linux user-space PCI mapping) because the DDR bar
|
||||
is very small compared to the DDR memory and only the driver can
|
||||
move the bar before and after the transaction.
|
||||
|
||||
If the IOMMU is disabled, it also allows the root user to read
|
||||
or write from the host a device VA of a host mapped memory
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Description:
|
|||
General information like which GPE is assigned to the EC and whether
|
||||
the global lock should get used.
|
||||
Knowing the EC GPE one can watch the amount of HW events related to
|
||||
the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
|
||||
the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
|
||||
/sys/firmware/acpi/interrupts/gpeXY
|
||||
|
||||
The io file is binary and a userspace tool located here:
|
||||
|
|
@ -14,7 +14,8 @@ ftp://ftp.suse.com/pub/people/trenn/sources/ec/
|
|||
should get used to read out the 256 Embedded Controller registers
|
||||
or writing to them.
|
||||
|
||||
CAUTION: Do not write to the Embedded Controller if you don't know
|
||||
what you are doing! Rebooting afterwards also is a good idea.
|
||||
This can influence the way your machine is cooled and fans may
|
||||
not get switched on again after you did a wrong write.
|
||||
CAUTION:
|
||||
Do not write to the Embedded Controller if you don't know
|
||||
what you are doing! Rebooting afterwards also is a good idea.
|
||||
This can influence the way your machine is cooled and fans may
|
||||
not get switched on again after you did a wrong write.
|
||||
|
|
|
|||
|
|
@ -2,13 +2,19 @@ What: /sys/kernel/debug/moxtet/input
|
|||
Date: March 2019
|
||||
KernelVersion: 5.3
|
||||
Contact: Marek Behún <marek.behun@nic.cz>
|
||||
Description: (R) Read input from the shift registers, in hexadecimal.
|
||||
Description: (Read) Read input from the shift registers, in hexadecimal.
|
||||
Returns N+1 bytes, where N is the number of Moxtet connected
|
||||
modules. The first byte is from the CPU board itself.
|
||||
Example: 101214
|
||||
10: CPU board with SD card
|
||||
12: 2 = PCIe module, 1 = IRQ not active
|
||||
14: 4 = Peridot module, 1 = IRQ not active
|
||||
|
||||
Example::
|
||||
|
||||
101214
|
||||
|
||||
== =======================================
|
||||
10 CPU board with SD card
|
||||
12 2 = PCIe module, 1 = IRQ not active
|
||||
14 4 = Peridot module, 1 = IRQ not active
|
||||
== =======================================
|
||||
|
||||
What: /sys/kernel/debug/moxtet/output
|
||||
Date: March 2019
|
||||
|
|
@ -17,7 +23,13 @@ Contact: Marek Behún <marek.behun@nic.cz>
|
|||
Description: (RW) Read last written value to the shift registers, in
|
||||
hexadecimal, or write values to the shift registers, also
|
||||
in hexadecimal.
|
||||
Example: 0102
|
||||
01: 01 was last written, or is to be written, to the
|
||||
first module's shift register
|
||||
02: the same for second module
|
||||
|
||||
Example::
|
||||
|
||||
0102
|
||||
|
||||
== ================================================
|
||||
01 01 was last written, or is to be written, to the
|
||||
first module's shift register
|
||||
02 the same for second module
|
||||
== ================================================
|
||||
|
|
|
|||
|
|
@ -4,42 +4,42 @@ KernelVersion: 3.4
|
|||
Contact: Kent Yoder <key@linux.vnet.ibm.com>
|
||||
Description:
|
||||
|
||||
These debugfs interfaces are built by the nx-crypto driver, built in
|
||||
These debugfs interfaces are built by the nx-crypto driver, built in
|
||||
arch/powerpc/crypto/nx.
|
||||
|
||||
Error Detection
|
||||
===============
|
||||
|
||||
errors:
|
||||
- A u32 providing a total count of errors since the driver was loaded. The
|
||||
only errors counted here are those returned from the hcall, H_COP_OP.
|
||||
A u32 providing a total count of errors since the driver was loaded. The
|
||||
only errors counted here are those returned from the hcall, H_COP_OP.
|
||||
|
||||
last_error:
|
||||
- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
|
||||
recorded here (the hcall will retry until -EBUSY goes away).
|
||||
The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
|
||||
recorded here (the hcall will retry until -EBUSY goes away).
|
||||
|
||||
last_error_pid:
|
||||
- The process ID of the process who received the most recent error from the
|
||||
hcall.
|
||||
The process ID of the process who received the most recent error from the
|
||||
hcall.
|
||||
|
||||
Device Use
|
||||
==========
|
||||
|
||||
aes_bytes:
|
||||
- The total number of bytes encrypted using AES in any of the driver's
|
||||
supported modes.
|
||||
The total number of bytes encrypted using AES in any of the driver's
|
||||
supported modes.
|
||||
|
||||
aes_ops:
|
||||
- The total number of AES operations submitted to the hardware.
|
||||
The total number of AES operations submitted to the hardware.
|
||||
|
||||
sha256_bytes:
|
||||
- The total number of bytes hashed by the hardware using SHA-256.
|
||||
The total number of bytes hashed by the hardware using SHA-256.
|
||||
|
||||
sha256_ops:
|
||||
- The total number of SHA-256 operations submitted to the hardware.
|
||||
The total number of SHA-256 operations submitted to the hardware.
|
||||
|
||||
sha512_bytes:
|
||||
- The total number of bytes hashed by the hardware using SHA-512.
|
||||
The total number of bytes hashed by the hardware using SHA-512.
|
||||
|
||||
sha512_ops:
|
||||
- The total number of SHA-512 operations submitted to the hardware.
|
||||
The total number of SHA-512 operations submitted to the hardware.
|
||||
|
|
|
|||
|
|
@ -4,16 +4,15 @@ KernelVersion: 2.6.20
|
|||
Contact: Thomas Maier <balagi@justmail.de>
|
||||
Description:
|
||||
|
||||
debugfs interface
|
||||
-----------------
|
||||
|
||||
The pktcdvd module (packet writing driver) creates
|
||||
these files in debugfs:
|
||||
|
||||
/sys/kernel/debug/pktcdvd/pktcdvd[0-7]/
|
||||
info (0444) Lots of driver statistics and infos.
|
||||
|
||||
Example:
|
||||
-------
|
||||
==== ====== ====================================
|
||||
info 0444 Lots of driver statistics and infos.
|
||||
==== ====== ====================================
|
||||
|
||||
cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
|
||||
Example::
|
||||
|
||||
cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
|
||||
|
|
|
|||
|
|
@ -2,8 +2,13 @@ What: /sys/kernel/debug/turris-mox-rwtm/do_sign
|
|||
Date: Jun 2020
|
||||
KernelVersion: 5.8
|
||||
Contact: Marek Behún <marek.behun@nic.cz>
|
||||
Description: (W) Message to sign with the ECDSA private key stored in
|
||||
device's OTP. The message must be exactly 64 bytes (since
|
||||
this is intended for SHA-512 hashes).
|
||||
(R) The resulting signature, 136 bytes. This contains the R and
|
||||
S values of the ECDSA signature, both in big-endian format.
|
||||
Description:
|
||||
|
||||
======= ===========================================================
|
||||
(Write) Message to sign with the ECDSA private key stored in
|
||||
device's OTP. The message must be exactly 64 bytes
|
||||
(since this is intended for SHA-512 hashes).
|
||||
(Read) The resulting signature, 136 bytes. This contains the
|
||||
R and S values of the ECDSA signature, both in
|
||||
big-endian format.
|
||||
======= ===========================================================
|
||||
|
|
|
|||
|
|
@ -27,16 +27,17 @@ Description:
|
|||
for writing, two for the type and at least a single byte of
|
||||
data.
|
||||
|
||||
Example:
|
||||
// Request EC info type 3 (EC firmware build date)
|
||||
// Corresponds with sending type 0x00f0 with
|
||||
// MBOX = [38, 00, 03, 00]
|
||||
$ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw
|
||||
// View the result. The decoded ASCII result "12/21/18" is
|
||||
// included after the raw hex.
|
||||
// Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...]
|
||||
$ cat /sys/kernel/debug/wilco_ec/raw
|
||||
00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8...
|
||||
Example::
|
||||
|
||||
// Request EC info type 3 (EC firmware build date)
|
||||
// Corresponds with sending type 0x00f0 with
|
||||
// MBOX = [38, 00, 03, 00]
|
||||
$ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw
|
||||
// View the result. The decoded ASCII result "12/21/18" is
|
||||
// included after the raw hex.
|
||||
// Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...]
|
||||
$ cat /sys/kernel/debug/wilco_ec/raw
|
||||
00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8...
|
||||
|
||||
Note that the first 16 bytes of the received MBOX[] will be
|
||||
printed, even if some of the data is junk, and skipping bytes
|
||||
|
|
|
|||
|
|
@ -10,29 +10,29 @@ Description:
|
|||
<uapi/linux/wmi.h>
|
||||
|
||||
1) To perform an SMBIOS call from userspace, you'll need to
|
||||
first determine the minimum size of the calling interface
|
||||
buffer for your machine.
|
||||
Platforms that contain larger buffers can return larger
|
||||
objects from the system firmware.
|
||||
Commonly this size is either 4k or 32k.
|
||||
first determine the minimum size of the calling interface
|
||||
buffer for your machine.
|
||||
Platforms that contain larger buffers can return larger
|
||||
objects from the system firmware.
|
||||
Commonly this size is either 4k or 32k.
|
||||
|
||||
To determine the size of the buffer read() a u64 dword from
|
||||
the WMI character device /dev/wmi/dell-smbios.
|
||||
To determine the size of the buffer read() a u64 dword from
|
||||
the WMI character device /dev/wmi/dell-smbios.
|
||||
|
||||
2) After you've determined the minimum size of the calling
|
||||
interface buffer, you can allocate a structure that represents
|
||||
the structure documented above.
|
||||
interface buffer, you can allocate a structure that represents
|
||||
the structure documented above.
|
||||
|
||||
3) In the 'length' object store the size of the buffer you
|
||||
determined above and allocated.
|
||||
determined above and allocated.
|
||||
|
||||
4) In this buffer object, prepare as necessary for the SMBIOS
|
||||
call you're interested in. Typically SMBIOS buffers have
|
||||
"class", "select", and "input" defined to values that coincide
|
||||
with the data you are interested in.
|
||||
Documenting class/select/input values is outside of the scope
|
||||
of this documentation. Check with the libsmbios project for
|
||||
further documentation on these values.
|
||||
call you're interested in. Typically SMBIOS buffers have
|
||||
"class", "select", and "input" defined to values that coincide
|
||||
with the data you are interested in.
|
||||
Documenting class/select/input values is outside of the scope
|
||||
of this documentation. Check with the libsmbios project for
|
||||
further documentation on these values.
|
||||
|
||||
6) Run the call by using ioctl() as described in the header.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ Description: The /dev/kmsg character device node provides userspace access
|
|||
to the kernel's printk buffer.
|
||||
|
||||
Injecting messages:
|
||||
|
||||
Every write() to the opened device node places a log entry in
|
||||
the kernel's printk buffer.
|
||||
|
||||
|
|
@ -21,6 +22,7 @@ Description: The /dev/kmsg character device node provides userspace access
|
|||
the messages can always be reliably determined.
|
||||
|
||||
Accessing the buffer:
|
||||
|
||||
Every read() from the opened device node receives one record
|
||||
of the kernel's printk buffer.
|
||||
|
||||
|
|
@ -48,6 +50,7 @@ Description: The /dev/kmsg character device node provides userspace access
|
|||
if needed, without limiting the interface to a single reader.
|
||||
|
||||
The device supports seek with the following parameters:
|
||||
|
||||
SEEK_SET, 0
|
||||
seek to the first entry in the buffer
|
||||
SEEK_END, 0
|
||||
|
|
@ -87,18 +90,22 @@ Description: The /dev/kmsg character device node provides userspace access
|
|||
readable context of the message, for reliable processing in
|
||||
userspace.
|
||||
|
||||
Example:
|
||||
7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
|
||||
SUBSYSTEM=acpi
|
||||
DEVICE=+acpi:PNP0A03:00
|
||||
6,339,5140900,-;NET: Registered protocol family 10
|
||||
30,340,5690716,-;udevd[80]: starting version 181
|
||||
Example::
|
||||
|
||||
7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
|
||||
SUBSYSTEM=acpi
|
||||
DEVICE=+acpi:PNP0A03:00
|
||||
6,339,5140900,-;NET: Registered protocol family 10
|
||||
30,340,5690716,-;udevd[80]: starting version 181
|
||||
|
||||
The DEVICE= key uniquely identifies devices the following way:
|
||||
b12:8 - block dev_t
|
||||
c127:3 - char dev_t
|
||||
n8 - netdev ifindex
|
||||
+sound:card0 - subsystem:devname
|
||||
|
||||
============ =================
|
||||
b12:8 block dev_t
|
||||
c127:3 char dev_t
|
||||
n8 netdev ifindex
|
||||
+sound:card0 subsystem:devname
|
||||
============ =================
|
||||
|
||||
The flags field carries '-' by default. A 'c' indicates a
|
||||
fragment of a line. Note, that these hints about continuation
|
||||
|
|
|
|||
|
|
@ -17,26 +17,33 @@ Description:
|
|||
echoing a value to <securityfs>/evm made up of the
|
||||
following bits:
|
||||
|
||||
=== ==================================================
|
||||
Bit Effect
|
||||
=== ==================================================
|
||||
0 Enable HMAC validation and creation
|
||||
1 Enable digital signature validation
|
||||
2 Permit modification of EVM-protected metadata at
|
||||
runtime. Not supported if HMAC validation and
|
||||
creation is enabled.
|
||||
31 Disable further runtime modification of EVM policy
|
||||
=== ==================================================
|
||||
|
||||
For example:
|
||||
For example::
|
||||
|
||||
echo 1 ><securityfs>/evm
|
||||
echo 1 ><securityfs>/evm
|
||||
|
||||
will enable HMAC validation and creation
|
||||
|
||||
echo 0x80000003 ><securityfs>/evm
|
||||
::
|
||||
|
||||
echo 0x80000003 ><securityfs>/evm
|
||||
|
||||
will enable HMAC and digital signature validation and
|
||||
HMAC creation and disable all further modification of policy.
|
||||
|
||||
echo 0x80000006 ><securityfs>/evm
|
||||
::
|
||||
|
||||
echo 0x80000006 ><securityfs>/evm
|
||||
|
||||
will enable digital signature validation, permit
|
||||
modification of EVM-protected metadata and
|
||||
|
|
@ -65,7 +72,7 @@ Description:
|
|||
Shows the set of extended attributes used to calculate or
|
||||
validate the EVM signature, and allows additional attributes
|
||||
to be added at runtime. Any signatures generated after
|
||||
additional attributes are added (and on files posessing those
|
||||
additional attributes are added (and on files possessing those
|
||||
additional attributes) will only be valid if the same
|
||||
additional attributes are configured on system boot. Writing
|
||||
a single period (.) will lock the xattr list from any further
|
||||
|
|
|
|||
|
|
@ -12,15 +12,16 @@ Description:
|
|||
The following file operations are supported:
|
||||
|
||||
open(2)
|
||||
Currently the only useful flags are O_RDWR.
|
||||
Currently the only useful flags are O_RDWR.
|
||||
|
||||
ioctl(2)
|
||||
Initiate various actions.
|
||||
See the inline documentation in [include/uapi]<linux/gpio.h>
|
||||
for descriptions of all ioctls.
|
||||
Initiate various actions.
|
||||
|
||||
See the inline documentation in [include/uapi]<linux/gpio.h>
|
||||
for descriptions of all ioctls.
|
||||
|
||||
close(2)
|
||||
Stops and free up the I/O contexts that was associated
|
||||
with the file descriptor.
|
||||
Stops and free up the I/O contexts that was associated
|
||||
with the file descriptor.
|
||||
|
||||
Users: TBD
|
||||
|
|
|
|||
|
|
@ -15,19 +15,22 @@ Description:
|
|||
IMA appraisal, if configured, uses these file measurements
|
||||
for local measurement appraisal.
|
||||
|
||||
rule format: action [condition ...]
|
||||
::
|
||||
|
||||
action: measure | dont_measure | appraise | dont_appraise |
|
||||
audit | hash | dont_hash
|
||||
condition:= base | lsm [option]
|
||||
rule format: action [condition ...]
|
||||
|
||||
action: measure | dont_measure | appraise | dont_appraise |
|
||||
audit | hash | dont_hash
|
||||
condition:= base | lsm [option]
|
||||
base: [[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
|
||||
[euid=] [fowner=] [fsname=]]
|
||||
lsm: [[subj_user=] [subj_role=] [subj_type=]
|
||||
[obj_user=] [obj_role=] [obj_type=]]
|
||||
option: [[appraise_type=]] [template=] [permit_directio]
|
||||
[appraise_flag=] [keyrings=]
|
||||
base: func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK][MODULE_CHECK]
|
||||
[FIRMWARE_CHECK]
|
||||
base:
|
||||
func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK]MODULE_CHECK]
|
||||
[FIRMWARE_CHECK]
|
||||
[KEXEC_KERNEL_CHECK] [KEXEC_INITRAMFS_CHECK]
|
||||
[KEXEC_CMDLINE] [KEY_CHECK]
|
||||
mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND]
|
||||
|
|
@ -37,8 +40,9 @@ Description:
|
|||
uid:= decimal value
|
||||
euid:= decimal value
|
||||
fowner:= decimal value
|
||||
lsm: are LSM specific
|
||||
option: appraise_type:= [imasig] [imasig|modsig]
|
||||
lsm: are LSM specific
|
||||
option:
|
||||
appraise_type:= [imasig] [imasig|modsig]
|
||||
appraise_flag:= [check_blacklist]
|
||||
Currently, blacklist check is only for files signed with appended
|
||||
signature.
|
||||
|
|
@ -49,7 +53,7 @@ Description:
|
|||
(eg, ima-ng). Only valid when action is "measure".
|
||||
pcr:= decimal value
|
||||
|
||||
default policy:
|
||||
default policy:
|
||||
# PROC_SUPER_MAGIC
|
||||
dont_measure fsmagic=0x9fa0
|
||||
dont_appraise fsmagic=0x9fa0
|
||||
|
|
@ -97,7 +101,8 @@ Description:
|
|||
|
||||
Examples of LSM specific definitions:
|
||||
|
||||
SELinux:
|
||||
SELinux::
|
||||
|
||||
dont_measure obj_type=var_log_t
|
||||
dont_appraise obj_type=var_log_t
|
||||
dont_measure obj_type=auditd_log_t
|
||||
|
|
@ -105,10 +110,11 @@ Description:
|
|||
measure subj_user=system_u func=FILE_CHECK mask=MAY_READ
|
||||
measure subj_role=system_r func=FILE_CHECK mask=MAY_READ
|
||||
|
||||
Smack:
|
||||
Smack::
|
||||
|
||||
measure subj_user=_ func=FILE_CHECK mask=MAY_READ
|
||||
|
||||
Example of measure rules using alternate PCRs:
|
||||
Example of measure rules using alternate PCRs::
|
||||
|
||||
measure func=KEXEC_KERNEL_CHECK pcr=4
|
||||
measure func=KEXEC_INITRAMFS_CHECK pcr=5
|
||||
|
|
|
|||
|
|
@ -6,32 +6,38 @@ Description:
|
|||
of block devices. Each line contains the following 14
|
||||
fields:
|
||||
|
||||
1 - major number
|
||||
2 - minor mumber
|
||||
3 - device name
|
||||
4 - reads completed successfully
|
||||
5 - reads merged
|
||||
6 - sectors read
|
||||
7 - time spent reading (ms)
|
||||
8 - writes completed
|
||||
9 - writes merged
|
||||
10 - sectors written
|
||||
11 - time spent writing (ms)
|
||||
12 - I/Os currently in progress
|
||||
13 - time spent doing I/Os (ms)
|
||||
14 - weighted time spent doing I/Os (ms)
|
||||
== ===================================
|
||||
1 major number
|
||||
2 minor mumber
|
||||
3 device name
|
||||
4 reads completed successfully
|
||||
5 reads merged
|
||||
6 sectors read
|
||||
7 time spent reading (ms)
|
||||
8 writes completed
|
||||
9 writes merged
|
||||
10 sectors written
|
||||
11 time spent writing (ms)
|
||||
12 I/Os currently in progress
|
||||
13 time spent doing I/Os (ms)
|
||||
14 weighted time spent doing I/Os (ms)
|
||||
== ===================================
|
||||
|
||||
Kernel 4.18+ appends four more fields for discard
|
||||
tracking putting the total at 18:
|
||||
|
||||
15 - discards completed successfully
|
||||
16 - discards merged
|
||||
17 - sectors discarded
|
||||
18 - time spent discarding
|
||||
== ===================================
|
||||
15 discards completed successfully
|
||||
16 discards merged
|
||||
17 sectors discarded
|
||||
18 time spent discarding
|
||||
== ===================================
|
||||
|
||||
Kernel 5.5+ appends two more fields for flush requests:
|
||||
|
||||
19 - flush requests completed successfully
|
||||
20 - time spent flushing
|
||||
== =====================================
|
||||
19 flush requests completed successfully
|
||||
20 time spent flushing
|
||||
== =====================================
|
||||
|
||||
For more details refer to Documentation/admin-guide/iostats.rst
|
||||
|
|
|
|||
|
|
@ -14,28 +14,28 @@ Description:
|
|||
For more details, see Documentation/filesystems/proc.rst
|
||||
and the procfs man page.
|
||||
|
||||
Typical output looks like this:
|
||||
Typical output looks like this::
|
||||
|
||||
00100000-ff709000 ---p 00000000 00:00 0 [rollup]
|
||||
Size: 1192 kB
|
||||
KernelPageSize: 4 kB
|
||||
MMUPageSize: 4 kB
|
||||
Rss: 884 kB
|
||||
Pss: 385 kB
|
||||
Pss_Anon: 301 kB
|
||||
Pss_File: 80 kB
|
||||
Pss_Shmem: 4 kB
|
||||
Shared_Clean: 696 kB
|
||||
Shared_Dirty: 0 kB
|
||||
Private_Clean: 120 kB
|
||||
Private_Dirty: 68 kB
|
||||
Referenced: 884 kB
|
||||
Anonymous: 68 kB
|
||||
LazyFree: 0 kB
|
||||
AnonHugePages: 0 kB
|
||||
ShmemPmdMapped: 0 kB
|
||||
Shared_Hugetlb: 0 kB
|
||||
Private_Hugetlb: 0 kB
|
||||
Swap: 0 kB
|
||||
SwapPss: 0 kB
|
||||
Locked: 385 kB
|
||||
00100000-ff709000 ---p 00000000 00:00 0 [rollup]
|
||||
Size: 1192 kB
|
||||
KernelPageSize: 4 kB
|
||||
MMUPageSize: 4 kB
|
||||
Rss: 884 kB
|
||||
Pss: 385 kB
|
||||
Pss_Anon: 301 kB
|
||||
Pss_File: 80 kB
|
||||
Pss_Shmem: 4 kB
|
||||
Shared_Clean: 696 kB
|
||||
Shared_Dirty: 0 kB
|
||||
Private_Clean: 120 kB
|
||||
Private_Dirty: 68 kB
|
||||
Referenced: 884 kB
|
||||
Anonymous: 68 kB
|
||||
LazyFree: 0 kB
|
||||
AnonHugePages: 0 kB
|
||||
ShmemPmdMapped: 0 kB
|
||||
Shared_Hugetlb: 0 kB
|
||||
Private_Hugetlb: 0 kB
|
||||
Swap: 0 kB
|
||||
SwapPss: 0 kB
|
||||
Locked: 385 kB
|
||||
|
|
|
|||
|
|
@ -9,25 +9,25 @@ Description: Generic interface to platform dependent persistent storage.
|
|||
provide a generic interface to show records captured in
|
||||
the dying moments. In the case of a panic the last part
|
||||
of the console log is captured, but other interesting
|
||||
data can also be saved.
|
||||
data can also be saved::
|
||||
|
||||
# mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
|
||||
# mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
|
||||
|
||||
$ ls -l /sys/fs/pstore/
|
||||
total 0
|
||||
-r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
|
||||
$ ls -l /sys/fs/pstore/
|
||||
total 0
|
||||
-r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
|
||||
|
||||
Different users of this interface will result in different
|
||||
filename prefixes. Currently two are defined:
|
||||
|
||||
"dmesg" - saved console log
|
||||
"mce" - architecture dependent data from fatal h/w error
|
||||
- "dmesg" - saved console log
|
||||
- "mce" - architecture dependent data from fatal h/w error
|
||||
|
||||
Once the information in a file has been read, removing
|
||||
the file will signal to the underlying persistent storage
|
||||
device that it can reclaim the space for later re-use.
|
||||
device that it can reclaim the space for later re-use::
|
||||
|
||||
$ rm /sys/fs/pstore/dmesg-erst-1
|
||||
$ rm /sys/fs/pstore/dmesg-erst-1
|
||||
|
||||
The expectation is that all files in /sys/fs/pstore/
|
||||
will be saved elsewhere and erased from persistent store
|
||||
|
|
@ -44,4 +44,3 @@ Description: Generic interface to platform dependent persistent storage.
|
|||
backends are available, the preferred backend may be
|
||||
set by passing the pstore.backend= argument to the kernel at
|
||||
boot time.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,23 +4,27 @@ Contact: Jerome Marchand <jmarchan@redhat.com>
|
|||
Description:
|
||||
The /sys/block/<disk>/stat files displays the I/O
|
||||
statistics of disk <disk>. They contain 11 fields:
|
||||
1 - reads completed successfully
|
||||
2 - reads merged
|
||||
3 - sectors read
|
||||
4 - time spent reading (ms)
|
||||
5 - writes completed
|
||||
6 - writes merged
|
||||
7 - sectors written
|
||||
8 - time spent writing (ms)
|
||||
9 - I/Os currently in progress
|
||||
10 - time spent doing I/Os (ms)
|
||||
11 - weighted time spent doing I/Os (ms)
|
||||
12 - discards completed
|
||||
13 - discards merged
|
||||
14 - sectors discarded
|
||||
15 - time spent discarding (ms)
|
||||
16 - flush requests completed
|
||||
17 - time spent flushing (ms)
|
||||
|
||||
== ==============================================
|
||||
1 reads completed successfully
|
||||
2 reads merged
|
||||
3 sectors read
|
||||
4 time spent reading (ms)
|
||||
5 writes completed
|
||||
6 writes merged
|
||||
7 sectors written
|
||||
8 time spent writing (ms)
|
||||
9 I/Os currently in progress
|
||||
10 time spent doing I/Os (ms)
|
||||
11 weighted time spent doing I/Os (ms)
|
||||
12 discards completed
|
||||
13 discards merged
|
||||
14 sectors discarded
|
||||
15 time spent discarding (ms)
|
||||
16 flush requests completed
|
||||
17 time spent flushing (ms)
|
||||
== ==============================================
|
||||
|
||||
For more details refer Documentation/admin-guide/iostats.rst
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -8,11 +8,13 @@ Description:
|
|||
|
||||
It has the following valid values:
|
||||
|
||||
== ========================================================
|
||||
0 OFF - the LED is not activated on activity
|
||||
1 BLINK_ON - the LED blinks on every 10ms when activity is
|
||||
detected.
|
||||
2 BLINK_OFF - the LED is on when idle, and blinks off
|
||||
every 10ms when activity is detected.
|
||||
== ========================================================
|
||||
|
||||
Note that the user must turn sw_activity OFF it they wish to
|
||||
control the activity LED via the em_message file.
|
||||
|
|
|
|||
|
|
@ -9,9 +9,9 @@ Description: To unmap a volume, "normal" or "force" has to be written to:
|
|||
is using the device. When "force" is used, the device is also unmapped
|
||||
when device is in use. All I/Os that are in progress will fail.
|
||||
|
||||
Example:
|
||||
Example::
|
||||
|
||||
# echo "normal" > /sys/block/rnbd0/rnbd/unmap_device
|
||||
# echo "normal" > /sys/block/rnbd0/rnbd/unmap_device
|
||||
|
||||
What: /sys/block/rnbd<N>/rnbd/state
|
||||
Date: Feb 2020
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ Description:
|
|||
This attribute indicates the full path of ACPI namespace
|
||||
object associated with the device object. For example,
|
||||
\_SB_.PCI0.
|
||||
|
||||
This file is not present for device objects representing
|
||||
fixed ACPI hardware features (like power and sleep
|
||||
buttons).
|
||||
|
|
@ -67,14 +68,16 @@ Description:
|
|||
The return value is a decimal integer representing the device's
|
||||
status bitmap:
|
||||
|
||||
Bit [0] – Set if the device is present.
|
||||
Bit [1] – Set if the device is enabled and decoding its
|
||||
resources.
|
||||
Bit [2] – Set if the device should be shown in the UI.
|
||||
Bit [3] – Set if the device is functioning properly (cleared if
|
||||
device failed its diagnostics).
|
||||
Bit [4] – Set if the battery is present.
|
||||
Bits [31:5] – Reserved (must be cleared)
|
||||
=========== ==================================================
|
||||
Bit [0] Set if the device is present.
|
||||
Bit [1] Set if the device is enabled and decoding its
|
||||
resources.
|
||||
Bit [2] Set if the device should be shown in the UI.
|
||||
Bit [3] Set if the device is functioning properly (cleared
|
||||
if device failed its diagnostics).
|
||||
Bit [4] Set if the battery is present.
|
||||
Bits [31:5] Reserved (must be cleared)
|
||||
=========== ==================================================
|
||||
|
||||
If bit [0] is clear, then bit 1 must also be clear (a device
|
||||
that is not present cannot be enabled).
|
||||
|
|
|
|||
|
|
@ -8,50 +8,50 @@ What: /sys/bus/coresight/devices/<cti-name>/powered
|
|||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Indicate if the CTI hardware is powered.
|
||||
Description: (Read) Indicate if the CTI hardware is powered.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/ctmid
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Display the associated CTM ID
|
||||
Description: (Read) Display the associated CTM ID
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Number of devices connected to triggers on this CTI
|
||||
Description: (Read) Number of devices connected to triggers on this CTI
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Name of connected device <N>
|
||||
Description: (Read) Name of connected device <N>
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Input trigger signals from connected device <N>
|
||||
Description: (Read) Input trigger signals from connected device <N>
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Functional types for the input trigger signals
|
||||
Description: (Read) Functional types for the input trigger signals
|
||||
from connected device <N>
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Output trigger signals to connected device <N>
|
||||
Description: (Read) Output trigger signals to connected device <N>
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Functional types for the output trigger signals
|
||||
Description: (Read) Functional types for the output trigger signals
|
||||
to connected device <N>
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/inout_sel
|
||||
|
|
@ -88,7 +88,7 @@ What: /sys/bus/coresight/devices/<cti-name>/regs/intack
|
|||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Write the INTACK register.
|
||||
Description: (Write) Write the INTACK register.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/appset
|
||||
Date: March 2020
|
||||
|
|
@ -101,99 +101,99 @@ What: /sys/bus/coresight/devices/<cti-name>/regs/appclear
|
|||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Write APPCLEAR register to deactivate channel.
|
||||
Description: (Write) Write APPCLEAR register to deactivate channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/apppulse
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Write APPPULSE to pulse a channel active for one clock
|
||||
Description: (Write) Write APPPULSE to pulse a channel active for one clock
|
||||
cycle.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/chinstatus
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Read current status of channel inputs.
|
||||
Description: (Read) Read current status of channel inputs.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/choutstatus
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) read current status of channel outputs.
|
||||
Description: (Read) read current status of channel outputs.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/triginstatus
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) read current status of input trigger signals
|
||||
Description: (Read) read current status of input trigger signals
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/regs/trigoutstatus
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) read current status of output trigger signals.
|
||||
Description: (Read) read current status of output trigger signals.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_attach
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Attach a CTI input trigger to a CTM channel.
|
||||
Description: (Write) Attach a CTI input trigger to a CTM channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_detach
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Detach a CTI input trigger from a CTM channel.
|
||||
Description: (Write) Detach a CTI input trigger from a CTM channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_attach
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Attach a CTI output trigger to a CTM channel.
|
||||
Description: (Write) Attach a CTI output trigger to a CTM channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_detach
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Detach a CTI output trigger from a CTM channel.
|
||||
Description: (Write) Detach a CTI output trigger from a CTM channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_enable
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (RW) Enable CTIGATE for single channel (W) or list enabled
|
||||
Description: (RW) Enable CTIGATE for single channel (Write) or list enabled
|
||||
channels through the gate (R).
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_disable
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Disable CTIGATE for single channel.
|
||||
Description: (Write) Disable CTIGATE for single channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_set
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Activate a single channel.
|
||||
Description: (Write) Activate a single channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_clear
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Deactivate a single channel.
|
||||
Description: (Write) Deactivate a single channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_pulse
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Pulse a single channel - activate for a single clock cycle.
|
||||
Description: (Write) Pulse a single channel - activate for a single clock cycle.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_filtered
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) List of output triggers filtered across all connections.
|
||||
Description: (Read) List of output triggers filtered across all connections.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/trig_filter_enable
|
||||
Date: March 2020
|
||||
|
|
@ -205,13 +205,13 @@ What: /sys/bus/coresight/devices/<cti-name>/channels/chan_inuse
|
|||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) show channels with at least one attached trigger signal.
|
||||
Description: (Read) show channels with at least one attached trigger signal.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_free
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) show channels with no attached trigger signals.
|
||||
Description: (Read) show channels with no attached trigger signals.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_sel
|
||||
Date: March 2020
|
||||
|
|
@ -224,18 +224,18 @@ What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_in
|
|||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Read to see input triggers connected to selected view
|
||||
Description: (Read) Read to see input triggers connected to selected view
|
||||
channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_out
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (R) Read to see output triggers connected to selected view
|
||||
Description: (Read) Read to see output triggers connected to selected view
|
||||
channel.
|
||||
|
||||
What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_reset
|
||||
Date: March 2020
|
||||
KernelVersion 5.7
|
||||
Contact: Mike Leach or Mathieu Poirier
|
||||
Description: (W) Clear all channel / trigger programming.
|
||||
Description: (Write) Clear all channel / trigger programming.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,10 @@ KernelVersion: 3.19
|
|||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (RW) Add/remove a sink from a trace path. There can be multiple
|
||||
source for a single sink.
|
||||
ex: echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink
|
||||
|
||||
ex::
|
||||
|
||||
echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.etb/trigger_cntr
|
||||
Date: November 2014
|
||||
|
|
@ -20,21 +23,21 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rdp
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Defines the depth, in words, of the trace RAM in powers of
|
||||
Description: (Read) Defines the depth, in words, of the trace RAM in powers of
|
||||
2. The value is read directly from HW register RDP, 0x004.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/sts
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB status register. The value
|
||||
Description: (Read) Shows the value held by the ETB status register. The value
|
||||
is read directly from HW register STS, 0x00C.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rrp
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB RAM Read Pointer register
|
||||
Description: (Read) Shows the value held by the ETB RAM Read Pointer register
|
||||
that is used to read entries from the Trace RAM over the APB
|
||||
interface. The value is read directly from HW register RRP,
|
||||
0x014.
|
||||
|
|
@ -43,7 +46,7 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rwp
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB RAM Write Pointer register
|
||||
Description: (Read) Shows the value held by the ETB RAM Write Pointer register
|
||||
that is used to sets the write pointer to write entries from
|
||||
the CoreSight bus into the Trace RAM. The value is read directly
|
||||
from HW register RWP, 0x018.
|
||||
|
|
@ -52,21 +55,21 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/trg
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Similar to "trigger_cntr" above except that this value is
|
||||
Description: (Read) Similar to "trigger_cntr" above except that this value is
|
||||
read directly from HW register TRG, 0x01C.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ctl
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB Control register. The value
|
||||
Description: (Read) Shows the value held by the ETB Control register. The value
|
||||
is read directly from HW register CTL, 0x020.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ffsr
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB Formatter and Flush Status
|
||||
Description: (Read) Shows the value held by the ETB Formatter and Flush Status
|
||||
register. The value is read directly from HW register FFSR,
|
||||
0x300.
|
||||
|
||||
|
|
@ -74,6 +77,6 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ffcr
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the ETB Formatter and Flush Control
|
||||
Description: (Read) Shows the value held by the ETB Formatter and Flush Control
|
||||
register. The value is read directly from HW register FFCR,
|
||||
0x304.
|
||||
|
|
|
|||
|
|
@ -146,28 +146,28 @@ What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_addr_cmp
|
|||
Date: November 2014
|
||||
KernelVersion: 3.19
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Provides the number of address comparators pairs accessible
|
||||
Description: (Read) Provides the number of address comparators pairs accessible
|
||||
on a trace unit, as specified by bit 3:0 of register ETMCCR.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_cntr
|
||||
Date: November 2014
|
||||
KernelVersion: 3.19
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Provides the number of counters accessible on a trace unit,
|
||||
Description: (Read) Provides the number of counters accessible on a trace unit,
|
||||
as specified by bit 15:13 of register ETMCCR.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/nr_ctxid_cmp
|
||||
Date: November 2014
|
||||
KernelVersion: 3.19
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Provides the number of context ID comparator available on a
|
||||
Description: (Read) Provides the number of context ID comparator available on a
|
||||
trace unit, as specified by bit 25:24 of register ETMCCR.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/reset
|
||||
Date: November 2014
|
||||
KernelVersion: 3.19
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (W) Cancels all configuration on a trace unit and set it back
|
||||
Description: (Write) Cancels all configuration on a trace unit and set it back
|
||||
to its boot configuration.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/seq_12_event
|
||||
|
|
@ -216,7 +216,7 @@ What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/curr_seq_state
|
|||
Date: November 2014
|
||||
KernelVersion: 3.19
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Holds the current state of the sequencer.
|
||||
Description: (Read) Holds the current state of the sequencer.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.[etm|ptm]/sync_freq
|
||||
Date: November 2014
|
||||
|
|
|
|||
|
|
@ -12,75 +12,75 @@ What: /sys/bus/coresight/devices/etm<N>/cpu
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) The CPU this tracing entity is associated with.
|
||||
Description: (Read) The CPU this tracing entity is associated with.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_pe_cmp
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of PE comparator inputs that are
|
||||
Description: (Read) Indicates the number of PE comparator inputs that are
|
||||
available for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_addr_cmp
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of address comparator pairs that are
|
||||
Description: (Read) Indicates the number of address comparator pairs that are
|
||||
available for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_cntr
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of counters that are available for
|
||||
Description: (Read) Indicates the number of counters that are available for
|
||||
tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_ext_inp
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates how many external inputs are implemented.
|
||||
Description: (Read) Indicates how many external inputs are implemented.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/numcidc
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of Context ID comparators that are
|
||||
Description: (Read) Indicates the number of Context ID comparators that are
|
||||
available for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/numvmidc
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of VMID comparators that are available
|
||||
Description: (Read) Indicates the number of VMID comparators that are available
|
||||
for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nrseqstate
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of sequencer states that are
|
||||
Description: (Read) Indicates the number of sequencer states that are
|
||||
implemented.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_resource
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of resource selection pairs that are
|
||||
Description: (Read) Indicates the number of resource selection pairs that are
|
||||
available for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/nr_ss_cmp
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the number of single-shot comparator controls that
|
||||
Description: (Read) Indicates the number of single-shot comparator controls that
|
||||
are available for tracing.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/reset
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (W) Cancels all configuration on a trace unit and set it back
|
||||
Description: (Write) Cancels all configuration on a trace unit and set it back
|
||||
to its boot configuration.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mode
|
||||
|
|
@ -300,7 +300,7 @@ What: /sys/bus/coresight/devices/etm<N>/addr_cmp_view
|
|||
Date: December 2019
|
||||
KernelVersion: 5.5
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the current settings for the selected address
|
||||
Description: (Read) Print the current settings for the selected address
|
||||
comparator.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/sshot_idx
|
||||
|
|
@ -319,7 +319,7 @@ What: /sys/bus/coresight/devices/etm<N>/sshot_status
|
|||
Date: December 2019
|
||||
KernelVersion: 5.5
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the current value of the selected single shot
|
||||
Description: (Read) Print the current value of the selected single shot
|
||||
status register.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/sshot_pe_ctrl
|
||||
|
|
@ -333,111 +333,111 @@ What: /sys/bus/coresight/devices/etm<N>/mgmt/trcoslsr
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the OS Lock Status Register (0x304).
|
||||
Description: (Read) Print the content of the OS Lock Status Register (0x304).
|
||||
The value it taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdcr
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Power Down Control Register
|
||||
Description: (Read) Print the content of the Power Down Control Register
|
||||
(0x310). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdsr
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Power Down Status Register
|
||||
Description: (Read) Print the content of the Power Down Status Register
|
||||
(0x314). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trclsr
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the SW Lock Status Register
|
||||
Description: (Read) Print the content of the SW Lock Status Register
|
||||
(0xFB4). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcauthstatus
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Authentication Status Register
|
||||
Description: (Read) Print the content of the Authentication Status Register
|
||||
(0xFB8). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevid
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Device ID Register
|
||||
Description: (Read) Print the content of the Device ID Register
|
||||
(0xFC8). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevtype
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Device Type Register
|
||||
Description: (Read) Print the content of the Device Type Register
|
||||
(0xFCC). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr0
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Peripheral ID0 Register
|
||||
Description: (Read) Print the content of the Peripheral ID0 Register
|
||||
(0xFE0). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr1
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Peripheral ID1 Register
|
||||
Description: (Read) Print the content of the Peripheral ID1 Register
|
||||
(0xFE4). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr2
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Peripheral ID2 Register
|
||||
Description: (Read) Print the content of the Peripheral ID2 Register
|
||||
(0xFE8). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr3
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the Peripheral ID3 Register
|
||||
Description: (Read) Print the content of the Peripheral ID3 Register
|
||||
(0xFEC). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trcconfig
|
||||
Date: February 2016
|
||||
KernelVersion: 4.07
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the trace configuration register
|
||||
Description: (Read) Print the content of the trace configuration register
|
||||
(0x010) as currently set by SW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/mgmt/trctraceid
|
||||
Date: February 2016
|
||||
KernelVersion: 4.07
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Print the content of the trace ID register (0x040).
|
||||
Description: (Read) Print the content of the trace ID register (0x040).
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr0
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the tracing capabilities of the trace unit (0x1E0).
|
||||
Description: (Read) Returns the tracing capabilities of the trace unit (0x1E0).
|
||||
The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr1
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the tracing capabilities of the trace unit (0x1E4).
|
||||
Description: (Read) Returns the tracing capabilities of the trace unit (0x1E4).
|
||||
The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr2
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the maximum size of the data value, data address,
|
||||
Description: (Read) Returns the maximum size of the data value, data address,
|
||||
VMID, context ID and instuction address in the trace unit
|
||||
(0x1E8). The value is taken directly from the HW.
|
||||
|
||||
|
|
@ -445,7 +445,7 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr3
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the value associated with various resources
|
||||
Description: (Read) Returns the value associated with various resources
|
||||
available to the trace unit. See the Trace Macrocell
|
||||
architecture specification for more details (0x1E8).
|
||||
The value is taken directly from the HW.
|
||||
|
|
@ -454,42 +454,42 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr4
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns how many resources the trace unit supports (0x1F0).
|
||||
Description: (Read) Returns how many resources the trace unit supports (0x1F0).
|
||||
The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr5
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns how many resources the trace unit supports (0x1F4).
|
||||
Description: (Read) Returns how many resources the trace unit supports (0x1F4).
|
||||
The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr8
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the maximum speculation depth of the instruction
|
||||
Description: (Read) Returns the maximum speculation depth of the instruction
|
||||
trace stream. (0x180). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr9
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the number of P0 right-hand keys that the trace unit
|
||||
Description: (Read) Returns the number of P0 right-hand keys that the trace unit
|
||||
can use (0x184). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr10
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the number of P1 right-hand keys that the trace unit
|
||||
Description: (Read) Returns the number of P1 right-hand keys that the trace unit
|
||||
can use (0x188). The value is taken directly from the HW.
|
||||
|
||||
What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr11
|
||||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the number of special P1 right-hand keys that the
|
||||
Description: (Read) Returns the number of special P1 right-hand keys that the
|
||||
trace unit can use (0x18C). The value is taken directly from
|
||||
the HW.
|
||||
|
||||
|
|
@ -497,7 +497,7 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr12
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the number of conditional P1 right-hand keys that
|
||||
Description: (Read) Returns the number of conditional P1 right-hand keys that
|
||||
the trace unit can use (0x190). The value is taken directly
|
||||
from the HW.
|
||||
|
||||
|
|
@ -505,6 +505,6 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr13
|
|||
Date: April 2015
|
||||
KernelVersion: 4.01
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Returns the number of special conditional P1 right-hand keys
|
||||
Description: (Read) Returns the number of special conditional P1 right-hand keys
|
||||
that the trace unit can use (0x194). The value is taken
|
||||
directly from the HW.
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ What: /sys/bus/coresight/devices/<memory_map>.stm/status
|
|||
Date: April 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) List various control and status registers. The specific
|
||||
Description: (Read) List various control and status registers. The specific
|
||||
layout and content is driver specific.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.stm/traceid
|
||||
|
|
|
|||
|
|
@ -11,21 +11,21 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rsz
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Defines the size, in 32-bit words, of the local RAM buffer.
|
||||
Description: (Read) Defines the size, in 32-bit words, of the local RAM buffer.
|
||||
The value is read directly from HW register RSZ, 0x004.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/sts
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC status register. The value
|
||||
Description: (Read) Shows the value held by the TMC status register. The value
|
||||
is read directly from HW register STS, 0x00C.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rrp
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC RAM Read Pointer register
|
||||
Description: (Read) Shows the value held by the TMC RAM Read Pointer register
|
||||
that is used to read entries from the Trace RAM over the APB
|
||||
interface. The value is read directly from HW register RRP,
|
||||
0x014.
|
||||
|
|
@ -34,7 +34,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rwp
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC RAM Write Pointer register
|
||||
Description: (Read) Shows the value held by the TMC RAM Write Pointer register
|
||||
that is used to sets the write pointer to write entries from
|
||||
the CoreSight bus into the Trace RAM. The value is read directly
|
||||
from HW register RWP, 0x018.
|
||||
|
|
@ -43,21 +43,21 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/trg
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Similar to "trigger_cntr" above except that this value is
|
||||
Description: (Read) Similar to "trigger_cntr" above except that this value is
|
||||
read directly from HW register TRG, 0x01C.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ctl
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC Control register. The value
|
||||
Description: (Read) Shows the value held by the TMC Control register. The value
|
||||
is read directly from HW register CTL, 0x020.
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ffsr
|
||||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC Formatter and Flush Status
|
||||
Description: (Read) Shows the value held by the TMC Formatter and Flush Status
|
||||
register. The value is read directly from HW register FFSR,
|
||||
0x300.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ffcr
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC Formatter and Flush Control
|
||||
Description: (Read) Shows the value held by the TMC Formatter and Flush Control
|
||||
register. The value is read directly from HW register FFCR,
|
||||
0x304.
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/mode
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Shows the value held by the TMC Mode register, which
|
||||
Description: (Read) Shows the value held by the TMC Mode register, which
|
||||
indicate the mode the device has been configured to enact. The
|
||||
The value is read directly from the MODE register, 0x028.
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/devid
|
|||
Date: March 2016
|
||||
KernelVersion: 4.7
|
||||
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
|
||||
Description: (R) Indicates the capabilities of the Coresight TMC.
|
||||
Description: (Read) Indicates the capabilities of the Coresight TMC.
|
||||
The value is read directly from the DEVID register, 0xFC8,
|
||||
|
||||
What: /sys/bus/coresight/devices/<memory_map>.tmc/buffer_size
|
||||
|
|
|
|||
|
|
@ -20,6 +20,7 @@ Contact: Cornelia Huck <cornelia.huck@de.ibm.com>
|
|||
Description: Contains the ids of the channel paths used by this
|
||||
subchannel, as reported by the channel subsystem
|
||||
during subchannel recognition.
|
||||
|
||||
Note: This is an I/O-subchannel specific attribute.
|
||||
Users: s390-tools, HAL
|
||||
|
||||
|
|
@ -31,6 +32,7 @@ Description: Contains the PIM/PAM/POM values, as reported by the
|
|||
channel subsystem when last queried by the common I/O
|
||||
layer (this implies that this attribute is not necessarily
|
||||
in sync with the values current in the channel subsystem).
|
||||
|
||||
Note: This is an I/O-subchannel specific attribute.
|
||||
Users: s390-tools, HAL
|
||||
|
||||
|
|
@ -53,6 +55,7 @@ Description: This file allows the driver for a device to be specified. When
|
|||
opt-out of driver binding using a driver_override name such as
|
||||
"none". Only a single driver may be specified in the override,
|
||||
there is no support for parsing delimiters.
|
||||
|
||||
Note that unlike the mechanism of the same name for pci, this
|
||||
file does not allow to override basic matching rules. I.e.,
|
||||
the driver must still match the subchannel type of the device.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ KernelVersion: 5.10
|
|||
Contact: Xu Yilun <yilun.xu@intel.com>
|
||||
Description: Read-only. It returns type of DFL FIU of the device. Now DFL
|
||||
supports 2 FIU types, 0 for FME, 1 for PORT.
|
||||
|
||||
Format: 0x%x
|
||||
|
||||
What: /sys/bus/dfl/devices/dfl_dev.X/feature_id
|
||||
|
|
@ -12,4 +13,5 @@ KernelVersion: 5.10
|
|||
Contact: Xu Yilun <yilun.xu@intel.com>
|
||||
Description: Read-only. It returns feature identifier local to its DFL FIU
|
||||
type.
|
||||
|
||||
Format: 0x%x
|
||||
|
|
|
|||
|
|
@ -8,13 +8,13 @@ Description: Read-only. Attribute group to describe the magic bits
|
|||
|
||||
Each attribute under this group defines a bit range of the
|
||||
perf_event_attr.config. All supported attributes are listed
|
||||
below.
|
||||
below::
|
||||
|
||||
event = "config:0-11" - event ID
|
||||
evtype = "config:12-15" - event type
|
||||
portid = "config:16-23" - event source
|
||||
|
||||
For example,
|
||||
For example::
|
||||
|
||||
fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff"
|
||||
|
||||
|
|
@ -40,11 +40,11 @@ Description: Read-only. Attribute group to describe performance monitoring
|
|||
|
||||
All supported performance monitoring events are listed below.
|
||||
|
||||
Basic events (evtype=0x00)
|
||||
Basic events (evtype=0x00)::
|
||||
|
||||
clock = "event=0x00,evtype=0x00,portid=0xff"
|
||||
|
||||
Cache events (evtype=0x01)
|
||||
Cache events (evtype=0x01)::
|
||||
|
||||
cache_read_hit = "event=0x00,evtype=0x01,portid=0xff"
|
||||
cache_read_miss = "event=0x01,evtype=0x01,portid=0xff"
|
||||
|
|
@ -59,7 +59,7 @@ Description: Read-only. Attribute group to describe performance monitoring
|
|||
cache_rx_req_stall = "event=0x09,evtype=0x01,portid=0xff"
|
||||
cache_eviction = "event=0x0a,evtype=0x01,portid=0xff"
|
||||
|
||||
Fabric events (evtype=0x02)
|
||||
Fabric events (evtype=0x02)::
|
||||
|
||||
fab_pcie0_read = "event=0x00,evtype=0x02,portid=0xff"
|
||||
fab_pcie0_write = "event=0x01,evtype=0x02,portid=0xff"
|
||||
|
|
@ -78,7 +78,7 @@ Description: Read-only. Attribute group to describe performance monitoring
|
|||
fab_port_mmio_read = "event=0x06,evtype=0x02,portid=?"
|
||||
fab_port_mmio_write = "event=0x07,evtype=0x02,portid=?"
|
||||
|
||||
VTD events (evtype=0x03)
|
||||
VTD events (evtype=0x03)::
|
||||
|
||||
vtd_port_read_transaction = "event=0x00,evtype=0x03,portid=?"
|
||||
vtd_port_write_transaction = "event=0x01,evtype=0x03,portid=?"
|
||||
|
|
@ -88,7 +88,7 @@ Description: Read-only. Attribute group to describe performance monitoring
|
|||
vtd_port_devtlb_2m_fill = "event=0x05,evtype=0x03,portid=?"
|
||||
vtd_port_devtlb_1g_fill = "event=0x06,evtype=0x03,portid=?"
|
||||
|
||||
VTD SIP events (evtype=0x04)
|
||||
VTD SIP events (evtype=0x04)::
|
||||
|
||||
vtd_sip_iotlb_4k_hit = "event=0x00,evtype=0x04,portid=0xff"
|
||||
vtd_sip_iotlb_2m_hit = "event=0x01,evtype=0x04,portid=0xff"
|
||||
|
|
|
|||
|
|
@ -10,7 +10,8 @@ Description:
|
|||
name/value pairs.
|
||||
|
||||
Userspace must be prepared for the possibility that attributes
|
||||
define overlapping bit ranges. For example:
|
||||
define overlapping bit ranges. For example::
|
||||
|
||||
attr1 = 'config:0-23'
|
||||
attr2 = 'config:0-7'
|
||||
attr3 = 'config:12-35'
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Description: Read-only. Attribute group to describe the magic bits
|
|||
|
||||
Each attribute under this group defines a bit range of the
|
||||
perf_event_attr.config. All supported attributes are listed
|
||||
below.
|
||||
below::
|
||||
|
||||
chip = "config:16-31"
|
||||
core = "config:16-31"
|
||||
|
|
@ -16,9 +16,9 @@ Description: Read-only. Attribute group to describe the magic bits
|
|||
offset = "config:32-63"
|
||||
vcpu = "config:16-31"
|
||||
|
||||
For example,
|
||||
For example::
|
||||
|
||||
PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"
|
||||
PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"
|
||||
|
||||
In this event, '?' after chip specifies that
|
||||
this value will be provided by user while running this event.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Description: Read-only. Attribute group to describe the magic bits
|
|||
|
||||
Each attribute under this group defines a bit range of the
|
||||
perf_event_attr.config. All supported attributes are listed
|
||||
below.
|
||||
below::
|
||||
|
||||
counter_info_version = "config:16-23"
|
||||
length = "config:24-31"
|
||||
|
|
@ -20,9 +20,9 @@ Description: Read-only. Attribute group to describe the magic bits
|
|||
secondary_index = "config:0-15"
|
||||
starting_index = "config:32-63"
|
||||
|
||||
For example,
|
||||
For example::
|
||||
|
||||
processor_core_utilization_instructions_completed = "request=0x94,
|
||||
processor_core_utilization_instructions_completed = "request=0x94,
|
||||
phys_processor_idx=?,counter_info_version=0x8,
|
||||
length=8,offset=0x18"
|
||||
|
||||
|
|
@ -36,6 +36,7 @@ Description:
|
|||
'0' if the hypervisor is configured to forbid access to event
|
||||
counters being accumulated by other guests and to physical
|
||||
domain event counters.
|
||||
|
||||
'1' if that access is allowed.
|
||||
|
||||
What: /sys/bus/event_source/devices/hv_gpci/interface/ga
|
||||
|
|
|
|||
|
|
@ -3,16 +3,19 @@ Date: August 2012
|
|||
KernelVersion: TBD
|
||||
Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
|
||||
Description: The FCoE bus. Attributes in this directory are control interfaces.
|
||||
|
||||
Attributes:
|
||||
|
||||
ctlr_create: 'FCoE Controller' instance creation interface. Writing an
|
||||
ctlr_create:
|
||||
'FCoE Controller' instance creation interface. Writing an
|
||||
<ifname> to this file will allocate and populate sysfs with a
|
||||
fcoe_ctlr_device (ctlr_X). The user can then configure any
|
||||
per-port settings and finally write to the fcoe_ctlr_device's
|
||||
'start' attribute to begin the kernel's discovery and login
|
||||
process.
|
||||
|
||||
ctlr_destroy: 'FCoE Controller' instance removal interface. Writing a
|
||||
ctlr_destroy:
|
||||
'FCoE Controller' instance removal interface. Writing a
|
||||
fcoe_ctlr_device's sysfs name to this file will log the
|
||||
fcoe_ctlr_device out of the fabric or otherwise connected
|
||||
FCoE devices. It will also free all kernel memory allocated
|
||||
|
|
@ -32,11 +35,13 @@ Description: 'FCoE Controller' instances on the fcoe bus.
|
|||
|
||||
Attributes:
|
||||
|
||||
fcf_dev_loss_tmo: Device loss timeout period (see below). Changing
|
||||
fcf_dev_loss_tmo:
|
||||
Device loss timeout period (see below). Changing
|
||||
this value will change the dev_loss_tmo for all
|
||||
FCFs discovered by this controller.
|
||||
|
||||
mode: Display or change the FCoE Controller's mode. Possible
|
||||
mode:
|
||||
Display or change the FCoE Controller's mode. Possible
|
||||
modes are 'Fabric' and 'VN2VN'. If a FCoE Controller
|
||||
is started in 'Fabric' mode then FIP FCF discovery is
|
||||
initiated and ultimately a fabric login is attempted.
|
||||
|
|
@ -44,23 +49,30 @@ Attributes:
|
|||
FIP VN2VN discovery and login is performed. A FCoE
|
||||
Controller only supports one mode at a time.
|
||||
|
||||
enabled: Whether an FCoE controller is enabled or disabled.
|
||||
enabled:
|
||||
Whether an FCoE controller is enabled or disabled.
|
||||
0 if disabled, 1 if enabled. Writing either 0 or 1
|
||||
to this file will enable or disable the FCoE controller.
|
||||
|
||||
lesb/link_fail: Link Error Status Block (LESB) link failure count.
|
||||
lesb/link_fail:
|
||||
Link Error Status Block (LESB) link failure count.
|
||||
|
||||
lesb/vlink_fail: Link Error Status Block (LESB) virtual link
|
||||
lesb/vlink_fail:
|
||||
Link Error Status Block (LESB) virtual link
|
||||
failure count.
|
||||
|
||||
lesb/miss_fka: Link Error Status Block (LESB) missed FCoE
|
||||
lesb/miss_fka:
|
||||
Link Error Status Block (LESB) missed FCoE
|
||||
Initialization Protocol (FIP) Keep-Alives (FKA).
|
||||
|
||||
lesb/symb_err: Link Error Status Block (LESB) symbolic error count.
|
||||
lesb/symb_err:
|
||||
Link Error Status Block (LESB) symbolic error count.
|
||||
|
||||
lesb/err_block: Link Error Status Block (LESB) block error count.
|
||||
lesb/err_block:
|
||||
Link Error Status Block (LESB) block error count.
|
||||
|
||||
lesb/fcs_error: Link Error Status Block (LESB) Fibre Channel
|
||||
lesb/fcs_error:
|
||||
Link Error Status Block (LESB) Fibre Channel
|
||||
Services error count.
|
||||
|
||||
Notes: ctlr_X (global increment starting at 0)
|
||||
|
|
@ -75,31 +87,41 @@ Description: 'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel
|
|||
Fibre Channel frames into a FC fabric. It can also take
|
||||
outbound FC frames and pack them in Ethernet packets to
|
||||
be sent to their destination on the Ethernet segment.
|
||||
|
||||
Attributes:
|
||||
|
||||
fabric_name: Identifies the fabric that the FCF services.
|
||||
fabric_name:
|
||||
Identifies the fabric that the FCF services.
|
||||
|
||||
switch_name: Identifies the FCF.
|
||||
switch_name:
|
||||
Identifies the FCF.
|
||||
|
||||
priority: The switch's priority amongst other FCFs on the same
|
||||
priority:
|
||||
The switch's priority amongst other FCFs on the same
|
||||
fabric.
|
||||
|
||||
selected: 1 indicates that the switch has been selected for use;
|
||||
selected:
|
||||
1 indicates that the switch has been selected for use;
|
||||
0 indicates that the switch will not be used.
|
||||
|
||||
fc_map: The Fibre Channel MAP
|
||||
fc_map:
|
||||
The Fibre Channel MAP
|
||||
|
||||
vfid: The Virtual Fabric ID
|
||||
vfid:
|
||||
The Virtual Fabric ID
|
||||
|
||||
mac: The FCF's MAC address
|
||||
mac:
|
||||
The FCF's MAC address
|
||||
|
||||
fka_period: The FIP Keep-Alive period
|
||||
fka_period:
|
||||
The FIP Keep-Alive period
|
||||
|
||||
fabric_state: The internal kernel state
|
||||
"Unknown" - Initialization value
|
||||
"Disconnected" - No link to the FCF/fabric
|
||||
"Connected" - Host is connected to the FCF
|
||||
"Deleted" - FCF is being removed from the system
|
||||
|
||||
- "Unknown" - Initialization value
|
||||
- "Disconnected" - No link to the FCF/fabric
|
||||
- "Connected" - Host is connected to the FCF
|
||||
- "Deleted" - FCF is being removed from the system
|
||||
|
||||
dev_loss_tmo: The device loss timeout period for this FCF.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,8 +6,10 @@ Description:
|
|||
the driver to attempt to bind to the device found at
|
||||
this location. The format for the location is Object.Id
|
||||
and is the same as found in /sys/bus/fsl-mc/devices/.
|
||||
For example:
|
||||
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind
|
||||
|
||||
For example::
|
||||
|
||||
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind
|
||||
|
||||
What: /sys/bus/fsl-mc/drivers/.../unbind
|
||||
Date: December 2016
|
||||
|
|
@ -17,5 +19,7 @@ Description:
|
|||
driver to attempt to unbind from the device found at
|
||||
this location. The format for the location is Object.Id
|
||||
and is the same as found in /sys/bus/fsl-mc/devices/.
|
||||
For example:
|
||||
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind
|
||||
|
||||
For example::
|
||||
|
||||
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind
|
||||
|
|
|
|||
|
|
@ -3,19 +3,25 @@ Date: February 2011
|
|||
Contact: Minkyu Kang <mk7.kang@samsung.com>
|
||||
Description:
|
||||
show what device is attached
|
||||
NONE - no device
|
||||
USB - USB device is attached
|
||||
UART - UART is attached
|
||||
CHARGER - Charger is attaced
|
||||
JIG - JIG is attached
|
||||
|
||||
======= ======================
|
||||
NONE no device
|
||||
USB USB device is attached
|
||||
UART UART is attached
|
||||
CHARGER Charger is attaced
|
||||
JIG JIG is attached
|
||||
======= ======================
|
||||
|
||||
What: /sys/bus/i2c/devices/.../switch
|
||||
Date: February 2011
|
||||
Contact: Minkyu Kang <mk7.kang@samsung.com>
|
||||
Description:
|
||||
show or set the state of manual switch
|
||||
VAUDIO - switch to VAUDIO path
|
||||
UART - switch to UART path
|
||||
AUDIO - switch to AUDIO path
|
||||
DHOST - switch to DHOST path
|
||||
AUTO - switch automatically by device
|
||||
|
||||
======= ==============================
|
||||
VAUDIO switch to VAUDIO path
|
||||
UART switch to UART path
|
||||
AUDIO switch to AUDIO path
|
||||
DHOST switch to DHOST path
|
||||
AUTO switch automatically by device
|
||||
======= ==============================
|
||||
|
|
|
|||
|
|
@ -6,15 +6,18 @@ Description:
|
|||
Value that exists only for mux devices that can be
|
||||
written to control the behaviour of the multiplexer on
|
||||
idle. Possible values:
|
||||
-2 - disconnect on idle, i.e. deselect the last used
|
||||
channel, which is useful when there is a device
|
||||
with an address that conflicts with another
|
||||
device on another mux on the same parent bus.
|
||||
-1 - leave the mux as-is, which is the most optimal
|
||||
setting in terms of I2C operations and is the
|
||||
default mode.
|
||||
0..<nchans> - set the mux to a predetermined channel,
|
||||
which is useful if there is one channel that is
|
||||
used almost always, and you want to reduce the
|
||||
latency for normal operations after rare
|
||||
transactions on other channels
|
||||
|
||||
=========== ===============================================
|
||||
-2 disconnect on idle, i.e. deselect the last used
|
||||
channel, which is useful when there is a device
|
||||
with an address that conflicts with another
|
||||
device on another mux on the same parent bus.
|
||||
-1 leave the mux as-is, which is the most optimal
|
||||
setting in terms of I2C operations and is the
|
||||
default mode.
|
||||
0..<nchans> set the mux to a predetermined channel,
|
||||
which is useful if there is one channel that is
|
||||
used almost always, and you want to reduce the
|
||||
latency for normal operations after rare
|
||||
transactions on other channels
|
||||
=========== ===============================================
|
||||
|
|
|
|||
|
|
@ -84,6 +84,7 @@ Description:
|
|||
by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".
|
||||
See the I3C specification for more details about these HDR
|
||||
modes.
|
||||
|
||||
This entry describes the HDRCAP of the master controller
|
||||
driving the bus.
|
||||
|
||||
|
|
@ -135,6 +136,7 @@ Description:
|
|||
Expose the HDR (High Data Rate) capabilities of a device.
|
||||
Returns a list of supported HDR mode, each element is separated
|
||||
by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".
|
||||
|
||||
See the I3C specification for more details about these HDR
|
||||
modes.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,7 @@ Description:
|
|||
based on hardware generated events (e.g. data ready) or
|
||||
provided by a separate driver for other hardware (e.g.
|
||||
periodic timer, GPIO or high resolution timer).
|
||||
|
||||
Contains trigger type specific elements. These do not
|
||||
generalize well and hence are not documented in this file.
|
||||
X is the IIO index of the trigger.
|
||||
|
|
@ -65,6 +66,7 @@ Contact: linux-iio@vger.kernel.org
|
|||
Description:
|
||||
When the internal sampling clock can only take a specific set of
|
||||
frequencies, we can specify the available values with:
|
||||
|
||||
- a small discrete set of values like "0 2 4 6 8"
|
||||
- a range with minimum, step and maximum frequencies like
|
||||
"[min step max]"
|
||||
|
|
@ -665,6 +667,7 @@ Description:
|
|||
<type>[Y][_name]_<raw|input>_thresh_falling_value may take
|
||||
different values, but the device can only enable both thresholds
|
||||
or neither.
|
||||
|
||||
Note the driver will assume the last p events requested are
|
||||
to be enabled where p is how many it supports (which may vary
|
||||
depending on the exact set requested. So if you want to be
|
||||
|
|
@ -719,6 +722,7 @@ Description:
|
|||
<type>[Y][_name]_<raw|input>_roc_falling_value may take
|
||||
different values, but the device can only enable both rate of
|
||||
change thresholds or neither.
|
||||
|
||||
Note the driver will assume the last p events requested are
|
||||
to be enabled where p is however many it supports (which may
|
||||
vary depending on the exact set requested. So if you want to be
|
||||
|
|
@ -774,9 +778,11 @@ Description:
|
|||
Specifies the value of threshold that the device is comparing
|
||||
against for the events enabled by
|
||||
<type>Y[_name]_thresh[_rising|falling]_en.
|
||||
|
||||
If separate attributes exist for the two directions, but
|
||||
direction is not specified for this attribute, then a single
|
||||
threshold value applies to both directions.
|
||||
|
||||
The raw or input element of the name indicates whether the
|
||||
value is in raw device units or in processed units (as _raw
|
||||
and _input do on sysfs direct channel read attributes).
|
||||
|
|
@ -859,6 +865,7 @@ Description:
|
|||
If separate attributes exist for the two directions, but
|
||||
direction is not specified for this attribute, then a single
|
||||
hysteresis value applies to both directions.
|
||||
|
||||
For falling events the hysteresis is added to the _value attribute for
|
||||
this event to get the upper threshold for when the event goes back to
|
||||
normal, for rising events the hysteresis is subtracted from the _value
|
||||
|
|
@ -905,6 +912,7 @@ Description:
|
|||
Specifies the value of rate of change threshold that the
|
||||
device is comparing against for the events enabled by
|
||||
<type>[Y][_name]_roc[_rising|falling]_en.
|
||||
|
||||
If separate attributes exist for the two directions,
|
||||
but direction is not specified for this attribute,
|
||||
then a single threshold value applies to both directions.
|
||||
|
|
@ -1304,6 +1312,7 @@ Description:
|
|||
Proximity measurement indicating that some
|
||||
object is near the sensor, usually by observing
|
||||
reflectivity of infrared or ultrasound emitted.
|
||||
|
||||
Often these sensors are unit less and as such conversion
|
||||
to SI units is not possible. Higher proximity measurements
|
||||
indicate closer objects, and vice versa. Units after
|
||||
|
|
@ -1449,9 +1458,12 @@ Contact: linux-iio@vger.kernel.org
|
|||
Description:
|
||||
A single positive integer specifying the maximum number of scan
|
||||
elements to wait for.
|
||||
|
||||
Poll will block until the watermark is reached.
|
||||
|
||||
Blocking read will wait until the minimum between the requested
|
||||
read amount or the low water mark is available.
|
||||
|
||||
Non-blocking read will retrieve the available samples from the
|
||||
buffer even if there are less samples then watermark level. This
|
||||
allows the application to block on poll with a timeout and read
|
||||
|
|
@ -1480,11 +1492,13 @@ Description:
|
|||
device settings allows it (e.g. if a trigger is set that samples
|
||||
data differently that the hardware fifo does then hardware fifo
|
||||
will not enabled).
|
||||
|
||||
If the hardware fifo is enabled and the level of the hardware
|
||||
fifo reaches the hardware fifo watermark level the device will
|
||||
flush its hardware fifo to the device buffer. Doing a non
|
||||
blocking read on the device when no samples are present in the
|
||||
device buffer will also force a flush.
|
||||
|
||||
When the hardware fifo is enabled there is no need to use a
|
||||
trigger to use buffer mode since the watermark settings
|
||||
guarantees that the hardware fifo is flushed to the device
|
||||
|
|
@ -1522,6 +1536,7 @@ Description:
|
|||
A single positive integer specifying the minimum watermark level
|
||||
for the hardware fifo of this device. If the device does not
|
||||
have a hardware fifo this entry is not present.
|
||||
|
||||
If the user sets buffer/watermark to a value less than this one,
|
||||
then the hardware watermark will remain unset.
|
||||
|
||||
|
|
@ -1532,6 +1547,7 @@ Description:
|
|||
A single positive integer specifying the maximum watermark level
|
||||
for the hardware fifo of this device. If the device does not
|
||||
have a hardware fifo this entry is not present.
|
||||
|
||||
If the user sets buffer/watermark to a value greater than this
|
||||
one, then the hardware watermark will be capped at this value.
|
||||
|
||||
|
|
@ -1543,6 +1559,7 @@ Description:
|
|||
levels for the hardware fifo. This entry is optional and if it
|
||||
is not present it means that all the values between
|
||||
hwfifo_watermark_min and hwfifo_watermark_max are supported.
|
||||
|
||||
If the user sets buffer/watermark to a value greater than
|
||||
hwfifo_watermak_min but not equal to any of the values in this
|
||||
list, the driver will chose an appropriate value for the
|
||||
|
|
@ -1604,7 +1621,8 @@ KernelVersion: 4.1.0
|
|||
Contact: linux-iio@vger.kernel.org
|
||||
Description:
|
||||
'1' (enable) or '0' (disable) specifying the enable
|
||||
of heater function. Same reading values apply
|
||||
of heater function. Same reading values apply.
|
||||
|
||||
This ABI is especially applicable for humidity sensors
|
||||
to heatup the device and get rid of any condensation
|
||||
in some humidity environment
|
||||
|
|
@ -1627,17 +1645,21 @@ Description:
|
|||
Mounting matrix for IIO sensors. This is a rotation matrix which
|
||||
informs userspace about sensor chip's placement relative to the
|
||||
main hardware it is mounted on.
|
||||
|
||||
Main hardware placement is defined according to the local
|
||||
reference frame related to the physical quantity the sensor
|
||||
measures.
|
||||
|
||||
Given that the rotation matrix is defined in a board specific
|
||||
way (platform data and / or device-tree), the main hardware
|
||||
reference frame definition is left to the implementor's choice
|
||||
(see below for a magnetometer example).
|
||||
|
||||
Applications should apply this rotation matrix to samples so
|
||||
that when main hardware reference frame is aligned onto local
|
||||
reference frame, then sensor chip reference frame is also
|
||||
perfectly aligned with it.
|
||||
|
||||
Matrix is a 3x3 unitary matrix and typically looks like
|
||||
[0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
|
||||
[1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware
|
||||
|
|
@ -1646,8 +1668,10 @@ Description:
|
|||
For example, a mounting matrix for a magnetometer sensor informs
|
||||
userspace about sensor chip's ORIENTATION relative to the main
|
||||
hardware.
|
||||
|
||||
More specifically, main hardware orientation is defined with
|
||||
respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where :
|
||||
|
||||
* Y is in the ground plane and positive towards magnetic North ;
|
||||
* X is in the ground plane, perpendicular to the North axis and
|
||||
positive towards the East ;
|
||||
|
|
@ -1656,13 +1680,16 @@ Description:
|
|||
An implementor might consider that for a hand-held device, a
|
||||
'natural' orientation would be 'front facing camera at the top'.
|
||||
The main hardware reference frame could then be described as :
|
||||
|
||||
* Y is in the plane of the screen and is positive towards the
|
||||
top of the screen ;
|
||||
* X is in the plane of the screen, perpendicular to Y axis, and
|
||||
positive towards the right hand side of the screen ;
|
||||
* Z is perpendicular to the screen plane and positive out of the
|
||||
screen.
|
||||
|
||||
Another example for a quadrotor UAV might be :
|
||||
|
||||
* Y is in the plane of the propellers and positive towards the
|
||||
front-view camera;
|
||||
* X is in the plane of the propellers, perpendicular to Y axis,
|
||||
|
|
@ -1704,6 +1731,7 @@ Description:
|
|||
This interface is deprecated; please use the Counter subsystem.
|
||||
|
||||
A list of possible counting directions which are:
|
||||
|
||||
- "up" : counter device is increasing.
|
||||
- "down": counter device is decreasing.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,8 @@ Contact: Peter Rosin <peda@axentia.se>
|
|||
Description:
|
||||
The DAC is used to find the peak level of an alternating
|
||||
voltage input signal by a binary search using the output
|
||||
of a comparator wired to an interrupt pin. Like so:
|
||||
of a comparator wired to an interrupt pin. Like so::
|
||||
|
||||
_
|
||||
| \
|
||||
input +------>-------|+ \
|
||||
|
|
@ -19,10 +20,12 @@ Description:
|
|||
| irq|------<-------'
|
||||
| |
|
||||
'-------'
|
||||
|
||||
The boolean invert attribute (0/1) should be set when the
|
||||
input signal is centered around the maximum value of the
|
||||
dac instead of zero. The envelope detector will search
|
||||
from below in this case and will also invert the result.
|
||||
|
||||
The edge/level of the interrupt is also switched to its
|
||||
opposite value.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,11 @@ Description:
|
|||
is separately set for "GND-Open" and "Supply-Open" modes.
|
||||
Channels 0..31 have common low threshold values, but could have different
|
||||
sensing_modes.
|
||||
|
||||
The low voltage threshold range is between 2..21V.
|
||||
Hysteresis between low and high thresholds can not be lower then 2 and
|
||||
can not be odd.
|
||||
|
||||
If falling threshold results hysteresis to odd value then rising
|
||||
threshold is automatically subtracted by one.
|
||||
|
||||
|
|
@ -34,10 +36,13 @@ Description:
|
|||
this value then the threshold rising event is pushed.
|
||||
Depending on in_voltageY_sensing_mode the high voltage threshold
|
||||
is separately set for "GND-Open" and "Supply-Open" modes.
|
||||
|
||||
Channels 0..31 have common high threshold values, but could have different
|
||||
sensing_modes.
|
||||
|
||||
The high voltage threshold range is between 3..22V.
|
||||
Hysteresis between low and high thresholds can not be lower then 2 and
|
||||
can not be odd.
|
||||
|
||||
If rising threshold results hysteresis to odd value then falling
|
||||
threshold is automatically appended by one.
|
||||
|
|
|
|||
|
|
@ -5,10 +5,13 @@ Description:
|
|||
The STM32 ADC can be configured to use external trigger sources
|
||||
(e.g. timers, pwm or exti gpio). Then, it can be tuned to start
|
||||
conversions on external trigger by either:
|
||||
|
||||
- "rising-edge"
|
||||
- "falling-edge"
|
||||
- "both-edges".
|
||||
|
||||
Reading returns current trigger polarity.
|
||||
|
||||
Writing value before enabling conversions sets trigger polarity.
|
||||
|
||||
What: /sys/bus/iio/devices/triggerX/trigger_polarity_available
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ KernelVersion: 4.7
|
|||
Contact: linux-iio@vger.kernel.org
|
||||
Description:
|
||||
Writing '1' will perform a FOC (Fast Online Calibration). The
|
||||
corresponding calibration offsets can be read from *_calibbias
|
||||
corresponding calibration offsets can be read from `*_calibbias`
|
||||
entries.
|
||||
|
||||
What: /sys/bus/iio/devices/iio:deviceX/location
|
||||
|
|
|
|||
|
|
@ -3,14 +3,20 @@ KernelVersion: 4.14
|
|||
Contact: arnaud.pouliquen@st.com
|
||||
Description:
|
||||
For audio purpose only.
|
||||
|
||||
Used by audio driver to set/get the spi input frequency.
|
||||
|
||||
This is mandatory if DFSDM is slave on SPI bus, to
|
||||
provide information on the SPI clock frequency during runtime
|
||||
Notice that the SPI frequency should be a multiple of sample
|
||||
frequency to ensure the precision.
|
||||
if DFSDM input is SPI master
|
||||
|
||||
if DFSDM input is SPI master:
|
||||
|
||||
Reading SPI clkout frequency,
|
||||
error on writing
|
||||
|
||||
If DFSDM input is SPI Slave:
|
||||
|
||||
Reading returns value previously set.
|
||||
Writing value before starting conversions.
|
||||
|
|
|
|||
|
|
@ -15,8 +15,11 @@ Description:
|
|||
first object echoed in meters. Default value is 6.020.
|
||||
This setting limits the time the driver is waiting for a
|
||||
echo.
|
||||
|
||||
Showing the range of available values is represented as the
|
||||
minimum value, the step and the maximum value, all enclosed
|
||||
in square brackets.
|
||||
Example:
|
||||
[0.043 0.043 11.008]
|
||||
|
||||
Example::
|
||||
|
||||
[0.043 0.043 11.008]
|
||||
|
|
|
|||
|
|
@ -8,7 +8,9 @@ KernelVersion: 3.4.0
|
|||
Contact: linux-iio@vger.kernel.org
|
||||
Description:
|
||||
Reading returns either '1' or '0'.
|
||||
|
||||
'1' means that the clock in question is present.
|
||||
|
||||
'0' means that the clock is missing.
|
||||
|
||||
What: /sys/bus/iio/devices/iio:deviceX/pllY_locked
|
||||
|
|
|
|||
|
|
@ -27,12 +27,12 @@ What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_name
|
|||
KernelVersion:
|
||||
Contact: linux-iio@vger.kernel.org
|
||||
Description:
|
||||
Reading returns the datasheet name for channel Y:
|
||||
Reading returns the datasheet name for channel Y::
|
||||
|
||||
out_altvoltage0_name: RF8x
|
||||
out_altvoltage1_name: RFAUX8x
|
||||
out_altvoltage2_name: RF16x
|
||||
out_altvoltage3_name: RF32x
|
||||
out_altvoltage0_name: RF8x
|
||||
out_altvoltage1_name: RFAUX8x
|
||||
out_altvoltage2_name: RF16x
|
||||
out_altvoltage3_name: RF32x
|
||||
|
||||
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
|
||||
KernelVersion:
|
||||
|
|
|
|||
|
|
@ -6,10 +6,14 @@ Description:
|
|||
Get measured values from the ADC for these stages. Y is the
|
||||
specific stage number corresponding to datasheet stage names
|
||||
as follows:
|
||||
1 -> LED2
|
||||
2 -> ALED2/LED3
|
||||
3 -> LED1
|
||||
4 -> ALED1/LED4
|
||||
|
||||
== ==========
|
||||
1 LED2
|
||||
2 ALED2/LED3
|
||||
3 LED1
|
||||
4 ALED1/LED4
|
||||
== ==========
|
||||
|
||||
Note that channels 5 and 6 represent LED2-ALED2 and LED1-ALED1
|
||||
respectively which simply helper channels containing the
|
||||
calculated difference in the value of stage 1 - 2 and 3 - 4.
|
||||
|
|
|
|||
|
|
@ -15,5 +15,7 @@ Description:
|
|||
Scheme 0 has wider dynamic range, Scheme 1 proximity detection
|
||||
is less affected by the ambient IR noise variation.
|
||||
|
||||
0 Sensing IR from LED and ambient
|
||||
1 Sensing IR from LED with ambient IR rejection
|
||||
== =============================================
|
||||
0 Sensing IR from LED and ambient
|
||||
1 Sensing IR from LED with ambient IR rejection
|
||||
== =============================================
|
||||
|
|
|
|||
|
|
@ -17,9 +17,11 @@ KernelVersion: 4.13
|
|||
Contact: fabrice.gasnier@st.com
|
||||
Description:
|
||||
Configure the device counter quadrature modes:
|
||||
|
||||
- non-quadrature:
|
||||
Encoder IN1 input servers as the count input (up
|
||||
direction).
|
||||
|
||||
- quadrature:
|
||||
Encoder IN1 and IN2 inputs are mixed to get direction
|
||||
and count.
|
||||
|
|
@ -35,23 +37,26 @@ KernelVersion: 4.13
|
|||
Contact: fabrice.gasnier@st.com
|
||||
Description:
|
||||
Configure the device encoder/counter active edge:
|
||||
|
||||
- rising-edge
|
||||
- falling-edge
|
||||
- both-edges
|
||||
|
||||
In non-quadrature mode, device counts up on active edge.
|
||||
|
||||
In quadrature mode, encoder counting scenarios are as follows:
|
||||
----------------------------------------------------------------
|
||||
|
||||
+---------+----------+--------------------+--------------------+
|
||||
| Active | Level on | IN1 signal | IN2 signal |
|
||||
| edge | opposite |------------------------------------------
|
||||
| edge | opposite +----------+---------+----------+---------+
|
||||
| | signal | Rising | Falling | Rising | Falling |
|
||||
----------------------------------------------------------------
|
||||
| Rising | High -> | Down | - | Up | - |
|
||||
| edge | Low -> | Up | - | Down | - |
|
||||
----------------------------------------------------------------
|
||||
| Falling | High -> | - | Up | - | Down |
|
||||
| edge | Low -> | - | Down | - | Up |
|
||||
----------------------------------------------------------------
|
||||
| Both | High -> | Down | Up | Up | Down |
|
||||
| edges | Low -> | Up | Down | Down | Up |
|
||||
----------------------------------------------------------------
|
||||
+---------+----------+----------+---------+----------+---------+
|
||||
| Rising | High -> | Down | - | Up | - |
|
||||
| edge | Low -> | Up | - | Down | - |
|
||||
+---------+----------+----------+---------+----------+---------+
|
||||
| Falling | High -> | - | Up | - | Down |
|
||||
| edge | Low -> | - | Down | - | Up |
|
||||
+---------+----------+----------+---------+----------+---------+
|
||||
| Both | High -> | Down | Up | Up | Down |
|
||||
| edges | Low -> | Up | Down | Down | Up |
|
||||
+---------+----------+----------+---------+----------+---------+
|
||||
|
|
|
|||
|
|
@ -5,11 +5,16 @@ Contact: linux-iio@vger.kernel.org
|
|||
Description:
|
||||
Current configuration and available configurations
|
||||
for the bias current.
|
||||
normal - Normal measurement configurations (default)
|
||||
positivebias - Positive bias configuration
|
||||
negativebias - Negative bias configuration
|
||||
disabled - Only available on HMC5983. Disables magnetic
|
||||
|
||||
============ ============================================
|
||||
normal Normal measurement configurations (default)
|
||||
positivebias Positive bias configuration
|
||||
negativebias Negative bias configuration
|
||||
disabled Only available on HMC5983. Disables magnetic
|
||||
sensor and enables temperature sensor.
|
||||
Note: The effect of this configuration may vary
|
||||
according to the device. For exact documentation
|
||||
check the device's datasheet.
|
||||
============ ============================================
|
||||
|
||||
Note:
|
||||
The effect of this configuration may vary
|
||||
according to the device. For exact documentation
|
||||
check the device's datasheet.
|
||||
|
|
|
|||
|
|
@ -5,9 +5,12 @@ Description:
|
|||
Open-circuit fault. The detection of open-circuit faults,
|
||||
such as those caused by broken thermocouple wires.
|
||||
Reading returns either '1' or '0'.
|
||||
'1' = An open circuit such as broken thermocouple wires
|
||||
has been detected.
|
||||
'0' = No open circuit or broken thermocouple wires are detected
|
||||
|
||||
=== =======================================================
|
||||
'1' An open circuit such as broken thermocouple wires
|
||||
has been detected.
|
||||
'0' No open circuit or broken thermocouple wires are detected
|
||||
=== =======================================================
|
||||
|
||||
What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv
|
||||
KernelVersion: 5.1
|
||||
|
|
@ -18,7 +21,11 @@ Description:
|
|||
cables by integrated MOSFETs at the T+ and T- inputs, and the
|
||||
BIAS output. These MOSFETs turn off when the input voltage is
|
||||
negative or greater than VDD.
|
||||
|
||||
Reading returns either '1' or '0'.
|
||||
'1' = The input voltage is negative or greater than VDD.
|
||||
'0' = The input voltage is positive and less than VDD (normal
|
||||
state).
|
||||
|
||||
=== =======================================================
|
||||
'1' The input voltage is negative or greater than VDD.
|
||||
'0' The input voltage is positive and less than VDD (normal
|
||||
state).
|
||||
=== =======================================================
|
||||
|
|
|
|||
|
|
@ -3,67 +3,85 @@ KernelVersion: 4.11
|
|||
Contact: benjamin.gaignard@st.com
|
||||
Description:
|
||||
Reading returns the list possible master modes which are:
|
||||
- "reset" : The UG bit from the TIMx_EGR register is
|
||||
|
||||
|
||||
- "reset"
|
||||
The UG bit from the TIMx_EGR register is
|
||||
used as trigger output (TRGO).
|
||||
- "enable" : The Counter Enable signal CNT_EN is used
|
||||
- "enable"
|
||||
The Counter Enable signal CNT_EN is used
|
||||
as trigger output.
|
||||
- "update" : The update event is selected as trigger output.
|
||||
- "update"
|
||||
The update event is selected as trigger output.
|
||||
For instance a master timer can then be used
|
||||
as a prescaler for a slave timer.
|
||||
- "compare_pulse" : The trigger output send a positive pulse
|
||||
when the CC1IF flag is to be set.
|
||||
- "OC1REF" : OC1REF signal is used as trigger output.
|
||||
- "OC2REF" : OC2REF signal is used as trigger output.
|
||||
- "OC3REF" : OC3REF signal is used as trigger output.
|
||||
- "OC4REF" : OC4REF signal is used as trigger output.
|
||||
- "compare_pulse"
|
||||
The trigger output send a positive pulse
|
||||
when the CC1IF flag is to be set.
|
||||
- "OC1REF"
|
||||
OC1REF signal is used as trigger output.
|
||||
- "OC2REF"
|
||||
OC2REF signal is used as trigger output.
|
||||
- "OC3REF"
|
||||
OC3REF signal is used as trigger output.
|
||||
- "OC4REF"
|
||||
OC4REF signal is used as trigger output.
|
||||
|
||||
Additional modes (on TRGO2 only):
|
||||
- "OC5REF" : OC5REF signal is used as trigger output.
|
||||
- "OC6REF" : OC6REF signal is used as trigger output.
|
||||
|
||||
- "OC5REF"
|
||||
OC5REF signal is used as trigger output.
|
||||
- "OC6REF"
|
||||
OC6REF signal is used as trigger output.
|
||||
- "compare_pulse_OC4REF":
|
||||
OC4REF rising or falling edges generate pulses.
|
||||
OC4REF rising or falling edges generate pulses.
|
||||
- "compare_pulse_OC6REF":
|
||||
OC6REF rising or falling edges generate pulses.
|
||||
OC6REF rising or falling edges generate pulses.
|
||||
- "compare_pulse_OC4REF_r_or_OC6REF_r":
|
||||
OC4REF or OC6REF rising edges generate pulses.
|
||||
OC4REF or OC6REF rising edges generate pulses.
|
||||
- "compare_pulse_OC4REF_r_or_OC6REF_f":
|
||||
OC4REF rising or OC6REF falling edges generate pulses.
|
||||
OC4REF rising or OC6REF falling edges generate
|
||||
pulses.
|
||||
- "compare_pulse_OC5REF_r_or_OC6REF_r":
|
||||
OC5REF or OC6REF rising edges generate pulses.
|
||||
OC5REF or OC6REF rising edges generate pulses.
|
||||
- "compare_pulse_OC5REF_r_or_OC6REF_f":
|
||||
OC5REF rising or OC6REF falling edges generate pulses.
|
||||
OC5REF rising or OC6REF falling edges generate
|
||||
pulses.
|
||||
|
||||
+-----------+ +-------------+ +---------+
|
||||
| Prescaler +-> | Counter | +-> | Master | TRGO(2)
|
||||
+-----------+ +--+--------+-+ |-> | Control +-->
|
||||
| | || +---------+
|
||||
+--v--------+-+ OCxREF || +---------+
|
||||
| Chx compare +----------> | Output | ChX
|
||||
+-----------+-+ | | Control +-->
|
||||
. | | +---------+
|
||||
. | | .
|
||||
+-----------v-+ OC6REF | .
|
||||
| Ch6 compare +---------+>
|
||||
+-------------+
|
||||
::
|
||||
|
||||
Example with: "compare_pulse_OC4REF_r_or_OC6REF_r":
|
||||
+-----------+ +-------------+ +---------+
|
||||
| Prescaler +-> | Counter | +-> | Master | TRGO(2)
|
||||
+-----------+ +--+--------+-+ |-> | Control +-->
|
||||
| | || +---------+
|
||||
+--v--------+-+ OCxREF || +---------+
|
||||
| Chx compare +----------> | Output | ChX
|
||||
+-----------+-+ | | Control +-->
|
||||
. | | +---------+
|
||||
. | | .
|
||||
+-----------v-+ OC6REF | .
|
||||
| Ch6 compare +---------+>
|
||||
+-------------+
|
||||
|
||||
X
|
||||
X X
|
||||
X . . X
|
||||
X . . X
|
||||
X . . X
|
||||
count X . . . . X
|
||||
. . . .
|
||||
. . . .
|
||||
+---------------+
|
||||
OC4REF | . . |
|
||||
+-+ . . +-+
|
||||
. +---+ .
|
||||
OC6REF . | | .
|
||||
+-------+ +-------+
|
||||
+-+ +-+
|
||||
TRGO2 | | | |
|
||||
+-+ +---+ +---------+
|
||||
Example with: "compare_pulse_OC4REF_r_or_OC6REF_r"::
|
||||
|
||||
X
|
||||
X X
|
||||
X . . X
|
||||
X . . X
|
||||
X . . X
|
||||
count X . . . . X
|
||||
. . . .
|
||||
. . . .
|
||||
+---------------+
|
||||
OC4REF | . . |
|
||||
+-+ . . +-+
|
||||
. +---+ .
|
||||
OC6REF . | | .
|
||||
+-------+ +-------+
|
||||
+-+ +-+
|
||||
TRGO2 | | | |
|
||||
+-+ +---+ +---------+
|
||||
|
||||
What: /sys/bus/iio/devices/triggerX/master_mode
|
||||
KernelVersion: 4.11
|
||||
|
|
@ -104,6 +122,7 @@ Description:
|
|||
Configure the device counter enable modes, in all case
|
||||
counting direction is set by in_count0_count_direction
|
||||
attribute and the counter is clocked by the internal clock.
|
||||
|
||||
always:
|
||||
Counter is always ON.
|
||||
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче