Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 473e0bc3 编写于 作者: E Emmanuel Grumbach
浏览文件
操作

Merge tag 'mac80211-next-for-davem-2015-08-14' into next 

Another pull request for the next cycle, this time with quite
a bit of content:
 * mesh fixes/improvements from Alexis, Bob, Chun-Yeow and Jesse
 * TDLS higher bandwidth support (Arik)
 * OCB fixes from Bertold Van den Bergh
 * suspend/resume fixes from Eliad
 * dynamic SMPS support for minstrel-HT (Krishna Chaitanya)
 * VHT bitrate mask support (Lorenzo Bianconi)
 * better regulatory support for 5/10 MHz channels (Matthias May)
 * basic support for MU-MIMO to avoid the multi-vif issue (Sara Sharon)
along with a number of other cleanups.
上级 1a84e771 8f9c98df
无相关合并请求
展开全部 隐藏空白更改
内联 并排
Showing with 54463 addition and 17186 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.mailmap
浏览文件 @ 473e0bc3
......@@ -84,6 +84,7 @@ Mayuresh Janorkar <mayur@ti.com>
Michael Buesch <m@bues.ch>
Michel Dänzer <michel@tungstengraphics.com>
Mitesh shah <mshah@teja.com>
Mohit Kumar <mohit.kumar@st.com> <mohit.kumar.dhaka@gmail.com>
Morten Welinder <terra@gnome.org>
Morten Welinder <welinder@anemone.rentec.com>
Morten Welinder <welinder@darter.rentec.com>
......@@ -95,10 +96,12 @@ Patrick Mochel <mochel@digitalimplant.org>
Peter A Jonsson <pj@ludd.ltu.se>
Peter Oruba <peter@oruba.de>
Peter Oruba <peter.oruba@amd.com>
Pratyush Anand <pratyush.anand@gmail.com> <pratyush.anand@st.com>
Praveen BP <praveenbp@ti.com>
Rajesh Shah <rajesh.shah@intel.com>
Ralf Baechle <ralf@linux-mips.org>
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Randy Dunlap <rdunlap@infradead.org> <rdunlap@xenotime.net>
Rémi Denis-Courmont <rdenis@simphalempin.com>
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Rudolf Marek <R.Marek@sh.cvut.cz>
......
CREDITS
浏览文件 @ 473e0bc3
......@@ -2740,6 +2740,10 @@ S: C/ Mieses 20, 9-B
S: Valladolid 47009
S: Spain
N: Jens Osterkamp
E: jens@de.ibm.com
D: Maintainer of Spidernet network driver for Cell
N: Gadi Oxman
E: gadio@netvision.net.il
D: Original author and maintainer of IDE/ATAPI floppy/tape drivers
......@@ -3219,11 +3223,6 @@ N: Dipankar Sarma
E: dipankar@in.ibm.com
D: RCU
N: Yoshinori Sato
E: ysato@users.sourceforge.jp
D: uClinux for Renesas H8/300 (H8300)
D: http://uclinux-h8.sourceforge.jp/
N: Hannu Savolainen
E: hannu@opensound.com
D: Maintainer of the sound drivers until 2.1.x days.
......
Documentation/ABI/stable/sysfs-bus-w1 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/bus/w1/devices/.../w1_master_timeout_us
Date: April 2015
Contact: Dmitry Khromov <dk@icelogic.net>
Description: Bus scanning interval, microseconds component.
Some of 1-Wire devices commonly associated with physical access
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 for detailed information.
Users: any user space application which wants to know bus scanning
interval
Documentation/ABI/stable/sysfs-driver-w1_ds28ea00 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/bus/w1/devices/.../w1_seq
Date: Apr 2015
Contact: Matt Campbell <mattrcampbell@gmail.com>
Description: Support for the DS28EA00 chain sequence function
see Documentation/w1/slaves/w1_therm for detailed information
Users: any user space application which wants to communicate with DS28EA00
Documentation/ABI/testing/configfs-spear-pcie-gadget
浏览文件 @ 473e0bc3
What: /config/pcie-gadget
Date: Feb 2011
KernelVersion: 2.6.37
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Interface is used to configure selected dual mode PCIe controller
......
Documentation/ABI/testing/dev-kmsg
浏览文件 @ 473e0bc3
......@@ -98,4 +98,13 @@ Description: The /dev/kmsg character device node provides userspace access
logic is used internally when messages are printed to the
console, /proc/kmsg or the syslog() syscall.
By default, kernel tries to avoid fragments by concatenating
when it can and fragments are rare; however, when extended
console support is enabled, the in-kernel concatenation is
disabled and /dev/kmsg output will contain more fragments. If
the log consumer performs concatenation, the end result
should be the same. In the future, the in-kernel concatenation
may be removed entirely and /dev/kmsg users are recommended to
implement fragment handling.
Users: dmesg(1), userspace kernel log consumers
Documentation/ABI/testing/ima_policy
浏览文件 @ 473e0bc3
......@@ -20,17 +20,19 @@ Description:
action: measure | dont_measure | appraise | dont_appraise | audit
condition:= base | lsm [option]
base: [[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
[fowner]]
[euid=] [fowner=]]
lsm: [[subj_user=] [subj_role=] [subj_type=]
[obj_user=] [obj_role=] [obj_type=]]
option: [[appraise_type=]] [permit_directio]
base: func:= [BPRM_CHECK][MMAP_CHECK][FILE_CHECK][MODULE_CHECK]
[FIRMWARE_CHECK]
mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC]
mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND]
[[^]MAY_EXEC]
fsmagic:= hex value
fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6)
uid:= decimal value
euid:= decimal value
fowner:=decimal value
lsm: are LSM specific
option: appraise_type:= [imasig]
......@@ -49,11 +51,25 @@ Description:
dont_measure fsmagic=0x01021994
dont_appraise fsmagic=0x01021994
# RAMFS_MAGIC
dont_measure fsmagic=0x858458f6
dont_appraise fsmagic=0x858458f6
# DEVPTS_SUPER_MAGIC
dont_measure fsmagic=0x1cd1
dont_appraise fsmagic=0x1cd1
# BINFMTFS_MAGIC
dont_measure fsmagic=0x42494e4d
dont_appraise fsmagic=0x42494e4d
# SECURITYFS_MAGIC
dont_measure fsmagic=0x73636673
dont_appraise fsmagic=0x73636673
# SELINUX_MAGIC
dont_measure fsmagic=0xf97cff8c
dont_appraise fsmagic=0xf97cff8c
# CGROUP_SUPER_MAGIC
dont_measure fsmagic=0x27e0eb
dont_appraise fsmagic=0x27e0eb
# NSFS_MAGIC
dont_measure fsmagic=0x6e736673
dont_appraise fsmagic=0x6e736673
measure func=BPRM_CHECK
measure func=FILE_MMAP mask=MAY_EXEC
......@@ -70,10 +86,6 @@ Description:
Examples of LSM specific definitions:
SELinux:
# SELINUX_MAGIC
dont_measure fsmagic=0xf97cff8c
dont_appraise fsmagic=0xf97cff8c
dont_measure obj_type=var_log_t
dont_appraise obj_type=var_log_t
dont_measure obj_type=auditd_log_t
......
Documentation/ABI/testing/sysfs-ata
浏览文件 @ 473e0bc3
......@@ -90,6 +90,17 @@ gscr
130: SATA_PMP_GSCR_SII_GPIO
Only valid if the device is a PM.
trim
Shows the DSM TRIM mode currently used by the device. Valid
values are:
unsupported: Drive does not support DSM TRIM
unqueued: Drive supports unqueued DSM TRIM only
queued: Drive supports queued DSM TRIM
forced_unqueued: Drive's queued DSM support is known to be
buggy and only unqueued TRIM commands
are sent
spdn_cnt
Number of time libata decided to lower the speed of link due to errors.
......
Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/bus/coresight/devices/<memory_map>.etm/enable_source
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Enable/disable tracing on this specific trace entiry.
Enabling a source implies the source has been configured
properly and a sink has been identidifed for it. The path
of coresight components linking the source to the sink is
configured and managed automatically by the coresight framework.
What: /sys/bus/coresight/devices/<memory_map>.etm/cpu
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (R) The CPU this tracing entity is associated with.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
available for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
available for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
available for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/nrseqstate
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (R) Indicates the number of sequencer states that are
implemented.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
available for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
are available for tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
to its boot configuration.
What: /sys/bus/coresight/devices/<memory_map>.etm/mode
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls various modes supported by this ETM, for example
P0 instruction tracing, branch broadcast, cycle counting and
context ID tracing.
What: /sys/bus/coresight/devices/<memory_map>.etm/pe
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls which PE to trace.
What: /sys/bus/coresight/devices/<memory_map>.etm/event
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls the tracing of arbitrary events from bank 0 to 3.
What: /sys/bus/coresight/devices/<memory_map>.etm/event_instren
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls the behavior of the events in bank 0 to 3.
What: /sys/bus/coresight/devices/<memory_map>.etm/event_ts
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls the insertion of global timestamps in the trace
streams.
What: /sys/bus/coresight/devices/<memory_map>.etm/syncfreq
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls how often trace synchronization requests occur.
What: /sys/bus/coresight/devices/<memory_map>.etm/cyc_threshold
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Sets the threshold value for cycle counting.
What: /sys/bus/coresight/devices/<memory_map>.etm/bb_ctrl
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls which regions in the memory map are enabled to
use branch broadcasting.
What: /sys/bus/coresight/devices/<memory_map>.etm/event_vinst
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls instruction trace filtering.
What: /sys/bus/coresight/devices/<memory_map>.etm/s_exlevel_vinst
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) In Secure state, each bit controls whether instruction
tracing is enabled for the corresponding exception level.
What: /sys/bus/coresight/devices/<memory_map>.etm/ns_exlevel_vinst
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) In non-secure state, each bit controls whether instruction
tracing is enabled for the corresponding exception level.
What: /sys/bus/coresight/devices/<memory_map>.etm/addr_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which address comparator or pair (of comparators) to
work with.
What: /sys/bus/coresight/devices/<memory_map>.etm/addr_instdatatype
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls what type of comparison the trace unit performs.
What: /sys/bus/coresight/devices/<memory_map>.etm/addr_single
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Used to setup single address comparator values.
What: /sys/bus/coresight/devices/<memory_map>.etm/addr_range
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Used to setup address range comparator values.
What: /sys/bus/coresight/devices/<memory_map>.etm/seq_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which sequensor.
What: /sys/bus/coresight/devices/<memory_map>.etm/seq_state
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Use this to set, or read, the sequencer state.
What: /sys/bus/coresight/devices/<memory_map>.etm/seq_event
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Moves the sequencer state to a specific state.
What: /sys/bus/coresight/devices/<memory_map>.etm/seq_reset_event
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Moves the sequencer to state 0 when a programmed event
occurs.
What: /sys/bus/coresight/devices/<memory_map>.etm/cntr_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which counter unit to work with.
What: /sys/bus/coresight/devices/<memory_map>.etm/cntrldvr
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) This sets or returns the reload count value of the
specific counter.
What: /sys/bus/coresight/devices/<memory_map>.etm/cntr_val
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) This sets or returns the current count value of the
specific counter.
What: /sys/bus/coresight/devices/<memory_map>.etm/cntr_ctrl
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls the operation of the selected counter.
What: /sys/bus/coresight/devices/<memory_map>.etm/res_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which resource selection unit to work with.
What: /sys/bus/coresight/devices/<memory_map>.etm/res_ctrl
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Controls the selection of the resources in the trace unit.
What: /sys/bus/coresight/devices/<memory_map>.etm/ctxid_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which context ID comparator to work with.
What: /sys/bus/coresight/devices/<memory_map>.etm/ctxid_val
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Get/Set the context ID comparator value to trigger on.
What: /sys/bus/coresight/devices/<memory_map>.etm/ctxid_masks
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Mask for all 8 context ID comparator value
registers (if implemented).
What: /sys/bus/coresight/devices/<memory_map>.etm/vmid_idx
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Select which virtual machine ID comparator to work with.
What: /sys/bus/coresight/devices/<memory_map>.etm/vmid_val
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Get/Set the virtual machine ID comparator value to
trigger on.
What: /sys/bus/coresight/devices/<memory_map>.etm/vmid_masks
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (RW) Mask for all 8 virtual machine ID comparator value
registers (if implemented).
What: /sys/bus/coresight/devices/<memory_map>.etm/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).
The value it taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0x310). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0x314). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFB4). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFB8). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFC8). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFCC). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFE0). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFE4). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFE8). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
(0xFEC). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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).
The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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).
The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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,
VMID, context ID and instuction address in the trace unit
(0x1E8). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/trcidr/trcidr3
Date: April 2015
KernelVersion: 4.01
Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
Description: (R) 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.
What: /sys/bus/coresight/devices/<memory_map>.etm/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).
The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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).
The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
trace stream. (0x180). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
can use (0x184). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
can use (0x188). The value is taken directly from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
trace unit can use (0x18C). The value is taken directly from
the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
the trace unit can use (0x190). The value is taken directly
from the HW.
What: /sys/bus/coresight/devices/<memory_map>.etm/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
that the trace unit can use (0x194). The value is taken
directly from the HW.
Documentation/ABI/testing/sysfs-bus-fcoe
浏览文件 @ 473e0bc3
......@@ -32,7 +32,7 @@ Description: 'FCoE Controller' instances on the fcoe bus.
Attributes:
fcf_dev_loss_tmo: Device loss timeout peroid (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.
......@@ -61,7 +61,7 @@ Attributes:
lesb/err_block: Link Error Status Block (LESB) block error count.
lesb/fcs_error: Link Error Status Block (LESB) Fibre Channel
Serivces error count.
Services error count.
Notes: ctlr_X (global increment starting at 0)
......@@ -85,7 +85,7 @@ Attributes:
fabric.
selected: 1 indicates that the switch has been selected for use;
0 indicates that the swich will not be used.
0 indicates that the switch will not be used.
fc_map: The Fibre Channel MAP
......@@ -93,7 +93,7 @@ Attributes:
mac: The FCF's MAC address
fka_peroid: The FIP Keep-Alive peroid
fka_period: The FIP Keep-Alive period
fabric_state: The internal kernel state
"Unknown" - Initialization value
......@@ -101,9 +101,9 @@ Attributes:
"Connected" - Host is connected to the FCF
"Deleted" - FCF is being removed from the system
dev_loss_tmo: The device loss timeout peroid for this FCF.
dev_loss_tmo: The device loss timeout period for this FCF.
Notes: A device loss infrastructre similar to the FC Transport's
Notes: A device loss infrastructure similar to the FC Transport's
is present in fcoe_sysfs. It is nice to have so that a
link flapping adapter doesn't continually advance the count
used to identify the discovered FCF. FCFs will exist in a
......
Documentation/ABI/testing/sysfs-bus-iio
浏览文件 @ 473e0bc3
......@@ -71,6 +71,8 @@ Description:
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_raw
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_raw
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
......@@ -81,6 +83,11 @@ Description:
unique to allow association with event codes. Units after
application of scale and offset are millivolts.
Channels with 'i' and 'q' modifiers always exist in pairs and both
channels refer to the same signal. The 'i' channel contains the in-phase
component of the signal while the 'q' channel contains the quadrature
component.
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
......@@ -246,8 +253,16 @@ What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_offset
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_offset
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_offset
What: /sys/bus/iio/devices/iio:deviceX/in_current_offset
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_offset
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_offset
What: /sys/bus/iio/devices/iio:deviceX/in_current_q_offset
What: /sys/bus/iio/devices/iio:deviceX/in_current_i_offset
What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
......@@ -273,14 +288,22 @@ Description:
to the _raw output.
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale
What: /sys/bus/iio/devices/iio:deviceX/in_current_scale
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_scale
What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_scale
What: /sys/bus/iio/devices/iio:deviceX/in_current_i_scale
What: /sys/bus/iio/devices/iio:deviceX/in_current_q_scale
What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
......@@ -328,6 +351,10 @@ Description:
What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
......@@ -420,6 +447,16 @@ Description:
to the underlying data channel, then this parameter
gives the 3dB frequency of the filter in Hz.
What: /sys/.../in_accel_filter_high_pass_3db_frequency
What: /sys/.../in_anglvel_filter_high_pass_3db_frequency
What: /sys/.../in_magn_filter_high_pass_3db_frequency
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
If a known or controllable high pass filter is applied
to the underlying data channel, then this parameter
gives the 3dB frequency of the filter in Hz.
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
KernelVersion: 2.6.37
......@@ -880,6 +917,26 @@ Description:
met before an event is generated. If direction is not
specified then this period applies to both directions.
What: /sys/.../events/in_accel_thresh_rising_low_pass_filter_3db
What: /sys/.../events/in_anglvel_thresh_rising_low_pass_filter_3db
What: /sys/.../events/in_magn_thresh_rising_low_pass_filter_3db
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
If a low pass filter can be applied to the event generation
this property gives its 3db frequency in Hz.
A value of zero disables the filter.
What: /sys/.../events/in_accel_thresh_rising_high_pass_filter_3db
What: /sys/.../events/in_anglvel_thresh_rising_high_pass_filter_3db
What: /sys/.../events/in_magn_thresh_rising_high_pass_filter_3db
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
If a high pass filter can be applied to the event generation
this property gives its 3db frequency in Hz.
A value of zero disables the filter.
What: /sys/.../events/in_activity_still_thresh_rising_en
What: /sys/.../events/in_activity_still_thresh_falling_en
What: /sys/.../events/in_activity_walking_thresh_rising_en
......@@ -1016,6 +1073,10 @@ What: /sys/.../iio:deviceX/scan_elements/in_timestamp_en
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_en
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_en
What: /sys/.../iio:deviceX/scan_elements/in_voltageY-voltageZ_en
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_en
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_en
What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_en
What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_en
What: /sys/.../iio:deviceX/scan_elements/in_incli_x_en
What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en
......@@ -1034,6 +1095,10 @@ What: /sys/.../iio:deviceX/scan_elements/in_incli_type
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_type
What: /sys/.../iio:deviceX/scan_elements/in_voltage_type
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_type
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_type
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_type
What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_type
What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_type
What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type
What: /sys/.../iio:deviceX/scan_elements/in_pressure_type
......@@ -1071,6 +1136,10 @@ Description:
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_index
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_index
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_index
What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_index
What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_index
What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_index
What: /sys/.../iio:deviceX/scan_elements/in_accel_x_index
What: /sys/.../iio:deviceX/scan_elements/in_accel_y_index
What: /sys/.../iio:deviceX/scan_elements/in_accel_z_index
......@@ -1230,6 +1299,8 @@ Description:
or without compensation from tilt sensors.
What: /sys/bus/iio/devices/iio:deviceX/in_currentX_raw
What: /sys/bus/iio/devices/iio:deviceX/in_currentX_i_raw
What: /sys/bus/iio/devices/iio:deviceX/in_currentX_q_raw
KernelVersion: 3.18
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1238,6 +1309,11 @@ Description:
present, output should be considered as processed with the
unit in milliamps.
Channels with 'i' and 'q' modifiers always exist in pairs and both
channels refer to the same signal. The 'i' channel contains the in-phase
component of the signal while the 'q' channel contains the quadrature
component.
What: /sys/.../iio:deviceX/in_energy_en
What: /sys/.../iio:deviceX/in_distance_en
What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_en
......@@ -1364,3 +1440,26 @@ Description:
hwfifo_watermak_min but not equal to any of the values in this
list, the driver will chose an appropriate value for the
hardware fifo watermark level.
What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibemissivity
What: /sys/bus/iio/devices/iio:deviceX/in_tempX_calibemissivity
What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibemissivity
What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibemissivity
KernelVersion: 4.1
Contact: linux-iio@vger.kernel.org
Description:
The emissivity ratio of the surface in the field of view of the
contactless temperature sensor. Emissivity varies from 0 to 1,
with 1 being the emissivity of a black body.
What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_oversampling_ratio
What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_oversampling_ratio
What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_oversampling_ratio
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
Hardware applied number of measurements for acquiring one
data point. The HW will do <type>[_name]_oversampling_ratio
measurements and return the average value as output data. Each
value resulted from <type>[_name]_oversampling_ratio measurements
is considered as one sample for <type>[_name]_sampling_frequency.
Documentation/ABI/testing/sysfs-bus-iio-vf610 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/bus/iio/devices/iio:deviceX/conversion_mode
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
Specifies the hardware conversion mode used. The three
available modes are "normal", "high-speed" and "low-power",
where the last is the default mode.
Documentation/ABI/testing/sysfs-bus-mei
浏览文件 @ 473e0bc3
......@@ -4,4 +4,18 @@ KernelVersion: 3.10
Contact: Samuel Ortiz <sameo@linux.intel.com>
linux-mei@linux.intel.com
Description: Stores the same MODALIAS value emitted by uevent
Format: mei:<mei device name>
Format: mei:<mei device name>:<device uuid>:
What: /sys/bus/mei/devices/.../name
Date: May 2015
KernelVersion: 4.2
Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Stores mei client device name
Format: string
What: /sys/bus/mei/devices/.../uuid
Date: May 2015
KernelVersion: 4.2
Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Stores mei client device uuid
Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Documentation/ABI/testing/sysfs-bus-usb-lvstest
浏览文件 @ 473e0bc3
......@@ -4,14 +4,14 @@ driver is bound with root hub device.
What: /sys/bus/usb/devices/.../get_dev_desc
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Write to this node to issue "Get Device Descriptor"
for Link Layer Validation device. It is needed for TD.7.06.
What: /sys/bus/usb/devices/.../u1_timeout
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Set "U1 timeout" for the downstream port where Link Layer
Validation device is connected. Timeout value must be between 0
......@@ -19,7 +19,7 @@ Description:
What: /sys/bus/usb/devices/.../u2_timeout
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Set "U2 timeout" for the downstream port where Link Layer
Validation device is connected. Timeout value must be between 0
......@@ -27,21 +27,21 @@ Description:
What: /sys/bus/usb/devices/.../hot_reset
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Write to this node to issue "Reset" for Link Layer Validation
device. It is needed for TD.7.29, TD.7.31, TD.7.34 and TD.7.35.
What: /sys/bus/usb/devices/.../u3_entry
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Write to this node to issue "U3 entry" for Link Layer
Validation device. It is needed for TD.7.35 and TD.7.36.
What: /sys/bus/usb/devices/.../u3_exit
Date: March 2014
Contact: Pratyush Anand <pratyush.anand@st.com>
Contact: Pratyush Anand <pratyush.anand@gmail.com>
Description:
Write to this node to issue "U3 exit" for Link Layer
Validation device. It is needed for TD.7.36.
Documentation/ABI/testing/sysfs-class-zram 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/class/zram-control/
Date: August 2015
KernelVersion: 4.2
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The zram-control/ class sub-directory belongs to zram
device class
What: /sys/class/zram-control/hot_add
Date: August 2015
KernelVersion: 4.2
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
RO attribute. Read operation will cause zram to add a new
device and return its device id back to user (so one can
use /dev/zram<id>), or error code.
What: /sys/class/zram-control/hot_remove
Date: August 2015
KernelVersion: 4.2
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
WO attribute. Remove a specific /dev/zramX device, where X
is a device_id provided by user.
Documentation/ABI/testing/sysfs-devices-system-cpu
浏览文件 @ 473e0bc3
......@@ -243,7 +243,7 @@ Description: Parameters for the CPU cache attributes
coherency_line_size: the minimum amount of data in bytes that gets
transferred from memory to cache
level: the cache hierarcy in the multi-level cache configuration
level: the cache hierarchy in the multi-level cache configuration
number_of_sets: total number of sets in the cache, a set is a
collection of cache lines with the same cache index
......
Documentation/ABI/testing/sysfs-driver-toshiba_haps 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/protection_level
Date: August 16, 2014
KernelVersion: 3.17
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the built-in accelerometer protection level,
valid values are:
* 0 -> Disabled
* 1 -> Low
* 2 -> Medium
* 3 -> High
The default potection value is set to 2 (Medium).
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/reset_protection
Date: August 16, 2014
KernelVersion: 3.17
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file turns off the built-in accelerometer for a few
seconds and then restore normal operation. Accepting 1 as the
only parameter.
Documentation/ABI/testing/sysfs-firmware-dmi 已删除 100644 → 0
浏览文件 @ 1a84e771
What: /sys/firmware/dmi/
Date: February 2011
Contact: Mike Waychison <mikew@google.com>
Description:
Many machines' firmware (x86 and ia64) export DMI /
SMBIOS tables to the operating system. Getting at this
information is often valuable to userland, especially in
cases where there are OEM extensions used.
The kernel itself does not rely on the majority of the
information in these tables being correct. It equally
cannot ensure that the data as exported to userland is
without error either.
DMI is structured as a large table of entries, where
each entry has a common header indicating the type and
length of the entry, as well as a firmware-provided
'handle' that is supposed to be unique amongst all
entries.
Some entries are required by the specification, but many
others are optional. In general though, users should
never expect to find a specific entry type on their
system unless they know for certain what their firmware
is doing. Machine to machine experiences will vary.
Multiple entries of the same type are allowed. In order
to handle these duplicate entry types, each entry is
assigned by the operating system an 'instance', which is
derived from an entry type's ordinal position. That is
to say, if there are 'N' multiple entries with the same type
'T' in the DMI tables (adjacent or spread apart, it
doesn't matter), they will be represented in sysfs as
entries "T-0" through "T-(N-1)":
Example entry directories:
/sys/firmware/dmi/entries/17-0
/sys/firmware/dmi/entries/17-1
/sys/firmware/dmi/entries/17-2
/sys/firmware/dmi/entries/17-3
...
Instance numbers are used in lieu of the firmware
assigned entry handles as the kernel itself makes no
guarantees that handles as exported are unique, and
there are likely firmware images that get this wrong in
the wild.
Each DMI entry in sysfs has the common header values
exported as attributes:
handle : The 16bit 'handle' that is assigned to this
entry by the firmware. This handle may be
referred to by other entries.
length : The length of the entry, as presented in the
entry itself. Note that this is _not the
total count of bytes associated with the
entry_. This value represents the length of
the "formatted" portion of the entry. This
"formatted" region is sometimes followed by
the "unformatted" region composed of nul
terminated strings, with termination signalled
by a two nul characters in series.
raw : The raw bytes of the entry. This includes the
"formatted" portion of the entry, the
"unformatted" strings portion of the entry,
and the two terminating nul characters.
type : The type of the entry. This value is the same
as found in the directory name. It indicates
how the rest of the entry should be interpreted.
instance: The instance ordinal of the entry for the
given type. This value is the same as found
in the parent directory name.
position: The ordinal position (zero-based) of the entry
within the entirety of the DMI entry table.
=== Entry Specialization ===
Some entry types may have other information available in
sysfs. Not all types are specialized.
--- Type 15 - System Event Log ---
This entry allows the firmware to export a log of
events the system has taken. This information is
typically backed by nvram, but the implementation
details are abstracted by this table. This entry's data
is exported in the directory:
/sys/firmware/dmi/entries/15-0/system_event_log
and has the following attributes (documented in the
SMBIOS / DMI specification under "System Event Log (Type 15)":
area_length
header_start_offset
data_start_offset
access_method
status
change_token
access_method_address
header_format
per_log_type_descriptor_length
type_descriptors_supported_count
As well, the kernel exports the binary attribute:
raw_event_log : The raw binary bits of the event log
as described by the DMI entry.
Documentation/ABI/testing/sysfs-firmware-dmi-entries 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/firmware/dmi/entries/
Date: February 2011
Contact: Mike Waychison <mikew@google.com>
Description:
Many machines' firmware (x86 and ia64) export DMI /
SMBIOS tables to the operating system. Getting at this
information is often valuable to userland, especially in
cases where there are OEM extensions used.
The kernel itself does not rely on the majority of the
information in these tables being correct. It equally
cannot ensure that the data as exported to userland is
without error either.
DMI is structured as a large table of entries, where
each entry has a common header indicating the type and
length of the entry, as well as a firmware-provided
'handle' that is supposed to be unique amongst all
entries.
Some entries are required by the specification, but many
others are optional. In general though, users should
never expect to find a specific entry type on their
system unless they know for certain what their firmware
is doing. Machine to machine experiences will vary.
Multiple entries of the same type are allowed. In order
to handle these duplicate entry types, each entry is
assigned by the operating system an 'instance', which is
derived from an entry type's ordinal position. That is
to say, if there are 'N' multiple entries with the same type
'T' in the DMI tables (adjacent or spread apart, it
doesn't matter), they will be represented in sysfs as
entries "T-0" through "T-(N-1)":
Example entry directories:
/sys/firmware/dmi/entries/17-0
/sys/firmware/dmi/entries/17-1
/sys/firmware/dmi/entries/17-2
/sys/firmware/dmi/entries/17-3
...
Instance numbers are used in lieu of the firmware
assigned entry handles as the kernel itself makes no
guarantees that handles as exported are unique, and
there are likely firmware images that get this wrong in
the wild.
Each DMI entry in sysfs has the common header values
exported as attributes:
handle : The 16bit 'handle' that is assigned to this
entry by the firmware. This handle may be
referred to by other entries.
length : The length of the entry, as presented in the
entry itself. Note that this is _not the
total count of bytes associated with the
entry_. This value represents the length of
the "formatted" portion of the entry. This
"formatted" region is sometimes followed by
the "unformatted" region composed of nul
terminated strings, with termination signalled
by a two nul characters in series.
raw : The raw bytes of the entry. This includes the
"formatted" portion of the entry, the
"unformatted" strings portion of the entry,
and the two terminating nul characters.
type : The type of the entry. This value is the same
as found in the directory name. It indicates
how the rest of the entry should be interpreted.
instance: The instance ordinal of the entry for the
given type. This value is the same as found
in the parent directory name.
position: The ordinal position (zero-based) of the entry
within the entirety of the DMI entry table.
=== Entry Specialization ===
Some entry types may have other information available in
sysfs. Not all types are specialized.
--- Type 15 - System Event Log ---
This entry allows the firmware to export a log of
events the system has taken. This information is
typically backed by nvram, but the implementation
details are abstracted by this table. This entry's data
is exported in the directory:
/sys/firmware/dmi/entries/15-0/system_event_log
and has the following attributes (documented in the
SMBIOS / DMI specification under "System Event Log (Type 15)":
area_length
header_start_offset
data_start_offset
access_method
status
change_token
access_method_address
header_format
per_log_type_descriptor_length
type_descriptors_supported_count
As well, the kernel exports the binary attribute:
raw_event_log : The raw binary bits of the event log
as described by the DMI entry.
Documentation/ABI/testing/sysfs-firmware-dmi-tables 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/firmware/dmi/tables/
Date: April 2015
Contact: Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>
Description:
The firmware provides DMI structures as a packed list of
data referenced by a SMBIOS table entry point. The SMBIOS
entry point contains general information, like SMBIOS
version, DMI table size, etc. The structure, content and
size of SMBIOS entry point is dependent on SMBIOS version.
The format of SMBIOS entry point and DMI structures
can be read in SMBIOS specification.
The dmi/tables provides raw SMBIOS entry point and DMI tables
through sysfs as an alternative to utilities reading them
from /dev/mem. The raw SMBIOS entry point and DMI table are
presented as binary attributes and are accessible via:
/sys/firmware/dmi/tables/smbios_entry_point
/sys/firmware/dmi/tables/DMI
The complete DMI information can be obtained using these two
tables.
Documentation/ABI/testing/sysfs-platform-twl4030-usb 0 → 100644
浏览文件 @ 473e0bc3
What: /sys/bus/platform/devices/*twl4030-usb/vbus
Description:
Read-only status reporting if VBUS (approx 5V)
is being supplied by the USB bus.
Possible values: "on", "off".
Changes are notified via select/poll.
Documentation/CodingStyle
浏览文件 @ 473e0bc3
......@@ -670,7 +670,7 @@ functions:
typeof(x) ret; \
ret = calc_ret(x); \
(ret); \
)}
})
ret is a common name for a local variable - __foo_ret is less likely
to collide with an existing variable.
......
Documentation/DMA-API-HOWTO.txt
浏览文件 @ 473e0bc3
......@@ -245,7 +245,7 @@ the case would look like this:
if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64))) {
using_dac = 1;
consistent_using_dac = 1;
consistent_using_dac = 1;
} else if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32))) {
using_dac = 0;
consistent_using_dac = 0;
......@@ -358,7 +358,7 @@ There are two types of DMA mappings:
transfer, unmapped right after it (unless you use dma_sync_* below)
and for which hardware can optimize for sequential accesses.
This of "streaming" as "asynchronous" or "outside the coherency
Think of "streaming" as "asynchronous" or "outside the coherency
domain".
Good examples of what to use streaming mappings for are:
......
Documentation/DocBook/drm.tmpl
浏览文件 @ 473e0bc3
......@@ -2439,6 +2439,18 @@ void intel_crt_init(struct drm_device *dev)
<title>Tile group</title>
!Pdrivers/gpu/drm/drm_crtc.c Tile group
</sect2>
<sect2>
<title>Bridges</title>
<sect3>
<title>Overview</title>
!Pdrivers/gpu/drm/drm_bridge.c overview
</sect3>
<sect3>
<title>Default bridge callback sequence</title>
!Pdrivers/gpu/drm/drm_bridge.c bridge callbacks
</sect3>
!Edrivers/gpu/drm/drm_bridge.c
</sect2>
</sect1>
<!-- Internals: kms properties -->
......@@ -2573,7 +2585,22 @@ void intel_crt_init(struct drm_device *dev)
<td valign="top" >Description/Restrictions</td>
</tr>
<tr>
<td rowspan="36" valign="top" >DRM</td>
<td rowspan="37" valign="top" >DRM</td>
<td valign="top" >Generic</td>
<td valign="top" >“rotation”</td>
<td valign="top" >BITMASK</td>
<td valign="top" >{ 0, "rotate-0" },
{ 1, "rotate-90" },
{ 2, "rotate-180" },
{ 3, "rotate-270" },
{ 4, "reflect-x" },
{ 5, "reflect-y" }</td>
<td valign="top" >CRTC, Plane</td>
<td valign="top" >rotate-(degrees) rotates the image by the specified amount in degrees
in counter clockwise direction. reflect-x and reflect-y reflects the
image along the specified axis prior to rotation</td>
</tr>
<tr>
<td rowspan="5" valign="top" >Connector</td>
<td valign="top" >“EDID”</td>
<td valign="top" >BLOB | IMMUTABLE</td>
......@@ -2834,7 +2861,7 @@ void intel_crt_init(struct drm_device *dev)
<td valign="top" >TBD</td>
</tr>
<tr>
<td rowspan="21" valign="top" >i915</td>
<td rowspan="20" valign="top" >i915</td>
<td rowspan="2" valign="top" >Generic</td>
<td valign="top" >"Broadcast RGB"</td>
<td valign="top" >ENUM</td>
......@@ -2850,14 +2877,6 @@ void intel_crt_init(struct drm_device *dev)
<td valign="top" >TBD</td>
</tr>
<tr>
<td rowspan="1" valign="top" >Plane</td>
<td valign="top" >“rotation”</td>
<td valign="top" >BITMASK</td>
<td valign="top" >{ 0, "rotate-0" }, { 2, "rotate-180" }</td>
<td valign="top" >Plane</td>
<td valign="top" >TBD</td>
</tr>
<tr>
<td rowspan="17" valign="top" >SDVO-TV</td>
<td valign="top" >“mode”</td>
<td valign="top" >ENUM</td>
......@@ -3365,19 +3384,7 @@ void intel_crt_init(struct drm_device *dev)
</tr>
<tr>
<td rowspan="2" valign="top" >omap</td>
<td rowspan="2" valign="top" >Generic</td>
<td valign="top" >“rotation”</td>
<td valign="top" >BITMASK</td>
<td valign="top" >{ 0, "rotate-0" },
{ 1, "rotate-90" },
{ 2, "rotate-180" },
{ 3, "rotate-270" },
{ 4, "reflect-x" },
{ 5, "reflect-y" }</td>
<td valign="top" >CRTC, Plane</td>
<td valign="top" >TBD</td>
</tr>
<tr>
<td valign="top" >Generic</td>
<td valign="top" >“zorder”</td>
<td valign="top" >RANGE</td>
<td valign="top" >Min=0, Max=3</td>
......@@ -4067,7 +4074,7 @@ int num_ioctls;</synopsis>
<title>DPIO</title>
!Pdrivers/gpu/drm/i915/i915_reg.h DPIO
<table id="dpiox2">
<title>Dual channel PHY (VLV/CHV)</title>
<title>Dual channel PHY (VLV/CHV/BXT)</title>
<tgroup cols="8">
<colspec colname="c0" />
<colspec colname="c1" />
......@@ -4118,7 +4125,7 @@ int num_ioctls;</synopsis>
</tgroup>
</table>
<table id="dpiox1">
<title>Single channel PHY (CHV)</title>
<title>Single channel PHY (CHV/BXT)</title>
<tgroup cols="4">
<colspec colname="c0" />
<colspec colname="c1" />
......@@ -4153,6 +4160,12 @@ int num_ioctls;</synopsis>
</tgroup>
</table>
</sect2>
<sect2>
<title>CSR firmware support for DMC</title>
!Pdrivers/gpu/drm/i915/intel_csr.c csr support for dmc
!Idrivers/gpu/drm/i915/intel_csr.c
</sect2>
</sect1>
<sect1>
......@@ -4204,7 +4217,6 @@ int num_ioctls;</synopsis>
!Idrivers/gpu/drm/i915/i915_gem_shrinker.c
</sect2>
</sect1>
<sect1>
<title> Tracing </title>
<para>
......
Documentation/DocBook/kernel-hacking.tmpl
浏览文件 @ 473e0bc3
......@@ -954,6 +954,8 @@ printk(KERN_INFO "my ip: %pI4\n", &amp;ipaddress);
<function>MODULE_LICENSE()</function> that specifies a GPL
compatible license. It implies that the function is considered
an internal implementation issue, and not really an interface.
Some maintainers and developers may however
require EXPORT_SYMBOL_GPL() when adding any new APIs or functionality.
</para>
</sect1>
</chapter>
......
Documentation/DocBook/media/.gitignore 0 → 100644
浏览文件 @ 473e0bc3
!*.svg
Documentation/DocBook/media/Makefile
浏览文件 @ 473e0bc3
......@@ -65,29 +65,31 @@ IOCTLS = \
$(shell perl -ne 'print "$$1 " if /\#define\s+([^\s]+)\s+_IO/' $(srctree)/include/uapi/linux/dvb/video.h) \
$(shell perl -ne 'print "$$1 " if /\#define\s+([^\s]+)\s+_IO/' $(srctree)/include/uapi/linux/media.h) \
$(shell perl -ne 'print "$$1 " if /\#define\s+([^\s]+)\s+_IO/' $(srctree)/include/uapi/linux/v4l2-subdev.h) \
VIDIOC_SUBDEV_G_FRAME_INTERVAL \
VIDIOC_SUBDEV_S_FRAME_INTERVAL \
VIDIOC_SUBDEV_ENUM_MBUS_CODE \
VIDIOC_SUBDEV_ENUM_FRAME_SIZE \
VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL \
VIDIOC_SUBDEV_G_SELECTION \
VIDIOC_SUBDEV_S_SELECTION \
DEFINES = \
$(shell perl -ne 'print "$$1 " if /\#define\s+(DTV_[^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/frontend.h) \
TYPES = \
$(shell perl -ne 'print "$$1 " if /^typedef\s+[^\s]+\s+([^\s]+)\;/' $(srctree)/include/uapi/linux/videodev2.h) \
$(shell perl -ne 'print "$$1 " if /^}\s+([a-z0-9_]+_t)/' $(srctree)/include/uapi/linux/dvb/frontend.h)
$(shell perl -ne 'print "$$1 " if /^typedef\s+.*\s+(\S+)\;/' $(srctree)/include/uapi/linux/videodev2.h) \
$(shell perl -ne 'print "$$1 " if /^typedef\s+.*\s+(\S+)\;/' $(srctree)/include/uapi/linux/dvb/frontend.h)
ENUMS = \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/videodev2.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/audio.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/ca.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/dmx.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/frontend.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/net.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/dvb/video.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/media.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/v4l2-mediabus.h) \
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/v4l2-subdev.h)
$(shell perl -ne 'print "$$1 " if /^enum\s+([^\s]+)\s+/' \
$(srctree)/include/uapi/linux/videodev2.h \
$(srctree)/include/uapi/linux/dvb/audio.h \
$(srctree)/include/uapi/linux/dvb/ca.h \
$(srctree)/include/uapi/linux/dvb/dmx.h \
$(srctree)/include/uapi/linux/dvb/frontend.h \
$(srctree)/include/uapi/linux/dvb/net.h \
$(srctree)/include/uapi/linux/dvb/video.h \
$(srctree)/include/uapi/linux/media.h \
$(srctree)/include/uapi/linux/v4l2-mediabus.h \
$(srctree)/include/uapi/linux/v4l2-subdev.h)
ENUM_DEFS = \
$(shell perl -e 'open IN,"cat @ARGV| cpp -fpreprocessed |"; while (<IN>) { if ($$enum) {print "$$1\n" if (/\s*([A-Z]\S+)\b/); } $$enum = 0 if ($$enum && /^\}/); $$enum = 1 if(/^\s*enum\s/); }; close IN;' \
$(srctree)/include/uapi/linux/dvb/dmx.h \
$(srctree)/include/uapi/linux/dvb/frontend.h)
STRUCTS = \
$(shell perl -ne 'print "$$1 " if /^struct\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/videodev2.h) \
......@@ -95,7 +97,7 @@ STRUCTS = \
$(shell perl -ne 'print "$$1 " if (/^struct\s+([^\s]+)\s+/)' $(srctree)/include/uapi/linux/dvb/ca.h) \
$(shell perl -ne 'print "$$1 " if (/^struct\s+([^\s]+)\s+/)' $(srctree)/include/uapi/linux/dvb/dmx.h) \
$(shell perl -ne 'print "$$1 " if (!/dtv\_cmds\_h/ && /^struct\s+([^\s]+)\s+/)' $(srctree)/include/uapi/linux/dvb/frontend.h) \
$(shell perl -ne 'print "$$1 " if (/^struct\s+([A-Z][^\s]+)\s+/)' $(srctree)/include/uapi/linux/dvb/net.h) \
$(shell perl -ne 'print "$$1 " if (/^struct\s+([^\s]+)\s+/ && !/_old/)' $(srctree)/include/uapi/linux/dvb/net.h) \
$(shell perl -ne 'print "$$1 " if (/^struct\s+([^\s]+)\s+/)' $(srctree)/include/uapi/linux/dvb/video.h) \
$(shell perl -ne 'print "$$1 " if /^struct\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/media.h) \
$(shell perl -ne 'print "$$1 " if /^struct\s+([^\s]+)\s+/' $(srctree)/include/uapi/linux/v4l2-subdev.h) \
......@@ -179,7 +181,6 @@ DOCUMENTED = \
-e "s/v4l2\-mpeg\-vbi\-ITV0/v4l2-mpeg-vbi-itv0-1/g"
DVB_DOCUMENTED = \
-e "s/\(linkend\=\"\)FE_SET_PROPERTY/\1FE_GET_PROPERTY/g" \
-e "s,\(struct\s\+\)\([a-z0-9_]\+\)\(\s\+{\),\1\<link linkend=\"\2\">\2\<\/link\>\3,g" \
-e "s,\(}\s\+\)\([a-z0-9_]\+_t\+\),\1\<link linkend=\"\2\">\2\<\/link\>,g" \
-e "s,\(define\s\+\)\(DTV_[A-Z0-9_]\+\)\(\s\+[0-9]\+\),\1\<link linkend=\"\2\">\2\<\/link\>\3,g" \
......@@ -188,14 +189,17 @@ DVB_DOCUMENTED = \
-e "s,\(audio-mixer\|audio-karaoke\|audio-status\|ca-slot-info\|ca-descr-info\|ca-caps\|ca-msg\|ca-descr\|ca-pid\|dmx-filter\|dmx-caps\|video-system\|video-highlight\|video-spu\|video-spu-palette\|video-navi-pack\)-t,\1,g" \
-e "s,DTV-ISDBT-LAYER[A-C],DTV-ISDBT-LAYER,g" \
-e "s,\(define\s\+\)\([A-Z0-9_]\+\)\(\s\+_IO\),\1\<link linkend=\"\2\">\2\<\/link\>\3,g" \
-e "s,\(define\s\+\)\(DTV_[A-Z0-9_]\+\)\(\s\+\),\1\<link linkend=\"\2\">\2\<\/link\>\3,g" \
-e "s,<link\s\+linkend=\".*\">\(__.*_OLD\)<\/link>,\1,g" \
-e "s/\(linkend\=\"\)FE_SET_PROPERTY/\1FE_GET_PROPERTY/g" \
-e "s,<link\s\+linkend=\".*\">\(DTV_ISDBS_TS_ID_LEGACY\|DTV_MAX_COMMAND\|DTV_IOCTL_MAX_MSGS\)<\/link>,\1,g" \
#
# Media targets and dependencies
#
install_media_images = \
$(Q)-cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
$(Q)-cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
$(MEDIA_OBJ_DIR)/%: $(MEDIA_SRC_DIR)/%.b64
$(Q)base64 -d $< >$@
......@@ -243,9 +247,14 @@ $(MEDIA_OBJ_DIR)/dmx.h.xml: $(srctree)/include/uapi/linux/dvb/dmx.h $(MEDIA_OBJ_
@( \
echo "<programlisting>") > $@
@( \
for ident in $(ENUM_DEFS) ; do \
entity=`echo $$ident | tr _ -` ; \
r="$$r s/([^\w\-])$$ident([^\w\-])/\1\&$$entity\;\2/g;";\
done; \
expand --tabs=8 < $< | \
sed $(ESCAPE) $(DVB_DOCUMENTED) | \
sed 's/i\.e\./&ie;/') >> $@
sed 's/i\.e\./&ie;/' | \
perl -ne "$$r print $$_;") >> $@
@( \
echo "</programlisting>") >> $@
......@@ -254,9 +263,14 @@ $(MEDIA_OBJ_DIR)/frontend.h.xml: $(srctree)/include/uapi/linux/dvb/frontend.h $(
@( \
echo "<programlisting>") > $@
@( \
for ident in $(ENUM_DEFS) ; do \
entity=`echo $$ident | tr _ -` ; \
r="$$r s/([^\w\-])$$ident([^\w\-])/\1\&$$entity\;\2/g;";\
done; \
expand --tabs=8 < $< | \
sed $(ESCAPE) $(DVB_DOCUMENTED) | \
sed 's/i\.e\./&ie;/') >> $@
sed 's/i\.e\./&ie;/' | \
perl -ne "$$r print $$_;") >> $@
@( \
echo "</programlisting>") >> $@
......@@ -298,11 +312,22 @@ $(MEDIA_OBJ_DIR)/media-entities.tmpl: $(MEDIA_OBJ_DIR)/v4l2.xml
@( \
echo -e "\n<!-- Ioctls -->") >>$@
@( \
for ident in $(IOCTLS) ; do \
for ident in `echo $(IOCTLS) | sed -e "s,VIDIOC_RESERVED,,"`; do\
entity=`echo $$ident | tr _ -` ; \
id=`grep "<refname>$$ident" $(MEDIA_OBJ_DIR)/vidioc-*.xml $(MEDIA_OBJ_DIR)/media-ioc-*.xml | sed -r s,"^.*/(.*).xml.*","\1",` ; \
echo "<!ENTITY $$entity \"<link" \
id=`grep -e "<refname>$$ident" -e "<section id=\"$$ident\"" $$(find $(MEDIA_SRC_DIR) -name *.xml -type f)| sed -r s,"^.*/(.*).xml.*","\1",` ; \
if [ "$$id" != "" ]; then echo "<!ENTITY $$entity \"<link" \
"linkend='$$id'><constant>$$ident</constant></link>\">" \
>>$@ ; else \
echo "Warning: undocumented ioctl: $$ident. Please document it at the media DocBook!" >&2; \
fi; \
done)
@( \
echo -e "\n<!-- Defines -->") >>$@
@( \
for ident in $(DEFINES) ; do \
entity=`echo $$ident | tr _ -` ; \
echo "<!ENTITY $$entity \"<link" \
"linkend='$$entity'><constant>$$ident</constant></link>\">" \
>>$@ ; \
done)
@( \
......@@ -322,6 +347,15 @@ $(MEDIA_OBJ_DIR)/media-entities.tmpl: $(MEDIA_OBJ_DIR)/v4l2.xml
"linkend='$$entity'>$$ident</link>\">" >>$@ ; \
done)
@( \
echo -e "\n<!-- Enum definitions -->") >>$@
@( \
for ident in $(ENUM_DEFS) ; do \
entity=`echo $$ident | tr _ -` ; \
echo "<!ENTITY $$entity \"<link" \
"linkend='$$entity'><constant>$$ident</constant></link>\">" \
>>$@ ; \
done)
@( \
echo -e "\n<!-- Structures -->") >>$@
@( \
for ident in $(STRUCTS) ; do \
......
Documentation/DocBook/media/dvb/audio.xml
浏览文件 @ 473e0bc3
<title>DVB Audio Device</title>
<para>The DVB audio device controls the MPEG2 audio decoder of the DVB hardware. It
can be accessed through <emphasis role="tt">/dev/dvb/adapter0/audio0</emphasis>. Data types and and
ioctl definitions can be accessed by including <emphasis role="tt">linux/dvb/audio.h</emphasis> in your
can be accessed through <constant>/dev/dvb/adapter?/audio?</constant>. Data types and and
ioctl definitions can be accessed by including <constant>linux/dvb/audio.h</constant> in your
application.
</para>
<para>Please note that some DVB cards don&#8217;t have their own MPEG decoder, which results in
......@@ -32,7 +32,7 @@ typedef enum {
</programlisting>
<para>AUDIO_SOURCE_DEMUX selects the demultiplexer (fed either by the frontend or the
DVR device) as the source of the video stream. If AUDIO_SOURCE_MEMORY
is selected the stream comes from the application through the <emphasis role="tt">write()</emphasis> system
is selected the stream comes from the application through the <constant>write()</constant> system
call.
</para>
......
Documentation/DocBook/media/dvb/ca.xml
浏览文件 @ 473e0bc3
<title>DVB CA Device</title>
<para>The DVB CA device controls the conditional access hardware. It can be accessed through
<emphasis role="tt">/dev/dvb/adapter0/ca0</emphasis>. Data types and and ioctl definitions can be accessed by
including <emphasis role="tt">linux/dvb/ca.h</emphasis> in your application.
<constant>/dev/dvb/adapter?/ca?</constant>. Data types and and ioctl definitions can be accessed by
including <constant>linux/dvb/ca.h</constant> in your application.
</para>
<section id="ca_data_types">
......
Documentation/DocBook/media/dvb/demux.xml
浏览文件 @ 473e0bc3
<title>DVB Demux Device</title>
<para>The DVB demux device controls the filters of the DVB hardware/software. It can be
accessed through <emphasis role="tt">/dev/adapter0/demux0</emphasis>. Data types and and ioctl definitions can be
accessed by including <emphasis role="tt">linux/dvb/dmx.h</emphasis> in your application.
accessed through <constant>/dev/adapter?/demux?</constant>. Data types and and ioctl definitions can be
accessed by including <constant>linux/dvb/dmx.h</constant> in your application.
</para>
<section id="dmx_types">
<title>Demux Data Types</title>
<section id="dmx-output-t">
<title>dmx_output_t</title>
<programlisting>
typedef enum
{
DMX_OUT_DECODER, /&#x22C6; Streaming directly to decoder. &#x22C6;/
DMX_OUT_TAP, /&#x22C6; Output going to a memory buffer &#x22C6;/
/&#x22C6; (to be retrieved via the read command).&#x22C6;/
DMX_OUT_TS_TAP, /&#x22C6; Output multiplexed into a new TS &#x22C6;/
/&#x22C6; (to be retrieved by reading from the &#x22C6;/
/&#x22C6; logical DVR device). &#x22C6;/
DMX_OUT_TSDEMUX_TAP /&#x22C6; Like TS_TAP but retrieved from the DMX device &#x22C6;/
} dmx_output_t;
</programlisting>
<para><emphasis role="tt">DMX_OUT_TAP</emphasis> delivers the stream output to the demux device on which the ioctl is
called.
</para>
<para><emphasis role="tt">DMX_OUT_TS_TAP</emphasis> routes output to the logical DVR device <emphasis role="tt">/dev/dvb/adapter0/dvr0</emphasis>,
which delivers a TS multiplexed from all filters for which <emphasis role="tt">DMX_OUT_TS_TAP</emphasis> was
specified.
</para>
<title>Output for the demux</title>
<table pgwide="1" frame="none" id="dmx-output">
<title>enum dmx_output</title>
<tgroup cols="2">
&cs-def;
<thead>
<row>
<entry>ID</entry>
<entry>Description</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry align="char" id="DMX-OUT-DECODER">DMX_OUT_DECODER</entry>
<entry>Streaming directly to decoder.</entry>
</row><row>
<entry align="char" id="DMX-OUT-TAP">DMX_OUT_TAP</entry>
<entry>Output going to a memory buffer (to be retrieved via the
read command). Delivers the stream output to the demux
device on which the ioctl is called.</entry>
</row><row>
<entry align="char" id="DMX-OUT-TS-TAP">DMX_OUT_TS_TAP</entry>
<entry>Output multiplexed into a new TS (to be retrieved by
reading from the logical DVR device). Routes output to the
logical DVR device <constant>/dev/dvb/adapter?/dvr?</constant>,
which delivers a TS multiplexed from all filters for which
<constant>DMX_OUT_TS_TAP</constant> was specified.</entry>
</row><row>
<entry align="char" id="DMX-OUT-TSDEMUX-TAP">DMX_OUT_TSDEMUX_TAP</entry>
<entry>Like &DMX-OUT-TS-TAP; but retrieved from the DMX
device.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id="dmx-input-t">
......
Documentation/DocBook/media/dvb/dvbapi.xml
浏览文件 @ 473e0bc3
......@@ -28,12 +28,22 @@
<holder>Convergence GmbH</holder>
</copyright>
<copyright>
<year>2009-2014</year>
<year>2009-2015</year>
<holder>Mauro Carvalho Chehab</holder>
</copyright>
<revhistory>
<!-- Put document revisions here, newest first. -->
<revision>
<revnumber>2.1.0</revnumber>
<date>2015-05-29</date>
<authorinitials>mcc</authorinitials>
<revremark>
DocBook improvements and cleanups, in order to document the
system calls on a more standard way and provide more description
about the current DVB API.
</revremark>
</revision>
<revision>
<revnumber>2.0.4</revnumber>
<date>2011-05-06</date>
......@@ -95,18 +105,26 @@ Added ISDB-T test originally written by Patrick Boettcher
<chapter id="dvb_demux">
&sub-demux;
</chapter>
<chapter id="dvb_video">
&sub-video;
</chapter>
<chapter id="dvb_audio">
&sub-audio;
</chapter>
<chapter id="dvb_ca">
&sub-ca;
</chapter>
<chapter id="dvb_net">
<chapter id="net">
&sub-net;
</chapter>
<chapter id="legacy_dvb_apis">
<title>DVB Deprecated APIs</title>
<para>The APIs described here are kept only for historical reasons. There's
just one driver for a very legacy hardware that uses this API. No
modern drivers should use it. Instead, audio and video should be using
the V4L2 and ALSA APIs, and the pipelines should be set using the
Media Controller API</para>
<section id="dvb_video">
&sub-video;
</section>
<section id="dvb_audio">
&sub-audio;
</section>
</chapter>
<chapter id="dvb_kdapi">
&sub-kdapi;
</chapter>
......
Documentation/DocBook/media/dvb/examples.xml
浏览文件 @ 473e0bc3
<title>Examples</title>
<para>In this section we would like to present some examples for using the DVB API.
</para>
<para>Maintainer note: This section is out of date. Please refer to the sample programs packaged
with the driver distribution from <ulink url="http://linuxtv.org/hg/dvb-apps" />.
<para>NOTE: This section is out of date, and the code below won't even
compile. Please refer to the
<ulink url="http://linuxtv.org/docs/libdvbv5/index.html">libdvbv5</ulink>
for updated/recommended examples.
</para>
<section id="tuning">
......
Documentation/DocBook/media/dvb/fe-diseqc-recv-slave-reply.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_DISEQC_RECV_SLAVE_REPLY">
<refmeta>
<refentrytitle>ioctl FE_DISEQC_RECV_SLAVE_REPLY</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_DISEQC_RECV_SLAVE_REPLY</refname>
<refpurpose>Receives reply from a DiSEqC 2.0 command</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct dvb_diseqc_slave_reply *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_DISEQC_RECV_SLAVE_REPLY</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para>pointer to &dvb-diseqc-slave-reply;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>Receives reply from a DiSEqC 2.0 command.</para>
&return-value-dvb;
<table pgwide="1" frame="none" id="dvb-diseqc-slave-reply">
<title>struct <structname>dvb_diseqc_slave_reply</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>uint8_t</entry>
<entry>msg[4]</entry>
<entry>DiSEqC message (framing, data[3])</entry>
</row><row>
<entry>uint8_t</entry>
<entry>msg_len</entry>
<entry>Length of the DiSEqC message. Valid values are 0 to 4,
where 0 means no msg</entry>
</row><row>
<entry>int</entry>
<entry>timeout</entry>
<entry>Return from ioctl after timeout ms with errorcode when no
message was received</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-diseqc-reset-overload.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_DISEQC_RESET_OVERLOAD">
<refmeta>
<refentrytitle>ioctl FE_DISEQC_RESET_OVERLOAD</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_DISEQC_RESET_OVERLOAD</refname>
<refpurpose>Restores the power to the antenna subsystem, if it was powered
off due to power overload.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>NULL</paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_DISEQC_RESET_OVERLOAD</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>If the bus has been automatically powered off due to power overload, this ioctl
call restores the power to the bus. The call requires read/write access to the
device. This call has no effect if the device is manually powered off. Not all
DVB adapters support this ioctl.</para>
&return-value-dvb;
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-diseqc-send-burst.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_DISEQC_SEND_BURST">
<refmeta>
<refentrytitle>ioctl FE_DISEQC_SEND_BURST</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_DISEQC_SEND_BURST</refname>
<refpurpose>Sends a 22KHz tone burst for 2x1 mini DiSEqC satellite selection.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>enum fe_sec_mini_cmd *<parameter>tone</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_DISEQC_SEND_BURST</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>tone</parameter></term>
<listitem>
<para>pointer to &fe-sec-mini-cmd;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>This ioctl is used to set the generation of a 22kHz tone burst for mini
DiSEqC satellite
selection for 2x1 switches.
This call requires read/write permissions.</para>
<para>It provides support for what's specified at
<ulink url="http://www.eutelsat.com/files/contributed/satellites/pdf/Diseqc/associated%20docs/simple_tone_burst_detec.pdf">Digital Satellite Equipment Control
(DiSEqC) - Simple "ToneBurst" Detection Circuit specification.</ulink>
</para>
&return-value-dvb;
</refsect1>
<refsect1 id="fe-sec-mini-cmd-t">
<title>enum fe_sec_mini_cmd</title>
<table pgwide="1" frame="none" id="fe-sec-mini-cmd">
<title>enum fe_sec_mini_cmd</title>
<tgroup cols="2">
&cs-def;
<thead>
<row>
<entry>ID</entry>
<entry>Description</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry align="char" id="SEC-MINI-A"><constant>SEC_MINI_A</constant></entry>
<entry align="char">Sends a mini-DiSEqC 22kHz '0' Tone Burst to
select satellite-A</entry>
</row><row>
<entry align="char" id="SEC-MINI-B"><constant>SEC_MINI_B</constant></entry>
<entry align="char">Sends a mini-DiSEqC 22kHz '1' Data Burst to
select satellite-B</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-diseqc-send-master-cmd.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_DISEQC_SEND_MASTER_CMD">
<refmeta>
<refentrytitle>ioctl FE_DISEQC_SEND_MASTER_CMD</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_DISEQC_SEND_MASTER_CMD</refname>
<refpurpose>Sends a DiSEqC command</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct dvb_diseqc_master_cmd *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_DISEQC_SEND_MASTER_CMD</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para>pointer to &dvb-diseqc-master-cmd;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>Sends a DiSEqC command to the antenna subsystem.</para>
&return-value-dvb;
<table pgwide="1" frame="none" id="dvb-diseqc-master-cmd">
<title>struct <structname>dvb_diseqc_master_cmd</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>uint8_t</entry>
<entry>msg[6]</entry>
<entry>DiSEqC message (framing, address, command, data[3])</entry>
</row><row>
<entry>uint8_t</entry>
<entry>msg_len</entry>
<entry>Length of the DiSEqC message. Valid values are 3 to 6</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-enable-high-lnb-voltage.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_ENABLE_HIGH_LNB_VOLTAGE">
<refmeta>
<refentrytitle>ioctl FE_ENABLE_HIGH_LNB_VOLTAGE</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_ENABLE_HIGH_LNB_VOLTAGE</refname>
<refpurpose>Select output DC level between normal LNBf voltages or higher
LNBf voltages.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>unsigned int <parameter>high</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_ENABLE_HIGH_LNB_VOLTAGE</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>high</parameter></term>
<listitem>
<para>Valid flags:</para>
<itemizedlist>
<listitem><para>0 - normal 13V and 18V.</para></listitem>
<listitem><para>&gt;0 - enables slightly higher voltages instead of
13/18V, in order to compensate for long antenna cables.</para></listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>Select output DC level between normal LNBf voltages or higher
LNBf voltages between 0 (normal) or a value grater than 0 for higher
voltages.</para>
&return-value-dvb;
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-get-info.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_GET_INFO">
<refmeta>
<refentrytitle>ioctl FE_GET_INFO</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_GET_INFO</refname>
<refpurpose>Query DVB frontend capabilities and returns information about
the front-end. This call only requires read-only access to the device</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct dvb_frontend_info *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_GET_INFO</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para>pointer to struct &dvb-frontend-info;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>All DVB frontend devices support the
<constant>FE_GET_INFO</constant> ioctl. It is used to identify
kernel devices compatible with this specification and to obtain
information about driver and hardware capabilities. The ioctl takes a
pointer to dvb_frontend_info which is filled by the driver. When the
driver is not compatible with this specification the ioctl returns an error.
</para>
&return-value-dvb;
<table pgwide="1" frame="none" id="dvb-frontend-info">
<title>struct <structname>dvb_frontend_info</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>char</entry>
<entry>name[128]</entry>
<entry>Name of the frontend</entry>
</row><row>
<entry>fe_type_t</entry>
<entry>type</entry>
<entry><emphasis role="bold">DEPRECATED</emphasis>. DVBv3 type. Should not be used on modern programs, as a
frontend may have more than one type. So, the DVBv5 API should
be used instead to enumerate and select the frontend type.</entry>
</row><row>
<entry>uint32_t</entry>
<entry>frequency_min</entry>
<entry>Minimal frequency supported by the frontend</entry>
</row><row>
<entry>uint32_t</entry>
<entry>frequency_max</entry>
<entry>Maximal frequency supported by the frontend</entry>
</row><row>
<entry>uint32_t</entry>
<entry>frequency_stepsize</entry>
<entry>Frequency step - all frequencies are multiple of this value</entry>
</row><row>
<entry>uint32_t</entry>
<entry>frequency_tolerance</entry>
<entry>Tolerance of the frequency</entry>
</row><row>
<entry>uint32_t</entry>
<entry>symbol_rate_min</entry>
<entry>Minimal symbol rate (for Cable/Satellite systems), in bauds</entry>
</row><row>
<entry>uint32_t</entry>
<entry>symbol_rate_max</entry>
<entry>Maximal symbol rate (for Cable/Satellite systems), in bauds</entry>
</row><row>
<entry>uint32_t</entry>
<entry>symbol_rate_tolerance</entry>
<entry>Maximal symbol rate tolerance, in ppm</entry>
</row><row>
<entry>uint32_t</entry>
<entry>notifier_delay</entry>
<entry><emphasis role="bold">DEPRECATED</emphasis>. Not used by any driver.</entry>
</row><row>
<entry>&fe-caps;</entry>
<entry>caps</entry>
<entry>Capabilities supported by the frontend</entry>
</row>
</tbody>
</tgroup>
</table>
<para>NOTE: The frequencies are specified in Hz for Terrestrial and Cable
systems. They're specified in kHz for Satellite systems</para>
</refsect1>
<refsect1 id="fe-caps-t">
<title>frontend capabilities</title>
<para>Capabilities describe what a frontend can do. Some capabilities are
supported only on some specific frontend types.</para>
<table pgwide="1" frame="none" id="fe-caps">
<title>enum fe_caps</title>
<tgroup cols="2">
&cs-def;
<thead>
<row>
<entry>ID</entry>
<entry>Description</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry id="FE-IS-STUPID"><constant>FE_IS_STUPID</constant></entry>
<entry>There's something wrong at the frontend, and it can't
report its capabilities</entry>
</row>
<row>
<entry id="FE-CAN-INVERSION-AUTO"><constant>FE_CAN_INVERSION_AUTO</constant></entry>
<entry>The frontend is capable of auto-detecting inversion</entry>
</row>
<row>
<entry id="FE-CAN-FEC-1-2"><constant>FE_CAN_FEC_1_2</constant></entry>
<entry>The frontend supports FEC 1/2</entry>
</row>
<row>
<entry id="FE-CAN-FEC-2-3"><constant>FE_CAN_FEC_2_3</constant></entry>
<entry>The frontend supports FEC 2/3</entry>
</row>
<row>
<entry id="FE-CAN-FEC-3-4"><constant>FE_CAN_FEC_3_4</constant></entry>
<entry>The frontend supports FEC 3/4</entry>
</row>
<row>
<entry id="FE-CAN-FEC-4-5"><constant>FE_CAN_FEC_4_5</constant></entry>
<entry>The frontend supports FEC 4/5</entry>
</row>
<row>
<entry id="FE-CAN-FEC-5-6"><constant>FE_CAN_FEC_5_6</constant></entry>
<entry>The frontend supports FEC 5/6</entry>
</row>
<row>
<entry id="FE-CAN-FEC-6-7"><constant>FE_CAN_FEC_6_7</constant></entry>
<entry>The frontend supports FEC 6/7</entry>
</row>
<row>
<entry id="FE-CAN-FEC-7-8"><constant>FE_CAN_FEC_7_8</constant></entry>
<entry>The frontend supports FEC 7/8</entry>
</row>
<row>
<entry id="FE-CAN-FEC-8-9"><constant>FE_CAN_FEC_8_9</constant></entry>
<entry>The frontend supports FEC 8/9</entry>
</row>
<row>
<entry id="FE-CAN-FEC-AUTO"><constant>FE_CAN_FEC_AUTO</constant></entry>
<entry>The frontend can autodetect FEC.</entry>
</row>
<row>
<entry id="FE-CAN-QPSK"><constant>FE_CAN_QPSK</constant></entry>
<entry>The frontend supports QPSK modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-16"><constant>FE_CAN_QAM_16</constant></entry>
<entry>The frontend supports 16-QAM modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-32"><constant>FE_CAN_QAM_32</constant></entry>
<entry>The frontend supports 32-QAM modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-64"><constant>FE_CAN_QAM_64</constant></entry>
<entry>The frontend supports 64-QAM modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-128"><constant>FE_CAN_QAM_128</constant></entry>
<entry>The frontend supports 128-QAM modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-256"><constant>FE_CAN_QAM_256</constant></entry>
<entry>The frontend supports 256-QAM modulation</entry>
</row>
<row>
<entry id="FE-CAN-QAM-AUTO"><constant>FE_CAN_QAM_AUTO</constant></entry>
<entry>The frontend can autodetect modulation</entry>
</row>
<row>
<entry id="FE-CAN-TRANSMISSION-MODE-AUTO"><constant>FE_CAN_TRANSMISSION_MODE_AUTO</constant></entry>
<entry>The frontend can autodetect the transmission mode</entry>
</row>
<row>
<entry id="FE-CAN-BANDWIDTH-AUTO"><constant>FE_CAN_BANDWIDTH_AUTO</constant></entry>
<entry>The frontend can autodetect the bandwidth</entry>
</row>
<row>
<entry id="FE-CAN-GUARD-INTERVAL-AUTO"><constant>FE_CAN_GUARD_INTERVAL_AUTO</constant></entry>
<entry>The frontend can autodetect the guard interval</entry>
</row>
<row>
<entry id="FE-CAN-HIERARCHY-AUTO"><constant>FE_CAN_HIERARCHY_AUTO</constant></entry>
<entry>The frontend can autodetect hierarch</entry>
</row>
<row>
<entry id="FE-CAN-8VSB"><constant>FE_CAN_8VSB</constant></entry>
<entry>The frontend supports 8-VSB modulation</entry>
</row>
<row>
<entry id="FE-CAN-16VSB"><constant>FE_CAN_16VSB</constant></entry>
<entry>The frontend supports 16-VSB modulation</entry>
</row>
<row>
<entry id="FE-HAS-EXTENDED-CAPS"><constant>FE_HAS_EXTENDED_CAPS</constant></entry>
<entry>Currently, unused</entry>
</row>
<row>
<entry id="FE-CAN-MULTISTREAM"><constant>FE_CAN_MULTISTREAM</constant></entry>
<entry>The frontend supports multistream filtering</entry>
</row>
<row>
<entry id="FE-CAN-TURBO-FEC"><constant>FE_CAN_TURBO_FEC</constant></entry>
<entry>The frontend supports turbo FEC modulation</entry>
</row>
<row>
<entry id="FE-CAN-2G-MODULATION"><constant>FE_CAN_2G_MODULATION</constant></entry>
<entry>The frontend supports "2nd generation modulation" (DVB-S2/T2)></entry>
</row>
<row>
<entry id="FE-NEEDS-BENDING"><constant>FE_NEEDS_BENDING</constant></entry>
<entry>Not supported anymore, don't use it</entry>
</row>
<row>
<entry id="FE-CAN-RECOVER"><constant>FE_CAN_RECOVER</constant></entry>
<entry>The frontend can recover from a cable unplug automatically</entry>
</row>
<row>
<entry id="FE-CAN-MUTE-TS"><constant>FE_CAN_MUTE_TS</constant></entry>
<entry>The frontend can stop spurious TS data output</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-get-property.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_GET_PROPERTY">
<refmeta>
<refentrytitle>ioctl FE_SET_PROPERTY, FE_GET_PROPERTY</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_SET_PROPERTY</refname>
<refname>FE_GET_PROPERTY</refname>
<refpurpose>FE_SET_PROPERTY sets one or more frontend properties.
FE_GET_PROPERTY returns one or more frontend properties.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct dtv_properties *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_SET_PROPERTY, FE_GET_PROPERTY</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para>pointer to &dtv-properties;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>All DVB frontend devices support the
<constant>FE_SET_PROPERTY</constant> and <constant>FE_GET_PROPERTY</constant>
ioctls. The supported properties and statistics depends on the delivery system
and on the device:</para>
<itemizedlist>
<listitem>
<para><constant>FE_SET_PROPERTY:</constant></para>
<itemizedlist>
<listitem><para>This ioctl is used to set one or more
frontend properties.</para></listitem>
<listitem><para>This is the basic command to request the frontend to tune into some
frequency and to start decoding the digital TV signal.</para></listitem>
<listitem><para>This call requires read/write access to the device.</para></listitem>
<listitem><para>At return, the values are updated to reflect the
actual parameters used.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><constant>FE_GET_PROPERTY:</constant></para>
<itemizedlist>
<listitem><para>This ioctl is used to get properties and
statistics from the frontend.</para></listitem>
<listitem><para>No properties are changed, and statistics aren't reset.</para></listitem>
<listitem><para>This call only requires read-only access to the device.</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
&return-value-dvb;
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-read-status.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_READ_STATUS">
<refmeta>
<refentrytitle>ioctl FE_READ_STATUS</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_READ_STATUS</refname>
<refpurpose>Returns status information about the front-end. This call only
requires read-only access to the device</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>unsigned int *<parameter>status</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_READ_STATUS</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>status</parameter></term>
<listitem>
<para>pointer to a bitmask integer filled with the values defined by
&fe-status;.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>All DVB frontend devices support the
<constant>FE_READ_STATUS</constant> ioctl. It is used to check about the
locking status of the frontend after being tuned. The ioctl takes a
pointer to an integer where the status will be written.
</para>
<para>NOTE: the size of status is actually sizeof(enum fe_status), with varies
according with the architecture. This needs to be fixed in the future.</para>
&return-value-dvb;
</refsect1>
<refsect1 id="fe-status-t">
<title>int fe_status</title>
<para>The fe_status parameter is used to indicate the current state
and/or state changes of the frontend hardware. It is produced using
the &fe-status; values on a bitmask</para>
<table pgwide="1" frame="none" id="fe-status">
<title>enum fe_status</title>
<tgroup cols="2">
&cs-def;
<thead>
<row>
<entry>ID</entry>
<entry>Description</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry align="char" id="FE-HAS-SIGNAL"><constant>FE_HAS_SIGNAL</constant></entry>
<entry align="char">The frontend has found something above the noise level</entry>
</row><row>
<entry align="char" id="FE-HAS-CARRIER"><constant>FE_HAS_CARRIER</constant></entry>
<entry align="char">The frontend has found a DVB signal</entry>
</row><row>
<entry align="char" id="FE-HAS-VITERBI"><constant>FE_HAS_VITERBI</constant></entry>
<entry align="char">The frontend FEC inner coding (Viterbi, LDPC or other inner code) is stable</entry>
</row><row>
<entry align="char" id="FE-HAS-SYNC"><constant>FE_HAS_SYNC</constant></entry>
<entry align="char">Synchronization bytes was found</entry>
</row><row>
<entry align="char" id="FE-HAS-LOCK"><constant>FE_HAS_LOCK</constant></entry>
<entry align="char">The DVB were locked and everything is working</entry>
</row><row>
<entry align="char" id="FE-TIMEDOUT"><constant>FE_TIMEDOUT</constant></entry>
<entry align="char">no lock within the last about 2 seconds</entry>
</row><row>
<entry align="char" id="FE-REINIT"><constant>FE_REINIT</constant></entry>
<entry align="char">The frontend was reinitialized, application is
recommended to reset DiSEqC, tone and parameters</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-set-frontend-tune-mode.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_SET_FRONTEND_TUNE_MODE">
<refmeta>
<refentrytitle>ioctl FE_SET_FRONTEND_TUNE_MODE</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_SET_FRONTEND_TUNE_MODE</refname>
<refpurpose>Allow setting tuner mode flags to the frontend.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>unsigned int <parameter>flags</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_SET_FRONTEND_TUNE_MODE</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>flags</parameter></term>
<listitem>
<para>Valid flags:</para>
<itemizedlist>
<listitem><para>0 - normal tune mode</para></listitem>
<listitem><para>FE_TUNE_MODE_ONESHOT - When set, this flag will
disable any zigzagging or other "normal" tuning behaviour.
Additionally, there will be no automatic monitoring of the
lock status, and hence no frontend events will be
generated. If a frontend device is closed, this flag will
be automatically turned off when the device is reopened
read-write.</para></listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>Allow setting tuner mode flags to the frontend, between 0 (normal)
or FE_TUNE_MODE_ONESHOT mode</para>
&return-value-dvb;
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-set-tone.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_SET_TONE">
<refmeta>
<refentrytitle>ioctl FE_SET_TONE</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_SET_TONE</refname>
<refpurpose>Sets/resets the generation of the continuous 22kHz tone.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>enum fe_sec_tone_mode *<parameter>tone</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_SET_TONE</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>tone</parameter></term>
<listitem>
<para>pointer to &fe-sec-tone-mode;</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>This ioctl is used to set the generation of the continuous 22kHz tone.
This call requires read/write permissions.</para>
<para>Usually, satellite antenna subsystems require that the digital TV
device to send a 22kHz tone in order to select between high/low band on
some dual-band LNBf. It is also used to send signals to DiSEqC equipment,
but this is done using the DiSEqC ioctls.</para>
<para>NOTE: if more than one device is connected to the same antenna,
setting a tone may interfere on other devices, as they may lose
the capability of selecting the band. So, it is recommended that
applications would change to SEC_TONE_OFF when the device is not used.</para>
&return-value-dvb;
</refsect1>
<refsect1 id="fe-sec-tone-mode-t">
<title>enum fe_sec_tone_mode</title>
<table pgwide="1" frame="none" id="fe-sec-tone-mode">
<title>enum fe_sec_tone_mode</title>
<tgroup cols="2">
&cs-def;
<thead>
<row>
<entry>ID</entry>
<entry>Description</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry align="char" id="SEC-TONE-ON"><constant>SEC_TONE_ON</constant></entry>
<entry align="char">Sends a 22kHz tone burst to the antenna</entry>
</row><row>
<entry align="char" id="SEC-TONE-OFF"><constant>SEC_TONE_OFF</constant></entry>
<entry align="char">Don't send a 22kHz tone to the antenna
(except if the FE_DISEQC_* ioctls are called)</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/fe-set-voltage.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="FE_SET_VOLTAGE">
<refmeta>
<refentrytitle>ioctl FE_SET_VOLTAGE</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>FE_SET_VOLTAGE</refname>
<refpurpose>Allow setting the DC level sent to the antenna subsystem.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>enum fe_sec_voltage *<parameter>voltage</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fe_fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>FE_SET_VOLTAGE</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>voltage</parameter></term>
<listitem>
<para>pointer to &fe-sec-voltage;</para>
<para>Valid values are described at &fe-sec-voltage;.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>This ioctl allows to set the DC voltage level sent through the antenna
cable to 13V, 18V or off.</para>
<para>Usually, a satellite antenna subsystems require that the digital TV
device to send a DC voltage to feed power to the LNBf. Depending on the
LNBf type, the polarization or the intermediate frequency (IF) of the LNBf
can controlled by the voltage level. Other devices (for example, the ones
that implement DISEqC and multipoint LNBf's don't need to control the
voltage level, provided that either 13V or 18V is sent to power up the
LNBf.</para>
<para>NOTE: if more than one device is connected to the same antenna,
setting a voltage level may interfere on other devices, as they may lose
the capability of setting polarization or IF. So, on those
cases, setting the voltage to SEC_VOLTAGE_OFF while the device is not is
used is recommended.</para>
&return-value-dvb;
</refsect1>
</refentry>
Documentation/DocBook/media/dvb/frontend_legacy_api.xml 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/DocBook/media/dvb/intro.xml
浏览文件 @ 473e0bc3
......@@ -129,41 +129,41 @@ hardware. It can depend on the individual security requirements of the
platform, if and how many of the CA functions are made available to the
application through this device.</para>
<para>All devices can be found in the <emphasis role="tt">/dev</emphasis>
tree under <emphasis role="tt">/dev/dvb</emphasis>. The individual devices
<para>All devices can be found in the <constant>/dev</constant>
tree under <constant>/dev/dvb</constant>. The individual devices
are called:</para>
<itemizedlist>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/audioM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/audioM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/videoM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/videoM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/frontendM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/frontendM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/netM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/netM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/demuxM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/demuxM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/dvrM</emphasis>,</para>
<para><constant>/dev/dvb/adapterN/dvrM</constant>,</para>
</listitem>
<listitem>
<para><emphasis role="tt">/dev/dvb/adapterN/caM</emphasis>,</para></listitem></itemizedlist>
<para><constant>/dev/dvb/adapterN/caM</constant>,</para></listitem></itemizedlist>
<para>where N enumerates the DVB PCI cards in a system starting
from&#x00A0;0, and M enumerates the devices of each type within each
adapter, starting from&#x00A0;0, too. We will omit the &#8220;<emphasis
role="tt">/dev/dvb/adapterN/</emphasis>&#8221; in the further dicussion
adapter, starting from&#x00A0;0, too. We will omit the &#8220;
<constant>/dev/dvb/adapterN/</constant>&#8221; in the further dicussion
of these devices. The naming scheme for the devices is the same wheter
devfs is used or not.</para>
......@@ -202,10 +202,10 @@ a partial path like:</para>
</programlisting>
<para>To enable applications to support different API version, an
additional include file <emphasis
role="tt">linux/dvb/version.h</emphasis> exists, which defines the
constant <emphasis role="tt">DVB_API_VERSION</emphasis>. This document
describes <emphasis role="tt">DVB_API_VERSION 5.8</emphasis>.
additional include file
<constant>linux/dvb/version.h</constant> exists, which defines the
constant <constant>DVB_API_VERSION</constant>. This document
describes <constant>DVB_API_VERSION 5.10</constant>.
</para>
</section>
......
Documentation/DocBook/media/dvb/kdapi.xml
浏览文件 @ 473e0bc3
<title>Kernel Demux API</title>
<para>The kernel demux API defines a driver-internal interface for registering low-level,
hardware specific driver to a hardware independent demux layer. It is only of interest for
DVB device driver writers. The header file for this API is named <emphasis role="tt">demux.h</emphasis> and located in
<emphasis role="tt">drivers/media/dvb-core</emphasis>.
DVB device driver writers. The header file for this API is named <constant>demux.h</constant> and located in
<constant>">drivers/media/dvb-core</constant>.
</para>
<para>Maintainer note: This section must be reviewed. It is probably out of date.
</para>
......
Documentation/DocBook/media/dvb/video.xml
浏览文件 @ 473e0bc3
<title>DVB Video Device</title>
<para>The DVB video device controls the MPEG2 video decoder of the DVB hardware. It
can be accessed through <emphasis role="tt">/dev/dvb/adapter0/video0</emphasis>. Data types and and
ioctl definitions can be accessed by including <emphasis role="tt">linux/dvb/video.h</emphasis> in your
can be accessed through <emphasis role="bold">/dev/dvb/adapter0/video0</emphasis>. Data types and and
ioctl definitions can be accessed by including <emphasis role="bold">linux/dvb/video.h</emphasis> in your
application.
</para>
<para>Note that the DVB video device only controls decoding of the MPEG video stream, not
its presentation on the TV or computer screen. On PCs this is typically handled by an
associated video4linux device, e.g. <emphasis role="tt">/dev/video</emphasis>, which allows scaling and defining output
associated video4linux device, e.g. <emphasis role="bold">/dev/video</emphasis>, which allows scaling and defining output
windows.
</para>
<para>Some DVB cards don&#8217;t have their own MPEG decoder, which results in the omission of
......@@ -24,7 +24,7 @@ have been created to replace that functionality.</para>
<section id="video-format-t">
<title>video_format_t</title>
<para>The <emphasis role="tt">video_format_t</emphasis> data type defined by
<para>The <constant>video_format_t</constant> data type defined by
</para>
<programlisting>
typedef enum {
......@@ -74,7 +74,7 @@ typedef enum {
</programlisting>
<para>VIDEO_SOURCE_DEMUX selects the demultiplexer (fed either by the frontend or the
DVR device) as the source of the video stream. If VIDEO_SOURCE_MEMORY
is selected the stream comes from the application through the <emphasis role="tt">write()</emphasis> system
is selected the stream comes from the application through the <emphasis role="bold">write()</emphasis> system
call.
</para>
</section>
......
Documentation/DocBook/media/typical_media_device.svg 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/DocBook/media/v4l/controls.xml
浏览文件 @ 473e0bc3
......@@ -4863,7 +4863,7 @@ interface and may change in the future.</para>
</note>
<para>
The Image Source control class is intended for low-level control of
The Image Process control class is intended for low-level control of
image processing functions. Unlike
<constant>V4L2_CID_IMAGE_SOURCE_CLASS</constant>, the controls in
this class affect processing the image, and do not control capturing
......@@ -4871,7 +4871,7 @@ interface and may change in the future.</para>
</para>
<table pgwide="1" frame="none" id="image-process-control-id">
<title>Image Source Control IDs</title>
<title>Image Process Control IDs</title>
<tgroup cols="4">
<colspec colname="c1" colwidth="1*" />
......
Documentation/DocBook/media/v4l/io.xml
浏览文件 @ 473e0bc3
......@@ -841,15 +841,15 @@ is the file descriptor associated with a DMABUF buffer.</entry>
<entry>__u32</entry>
<entry><structfield>reserved2</structfield></entry>
<entry></entry>
<entry>A place holder for future extensions. Applications
should set this to 0.</entry>
<entry>A place holder for future extensions. Drivers and applications
must set this to 0.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield></entry>
<entry></entry>
<entry>A place holder for future extensions. Applications
should set this to 0.</entry>
<entry>A place holder for future extensions. Drivers and applications
must set this to 0.</entry>
</row>
</tbody>
</tgroup>
......@@ -930,8 +930,8 @@ should set this to 0.</entry>
<entry>__u32</entry>
<entry><structfield>reserved[11]</structfield></entry>
<entry></entry>
<entry>Reserved for future use. Should be zeroed by an
application.</entry>
<entry>Reserved for future use. Should be zeroed by drivers and
applications.</entry>
</row>
</tbody>
</tgroup>
......@@ -1127,6 +1127,18 @@ passed on to a DMA-capable hardware unit for further processing or output.
Typically applications shall use this flag for output buffers if the data
in this buffer has not been created by the CPU but by some DMA-capable unit,
in which case caches have not been used.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_LAST</constant></entry>
<entry>0x00100000</entry>
<entry>Last buffer produced by the hardware. mem2mem codec drivers
set this flag on the capture queue for the last buffer when the
<link linkend="vidioc-querybuf">VIDIOC_QUERYBUF</link> or
<link linkend="vidioc-qbuf">VIDIOC_DQBUF</link> ioctl is called. Due to hardware
limitations, the last buffer may be empty. In this case the driver will set the
<structfield>bytesused</structfield> field to 0, regardless of the format. Any
Any subsequent call to the <link linkend="vidioc-qbuf">VIDIOC_DQBUF</link> ioctl
will not block anymore, but return an &EPIPE;.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_MASK</constant></entry>
......@@ -1155,7 +1167,7 @@ in which case caches have not been used.</entry>
<entry>The buffer timestamp has been taken from the
<constant>CLOCK_MONOTONIC</constant> clock. To access the
same clock outside V4L2, use
<function>clock_gettime(2)</function> .</entry>
<function>clock_gettime(2)</function>.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_COPY</constant></entry>
......
Documentation/DocBook/media/v4l/media-func-open.xml
浏览文件 @ 473e0bc3
......@@ -44,7 +44,7 @@
<para>To open a media device applications call <function>open()</function>
with the desired device name. The function has no side effects; the device
configuration remain unchanged.</para>
<para>When the device is opened in read-only mode, attemps to modify its
<para>When the device is opened in read-only mode, attempts to modify its
configuration will result in an error, and <varname>errno</varname> will be
set to <errorcode>EBADF</errorcode>.</para>
</refsect1>
......
Documentation/DocBook/media/v4l/pixfmt-y16-be.xml 0 → 100644
浏览文件 @ 473e0bc3
<refentry id="V4L2-PIX-FMT-Y16-BE">
<refmeta>
<refentrytitle>V4L2_PIX_FMT_Y16_BE ('Y16 ' | (1 &lt;&lt; 31))</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname><constant>V4L2_PIX_FMT_Y16_BE</constant></refname>
<refpurpose>Grey-scale image</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
<para>This is a grey-scale image with a depth of 16 bits per
pixel. The most significant byte is stored at lower memory addresses
(big-endian). Note the actual sampling precision may be lower than
16 bits, for example 10 bits per pixel with values in range 0 to
1023.</para>
<example>
<title><constant>V4L2_PIX_FMT_Y16_BE</constant> 4 &times; 4
pixel image</title>
<formalpara>
<title>Byte Order.</title>
<para>Each cell is one byte.
<informaltable frame="none">
<tgroup cols="9" align="center">
<colspec align="left" colwidth="2*" />
<tbody valign="top">
<row>
<entry>start&nbsp;+&nbsp;0:</entry>
<entry>Y'<subscript>00high</subscript></entry>
<entry>Y'<subscript>00low</subscript></entry>
<entry>Y'<subscript>01high</subscript></entry>
<entry>Y'<subscript>01low</subscript></entry>
<entry>Y'<subscript>02high</subscript></entry>
<entry>Y'<subscript>02low</subscript></entry>
<entry>Y'<subscript>03high</subscript></entry>
<entry>Y'<subscript>03low</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;8:</entry>
<entry>Y'<subscript>10high</subscript></entry>
<entry>Y'<subscript>10low</subscript></entry>
<entry>Y'<subscript>11high</subscript></entry>
<entry>Y'<subscript>11low</subscript></entry>
<entry>Y'<subscript>12high</subscript></entry>
<entry>Y'<subscript>12low</subscript></entry>
<entry>Y'<subscript>13high</subscript></entry>
<entry>Y'<subscript>13low</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;16:</entry>
<entry>Y'<subscript>20high</subscript></entry>
<entry>Y'<subscript>20low</subscript></entry>
<entry>Y'<subscript>21high</subscript></entry>
<entry>Y'<subscript>21low</subscript></entry>
<entry>Y'<subscript>22high</subscript></entry>
<entry>Y'<subscript>22low</subscript></entry>
<entry>Y'<subscript>23high</subscript></entry>
<entry>Y'<subscript>23low</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;24:</entry>
<entry>Y'<subscript>30high</subscript></entry>
<entry>Y'<subscript>30low</subscript></entry>
<entry>Y'<subscript>31high</subscript></entry>
<entry>Y'<subscript>31low</subscript></entry>
<entry>Y'<subscript>32high</subscript></entry>
<entry>Y'<subscript>32low</subscript></entry>
<entry>Y'<subscript>33high</subscript></entry>
<entry>Y'<subscript>33low</subscript></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</formalpara>
</example>
</refsect1>
</refentry>
Documentation/DocBook/media/v4l/remote_controllers.xml
浏览文件 @ 473e0bc3
......@@ -284,7 +284,7 @@ different IR's. Due to that, V4L2 API now specifies a standard for mapping Media
</tgroup>
</table>
<para>It should be noticed that, sometimes, there some fundamental missing keys at some cheaper IR's. Due to that, it is recommended to:</para>
<para>It should be noted that, sometimes, there some fundamental missing keys at some cheaper IR's. Due to that, it is recommended to:</para>
<table pgwide="1" frame="none" id="rc_keymap_notes">
<title>Notes</title>
......
Documentation/DocBook/scsi.tmpl
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/RCU/RTFP.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/SubmittingPatches
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/CCN.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/Samsung/Bootloader-interface.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/stm32/overview.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/stm32/stm32f429-overview.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/sunxi/README
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/arm/vlocks.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/blockdev/zram.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/cgroups/memory.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/clk.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/debugging-via-ohci1394.txt
浏览文件 @ 473e0bc3
......@@ -181,4 +181,4 @@ Notes
Documentation and specifications: http://halobates.de/firewire/
FireWire is a trademark of Apple Inc. - for more information please refer to:
http://en.wikipedia.org/wiki/FireWire
https://en.wikipedia.org/wiki/FireWire
Documentation/devicetree/bindings/arc/archs-intc.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/arc/axs101.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/arc/axs103.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/arm/scu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/arm/ux500/boards.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/arm/zte.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/ata/ahci-ceva.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/clock/imx7d-clock.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/clock/ingenic,cgu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/clock/lpc1850-ccu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/clock/lpc1850-cgu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/clock/ti,cdce925.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/drm/msm/dsi.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/drm/msm/edp.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/gpio/gpio-ath79.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/gpio/gpio-atlas7.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/h8300/cpu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/hwlock/hwlock.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-mt6577.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/input/ti,drv2665.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/leds/leds-aat1290.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/leds/leds-bcm6328.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/leds/leds-bcm6358.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/leds/leds-ktd2692.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/adp1653.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/media/st,stih4xx.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/mfd/mfd.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/mfd/tps6507x.txt 100755 → 100644
浏览文件 @ 473e0bc3
文件模式从 100755 更改为 100644
Documentation/devicetree/bindings/mips/ath79-soc.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/panel/lg,lb070wv8.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/soc/sunxi/sram.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/bt-sco.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/gtm601.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/mtk-afe-pcm.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/rt5645.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/tas571x.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/sound/zte,zx-i2s.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/timer/renesas,tpu.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/devicetree/bindings/video/exynos-mic.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/dmaengine/pxa_dma.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/edac.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/core/BPF-JIT/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/core/tracehook/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/debug/KASAN/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/debug/kgdb/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/debug/kprobes/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/debug/optprobes/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/debug/uprobes/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/io/sg-chain/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/lib/strncasecmp/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/list-arch.sh 0 → 100755
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/locking/lockdep/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/perf/perf-regs/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/ELF-ASLR/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/PG_uncached/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/THP/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/huge-vmap/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/ioremap_prot/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/features/vm/pte_special/arch-support.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/dax.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/quota.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/filesystems/xfs.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/gpio/consumer.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/hwmon/w83792d
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/hwspinlock.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/i2c/slave-interface
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/ja_JP/HOWTO
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/kasan.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/kbuild/makefiles.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/kmemleak.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/laptops/.gitignore
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/laptops/00-INDEX
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/laptops/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/leds/leds-class.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/leds/leds-lp5523.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/lockup-watchdogs.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/magic-number.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/md.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/mic/mic_overview.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/mic/mpssd/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/mic/mpssd/mpss
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/mic/scif_overview.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/ntb.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/nvdimm/btt.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/nvdimm/nvdimm.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/phy.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/pinctrl.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/power/swsusp.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/pps/pps.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/prctl/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/remoteproc.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/security/Smack.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/serial/tty.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/sound/alsa/Jack-Controls.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/sound/oss/PSS-updates
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/sound/oss/README.OSS
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/sound/oss/btaudio
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/thermal/power_allocator.txt 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/thermal/sysfs-api.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/trace/ftrace.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/usb/usb-serial.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/vDSO/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/video4linux/vivid.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/vm/zswap.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/vme_api.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/w1/slaves/w1_therm
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/w1/w1.generic
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/workqueue.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/x86/boot.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Documentation/x86/entry_64.txt
浏览文件 @ 473e0bc3
此差异已折叠。
Kbuild
浏览文件 @ 473e0bc3
此差异已折叠。
MAINTAINERS
浏览文件 @ 473e0bc3
此差异已折叠。
Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/Kconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/alpha/include/asm/Kbuild
浏览文件 @ 473e0bc3
此差异已折叠。
arch/alpha/include/asm/mm-arch-hooks.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/alpha/include/asm/pci.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/alpha/include/asm/serial.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/Kconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/angel4.dts 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/boot/dts/axc001.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axc003.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axc003_idu.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axs101.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axs103.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axs103_idu.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/axs10x_mb.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/nsim_700.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/nsim_hs.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/nsim_hs_idu.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/nsimosci_hs.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/nsimosci_hs_idu.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/vdk_axc003.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/vdk_axc003_idu.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/vdk_axs10x_mb.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/vdk_hs38.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/boot/dts/vdk_hs38_smp.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/axs101_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/axs103_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/axs103_smp_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsim_700_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsim_hs_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsim_hs_smp_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsimosci_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsimosci_hs_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/nsimosci_hs_smp_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/tb10x_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/vdk_hs38_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/configs/vdk_hs38_smp_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/Kbuild
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/arcregs.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/atomic.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/barrier.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/bitops.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/cache.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/cacheflush.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/cmpxchg.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/delay.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/dma-mapping.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/elf.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/entry-arcv2.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/entry-compact.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/entry.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/io.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/irq.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/irqflags-arcv2.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/irqflags-compact.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/irqflags.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/mcip.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/mm-arch-hooks.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/mmu.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/pgtable.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/processor.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/ptrace.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/spinlock.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/thread_info.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/asm/uaccess.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/include/uapi/asm/page.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/asm-offsets.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/devtree.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/entry-arcv2.S 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/entry-compact.S 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/entry.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/head.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/intc-arcv2.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/intc-compact.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/irq.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/mcip.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/perf_event.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/process.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/ptrace.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/setup.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/signal.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/smp.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/stacktrace.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/time.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/kernel/troubleshoot.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/lib/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/lib/memcmp.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/lib/memcpy-archs.S 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/lib/memset-archs.S 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/lib/strcmp-archs.S 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/mm/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/mm/cache.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/mm/cache_arc700.c 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/mm/dma.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/mm/tlb.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/mm/tlbex.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-arcfpga/Kconfig 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/plat-arcfpga/Makefile 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/plat-arcfpga/include/plat/smp.h 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/plat-arcfpga/platform.c 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/plat-arcfpga/smp.c 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arc/plat-axs10x/Kconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-axs10x/Makefile 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-axs10x/axs10x.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-sim/Kconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-sim/Makefile 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arc/plat-sim/platform.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/compressed/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/compressed/head.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am335x-baltos-ir5221.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am335x-sl50.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am3517.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-370-dlink-dns327l.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-385-linksys-caiman.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-385-linksys-cobra.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-385-linksys.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-388-db.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-388-gp.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-388-rd.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-398-db.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-39x.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/armv7-m.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91-ariettag25.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91-kizbox.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91-kizbox2.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91-kizboxmini.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91rm9200.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91rm9200ek.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9261ek.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9263ek.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9n12ek.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9rlek.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/at91sam9x5ek.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/atlas7.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/axp209.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm-cygnus.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi-b.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm2835.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm4708-asus-rt-ac56u.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm4708-asus-rt-ac68u.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm5301x-nand-cs0-bch8.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm5301x.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm63138.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm7445.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm958300k.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/bcm963138dvt.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/berlin2.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/berlin2cd.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/berlin2q.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/cx92755.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/dove-cm-a510.dts 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/boot/dts/dove-cm-a510.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/dove-sbc-a510.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/dove.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/emev2-kzm9d.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4212.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4415.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx23.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6dl-apf6dev.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6dl-aristainetos2_4.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6dl-aristainetos2_7.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw551x.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6dl.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6q-apf6dev.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6q-cubox-i.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6q-gw551x.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-apf6.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-apf6dev.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw551x.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx6sl-warp.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx7d-pinfunc.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx7d-sdb.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/imx7d.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/integrator.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2e-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2e-netcp.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2e.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2hk-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2hk-netcp.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2hk.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2l-evm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2l-netcp.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/k2l.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/kirkwood-b3.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/kizbox.dts 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/logicpd-torpedo-som.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/lpc18xx.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/lpc4350-hitex-eval.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/lpc4350.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/lpc4357-ea4357-devkit.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/lpc4357.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/mt8127.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/mt8135-pinfunc.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/mt8135.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/omap3-ldp.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/omap5-uevm.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/pxa27x.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/pxa2xx.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/pxa3xx.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/qcom-msm8660.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/qcom-pm8841.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/qcom-pm8941.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/qcom-pma8084.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a73a4.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7740.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7778-bockw.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7779.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/r8a7794.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/rk3066a.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/rk3188.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/rk3288-evb.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/rk3288.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/rk3xxx.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/s3c2416.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sama5d3.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sama5d3xcm.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sama5d4.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sh73a0-kzm9g.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sh73a0.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/socfpga_arria10_socdk.dts 已删除 100755 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/boot/dts/socfpga_arria10_socdk.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/socfpga_arria10_socdk_sdmmc.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/ste-dbx5x0.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/ste-snowball.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stih407-b2120.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stih407.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stih410-b2120.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stih416.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stih418-b2199.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stm32f429-disco.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/stm32f429.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun4i-a10-gemei-g9.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun4i-a10-jesurun-q5.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s-auxtek-t004.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun5i-a13-utoo-p66.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun5i-a13.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun5i.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun6i-a31-i7.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun6i-a31-m9.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun6i-a31-mele-a1000g-quad.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun6i-a31.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun6i-a31s.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-m3.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-mk808c.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-orangepi.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a23-a33.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a23-evb.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a23.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a33-et-q8-v1.6.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a33-ga10h-v1.1.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun8i-a33.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun9i-a80-cubieboard4.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/sun9i-a80.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/tegra124.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/tegra20.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/tegra30.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-ld4.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-pro4-ref.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-pro4.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-sld3-ref.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-sld3.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-sld8-ref.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-ph1-sld8.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/uniphier-support-card.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf-colibri.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf610-cosmic.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf610-pinfunc.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf610-twr.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf610m4-colibri.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/vf610m4.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zx296702-ad1.dts 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zx296702.dtsi 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zynq-7000.dtsi
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zynq-zc702.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zynq-zc706.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zynq-zed.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/boot/dts/zynq-zybo.dts
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/common/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/common/edma.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/common/mcpm_entry.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/common/mcpm_head.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/common/timer-sp.c 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/configs/at91_dt_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/efm32_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/hisi_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/keystone_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/lpc18xx_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/qcom_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/sama5_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/shmobile_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/stm32_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/tegra_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/u8500_defconfig
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/vf610m4_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/configs/zx_defconfig 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/Kbuild
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/assembler.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/cacheflush.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/cmpxchg.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/dma.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/edac.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/firmware.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/hardware/arm_timer.h 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/include/asm/hardware/timer-sp.h 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/include/asm/hugetlb.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/io.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/irqflags.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/mach/arch.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/mcpm.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/memory.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/mm-arch-hooks.h 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/module.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/perf_event.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/pmu.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/proc-fns.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/smp.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/suspend.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/system_info.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/unified.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/vfp.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/asm/xen/page.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/debug/8250.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/debug/efm32.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/debug/imx-uart.h
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/include/debug/pl01x.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/debug.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/entry-ftrace.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/entry-v7m.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/head-nommu.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/module-plts.c 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/module.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/module.lds 0 → 100644
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/perf_event_cpu.c 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
arch/arm/kernel/perf_event_v6.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/perf_event_v7.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/perf_event_xscale.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/sleep.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/tcm.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/kvm/interrupts.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/lib/call_with_stack.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/lib/memcpy.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/lib/memset.S
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 473e0bc3
此差异已折叠。
arch/arm/mach-at91/Makefile.boot 已删除 100644 → 0
浏览文件 @ 1a84e771
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或
反馈
建议 客服 返回
顶部