]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/blame - Documentation/ABI/testing/sysfs-platform-hidma-mgmt
Merge remote-tracking branches 'asoc/fix/arizona', 'asoc/fix/dpcm', 'asoc/fix/dwc...
[mirror_ubuntu-zesty-kernel.git] / Documentation / ABI / testing / sysfs-platform-hidma-mgmt
CommitLineData
7f8f209f
SK
1What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
2 /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
3Date: Nov 2015
4KernelVersion: 4.4
5Contact: "Sinan Kaya <okaya@cudeaurora.org>"
6Description:
7 Contains either 0 or 1 and indicates if the DMA channel is a
8 low priority (0) or high priority (1) channel.
9
10What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/weight
11 /sys/devices/platform/QCOM8060:*/chanops/chan*/weight
12Date: Nov 2015
13KernelVersion: 4.4
14Contact: "Sinan Kaya <okaya@cudeaurora.org>"
15Description:
16 Contains 0..15 and indicates the weight of the channel among
17 equal priority channels during round robin scheduling.
18
19What: /sys/devices/platform/hidma-mgmt*/chreset_timeout_cycles
20 /sys/devices/platform/QCOM8060:*/chreset_timeout_cycles
21Date: Nov 2015
22KernelVersion: 4.4
23Contact: "Sinan Kaya <okaya@cudeaurora.org>"
24Description:
25 Contains the platform specific cycle value to wait after a
26 reset command is issued. If the value is chosen too short,
27 then the HW will issue a reset failure interrupt. The value
28 is platform specific and should not be changed without
29 consultance.
30
31What: /sys/devices/platform/hidma-mgmt*/dma_channels
32 /sys/devices/platform/QCOM8060:*/dma_channels
33Date: Nov 2015
34KernelVersion: 4.4
35Contact: "Sinan Kaya <okaya@cudeaurora.org>"
36Description:
37 Contains the number of dma channels supported by one instance
38 of HIDMA hardware. The value may change from chip to chip.
39
40What: /sys/devices/platform/hidma-mgmt*/hw_version_major
41 /sys/devices/platform/QCOM8060:*/hw_version_major
42Date: Nov 2015
43KernelVersion: 4.4
44Contact: "Sinan Kaya <okaya@cudeaurora.org>"
45Description:
46 Version number major for the hardware.
47
48What: /sys/devices/platform/hidma-mgmt*/hw_version_minor
49 /sys/devices/platform/QCOM8060:*/hw_version_minor
50Date: Nov 2015
51KernelVersion: 4.4
52Contact: "Sinan Kaya <okaya@cudeaurora.org>"
53Description:
54 Version number minor for the hardware.
55
56What: /sys/devices/platform/hidma-mgmt*/max_rd_xactions
57 /sys/devices/platform/QCOM8060:*/max_rd_xactions
58Date: Nov 2015
59KernelVersion: 4.4
60Contact: "Sinan Kaya <okaya@cudeaurora.org>"
61Description:
62 Contains a value between 0 and 31. Maximum number of
63 read transactions that can be issued back to back.
64 Choosing a higher number gives better performance but
65 can also cause performance reduction to other peripherals
66 sharing the same bus.
67
68What: /sys/devices/platform/hidma-mgmt*/max_read_request
69 /sys/devices/platform/QCOM8060:*/max_read_request
70Date: Nov 2015
71KernelVersion: 4.4
72Contact: "Sinan Kaya <okaya@cudeaurora.org>"
73Description:
74 Size of each read request. The value needs to be a power
75 of two and can be between 128 and 1024.
76
77What: /sys/devices/platform/hidma-mgmt*/max_wr_xactions
78 /sys/devices/platform/QCOM8060:*/max_wr_xactions
79Date: Nov 2015
80KernelVersion: 4.4
81Contact: "Sinan Kaya <okaya@cudeaurora.org>"
82Description:
83 Contains a value between 0 and 31. Maximum number of
84 write transactions that can be issued back to back.
85 Choosing a higher number gives better performance but
86 can also cause performance reduction to other peripherals
87 sharing the same bus.
88
89
90What: /sys/devices/platform/hidma-mgmt*/max_write_request
91 /sys/devices/platform/QCOM8060:*/max_write_request
92Date: Nov 2015
93KernelVersion: 4.4
94Contact: "Sinan Kaya <okaya@cudeaurora.org>"
95Description:
96 Size of each write request. The value needs to be a power
97 of two and can be between 128 and 1024.