Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
提交 af5666e0 编写于 作者: J Jiri Kosina
浏览文件
操作

Merge branches 'for-3.15/upstream-fixes' and 'for-3.16/upstream' into for-linus 

Conflicts:
	drivers/hid/hid-sensor-hub.c
上级 1b15d2e5 368c9664
展开全部 隐藏空白更改
内联 并排
Showing with 53687 addition and 17868 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ af5666e0
......@@ -630,6 +630,13 @@ N: Michael Elizabeth Chastain
E: mec@shout.net
D: Configure, Menuconfig, xconfig
N: Mauro Carvalho Chehab
E: m.chehab@samsung.org
E: mchehab@infradead.org
D: Media subsystem (V4L/DVB) drivers and core
D: EDAC drivers and EDAC 3.0 core rework
S: Brazil
N: Raymond Chen
E: raymondc@microsoft.com
D: Author of Configure script
......@@ -2564,6 +2571,10 @@ N: Wolfgang Muees
E: wolfgang@iksw-muees.de
D: Auerswald USB driver
N: Paul Mundt
E: paul.mundt@gmail.com
D: SuperH maintainer
N: Ian A. Murdock
E: imurdock@gnu.ai.mit.edu
D: Creator of Debian distribution
......@@ -2707,6 +2718,9 @@ N: Greg Page
E: gpage@sovereign.org
D: IPX development and support
N: Venkatesh Pallipadi (Venki)
D: x86/HPET
N: David Parsons
E: orc@pell.chi.il.us
D: improved memory detection code.
......
Documentation/ABI/testing/sysfs-block-zram
浏览文件 @ af5666e0
......@@ -43,6 +43,36 @@ Description:
The invalid_io file is read-only and specifies the number of
non-page-size-aligned I/O requests issued to this device.
What: /sys/block/zram<id>/failed_reads
Date: February 2014
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The failed_reads file is read-only and specifies the number of
failed reads happened on this device.
What: /sys/block/zram<id>/failed_writes
Date: February 2014
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The failed_writes file is read-only and specifies the number of
failed writes happened on this device.
What: /sys/block/zram<id>/max_comp_streams
Date: February 2014
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The max_comp_streams file is read-write and specifies the
number of backend's zcomp_strm compression streams (number of
concurrent compress operations).
What: /sys/block/zram<id>/comp_algorithm
Date: February 2014
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The comp_algorithm file is read-write and lets to show
available and selected compression algorithms, change
compression algorithm selection.
What: /sys/block/zram<id>/notify_free
Date: August 2010
Contact: Nitin Gupta <ngupta@vflare.org>
......@@ -53,15 +83,6 @@ Description:
is freed. This statistic is applicable only when this disk is
being used as a swap disk.
What: /sys/block/zram<id>/discard
Date: August 2010
Contact: Nitin Gupta <ngupta@vflare.org>
Description:
The discard file is read-only and specifies the number of
discard requests received by this device. These requests
provide information to block device regarding blocks which are
no longer used by filesystem.
What: /sys/block/zram<id>/zero_pages
Date: August 2010
Contact: Nitin Gupta <ngupta@vflare.org>
......
Documentation/ABI/testing/sysfs-bus-mdio
浏览文件 @ af5666e0
......@@ -7,3 +7,23 @@ Description:
by the device during bus enumeration, encoded in hexadecimal.
This ID is used to match the device with the appropriate
driver.
What: /sys/bus/mdio_bus/devices/.../phy_interface
Date: February 2014
KernelVersion: 3.15
Contact: netdev@vger.kernel.org
Description:
This attribute contains the PHY interface as configured by the
Ethernet driver during bus enumeration, encoded in string.
This interface mode is used to configure the Ethernet MAC with the
appropriate mode for its data lines to the PHY hardware.
What: /sys/bus/mdio_bus/devices/.../phy_has_fixups
Date: February 2014
KernelVersion: 3.15
Contact: netdev@vger.kernel.org
Description:
This attribute contains the boolean value whether a given PHY
device has had any "fixup" workaround running on it, encoded as
a boolean. This information is provided to help troubleshooting
PHY configurations.
Documentation/ABI/testing/sysfs-class-net 0 → 100644
浏览文件 @ af5666e0
What: /sys/class/net/<iface>/addr_assign_type
Date: July 2010
KernelVersion: 3.2
Contact: netdev@vger.kernel.org
Description:
Indicates the address assignment type. Possible values are:
0: permanent address
1: randomly generated
2: stolen from another device
3: set using dev_set_mac_address
What: /sys/class/net/<iface>/addr_len
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the hardware address size in bytes.
Values vary based on the lower-level protocol used by the
interface (Ethernet, FDDI, ATM, IEEE 802.15.4...). See
include/uapi/linux/if_*.h for actual values.
What: /sys/class/net/<iface>/address
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Hardware address currently assigned to this interface.
Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC
address.
What: /sys/class/net/<iface>/broadcast
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Hardware broadcast address for this interface. Format is a
string, e.g: ff:ff:ff:ff:ff:ff for an Ethernet broadcast MAC
address.
What: /sys/class/net/<iface>/carrier
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the current physical link state of the interface.
Posssible values are:
0: physical link is down
1: physical link is up
Note: some special devices, e.g: bonding and team drivers will
allow this attribute to be written to force a link state for
operating correctly and designating another fallback interface.
What: /sys/class/net/<iface>/dev_id
Date: April 2008
KernelVersion: 2.6.26
Contact: netdev@vger.kernel.org
Description:
Indicates the device unique identifier. Format is an hexadecimal
value. This is used to disambiguate interfaces which might be
stacked (e.g: VLAN interfaces) but still have the same MAC
address as their parent device.
What: /sys/class/net/<iface>/dormant
Date: March 2006
KernelVersion: 2.6.17
Contact: netdev@vger.kernel.org
Description:
Indicates whether the interface is in dormant state. Possible
values are:
0: interface is not dormant
1: interface is dormant
This attribute can be used by supplicant software to signal that
the device is not usable unless some supplicant-based
authentication is performed (e.g: 802.1x). 'link_mode' attribute
will also reflect the dormant state.
What: /sys/clas/net/<iface>/duplex
Date: October 2009
KernelVersion: 2.6.33
Contact: netdev@vger.kernel.org
Description:
Indicates the interface latest or current duplex value. Possible
values are:
half: half duplex
full: full duplex
Note: This attribute is only valid for interfaces that implement
the ethtool get_settings method (mostly Ethernet).
What: /sys/class/net/<iface>/flags
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the interface flags as a bitmask in hexadecimal. See
include/uapi/linux/if.h for a list of all possible values and
the flags semantics.
What: /sys/class/net/<iface>/ifalias
Date: September 2008
KernelVersion: 2.6.28
Contact: netdev@vger.kernel.org
Description:
Indicates/stores an interface alias name as a string. This can
be used for system management purposes.
What: /sys/class/net/<iface>/ifindex
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the system-wide interface unique index identifier as a
decimal number. This attribute is used for mapping an interface
identifier to an interface name. It is used throughout the
networking stack for specifying the interface specific
requests/events.
What: /sys/class/net/<iface>/iflink
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the system-wide interface unique index identifier a
the interface is linked to. Format is decimal. This attribute is
used to resolve interfaces chaining, linking and stacking.
Physical interfaces have the same 'ifindex' and 'iflink' values.
What: /sys/class/net/<iface>/link_mode
Date: March 2006
KernelVersion: 2.6.17
Contact: netdev@vger.kernel.org
Description:
Indicates the interface link mode, as a decimal number. This
attribute should be used in conjunction with 'dormant' attribute
to determine the interface usability. Possible values:
0: default link mode
1: dormant link mode
What: /sys/class/net/<iface>/mtu
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the interface currently configured MTU value, in
bytes, and in decimal format. Specific values depends on the
lower-level interface protocol used. Ethernet devices will show
a 'mtu' attribute value of 1500 unless changed.
What: /sys/calss/net/<iface>/netdev_group
Date: January 2011
KernelVersion: 2.6.39
Contact: netdev@vger.kernel.org
Description:
Indicates the interface network device group, as a decimal
integer. Default value is 0 which corresponds to the initial
network devices group. The group can be changed to affect
routing decisions (see: net/ipv4/fib_rules and
net/ipv6/fib6_rules.c).
What: /sys/class/net/<iface>/operstate
Date: March 2006
KernelVersion: 2.6.17
Contact: netdev@vger.kernel.org
Description:
Indicates the interface RFC2863 operational state as a string.
Possible values are:
"unknown", "notpresent", "down", "lowerlayerdown", "testing",
"dormant", "up".
What: /sys/class/net/<iface>/speed
Date: October 2009
KernelVersion: 2.6.33
Contact: netdev@vger.kernel.org
Description:
Indicates the interface latest or current speed value. Value is
an integer representing the link speed in Mbits/sec.
Note: this attribute is only valid for interfaces that implement
the ethtool get_settings method (mostly Ethernet ).
What: /sys/class/net/<iface>/tx_queue_len
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the interface transmit queue len in number of packets,
as an integer value. Value depend on the type of interface,
Ethernet network adapters have a default value of 1000 unless
configured otherwise
What: /sys/class/net/<iface>/type
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the interface protocol type as a decimal value. See
include/uapi/linux/if_arp.h for all possible values.
Documentation/ABI/testing/sysfs-class-net-mesh
浏览文件 @ af5666e0
......@@ -76,6 +76,15 @@ Description:
is used to classify clients as "isolated" by the
Extended Isolation feature.
What: /sys/class/net/<mesh_iface>/mesh/multicast_mode
Date: Feb 2014
Contact: Linus Lüssing <linus.luessing@web.de>
Description:
Indicates whether multicast optimizations are enabled
or disabled. If set to zero then all nodes in the
mesh are going to use classic flooding for any
multicast packet with no optimizations.
What: /sys/class/net/<mesh_iface>/mesh/network_coding
Date: Nov 2012
Contact: Martin Hundeboll <martin@hundeboll.net>
......
Documentation/ABI/testing/sysfs-class-rc 0 → 100644
浏览文件 @ af5666e0
What: /sys/class/rc/
Date: Apr 2010
KernelVersion: 2.6.35
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
The rc/ class sub-directory belongs to the Remote Controller
core and provides a sysfs interface for configuring infrared
remote controller receivers.
What: /sys/class/rc/rcN/
Date: Apr 2010
KernelVersion: 2.6.35
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
A /sys/class/rc/rcN directory is created for each remote
control receiver device where N is the number of the receiver.
What: /sys/class/rc/rcN/protocols
Date: Jun 2010
KernelVersion: 2.6.36
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Reading this file returns a list of available protocols,
something like:
"rc5 [rc6] nec jvc [sony]"
Enabled protocols are shown in [] brackets.
Writing "+proto" will add a protocol to the list of enabled
protocols.
Writing "-proto" will remove a protocol from the list of enabled
protocols.
Writing "proto" will enable only "proto".
Writing "none" will disable all protocols.
Write fails with EINVAL if an invalid protocol combination or
unknown protocol name is used.
What: /sys/class/rc/rcN/filter
Date: Jan 2014
KernelVersion: 3.15
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Sets the scancode filter expected value.
Use in combination with /sys/class/rc/rcN/filter_mask to set the
expected value of the bits set in the filter mask.
If the hardware supports it then scancodes which do not match
the filter will be ignored. Otherwise the write will fail with
an error.
This value may be reset to 0 if the current protocol is altered.
What: /sys/class/rc/rcN/filter_mask
Date: Jan 2014
KernelVersion: 3.15
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Sets the scancode filter mask of bits to compare.
Use in combination with /sys/class/rc/rcN/filter to set the bits
of the scancode which should be compared against the expected
value. A value of 0 disables the filter to allow all valid
scancodes to be processed.
If the hardware supports it then scancodes which do not match
the filter will be ignored. Otherwise the write will fail with
an error.
This value may be reset to 0 if the current protocol is altered.
What: /sys/class/rc/rcN/wakeup_protocols
Date: Feb 2014
KernelVersion: 3.15
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Reading this file returns a list of available protocols to use
for the wakeup filter, something like:
"rc5 rc6 nec jvc [sony]"
The enabled wakeup protocol is shown in [] brackets.
Writing "+proto" will add a protocol to the list of enabled
wakeup protocols.
Writing "-proto" will remove a protocol from the list of enabled
wakeup protocols.
Writing "proto" will use "proto" for wakeup events.
Writing "none" will disable wakeup.
Write fails with EINVAL if an invalid protocol combination or
unknown protocol name is used, or if wakeup is not supported by
the hardware.
What: /sys/class/rc/rcN/wakeup_filter
Date: Jan 2014
KernelVersion: 3.15
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Sets the scancode wakeup filter expected value.
Use in combination with /sys/class/rc/rcN/wakeup_filter_mask to
set the expected value of the bits set in the wakeup filter mask
to trigger a system wake event.
If the hardware supports it and wakeup_filter_mask is not 0 then
scancodes which match the filter will wake the system from e.g.
suspend to RAM or power off.
Otherwise the write will fail with an error.
This value may be reset to 0 if the wakeup protocol is altered.
What: /sys/class/rc/rcN/wakeup_filter_mask
Date: Jan 2014
KernelVersion: 3.15
Contact: Mauro Carvalho Chehab <m.chehab@samsung.com>
Description:
Sets the scancode wakeup filter mask of bits to compare.
Use in combination with /sys/class/rc/rcN/wakeup_filter to set
the bits of the scancode which should be compared against the
expected value to trigger a system wake event.
If the hardware supports it and wakeup_filter_mask is not 0 then
scancodes which match the filter will wake the system from e.g.
suspend to RAM or power off.
Otherwise the write will fail with an error.
This value may be reset to 0 if the wakeup protocol is altered.
Documentation/ABI/testing/sysfs-devices-power
浏览文件 @ af5666e0
......@@ -83,8 +83,10 @@ Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
The /sys/devices/.../wakeup_count attribute contains the number
of signaled wakeup events associated with the device. This
attribute is read-only. If the device is not enabled to wake up
attribute is read-only. If the device is not capable to wake up
the system from sleep states, this attribute is not present.
If the device is not enabled to wake up the system from sleep
states, this attribute is empty.
What: /sys/devices/.../power/wakeup_active_count
Date: September 2010
......@@ -93,8 +95,10 @@ Description:
The /sys/devices/.../wakeup_active_count attribute contains the
number of times the processing of wakeup events associated with
the device was completed (at the kernel level). This attribute
is read-only. If the device is not enabled to wake up the
system from sleep states, this attribute is not present.
is read-only. If the device is not capable to wake up the
system from sleep states, this attribute is not present. If
the device is not enabled to wake up the system from sleep
states, this attribute is empty.
What: /sys/devices/.../power/wakeup_abort_count
Date: February 2012
......@@ -104,8 +108,9 @@ Description:
number of times the processing of a wakeup event associated with
the device might have aborted system transition into a sleep
state in progress. This attribute is read-only. If the device
is not enabled to wake up the system from sleep states, this
attribute is not present.
is not capable to wake up the system from sleep states, this
attribute is not present. If the device is not enabled to wake
up the system from sleep states, this attribute is empty.
What: /sys/devices/.../power/wakeup_expire_count
Date: February 2012
......@@ -114,8 +119,10 @@ Description:
The /sys/devices/.../wakeup_expire_count attribute contains the
number of times a wakeup event associated with the device has
been reported with a timeout that expired. This attribute is
read-only. If the device is not enabled to wake up the system
from sleep states, this attribute is not present.
read-only. If the device is not capable to wake up the system
from sleep states, this attribute is not present. If the
device is not enabled to wake up the system from sleep states,
this attribute is empty.
What: /sys/devices/.../power/wakeup_active
Date: September 2010
......@@ -124,8 +131,10 @@ Description:
The /sys/devices/.../wakeup_active attribute contains either 1,
or 0, depending on whether or not a wakeup event associated with
the device is being processed (1). This attribute is read-only.
If the device is not enabled to wake up the system from sleep
states, this attribute is not present.
If the device is not capable to wake up the system from sleep
states, this attribute is not present. If the device is not
enabled to wake up the system from sleep states, this attribute
is empty.
What: /sys/devices/.../power/wakeup_total_time_ms
Date: September 2010
......@@ -134,8 +143,9 @@ Description:
The /sys/devices/.../wakeup_total_time_ms attribute contains
the total time of processing wakeup events associated with the
device, in milliseconds. This attribute is read-only. If the
device is not enabled to wake up the system from sleep states,
this attribute is not present.
device is not capable to wake up the system from sleep states,
this attribute is not present. If the device is not enabled to
wake up the system from sleep states, this attribute is empty.
What: /sys/devices/.../power/wakeup_max_time_ms
Date: September 2010
......@@ -144,8 +154,10 @@ Description:
The /sys/devices/.../wakeup_max_time_ms attribute contains
the maximum time of processing a single wakeup event associated
with the device, in milliseconds. This attribute is read-only.
If the device is not enabled to wake up the system from sleep
states, this attribute is not present.
If the device is not capable to wake up the system from sleep
states, this attribute is not present. If the device is not
enabled to wake up the system from sleep states, this attribute
is empty.
What: /sys/devices/.../power/wakeup_last_time_ms
Date: September 2010
......@@ -156,7 +168,8 @@ Description:
signaling the last wakeup event associated with the device, in
milliseconds. This attribute is read-only. If the device is
not enabled to wake up the system from sleep states, this
attribute is not present.
attribute is not present. If the device is not enabled to wake
up the system from sleep states, this attribute is empty.
What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms
Date: February 2012
......@@ -165,9 +178,10 @@ Description:
The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute
contains the total time the device has been preventing
opportunistic transitions to sleep states from occurring.
This attribute is read-only. If the device is not enabled to
This attribute is read-only. If the device is not capable to
wake up the system from sleep states, this attribute is not
present.
present. If the device is not enabled to wake up the system
from sleep states, this attribute is empty.
What: /sys/devices/.../power/autosuspend_delay_ms
Date: September 2010
......
Documentation/ABI/testing/sysfs-fs-f2fs
浏览文件 @ af5666e0
......@@ -55,3 +55,15 @@ Date: January 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the number of trials to find a victim segment.
What: /sys/fs/f2fs/<disk>/dir_level
Date: March 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the directory level for large directory.
What: /sys/fs/f2fs/<disk>/ram_thresh
Date: March 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the memory footprint used by f2fs.
Documentation/ABI/testing/sysfs-module
浏览文件 @ af5666e0
......@@ -49,3 +49,4 @@ Description: Module taint flags:
O - out-of-tree module
F - force-loaded module
C - staging driver module
E - unsigned module
Documentation/ABI/testing/sysfs-ptp
浏览文件 @ af5666e0
......@@ -54,6 +54,26 @@ Description:
This file contains the number of programmable periodic
output channels offered by the PTP hardware clock.
What: /sys/class/ptp/ptpN/n_pins
Date: March 2014
Contact: Richard Cochran <richardcochran@gmail.com>
Description:
This file contains the number of programmable pins
offered by the PTP hardware clock.
What: /sys/class/ptp/ptpN/pins
Date: March 2014
Contact: Richard Cochran <richardcochran@gmail.com>
Description:
This directory contains one file for each programmable
pin offered by the PTP hardware clock. The file name
is the hardware dependent pin name. Reading from this
file produces two numbers, the assigned function (see
the PTP_PF_ enumeration values in linux/ptp_clock.h)
and the channel number. The function and channel
assignment may be changed by two writing numbers into
the file.
What: /sys/class/ptp/ptpN/pps_avaiable
Date: September 2010
Contact: Richard Cochran <richardcochran@gmail.com>
......
Documentation/DocBook/80211.tmpl
浏览文件 @ af5666e0
......@@ -98,6 +98,8 @@
!Finclude/net/cfg80211.h priv_to_wiphy
!Finclude/net/cfg80211.h set_wiphy_dev
!Finclude/net/cfg80211.h wdev_priv
!Finclude/net/cfg80211.h ieee80211_iface_limit
!Finclude/net/cfg80211.h ieee80211_iface_combination
</chapter>
<chapter>
<title>Actions and configuration</title>
......
Documentation/DocBook/Makefile
浏览文件 @ af5666e0
......@@ -16,7 +16,7 @@ DOCBOOKS := z8530book.xml device-drivers.xml \
alsa-driver-api.xml writing-an-alsa-driver.xml \
tracepoint.xml drm.xml media_api.xml w1.xml
include $(srctree)/Documentation/DocBook/media/Makefile
include Documentation/DocBook/media/Makefile
###
# The build process is as follows (targets):
......@@ -36,6 +36,7 @@ PS_METHOD = $(prefer-db2x)
# The targets that may be used.
PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs
targets += $(DOCBOOKS)
BOOKS := $(addprefix $(obj)/,$(DOCBOOKS))
xmldocs: $(BOOKS)
sgmldocs: xmldocs
......@@ -58,14 +59,14 @@ mandocs: $(MAN)
installmandocs: mandocs
mkdir -p /usr/local/man/man9/
install Documentation/DocBook/man/*.9.gz /usr/local/man/man9/
install $(obj)/man/*.9.gz /usr/local/man/man9/
###
#External programs used
KERNELDOC = $(srctree)/scripts/kernel-doc
DOCPROC = $(objtree)/scripts/docproc
XMLTOFLAGS = -m $(srctree)/Documentation/DocBook/stylesheet.xsl
XMLTOFLAGS = -m $(srctree)/$(src)/stylesheet.xsl
XMLTOFLAGS += --skip-validation
###
......@@ -87,21 +88,9 @@ define rule_docproc
) > $(dir $@).$(notdir $@).cmd
endef
%.xml: %.tmpl FORCE
%.xml: %.tmpl $(KERNELDOC) $(DOCPROC) FORCE
$(call if_changed_rule,docproc)
###
#Read in all saved dependency files
cmd_files := $(wildcard $(foreach f,$(BOOKS),$(dir $(f)).$(notdir $(f)).cmd))
ifneq ($(cmd_files),)
include $(cmd_files)
endif
###
# Changes in kernel-doc force a rebuild of all documentation
$(BOOKS): $(KERNELDOC)
# Tell kbuild to always build the programs
always := $(hostprogs-y)
......@@ -139,7 +128,7 @@ quiet_cmd_db2pdf = PDF $@
index = index.html
main_idx = Documentation/DocBook/$(index)
main_idx = $(obj)/$(index)
build_main_index = rm -rf $(main_idx); \
echo '<h1>Linux Kernel HTML Documentation</h1>' >> $(main_idx) && \
echo '<h2>Kernel Version: $(KERNELVERSION)</h2>' >> $(main_idx) && \
......@@ -148,7 +137,7 @@ build_main_index = rm -rf $(main_idx); \
quiet_cmd_db2html = HTML $@
cmd_db2html = xmlto html $(XMLTOFLAGS) -o $(patsubst %.html,%,$@) $< && \
echo '<a HREF="$(patsubst %.html,%,$(notdir $@))/index.html"> \
$(patsubst %.html,%,$(notdir $@))</a><p>' > $@
$(patsubst %.html,%,$(notdir $@))</a><p>' > $@
%.html: %.xml
@(which xmlto > /dev/null 2>&1) || \
......
Documentation/DocBook/device-drivers.tmpl
浏览文件 @ af5666e0
......@@ -276,7 +276,7 @@ X!Isound/sound_firmware.c
</para>
<sect1><title>Frame Buffer Memory</title>
!Edrivers/video/fbmem.c
!Edrivers/video/fbdev/core/fbmem.c
</sect1>
<!--
<sect1><title>Frame Buffer Console</title>
......@@ -284,7 +284,7 @@ X!Edrivers/video/console/fbcon.c
</sect1>
-->
<sect1><title>Frame Buffer Colormap</title>
!Edrivers/video/fbcmap.c
!Edrivers/video/fbdev/core/fbcmap.c
</sect1>
<!-- FIXME:
drivers/video/fbgen.c has no docs, which stuffs up the sgml. Comment
......@@ -294,11 +294,11 @@ X!Idrivers/video/fbgen.c
</sect1>
KAO -->
<sect1><title>Frame Buffer Video Mode Database</title>
!Idrivers/video/modedb.c
!Edrivers/video/modedb.c
!Idrivers/video/fbdev/core/modedb.c
!Edrivers/video/fbdev/core/modedb.c
</sect1>
<sect1><title>Frame Buffer Macintosh Video Mode Database</title>
!Edrivers/video/macmodes.c
!Edrivers/video/fbdev/macmodes.c
</sect1>
<sect1><title>Frame Buffer Fonts</title>
<para>
......
Documentation/DocBook/drm.tmpl
浏览文件 @ af5666e0
此差异已折叠。
Documentation/DocBook/kernel-hacking.tmpl
浏览文件 @ af5666e0
......@@ -671,7 +671,7 @@ printk(KERN_INFO "my ip: %pI4\n", &amp;ipaddress);
<sect1 id="routines-local-irqs">
<title><function>local_irq_save()</function>/<function>local_irq_restore()</function>
<filename class="headerfile">include/asm/system.h</filename>
<filename class="headerfile">include/linux/irqflags.h</filename>
</title>
<para>
......@@ -850,16 +850,6 @@ printk(KERN_INFO "my ip: %pI4\n", &amp;ipaddress);
<returnvalue>-ERESTARTSYS</returnvalue> if a signal is received.
The <function>wait_event()</function> version ignores signals.
</para>
<para>
Do not use the <function>sleep_on()</function> function family -
it is very easy to accidentally introduce races; almost certainly
one of the <function>wait_event()</function> family will do, or a
loop around <function>schedule_timeout()</function>. If you choose
to loop around <function>schedule_timeout()</function> remember
you must set the task state (with
<function>set_current_state()</function>) on each iteration to avoid
busy-looping.
</para>
</sect1>
......
Documentation/DocBook/media/dvb/demux.xml
浏览文件 @ af5666e0
......@@ -1042,7 +1042,14 @@ role="subsection"><title>DMX_ADD_PID</title>
</para>
<informaltable><tgroup cols="1"><tbody><row><entry
align="char">
<para>This ioctl is undocumented. Documentation is welcome.</para>
<para>This ioctl call allows to add multiple PIDs to a transport stream filter
previously set up with DMX_SET_PES_FILTER and output equal to DMX_OUT_TSDEMUX_TAP.
</para></entry></row><row><entry align="char"><para>
It is used by readers of /dev/dvb/adapterX/demuxY.
</para></entry></row><row><entry align="char"><para>
It may be called at any time, i.e. before or after the first filter on the
shared file descriptor was started. It makes it possible to record multiple
services without the need to de-multiplex or re-multiplex TS packets.</para>
</entry>
</row></tbody></tgroup></informaltable>
<para>SYNOPSIS
......@@ -1075,7 +1082,7 @@ role="subsection"><title>DMX_ADD_PID</title>
</para>
</entry><entry
align="char">
<para>Undocumented.</para>
<para>PID number to be filtered.</para>
</entry>
</row></tbody></tgroup></informaltable>
&return-value-dvb;
......@@ -1087,7 +1094,15 @@ role="subsection"><title>DMX_REMOVE_PID</title>
</para>
<informaltable><tgroup cols="1"><tbody><row><entry
align="char">
<para>This ioctl is undocumented. Documentation is welcome.</para>
<para>This ioctl call allows to remove a PID when multiple PIDs are set on a
transport stream filter, e. g. a filter previously set up with output equal to
DMX_OUT_TSDEMUX_TAP, created via either DMX_SET_PES_FILTER or DMX_ADD_PID.
</para></entry></row><row><entry align="char"><para>
It is used by readers of /dev/dvb/adapterX/demuxY.
</para></entry></row><row><entry align="char"><para>
It may be called at any time, i.e. before or after the first filter on the
shared file descriptor was started. It makes it possible to record multiple
services without the need to de-multiplex or re-multiplex TS packets.</para>
</entry>
</row></tbody></tgroup></informaltable>
<para>SYNOPSIS
......@@ -1120,7 +1135,7 @@ role="subsection"><title>DMX_REMOVE_PID</title>
</para>
</entry><entry
align="char">
<para>Undocumented.</para>
<para>PID of the PES filter to be removed.</para>
</entry>
</row></tbody></tgroup></informaltable>
&return-value-dvb;
......
Documentation/DocBook/media/dvb/dvbapi.xml
浏览文件 @ af5666e0
......@@ -18,7 +18,7 @@
<firstname>Mauro</firstname>
<othername role="mi">Carvalho</othername>
<surname>Chehab</surname>
<affiliation><address><email>mchehab@redhat.com</email></address></affiliation>
<affiliation><address><email>m.chehab@samsung.com</email></address></affiliation>
<contrib>Ported document to Docbook XML.</contrib>
</author>
</authorgroup>
......@@ -28,7 +28,7 @@
<holder>Convergence GmbH</holder>
</copyright>
<copyright>
<year>2009-2012</year>
<year>2009-2014</year>
<holder>Mauro Carvalho Chehab</holder>
</copyright>
......
Documentation/DocBook/media/dvb/frontend.xml
浏览文件 @ af5666e0
......@@ -744,7 +744,7 @@ typedef enum fe_hierarchy {
</para>
<informaltable><tgroup cols="1"><tbody><row><entry
align="char">
<para>int ioctl(int fd, int request = <link linkend="FE_READ_SNR">FE_READ_SNR</link>, int16_t
<para>int ioctl(int fd, int request = <link linkend="FE_READ_SNR">FE_READ_SNR</link>, uint16_t
&#x22C6;snr);</para>
</entry>
</row></tbody></tgroup></informaltable>
......@@ -766,7 +766,7 @@ typedef enum fe_hierarchy {
</entry>
</row><row><entry
align="char">
<para>int16_t *snr</para>
<para>uint16_t *snr</para>
</entry><entry
align="char">
<para>The signal-to-noise ratio is stored into *snr.</para>
......@@ -791,7 +791,7 @@ typedef enum fe_hierarchy {
<informaltable><tgroup cols="1"><tbody><row><entry
align="char">
<para>int ioctl( int fd, int request =
<link linkend="FE_READ_SIGNAL_STRENGTH">FE_READ_SIGNAL_STRENGTH</link>, int16_t &#x22C6;strength);</para>
<link linkend="FE_READ_SIGNAL_STRENGTH">FE_READ_SIGNAL_STRENGTH</link>, uint16_t &#x22C6;strength);</para>
</entry>
</row></tbody></tgroup></informaltable>
......@@ -814,7 +814,7 @@ typedef enum fe_hierarchy {
</entry>
</row><row><entry
align="char">
<para>int16_t *strength</para>
<para>uint16_t *strength</para>
</entry><entry
align="char">
<para>The signal strength value is stored into *strength.</para>
......
Documentation/DocBook/media/v4l/compat.xml
浏览文件 @ af5666e0
......@@ -2535,6 +2535,16 @@ fields changed from _s32 to _u32.
</orderedlist>
</section>
<section>
<title>V4L2 in Linux 3.15</title>
<orderedlist>
<listitem>
<para>Added Software Defined Radio (SDR) Interface.
</para>
</listitem>
</orderedlist>
</section>
<section id="other">
<title>Relation of V4L2 to other Linux multimedia APIs</title>
......@@ -2651,6 +2661,9 @@ ioctls.</para>
<listitem>
<para>Exporting DMABUF files using &VIDIOC-EXPBUF; ioctl.</para>
</listitem>
<listitem>
<para>Software Defined Radio (SDR) Interface, <xref linkend="sdr" />.</para>
</listitem>
</itemizedlist>
</section>
......
Documentation/DocBook/media/v4l/controls.xml
浏览文件 @ af5666e0
......@@ -2256,6 +2256,26 @@ Applicable to the MPEG1, MPEG2, MPEG4 encoders.</entry>
<entry>integer</entry>
</row><row><entry spanname="descr">Sets the initial delay in milliseconds for
VBV buffer control.</entry>
</row>
<row><entry></entry></row>
<row id="v4l2-mpeg-video-hor-search-range">
<entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_MV_H_SEARCH_RANGE</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row><entry spanname="descr">Horizontal search range defines maximum horizontal search area in pixels
to search and match for the present Macroblock (MB) in the reference picture. This V4L2 control macro is used to set
horizontal search range for motion estimation module in video encoder.</entry>
</row>
<row><entry></entry></row>
<row id="v4l2-mpeg-video-vert-search-range">
<entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_MV_V_SEARCH_RANGE</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row><entry spanname="descr">Vertical search range defines maximum vertical search area in pixels
to search and match for the present Macroblock (MB) in the reference picture. This V4L2 control macro is used to set
vertical search range for motion estimation module in video encoder.</entry>
</row>
<row><entry></entry></row>
......@@ -4370,6 +4390,24 @@ interface and may change in the future.</para>
<entry>The flash controller has detected a short or open
circuit condition on the indicator LED.</entry>
</row>
<row>
<entry><constant>V4L2_FLASH_FAULT_UNDER_VOLTAGE</constant></entry>
<entry>Flash controller voltage to the flash LED
has been below the minimum limit specific to the flash
controller.</entry>
</row>
<row>
<entry><constant>V4L2_FLASH_FAULT_INPUT_VOLTAGE</constant></entry>
<entry>The input voltage of the flash controller is below
the limit under which strobing the flash at full current
will not be possible.The condition persists until this flag
is no longer set.</entry>
</row>
<row>
<entry><constant>V4L2_FLASH_FAULT_LED_OVER_TEMPERATURE</constant></entry>
<entry>The temperature of the LED has exceeded its
allowed upper limit.</entry>
</row>
</tbody>
</entrytbl>
</row>
......@@ -4971,4 +5009,142 @@ defines possible values for de-emphasis. Here they are:</entry>
</table>
</section>
<section id="rf-tuner-controls">
<title>RF Tuner Control Reference</title>
<para>
The RF Tuner (RF_TUNER) class includes controls for common features of devices
having RF tuner.
</para>
<para>
In this context, RF tuner is radio receiver circuit between antenna and
demodulator. It receives radio frequency (RF) from the antenna and converts that
received signal to lower intermediate frequency (IF) or baseband frequency (BB).
Tuners that could do baseband output are often called Zero-IF tuners. Older
tuners were typically simple PLL tuners inside a metal box, whilst newer ones
are highly integrated chips without a metal box "silicon tuners". These controls
are mostly applicable for new feature rich silicon tuners, just because older
tuners does not have much adjustable features.
</para>
<para>
For more information about RF tuners see
<ulink url="http://en.wikipedia.org/wiki/Tuner_%28radio%29">Tuner (radio)</ulink>
and
<ulink url="http://en.wikipedia.org/wiki/RF_front_end">RF front end</ulink>
from Wikipedia.
</para>
<table pgwide="1" frame="none" id="rf-tuner-control-id">
<title>RF_TUNER Control IDs</title>
<tgroup cols="4">
<colspec colname="c1" colwidth="1*" />
<colspec colname="c2" colwidth="6*" />
<colspec colname="c3" colwidth="2*" />
<colspec colname="c4" colwidth="6*" />
<spanspec namest="c1" nameend="c2" spanname="id" />
<spanspec namest="c2" nameend="c4" spanname="descr" />
<thead>
<row>
<entry spanname="id" align="left">ID</entry>
<entry align="left">Type</entry>
</row>
<row rowsep="1">
<entry spanname="descr" align="left">Description</entry>
</row>
</thead>
<tbody valign="top">
<row><entry></entry></row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_CLASS</constant>&nbsp;</entry>
<entry>class</entry>
</row><row><entry spanname="descr">The RF_TUNER class
descriptor. Calling &VIDIOC-QUERYCTRL; for this control will return a
description of this control class.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_BANDWIDTH_AUTO</constant>&nbsp;</entry>
<entry>boolean</entry>
</row>
<row>
<entry spanname="descr">Enables/disables tuner radio channel
bandwidth configuration. In automatic mode bandwidth configuration is performed
by the driver.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_BANDWIDTH</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row>
<entry spanname="descr">Filter(s) on tuner signal path are used to
filter signal according to receiving party needs. Driver configures filters to
fulfill desired bandwidth requirement. Used when V4L2_CID_RF_TUNER_BANDWIDTH_AUTO is not
set. Unit is in Hz. The range and step are driver-specific.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_LNA_GAIN_AUTO</constant>&nbsp;</entry>
<entry>boolean</entry>
</row>
<row>
<entry spanname="descr">Enables/disables LNA automatic gain control (AGC)</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_MIXER_GAIN_AUTO</constant>&nbsp;</entry>
<entry>boolean</entry>
</row>
<row>
<entry spanname="descr">Enables/disables mixer automatic gain control (AGC)</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_IF_GAIN_AUTO</constant>&nbsp;</entry>
<entry>boolean</entry>
</row>
<row>
<entry spanname="descr">Enables/disables IF automatic gain control (AGC)</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_LNA_GAIN</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row>
<entry spanname="descr">LNA (low noise amplifier) gain is first
gain stage on the RF tuner signal path. It is located very close to tuner
antenna input. Used when <constant>V4L2_CID_RF_TUNER_LNA_GAIN_AUTO</constant> is not set.
The range and step are driver-specific.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_MIXER_GAIN</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row>
<entry spanname="descr">Mixer gain is second gain stage on the RF
tuner signal path. It is located inside mixer block, where RF signal is
down-converted by the mixer. Used when <constant>V4L2_CID_RF_TUNER_MIXER_GAIN_AUTO</constant>
is not set. The range and step are driver-specific.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_IF_GAIN</constant>&nbsp;</entry>
<entry>integer</entry>
</row>
<row>
<entry spanname="descr">IF gain is last gain stage on the RF tuner
signal path. It is located on output of RF tuner. It controls signal level of
intermediate frequency output or baseband output. Used when
<constant>V4L2_CID_RF_TUNER_IF_GAIN_AUTO</constant> is not set. The range and step are
driver-specific.</entry>
</row>
<row>
<entry spanname="id"><constant>V4L2_CID_RF_TUNER_PLL_LOCK</constant>&nbsp;</entry>
<entry>boolean</entry>
</row>
<row>
<entry spanname="descr">Is synthesizer PLL locked? RF tuner is
receiving given frequency when that control is set. This is a read-only control.
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
Documentation/DocBook/media/v4l/dev-osd.xml
浏览文件 @ af5666e0
......@@ -56,18 +56,18 @@ framebuffer device.</para>
unsigned int i;
int fb_fd;
if (-1 == ioctl (fd, VIDIOC_G_FBUF, &amp;fbuf)) {
perror ("VIDIOC_G_FBUF");
exit (EXIT_FAILURE);
if (-1 == ioctl(fd, VIDIOC_G_FBUF, &amp;fbuf)) {
perror("VIDIOC_G_FBUF");
exit(EXIT_FAILURE);
}
for (i = 0; i &gt; 30; ++i) {
for (i = 0; i &lt; 30; i++) {
char dev_name[16];
struct fb_fix_screeninfo si;
snprintf (dev_name, sizeof (dev_name), "/dev/fb%u", i);
snprintf(dev_name, sizeof(dev_name), "/dev/fb%u", i);
fb_fd = open (dev_name, O_RDWR);
fb_fd = open(dev_name, O_RDWR);
if (-1 == fb_fd) {
switch (errno) {
case ENOENT: /* no such file */
......@@ -75,19 +75,19 @@ for (i = 0; i &gt; 30; ++i) {
continue;
default:
perror ("open");
exit (EXIT_FAILURE);
perror("open");
exit(EXIT_FAILURE);
}
}
if (0 == ioctl (fb_fd, FBIOGET_FSCREENINFO, &amp;si)) {
if (si.smem_start == (unsigned long) fbuf.base)
if (0 == ioctl(fb_fd, FBIOGET_FSCREENINFO, &amp;si)) {
if (si.smem_start == (unsigned long)fbuf.base)
break;
} else {
/* Apparently not a framebuffer device. */
}
close (fb_fd);
close(fb_fd);
fb_fd = -1;
}
......
Documentation/DocBook/media/v4l/dev-sdr.xml 0 → 100644
浏览文件 @ af5666e0
<title>Software Defined Radio Interface (SDR)</title>
<note>
<title>Experimental</title>
<para>This is an <link linkend="experimental"> experimental </link>
interface and may change in the future.</para>
</note>
<para>
SDR is an abbreviation of Software Defined Radio, the radio device
which uses application software for modulation or demodulation. This interface
is intended for controlling and data streaming of such devices.
</para>
<para>
SDR devices are accessed through character device special files named
<filename>/dev/swradio0</filename> to <filename>/dev/swradio255</filename>
with major number 81 and dynamically allocated minor numbers 0 to 255.
</para>
<section>
<title>Querying Capabilities</title>
<para>
Devices supporting the SDR receiver interface set the
<constant>V4L2_CAP_SDR_CAPTURE</constant> and
<constant>V4L2_CAP_TUNER</constant> flag in the
<structfield>capabilities</structfield> field of &v4l2-capability;
returned by the &VIDIOC-QUERYCAP; ioctl. That flag means the device has an
Analog to Digital Converter (ADC), which is a mandatory element for the SDR receiver.
At least one of the read/write, streaming or asynchronous I/O methods must
be supported.
</para>
</section>
<section>
<title>Supplemental Functions</title>
<para>
SDR devices can support <link linkend="control">controls</link>, and must
support the <link linkend="tuner">tuner</link> ioctls. Tuner ioctls are used
for setting the ADC sampling rate (sampling frequency) and the possible RF tuner
frequency.
</para>
<para>
The <constant>V4L2_TUNER_ADC</constant> tuner type is used for ADC tuners, and
the <constant>V4L2_TUNER_RF</constant> tuner type is used for RF tuners. The
tuner index of the RF tuner (if any) must always follow the ADC tuner index.
Normally the ADC tuner is #0 and the RF tuner is #1.
</para>
<para>
The &VIDIOC-S-HW-FREQ-SEEK; ioctl is not supported.
</para>
</section>
<section>
<title>Data Format Negotiation</title>
<para>
The SDR capture device uses the <link linkend="format">format</link> ioctls to
select the capture format. Both the sampling resolution and the data streaming
format are bound to that selectable format. In addition to the basic
<link linkend="format">format</link> ioctls, the &VIDIOC-ENUM-FMT; ioctl
must be supported as well.
</para>
<para>
To use the <link linkend="format">format</link> ioctls applications set the
<structfield>type</structfield> field of a &v4l2-format; to
<constant>V4L2_BUF_TYPE_SDR_CAPTURE</constant> and use the &v4l2-sdr-format;
<structfield>sdr</structfield> member of the <structfield>fmt</structfield>
union as needed per the desired operation.
Currently only the <structfield>pixelformat</structfield> field of
&v4l2-sdr-format; is used. The content of that field is the V4L2 fourcc code
of the data format.
</para>
<table pgwide="1" frame="none" id="v4l2-sdr-format">
<title>struct <structname>v4l2_sdr_format</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>pixelformat</structfield></entry>
<entry>
The data format or type of compression, set by the application. This is a
little endian <link linkend="v4l2-fourcc">four character code</link>.
V4L2 defines SDR formats in <xref linkend="sdr-formats" />.
</entry>
</row>
<row>
<entry>__u8</entry>
<entry><structfield>reserved[28]</structfield></entry>
<entry>This array is reserved for future extensions.
Drivers and applications must set it to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
An SDR device may support <link linkend="rw">read/write</link>
and/or streaming (<link linkend="mmap">memory mapping</link>
or <link linkend="userp">user pointer</link>) I/O.
</para>
</section>
Documentation/DocBook/media/v4l/io.xml
浏览文件 @ af5666e0
......@@ -339,8 +339,8 @@ returns immediately with an &EAGAIN; when no buffer is available. The
queues as a side effect. Since there is no notion of doing anything
"now" on a multitasking system, if an application needs to synchronize
with another event it should examine the &v4l2-buffer;
<structfield>timestamp</structfield> of captured buffers, or set the
field before enqueuing buffers for output.</para>
<structfield>timestamp</structfield> of captured or outputted buffers.
</para>
<para>Drivers implementing memory mapping I/O must
support the <constant>VIDIOC_REQBUFS</constant>,
......@@ -457,7 +457,7 @@ queues and unlocks all buffers as a side effect. Since there is no
notion of doing anything "now" on a multitasking system, if an
application needs to synchronize with another event it should examine
the &v4l2-buffer; <structfield>timestamp</structfield> of captured
buffers, or set the field before enqueuing buffers for output.</para>
or outputted buffers.</para>
<para>Drivers implementing user pointer I/O must
support the <constant>VIDIOC_REQBUFS</constant>,
......@@ -620,8 +620,7 @@ returns immediately with an &EAGAIN; when no buffer is available. The
unlocks all buffers as a side effect. Since there is no notion of doing
anything "now" on a multitasking system, if an application needs to synchronize
with another event it should examine the &v4l2-buffer;
<structfield>timestamp</structfield> of captured buffers, or set the field
before enqueuing buffers for output.</para>
<structfield>timestamp</structfield> of captured or outputted buffers.</para>
<para>Drivers implementing DMABUF importing I/O must support the
<constant>VIDIOC_REQBUFS</constant>, <constant>VIDIOC_QBUF</constant>,
......@@ -654,38 +653,19 @@ plane, are stored in struct <structname>v4l2_plane</structname> instead.
In that case, struct <structname>v4l2_buffer</structname> contains an array of
plane structures.</para>
<para>Nominally timestamps refer to the first data byte transmitted.
In practice however the wide range of hardware covered by the V4L2 API
limits timestamp accuracy. Often an interrupt routine will
sample the system clock shortly after the field or frame was stored
completely in memory. So applications must expect a constant
difference up to one field or frame period plus a small (few scan
lines) random error. The delay and error can be much
larger due to compression or transmission over an external bus when
the frames are not properly stamped by the sender. This is frequently
the case with USB cameras. Here timestamps refer to the instant the
field or frame was received by the driver, not the capture time. These
devices identify by not enumerating any video standards, see <xref
linkend="standard" />.</para>
<para>Similar limitations apply to output timestamps. Typically
the video hardware locks to a clock controlling the video timing, the
horizontal and vertical synchronization pulses. At some point in the
line sequence, possibly the vertical blanking, an interrupt routine
samples the system clock, compares against the timestamp and programs
the hardware to repeat the previous field or frame, or to display the
buffer contents.</para>
<para>Apart of limitations of the video device and natural
inaccuracies of all clocks, it should be noted system time itself is
not perfectly stable. It can be affected by power saving cycles,
warped to insert leap seconds, or even turned back or forth by the
system administrator affecting long term measurements. <footnote>
<para>Since no other Linux multimedia
API supports unadjusted time it would be foolish to introduce here. We
must use a universally supported clock to synchronize different media,
hence time of day.</para>
</footnote></para>
<para>Dequeued video buffers come with timestamps. The driver
decides at which part of the frame and with which clock the
timestamp is taken. Please see flags in the masks
<constant>V4L2_BUF_FLAG_TIMESTAMP_MASK</constant> and
<constant>V4L2_BUF_FLAG_TSTAMP_SRC_MASK</constant> in <xref
linkend="buffer-flags" />. These flags are always valid and constant
across all buffers during the whole video stream. Changes in these
flags may take place as a side effect of &VIDIOC-S-INPUT; or
&VIDIOC-S-OUTPUT; however. The
<constant>V4L2_BUF_FLAG_TIMESTAMP_COPY</constant> timestamp type
which is used by e.g. on mem-to-mem devices is an exception to the
rule: the timestamp source flags are copied from the OUTPUT video
buffer to the CAPTURE video buffer.</para>
<table frame="none" pgwide="1" id="v4l2-buffer">
<title>struct <structname>v4l2_buffer</structname></title>
......@@ -696,10 +676,11 @@ hence time of day.</para>
<entry>__u32</entry>
<entry><structfield>index</structfield></entry>
<entry></entry>
<entry>Number of the buffer, set by the application. This
field is only used for <link linkend="mmap">memory mapping</link> I/O
and can range from zero to the number of buffers allocated
with the &VIDIOC-REQBUFS; ioctl (&v4l2-requestbuffers; <structfield>count</structfield>) minus one.</entry>
<entry>Number of the buffer, set by the application except
when calling &VIDIOC-DQBUF;, then it is set by the driver.
This field can range from zero to the number of buffers allocated
with the &VIDIOC-REQBUFS; ioctl (&v4l2-requestbuffers; <structfield>count</structfield>),
plus any buffers allocated with &VIDIOC-CREATE-BUFS; minus one.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -718,7 +699,7 @@ linkend="v4l2-buf-type" /></entry>
buffer. It depends on the negotiated data format and may change with
each buffer for compressed variable size data like JPEG images.
Drivers must set this field when <structfield>type</structfield>
refers to an input stream, applications when an output stream.</entry>
refers to an input stream, applications when it refers to an output stream.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -735,7 +716,7 @@ linkend="buffer-flags" />.</entry>
buffer, see <xref linkend="v4l2-field" />. This field is not used when
the buffer contains VBI data. Drivers must set it when
<structfield>type</structfield> refers to an input stream,
applications when an output stream.</entry>
applications when it refers to an output stream.</entry>
</row>
<row>
<entry>struct timeval</entry>
......@@ -745,15 +726,13 @@ applications when an output stream.</entry>
byte was captured, as returned by the
<function>clock_gettime()</function> function for the relevant
clock id; see <constant>V4L2_BUF_FLAG_TIMESTAMP_*</constant> in
<xref linkend="buffer-flags" />. For output streams the data
will not be displayed before this time, secondary to the nominal
frame rate determined by the current video standard in enqueued
order. Applications can for example zero this field to display
frames as soon as possible. The driver stores the time at which
the first data byte was actually sent out in the
<structfield>timestamp</structfield> field. This permits
<xref linkend="buffer-flags" />. For output streams the driver
stores the time at which the last data byte was actually sent out
in the <structfield>timestamp</structfield> field. This permits
applications to monitor the drift between the video and system
clock.</para></entry>
clock. For output streams that use <constant>V4L2_BUF_FLAG_TIMESTAMP_COPY</constant>
the application has to fill in the timestamp which will be copied
by the driver to the capture stream.</para></entry>
</row>
<row>
<entry>&v4l2-timecode;</entry>
......@@ -846,7 +825,8 @@ is the file descriptor associated with a DMABUF buffer.</entry>
<entry><structfield>length</structfield></entry>
<entry></entry>
<entry>Size of the buffer (not the payload) in bytes for the
single-planar API. For the multi-planar API the application sets
single-planar API. This is set by the driver based on the calls to
&VIDIOC-REQBUFS; and/or &VIDIOC-CREATE-BUFS;. For the multi-planar API the application sets
this to the number of elements in the <structfield>planes</structfield>
array. The driver will fill in the actual number of valid elements in
that array.
......@@ -880,13 +860,15 @@ should set this to 0.</entry>
<entry><structfield>bytesused</structfield></entry>
<entry></entry>
<entry>The number of bytes occupied by data in the plane
(its payload).</entry>
(its payload). Drivers must set this field when <structfield>type</structfield>
refers to an input stream, applications when it refers to an output stream.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>length</structfield></entry>
<entry></entry>
<entry>Size in bytes of the plane (not its payload).</entry>
<entry>Size in bytes of the plane (not its payload). This is set by the driver
based on the calls to &VIDIOC-REQBUFS; and/or &VIDIOC-CREATE-BUFS;.</entry>
</row>
<row>
<entry>union</entry>
......@@ -925,7 +907,9 @@ should set this to 0.</entry>
<entry>__u32</entry>
<entry><structfield>data_offset</structfield></entry>
<entry></entry>
<entry>Offset in bytes to video data in the plane, if applicable.
<entry>Offset in bytes to video data in the plane.
Drivers must set this field when <structfield>type</structfield>
refers to an input stream, applications when it refers to an output stream.
</entry>
</row>
<row>
......@@ -1005,6 +989,12 @@ should set this to 0.</entry>
<entry>Buffer for video output overlay (OSD), see <xref
linkend="osd" />.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_TYPE_SDR_CAPTURE</constant></entry>
<entry>11</entry>
<entry>Buffer for Software Defined Radio (SDR), see <xref
linkend="sdr" />.</entry>
</row>
</tbody>
</tgroup>
</table>
......@@ -1016,7 +1006,7 @@ should set this to 0.</entry>
<tbody valign="top">
<row>
<entry><constant>V4L2_BUF_FLAG_MAPPED</constant></entry>
<entry>0x0001</entry>
<entry>0x00000001</entry>
<entry>The buffer resides in device memory and has been mapped
into the application's address space, see <xref linkend="mmap" /> for details.
Drivers set or clear this flag when the
......@@ -1026,7 +1016,7 @@ Drivers set or clear this flag when the
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_QUEUED</constant></entry>
<entry>0x0002</entry>
<entry>0x00000002</entry>
<entry>Internally drivers maintain two buffer queues, an
incoming and outgoing queue. When this flag is set, the buffer is
currently on the incoming queue. It automatically moves to the
......@@ -1039,7 +1029,7 @@ cleared.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_DONE</constant></entry>
<entry>0x0004</entry>
<entry>0x00000004</entry>
<entry>When this flag is set, the buffer is currently on
the outgoing queue, ready to be dequeued from the driver. Drivers set
or clear this flag when the <constant>VIDIOC_QUERYBUF</constant> ioctl
......@@ -1049,11 +1039,11 @@ buffer cannot be on both queues at the same time, the
<constant>V4L2_BUF_FLAG_QUEUED</constant> and
<constant>V4L2_BUF_FLAG_DONE</constant> flag are mutually exclusive.
They can be both cleared however, then the buffer is in "dequeued"
state, in the application domain to say so.</entry>
state, in the application domain so to say.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_ERROR</constant></entry>
<entry>0x0040</entry>
<entry>0x00000040</entry>
<entry>When this flag is set, the buffer has been dequeued
successfully, although the data might have been corrupted.
This is recoverable, streaming may continue as normal and
......@@ -1063,35 +1053,43 @@ state, in the application domain to say so.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_KEYFRAME</constant></entry>
<entry>0x0008</entry>
<entry>0x00000008</entry>
<entry>Drivers set or clear this flag when calling the
<constant>VIDIOC_DQBUF</constant> ioctl. It may be set by video
capture devices when the buffer contains a compressed image which is a
key frame (or field), &ie; can be decompressed on its own.</entry>
key frame (or field), &ie; can be decompressed on its own. Also know as
an I-frame. Applications can set this bit when <structfield>type</structfield>
refers to an output stream.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_PFRAME</constant></entry>
<entry>0x0010</entry>
<entry>0x00000010</entry>
<entry>Similar to <constant>V4L2_BUF_FLAG_KEYFRAME</constant>
this flags predicted frames or fields which contain only differences to a
previous key frame.</entry>
previous key frame. Applications can set this bit when <structfield>type</structfield>
refers to an output stream.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_BFRAME</constant></entry>
<entry>0x0020</entry>
<entry>Similar to <constant>V4L2_BUF_FLAG_PFRAME</constant>
this is a bidirectional predicted frame or field. [ooc tbd]</entry>
<entry>0x00000020</entry>
<entry>Similar to <constant>V4L2_BUF_FLAG_KEYFRAME</constant>
this flags a bi-directional predicted frame or field which contains only
the differences between the current frame and both the preceding and following
key frames to specify its content. Applications can set this bit when
<structfield>type</structfield> refers to an output stream.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMECODE</constant></entry>
<entry>0x0100</entry>
<entry>0x00000100</entry>
<entry>The <structfield>timecode</structfield> field is valid.
Drivers set or clear this flag when the <constant>VIDIOC_DQBUF</constant>
ioctl is called.</entry>
ioctl is called. Applications can set this bit and the corresponding
<structfield>timecode</structfield> structure when <structfield>type</structfield>
refers to an output stream.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_PREPARED</constant></entry>
<entry>0x0400</entry>
<entry>0x00000400</entry>
<entry>The buffer has been prepared for I/O and can be queued by the
application. Drivers set or clear this flag when the
<link linkend="vidioc-querybuf">VIDIOC_QUERYBUF</link>, <link
......@@ -1101,7 +1099,7 @@ application. Drivers set or clear this flag when the
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_NO_CACHE_INVALIDATE</constant></entry>
<entry>0x0800</entry>
<entry>0x00000800</entry>
<entry>Caches do not have to be invalidated for this buffer.
Typically applications shall use this flag if the data captured in the buffer
is not going to be touched by the CPU, instead the buffer will, probably, be
......@@ -1110,7 +1108,7 @@ passed on to a DMA-capable hardware unit for further processing or output.
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_NO_CACHE_CLEAN</constant></entry>
<entry>0x1000</entry>
<entry>0x00001000</entry>
<entry>Caches do not have to be cleaned for this buffer.
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,
......@@ -1118,7 +1116,7 @@ in which case caches have not been used.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_MASK</constant></entry>
<entry>0xe000</entry>
<entry>0x0000e000</entry>
<entry>Mask for timestamp types below. To test the
timestamp type, mask out bits not belonging to timestamp
type by performing a logical and operation with buffer
......@@ -1126,7 +1124,7 @@ in which case caches have not been used.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_UNKNOWN</constant></entry>
<entry>0x0000</entry>
<entry>0x00000000</entry>
<entry>Unknown timestamp type. This type is used by
drivers before Linux 3.9 and may be either monotonic (see
below) or realtime (wall clock). Monotonic clock has been
......@@ -1139,7 +1137,7 @@ in which case caches have not been used.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_MONOTONIC</constant></entry>
<entry>0x2000</entry>
<entry>0x00002000</entry>
<entry>The buffer timestamp has been taken from the
<constant>CLOCK_MONOTONIC</constant> clock. To access the
same clock outside V4L2, use
......@@ -1147,10 +1145,42 @@ in which case caches have not been used.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TIMESTAMP_COPY</constant></entry>
<entry>0x4000</entry>
<entry>0x00004000</entry>
<entry>The CAPTURE buffer timestamp has been taken from the
corresponding OUTPUT buffer. This flag applies only to mem2mem devices.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TSTAMP_SRC_MASK</constant></entry>
<entry>0x00070000</entry>
<entry>Mask for timestamp sources below. The timestamp source
defines the point of time the timestamp is taken in relation to
the frame. Logical 'and' operation between the
<structfield>flags</structfield> field and
<constant>V4L2_BUF_FLAG_TSTAMP_SRC_MASK</constant> produces the
value of the timestamp source. Applications must set the timestamp
source when <structfield>type</structfield> refers to an output stream
and <constant>V4L2_BUF_FLAG_TIMESTAMP_COPY</constant> is set.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TSTAMP_SRC_EOF</constant></entry>
<entry>0x00000000</entry>
<entry>End Of Frame. The buffer timestamp has been taken
when the last pixel of the frame has been received or the
last pixel of the frame has been transmitted. In practice,
software generated timestamps will typically be read from
the clock a small amount of time after the last pixel has
been received or transmitten, depending on the system and
other activity in it.</entry>
</row>
<row>
<entry><constant>V4L2_BUF_FLAG_TSTAMP_SRC_SOE</constant></entry>
<entry>0x00010000</entry>
<entry>Start Of Exposure. The buffer timestamp has been
taken when the exposure of the frame has begun. This is
only valid for the
<constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant> buffer
type.</entry>
</row>
</tbody>
</tgroup>
</table>
......@@ -1440,10 +1470,9 @@ or application, depending on data direction, must set &v4l2-buffer;
<constant>V4L2_FIELD_BOTTOM</constant>. Any two successive fields pair
to build a frame. If fields are successive, without any dropped fields
between them (fields can drop individually), can be determined from
the &v4l2-buffer; <structfield>sequence</structfield> field. Image
sizes refer to the frame, not fields. This format cannot be selected
when using the read/write I/O method.<!-- Where it's indistinguishable
from V4L2_FIELD_SEQ_*. --></entry>
the &v4l2-buffer; <structfield>sequence</structfield> field. This format
cannot be selected when using the read/write I/O method since there
is no way to communicate if a field was a top or bottom field.</entry>
</row>
<row>
<entry><constant>V4L2_FIELD_INTERLACED_TB</constant></entry>
......
Documentation/DocBook/media/v4l/pixfmt-nv16m.xml
浏览文件 @ af5666e0
......@@ -12,18 +12,17 @@
<refsect1>
<title>Description</title>
<para>This is a multi-planar, two-plane version of the YUV 4:2:0 format.
<para>This is a multi-planar, two-plane version of the YUV 4:2:2 format.
The three components are separated into two sub-images or planes.
<constant>V4L2_PIX_FMT_NV16M</constant> differs from <constant>V4L2_PIX_FMT_NV16
</constant> in that the two planes are non-contiguous in memory, i.e. the chroma
plane does not necessarily immediately follows the luma plane.
plane does not necessarily immediately follow the luma plane.
The luminance data occupies the first plane. The Y plane has one byte per pixel.
In the second plane there is chrominance data with alternating chroma samples.
The CbCr plane is the same width and height, in bytes, as the Y plane.
Each CbCr pair belongs to four pixels. For example,
Each CbCr pair belongs to two pixels. For example,
Cb<subscript>0</subscript>/Cr<subscript>0</subscript> belongs to
Y'<subscript>00</subscript>, Y'<subscript>01</subscript>,
Y'<subscript>10</subscript>, Y'<subscript>11</subscript>.
Y'<subscript>00</subscript>, Y'<subscript>01</subscript>.
<constant>V4L2_PIX_FMT_NV61M</constant> is the same as <constant>V4L2_PIX_FMT_NV16M</constant>
except the Cb and Cr bytes are swapped, the CrCb plane starts with a Cr byte.</para>
......
Documentation/DocBook/media/v4l/pixfmt-sdr-cu08.xml 0 → 100644
浏览文件 @ af5666e0
<refentry id="V4L2-SDR-FMT-CU08">
<refmeta>
<refentrytitle>V4L2_SDR_FMT_CU8 ('CU08')</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>
<constant>V4L2_SDR_FMT_CU8</constant>
</refname>
<refpurpose>Complex unsigned 8-bit IQ sample</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
<para>
This format contains sequence of complex number samples. Each complex number
consist two parts, called In-phase and Quadrature (IQ). Both I and Q are
represented as a 8 bit unsigned number. I value comes first and Q value after
that.
</para>
<example>
<title><constant>V4L2_SDR_FMT_CU8</constant> 1 sample</title>
<formalpara>
<title>Byte Order.</title>
<para>Each cell is one byte.
<informaltable frame="none">
<tgroup cols="2" align="center">
<colspec align="left" colwidth="2*" />
<tbody valign="top">
<row>
<entry>start&nbsp;+&nbsp;0:</entry>
<entry>I'<subscript>0</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;1:</entry>
<entry>Q'<subscript>0</subscript></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</formalpara>
</example>
</refsect1>
</refentry>
Documentation/DocBook/media/v4l/pixfmt-sdr-cu16le.xml 0 → 100644
浏览文件 @ af5666e0
<refentry id="V4L2-SDR-FMT-CU16LE">
<refmeta>
<refentrytitle>V4L2_SDR_FMT_CU16LE ('CU16')</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>
<constant>V4L2_SDR_FMT_CU16LE</constant>
</refname>
<refpurpose>Complex unsigned 16-bit little endian IQ sample</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
<para>
This format contains sequence of complex number samples. Each complex number
consist two parts, called In-phase and Quadrature (IQ). Both I and Q are
represented as a 16 bit unsigned little endian number. I value comes first
and Q value after that.
</para>
<example>
<title><constant>V4L2_SDR_FMT_CU16LE</constant> 1 sample</title>
<formalpara>
<title>Byte Order.</title>
<para>Each cell is one byte.
<informaltable frame="none">
<tgroup cols="3" align="center">
<colspec align="left" colwidth="2*" />
<tbody valign="top">
<row>
<entry>start&nbsp;+&nbsp;0:</entry>
<entry>I'<subscript>0[7:0]</subscript></entry>
<entry>I'<subscript>0[15:8]</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;2:</entry>
<entry>Q'<subscript>0[7:0]</subscript></entry>
<entry>Q'<subscript>0[15:8]</subscript></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</formalpara>
</example>
</refsect1>
</refentry>
Documentation/DocBook/media/v4l/pixfmt.xml
浏览文件 @ af5666e0
......@@ -25,7 +25,12 @@ capturing and output, for overlay frame buffer formats see also
<row>
<entry>__u32</entry>
<entry><structfield>height</structfield></entry>
<entry>Image height in pixels.</entry>
<entry>Image height in pixels. If <structfield>field</structfield> is
one of <constant>V4L2_FIELD_TOP</constant>, <constant>V4L2_FIELD_BOTTOM</constant>
or <constant>V4L2_FIELD_ALTERNATE</constant> then height refers to the
number of lines in the field, otherwise it refers to the number of
lines in the frame (which is twice the field height for interlaced
formats).</entry>
</row>
<row>
<entry spanname="hspan">Applications set these fields to
......@@ -54,7 +59,7 @@ linkend="reserved-formats" /></entry>
can request to capture or output only the top or bottom field, or both
fields interlaced or sequentially stored in one buffer or alternating
in separate buffers. Drivers return the actual field order selected.
For details see <xref linkend="field-order" />.</entry>
For more details on fields see <xref linkend="field-order" />.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -81,7 +86,10 @@ plane and is divided by the same factor as the
example the Cb and Cr planes of a YUV 4:2:0 image have half as many
padding bytes following each line as the Y plane. To avoid ambiguities
drivers must return a <structfield>bytesperline</structfield> value
rounded up to a multiple of the scale factor.</para></entry>
rounded up to a multiple of the scale factor.</para>
<para>For compressed formats the <structfield>bytesperline</structfield>
value makes no sense. Applications and drivers must set this to 0 in
that case.</para></entry>
</row>
<row>
<entry>__u32</entry>
......@@ -97,7 +105,8 @@ hold an image.</entry>
<entry>&v4l2-colorspace;</entry>
<entry><structfield>colorspace</structfield></entry>
<entry>This information supplements the
<structfield>pixelformat</structfield> and must be set by the driver,
<structfield>pixelformat</structfield> and must be set by the driver for
capture streams and by the application for output streams,
see <xref linkend="colorspaces" />.</entry>
</row>
<row>
......@@ -135,7 +144,7 @@ set this field to zero.</entry>
<entry>__u16</entry>
<entry><structfield>bytesperline</structfield></entry>
<entry>Distance in bytes between the leftmost pixels in two adjacent
lines.</entry>
lines. See &v4l2-pix-format;.</entry>
</row>
<row>
<entry>__u16</entry>
......@@ -154,12 +163,12 @@ set this field to zero.</entry>
<row>
<entry>__u32</entry>
<entry><structfield>width</structfield></entry>
<entry>Image width in pixels.</entry>
<entry>Image width in pixels. See &v4l2-pix-format;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>height</structfield></entry>
<entry>Image height in pixels.</entry>
<entry>Image height in pixels. See &v4l2-pix-format;.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -811,6 +820,17 @@ extended control <constant>V4L2_CID_MPEG_STREAM_TYPE</constant>, see
</table>
</section>
<section id="sdr-formats">
<title>SDR Formats</title>
<para>These formats are used for <link linkend="sdr">SDR Capture</link>
interface only.</para>
&sub-sdr-cu08;
&sub-sdr-cu16le;
</section>
<section id="pixfmt-reserved">
<title>Reserved Format Identifiers</title>
......
Documentation/DocBook/media/v4l/remote_controllers.xml
浏览文件 @ af5666e0
<partinfo>
<authorgroup>
<author>
<firstname>Mauro</firstname>
<surname>Chehab</surname>
<othername role="mi">Carvalho</othername>
<affiliation><address><email>m.chehab@samsung.com</email></address></affiliation>
<contrib>Initial version.</contrib>
</author>
</authorgroup>
<copyright>
<year>2009-2014</year>
<holder>Mauro Carvalho Chehab</holder>
</copyright>
<revhistory>
<!-- Put document revisions here, newest first. -->
<revision>
<revnumber>3.15</revnumber>
<date>2014-02-06</date>
<authorinitials>mcc</authorinitials>
<revremark>Added the interface description and the RC sysfs class description.</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>2009-09-06</date>
<authorinitials>mcc</authorinitials>
<revremark>Initial revision</revremark>
</revision>
</revhistory>
</partinfo>
<title>Remote Controller API</title>
<chapter id="remote_controllers">
<title>Remote Controllers</title>
<section id="Remote_controllers_Intro">
<title>Introduction</title>
<para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each
manufacturer has their own type of control. It is not rare for the same manufacturer to ship different
types of controls, depending on the device.</para>
<para>A Remote Controller interface is mapped as a normal evdev/input interface, just like a keyboard or a mouse.
So, it uses all ioctls already defined for any other input devices.</para>
<para>However, remove controllers are more flexible than a normal input device, as the IR
receiver (and/or transmitter) can be used in conjunction with a wide variety of different IR remotes.</para>
<para>In order to allow flexibility, the Remote Controller subsystem allows controlling the
RC-specific attributes via <link linkend="remote_controllers_sysfs_nodes">the sysfs class nodes</link>.</para>
</section>
<section id="remote_controllers_sysfs_nodes">
<title>Remote Controller's sysfs nodes</title>
<para>As defined at <constant>Documentation/ABI/testing/sysfs-class-rc</constant>, those are the sysfs nodes that control the Remote Controllers:</para>
<section id="sys_class_rc">
<title>/sys/class/rc/</title>
<para>The <constant>/sys/class/rc/</constant> class sub-directory belongs to the Remote Controller
core and provides a sysfs interface for configuring infrared remote controller receivers.
</para>
</section>
<section id="sys_class_rc_rcN">
<title>/sys/class/rc/rcN/</title>
<para>A <constant>/sys/class/rc/rcN</constant> directory is created for each remote
control receiver device where N is the number of the receiver.</para>
</section>
<section id="sys_class_rc_rcN_protocols">
<title>/sys/class/rc/rcN/protocols</title>
<para>Reading this file returns a list of available protocols, something like:</para>
<para><constant>rc5 [rc6] nec jvc [sony]</constant></para>
<para>Enabled protocols are shown in [] brackets.</para>
<para>Writing "+proto" will add a protocol to the list of enabled protocols.</para>
<para>Writing "-proto" will remove a protocol from the list of enabled protocols.</para>
<para>Writing "proto" will enable only "proto".</para>
<para>Writing "none" will disable all protocols.</para>
<para>Write fails with EINVAL if an invalid protocol combination or unknown protocol name is used.</para>
</section>
<section id="sys_class_rc_rcN_filter">
<title>/sys/class/rc/rcN/filter</title>
<para>Sets the scancode filter expected value.</para>
<para>Use in combination with <constant>/sys/class/rc/rcN/filter_mask</constant> to set the
expected value of the bits set in the filter mask.
If the hardware supports it then scancodes which do not match
the filter will be ignored. Otherwise the write will fail with
an error.</para>
<para>This value may be reset to 0 if the current protocol is altered.</para>
</section>
<section id="sys_class_rc_rcN_filter_mask">
<title>/sys/class/rc/rcN/filter_mask</title>
<para>Sets the scancode filter mask of bits to compare.
Use in combination with <constant>/sys/class/rc/rcN/filter</constant> to set the bits
of the scancode which should be compared against the expected
value. A value of 0 disables the filter to allow all valid
scancodes to be processed.</para>
<para>If the hardware supports it then scancodes which do not match
the filter will be ignored. Otherwise the write will fail with
an error.</para>
<para>This value may be reset to 0 if the current protocol is altered.</para>
</section>
<section id="sys_class_rc_rcN_wakeup_protocols">
<title>/sys/class/rc/rcN/wakeup_protocols</title>
<para>Reading this file returns a list of available protocols to use for the
wakeup filter, something like:</para>
<para><constant>rc5 rc6 nec jvc [sony]</constant></para>
<para>The enabled wakeup protocol is shown in [] brackets.</para>
<para>Writing "+proto" will add a protocol to the list of enabled wakeup
protocols.</para>
<para>Writing "-proto" will remove a protocol from the list of enabled wakeup
protocols.</para>
<para>Writing "proto" will use "proto" for wakeup events.</para>
<para>Writing "none" will disable wakeup.</para>
<para>Write fails with EINVAL if an invalid protocol combination or unknown
protocol name is used, or if wakeup is not supported by the hardware.</para>
</section>
<section id="sys_class_rc_rcN_wakeup_filter">
<title>/sys/class/rc/rcN/wakeup_filter</title>
<para>Sets the scancode wakeup filter expected value.
Use in combination with <constant>/sys/class/rc/rcN/wakeup_filter_mask</constant> to
set the expected value of the bits set in the wakeup filter mask
to trigger a system wake event.</para>
<para>If the hardware supports it and wakeup_filter_mask is not 0 then
scancodes which match the filter will wake the system from e.g.
suspend to RAM or power off.
Otherwise the write will fail with an error.</para>
<para>This value may be reset to 0 if the wakeup protocol is altered.</para>
</section>
<section id="sys_class_rc_rcN_wakeup_filter_mask">
<title>/sys/class/rc/rcN/wakeup_filter_mask</title>
<para>Sets the scancode wakeup filter mask of bits to compare.
Use in combination with <constant>/sys/class/rc/rcN/wakeup_filter</constant> to set
the bits of the scancode which should be compared against the
expected value to trigger a system wake event.</para>
<para>If the hardware supports it and wakeup_filter_mask is not 0 then
scancodes which match the filter will wake the system from e.g.
suspend to RAM or power off.
Otherwise the write will fail with an error.</para>
<para>This value may be reset to 0 if the wakeup protocol is altered.</para>
</section>
</section>
<section id="Remote_controllers_tables">
<title>Remote controller tables</title>
<para>Unfortunately, for several years, there was no effort to create uniform IR keycodes for
different devices. This caused the same IR keyname to be mapped completely differently on
different IR devices. This resulted that the same IR keyname to be mapped completely different on
......@@ -175,3 +317,4 @@ keymapping.</para>
</section>
&sub-lirc_device_interface;
</chapter>
Documentation/DocBook/media/v4l/v4l2.xml
浏览文件 @ af5666e0
......@@ -70,7 +70,7 @@ MPEG stream embedded, sliced VBI data format in this specification.
Remote Controller chapter.</contrib>
<affiliation>
<address>
<email>mchehab@redhat.com</email>
<email>m.chehab@samsung.com</email>
</address>
</affiliation>
</author>
......@@ -107,6 +107,16 @@ Remote Controller chapter.</contrib>
</address>
</affiliation>
</author>
<author>
<firstname>Antti</firstname>
<surname>Palosaari</surname>
<contrib>SDR API.</contrib>
<affiliation>
<address>
<email>crope@iki.fi</email>
</address>
</affiliation>
</author>
</authorgroup>
<copyright>
......@@ -125,6 +135,7 @@ Remote Controller chapter.</contrib>
<year>2011</year>
<year>2012</year>
<year>2013</year>
<year>2014</year>
<holder>Bill Dirks, Michael H. Schimek, Hans Verkuil, Martin
Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab,
Pawel Osciak</holder>
......@@ -140,6 +151,16 @@ structs, ioctls) must be noted in more detail in the history chapter
(compat.xml), along with the possible impact on existing drivers and
applications. -->
<revision>
<revnumber>3.15</revnumber>
<date>2014-02-03</date>
<authorinitials>hv, ap</authorinitials>
<revremark>Update several sections of "Common API Elements": "Opening and Closing Devices"
"Querying Capabilities", "Application Priority", "Video Inputs and Outputs", "Audio Inputs and Outputs"
"Tuners and Modulators", "Video Standards" and "Digital Video (DV) Timings". Added SDR API.
</revremark>
</revision>
<revision>
<revnumber>3.14</revnumber>
<date>2013-11-25</date>
......@@ -537,6 +558,7 @@ and discussions on the V4L mailing list.</revremark>
<section id="ttx"> &sub-dev-teletext; </section>
<section id="radio"> &sub-dev-radio; </section>
<section id="rds"> &sub-dev-rds; </section>
<section id="sdr"> &sub-dev-sdr; </section>
<section id="event"> &sub-dev-event; </section>
<section id="subdev"> &sub-dev-subdev; </section>
</chapter>
......@@ -585,6 +607,7 @@ and discussions on the V4L mailing list.</revremark>
&sub-g-crop;
&sub-g-ctrl;
&sub-g-dv-timings;
&sub-g-edid;
&sub-g-enc-index;
&sub-g-ext-ctrls;
&sub-g-fbuf;
......@@ -616,7 +639,6 @@ and discussions on the V4L mailing list.</revremark>
&sub-subdev-enum-frame-size;
&sub-subdev-enum-mbus-code;
&sub-subdev-g-crop;
&sub-subdev-g-edid;
&sub-subdev-g-fmt;
&sub-subdev-g-frame-interval;
&sub-subdev-g-selection;
......
Documentation/DocBook/media/v4l/vidioc-enum-freq-bands.xml
浏览文件 @ af5666e0
......@@ -100,7 +100,7 @@ See <xref linkend="v4l2-tuner-type" /></entry>
<entry><structfield>capability</structfield></entry>
<entry spanname="hspan">The tuner/modulator capability flags for
this frequency band, see <xref linkend="tuner-capability" />. The <constant>V4L2_TUNER_CAP_LOW</constant>
capability must be the same for all frequency bands of the selected tuner/modulator.
or <constant>V4L2_TUNER_CAP_1HZ</constant> capability must be the same for all frequency bands of the selected tuner/modulator.
So either all bands have that capability set, or none of them have that capability.</entry>
</row>
<row>
......@@ -109,7 +109,8 @@ So either all bands have that capability set, or none of them have that capabili
<entry spanname="hspan">The lowest tunable frequency in
units of 62.5 kHz, or if the <structfield>capability</structfield>
flag <constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz, for this frequency band.</entry>
Hz, for this frequency band. A 1 Hz unit is used when the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -117,7 +118,8 @@ Hz, for this frequency band.</entry>
<entry spanname="hspan">The highest tunable frequency in
units of 62.5 kHz, or if the <structfield>capability</structfield>
flag <constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz, for this frequency band.</entry>
Hz, for this frequency band. A 1 Hz unit is used when the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set.</entry>
</row>
<row>
<entry>__u32</entry>
......
Documentation/DocBook/media/v4l/vidioc-g-edid.xml 0 → 100644
浏览文件 @ af5666e0
<refentry id="vidioc-g-edid">
<refmeta>
<refentrytitle>ioctl VIDIOC_G_EDID, VIDIOC_S_EDID</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_G_EDID</refname>
<refname>VIDIOC_S_EDID</refname>
<refpurpose>Get or set the EDID of a video receiver/transmitter</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 v4l2_edid *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>const struct v4l2_edid *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_G_EDID, VIDIOC_S_EDID</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>These ioctls can be used to get or set an EDID associated with an input
from a receiver or an output of a transmitter device. They can be
used with subdevice nodes (/dev/v4l-subdevX) or with video nodes (/dev/videoX).</para>
<para>When used with video nodes the <structfield>pad</structfield> field represents the
input (for video capture devices) or output (for video output devices) index as
is returned by &VIDIOC-ENUMINPUT; and &VIDIOC-ENUMOUTPUT; respectively. When used
with subdevice nodes the <structfield>pad</structfield> field represents the
input or output pad of the subdevice. If there is no EDID support for the given
<structfield>pad</structfield> value, then the &EINVAL; will be returned.</para>
<para>To get the EDID data the application has to fill in the <structfield>pad</structfield>,
<structfield>start_block</structfield>, <structfield>blocks</structfield> and <structfield>edid</structfield>
fields and call <constant>VIDIOC_G_EDID</constant>. The current EDID from block
<structfield>start_block</structfield> and of size <structfield>blocks</structfield>
will be placed in the memory <structfield>edid</structfield> points to. The <structfield>edid</structfield>
pointer must point to memory at least <structfield>blocks</structfield>&nbsp;*&nbsp;128 bytes
large (the size of one block is 128 bytes).</para>
<para>If there are fewer blocks than specified, then the driver will set <structfield>blocks</structfield>
to the actual number of blocks. If there are no EDID blocks available at all, then the error code
ENODATA is set.</para>
<para>If blocks have to be retrieved from the sink, then this call will block until they
have been read.</para>
<para>To set the EDID blocks of a receiver the application has to fill in the <structfield>pad</structfield>,
<structfield>blocks</structfield> and <structfield>edid</structfield> fields and set
<structfield>start_block</structfield> to 0. It is not possible to set part of an EDID,
it is always all or nothing. Setting the EDID data is only valid for receivers as it makes
no sense for a transmitter.</para>
<para>The driver assumes that the full EDID is passed in. If there are more EDID blocks than
the hardware can handle then the EDID is not written, but instead the error code E2BIG is set
and <structfield>blocks</structfield> is set to the maximum that the hardware supports.
If <structfield>start_block</structfield> is any
value other than 0 then the error code EINVAL is set.</para>
<para>To disable an EDID you set <structfield>blocks</structfield> to 0. Depending on the
hardware this will drive the hotplug pin low and/or block the source from reading the EDID
data in some way. In any case, the end result is the same: the EDID is no longer available.
</para>
<table pgwide="1" frame="none" id="v4l2-edid">
<title>struct <structname>v4l2_edid</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>pad</structfield></entry>
<entry>Pad for which to get/set the EDID blocks. When used with a video device
node the pad represents the input or output index as returned by
&VIDIOC-ENUMINPUT; and &VIDIOC-ENUMOUTPUT; respectively.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>start_block</structfield></entry>
<entry>Read the EDID from starting with this block. Must be 0 when setting
the EDID.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>blocks</structfield></entry>
<entry>The number of blocks to get or set. Must be less or equal to 256 (the
maximum number of blocks as defined by the standard). When you set the EDID and
<structfield>blocks</structfield> is 0, then the EDID is disabled or erased.</entry>
</row>
<row>
<entry>__u8&nbsp;*</entry>
<entry><structfield>edid</structfield></entry>
<entry>Pointer to memory that contains the EDID. The minimum size is
<structfield>blocks</structfield>&nbsp;*&nbsp;128.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[5]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>ENODATA</errorcode></term>
<listitem>
<para>The EDID data is not available.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>E2BIG</errorcode></term>
<listitem>
<para>The EDID data you provided is more than the hardware can handle.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml
浏览文件 @ af5666e0
......@@ -327,7 +327,12 @@ These controls are described in <xref
These controls are described in <xref
linkend="fm-rx-controls" />.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_CLASS_RF_TUNER</constant></entry>
<entry>0xa20000</entry>
<entry>The class containing RF tuner controls.
These controls are described in <xref linkend="rf-tuner-controls" />.</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/vidioc-g-fmt.xml
浏览文件 @ af5666e0
......@@ -169,6 +169,13 @@ capture and output devices.</entry>
<entry>Sliced VBI capture or output parameters. See
<xref linkend="sliced" /> for details. Used by sliced VBI
capture and output devices.</entry>
</row>
<row>
<entry></entry>
<entry>&v4l2-sdr-format;</entry>
<entry><structfield>sdr</structfield></entry>
<entry>Definition of a data format, see
<xref linkend="pixfmt" />, used by SDR capture devices.</entry>
</row>
<row>
<entry></entry>
......
Documentation/DocBook/media/v4l/vidioc-g-frequency.xml
浏览文件 @ af5666e0
......@@ -109,9 +109,10 @@ See <xref linkend="v4l2-tuner-type" /></entry>
<entry>__u32</entry>
<entry><structfield>frequency</structfield></entry>
<entry>Tuning frequency in units of 62.5 kHz, or if the
&v4l2-tuner; or &v4l2-modulator; <structfield>capabilities</structfield> flag
&v4l2-tuner; or &v4l2-modulator; <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz.</entry>
Hz. A 1 Hz unit is used when the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set.</entry>
</row>
<row>
<entry>__u32</entry>
......
Documentation/DocBook/media/v4l/vidioc-g-modulator.xml
浏览文件 @ af5666e0
......@@ -113,7 +113,8 @@ change for example with the current video standard.</entry>
<entry>The lowest tunable frequency in units of 62.5
KHz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz.</entry>
Hz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set, in units of 1 Hz.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -121,7 +122,8 @@ Hz.</entry>
<entry>The highest tunable frequency in units of 62.5
KHz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz.</entry>
Hz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set, in units of 1 Hz.</entry>
</row>
<row>
<entry>__u32</entry>
......
Documentation/DocBook/media/v4l/vidioc-g-tuner.xml
浏览文件 @ af5666e0
......@@ -134,7 +134,9 @@ the structure refers to a radio tuner the
<entry spanname="hspan">The lowest tunable frequency in
units of 62.5 kHz, or if the <structfield>capability</structfield>
flag <constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz. If multiple frequency bands are supported, then
Hz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set, in units of 1 Hz.
If multiple frequency bands are supported, then
<structfield>rangelow</structfield> is the lowest frequency
of all the frequency bands.</entry>
</row>
......@@ -144,7 +146,9 @@ of all the frequency bands.</entry>
<entry spanname="hspan">The highest tunable frequency in
units of 62.5 kHz, or if the <structfield>capability</structfield>
flag <constant>V4L2_TUNER_CAP_LOW</constant> is set, in units of 62.5
Hz. If multiple frequency bands are supported, then
Hz, or if the <structfield>capability</structfield> flag
<constant>V4L2_TUNER_CAP_1HZ</constant> is set, in units of 1 Hz.
If multiple frequency bands are supported, then
<structfield>rangehigh</structfield> is the highest frequency
of all the frequency bands.</entry>
</row>
......@@ -270,7 +274,7 @@ applications must set the array to zero.</entry>
<entry><constant>V4L2_TUNER_CAP_LOW</constant></entry>
<entry>0x0001</entry>
<entry>When set, tuning frequencies are expressed in units of
62.5&nbsp;Hz, otherwise in units of 62.5&nbsp;kHz.</entry>
62.5 Hz instead of 62.5 kHz.</entry>
</row>
<row>
<entry><constant>V4L2_TUNER_CAP_NORM</constant></entry>
......@@ -360,6 +364,11 @@ radio tuners.</entry>
<entry>The range to search when using the hardware seek functionality
is programmable, see &VIDIOC-S-HW-FREQ-SEEK; for details.</entry>
</row>
<row>
<entry><constant>V4L2_TUNER_CAP_1HZ</constant></entry>
<entry>0x1000</entry>
<entry>When set, tuning frequencies are expressed in units of 1 Hz instead of 62.5 kHz.</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/vidioc-querycap.xml
浏览文件 @ af5666e0
......@@ -294,6 +294,12 @@ interface. For more information on audio inputs and outputs see <xref
emit RF-modulated video/audio signals. For more information about
modulator programming see
<xref linkend="tuner" />.</entry>
</row>
<row>
<entry><constant>V4L2_CAP_SDR_CAPTURE</constant></entry>
<entry>0x00100000</entry>
<entry>The device supports the
<link linkend="sdr">SDR Capture</link> interface.</entry>
</row>
<row>
<entry><constant>V4L2_CAP_READWRITE</constant></entry>
......
Documentation/DocBook/media/v4l/vidioc-s-hw-freq-seek.xml
浏览文件 @ af5666e0
......@@ -121,7 +121,9 @@ field and the &v4l2-tuner; <structfield>index</structfield> field.</entry>
<entry>If non-zero, the lowest tunable frequency of the band to
search in units of 62.5 kHz, or if the &v4l2-tuner;
<structfield>capability</structfield> field has the
<constant>V4L2_TUNER_CAP_LOW</constant> flag set, in units of 62.5 Hz.
<constant>V4L2_TUNER_CAP_LOW</constant> flag set, in units of 62.5 Hz or if the &v4l2-tuner;
<structfield>capability</structfield> field has the
<constant>V4L2_TUNER_CAP_1HZ</constant> flag set, in units of 1 Hz.
If <structfield>rangelow</structfield> is zero a reasonable default value
is used.</entry>
</row>
......@@ -131,7 +133,9 @@ is used.</entry>
<entry>If non-zero, the highest tunable frequency of the band to
search in units of 62.5 kHz, or if the &v4l2-tuner;
<structfield>capability</structfield> field has the
<constant>V4L2_TUNER_CAP_LOW</constant> flag set, in units of 62.5 Hz.
<constant>V4L2_TUNER_CAP_LOW</constant> flag set, in units of 62.5 Hz or if the &v4l2-tuner;
<structfield>capability</structfield> field has the
<constant>V4L2_TUNER_CAP_1HZ</constant> flag set, in units of 1 Hz.
If <structfield>rangehigh</structfield> is zero a reasonable default value
is used.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-streamon.xml
浏览文件 @ af5666e0
......@@ -52,16 +52,24 @@
<para>The <constant>VIDIOC_STREAMON</constant> and
<constant>VIDIOC_STREAMOFF</constant> ioctl start and stop the capture
or output process during streaming (<link linkend="mmap">memory
mapping</link> or <link linkend="userp">user pointer</link>) I/O.</para>
mapping</link>, <link linkend="userp">user pointer</link> or
<link linkend="dmabuf">DMABUF</link>) I/O.</para>
<para>Specifically the capture hardware is disabled and no input
<para>Capture hardware is disabled and no input
buffers are filled (if there are any empty buffers in the incoming
queue) until <constant>VIDIOC_STREAMON</constant> has been called.
Accordingly the output hardware is disabled, no video signal is
Output hardware is disabled and no video signal is
produced until <constant>VIDIOC_STREAMON</constant> has been called.
The ioctl will succeed when at least one output buffer is in the
incoming queue.</para>
<para>Memory-to-memory devices will not start until
<constant>VIDIOC_STREAMON</constant> has been called for both the capture
and output stream types.</para>
<para>If <constant>VIDIOC_STREAMON</constant> fails then any already
queued buffers will remain queued.</para>
<para>The <constant>VIDIOC_STREAMOFF</constant> ioctl, apart of
aborting or finishing any DMA in progress, unlocks any user pointer
buffers locked in physical memory, and it removes all buffers from the
......@@ -70,14 +78,22 @@ dequeued yet will be lost, likewise all images enqueued for output but
not transmitted yet. I/O returns to the same state as after calling
&VIDIOC-REQBUFS; and can be restarted accordingly.</para>
<para>If buffers have been queued with &VIDIOC-QBUF; and
<constant>VIDIOC_STREAMOFF</constant> is called without ever having
called <constant>VIDIOC_STREAMON</constant>, then those queued buffers
will also be removed from the incoming queue and all are returned to the
same state as after calling &VIDIOC-REQBUFS; and can be restarted
accordingly.</para>
<para>Both ioctls take a pointer to an integer, the desired buffer or
stream type. This is the same as &v4l2-requestbuffers;
<structfield>type</structfield>.</para>
<para>If <constant>VIDIOC_STREAMON</constant> is called when streaming
is already in progress, or if <constant>VIDIOC_STREAMOFF</constant> is called
when streaming is already stopped, then the ioctl does nothing and 0 is
returned.</para>
when streaming is already stopped, then 0 is returned. Nothing happens in the
case of <constant>VIDIOC_STREAMON</constant>, but <constant>VIDIOC_STREAMOFF</constant>
will return queued buffers to their starting state as mentioned above.</para>
<para>Note that applications can be preempted for unknown periods right
before or after the <constant>VIDIOC_STREAMON</constant> or
......@@ -93,7 +109,7 @@ synchronize with other events.</para>
<varlistentry>
<term><errorcode>EINVAL</errorcode></term>
<listitem>
<para>The buffer<structfield>type</structfield> is not supported,
<para>The buffer <structfield>type</structfield> is not supported,
or no buffers have been allocated (memory mapping) or enqueued
(output) yet.</para>
</listitem>
......
Documentation/DocBook/media/v4l/vidioc-subdev-g-edid.xml 已删除 100644 → 0
浏览文件 @ 1b15d2e5
<refentry id="vidioc-subdev-g-edid">
<refmeta>
<refentrytitle>ioctl VIDIOC_SUBDEV_G_EDID, VIDIOC_SUBDEV_S_EDID</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_SUBDEV_G_EDID</refname>
<refname>VIDIOC_SUBDEV_S_EDID</refname>
<refpurpose>Get or set the EDID of a video receiver/transmitter</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 v4l2_subdev_edid *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>const struct v4l2_subdev_edid *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_SUBDEV_G_EDID, VIDIOC_SUBDEV_S_EDID</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>These ioctls can be used to get or set an EDID associated with an input pad
from a receiver or an output pad of a transmitter subdevice.</para>
<para>To get the EDID data the application has to fill in the <structfield>pad</structfield>,
<structfield>start_block</structfield>, <structfield>blocks</structfield> and <structfield>edid</structfield>
fields and call <constant>VIDIOC_SUBDEV_G_EDID</constant>. The current EDID from block
<structfield>start_block</structfield> and of size <structfield>blocks</structfield>
will be placed in the memory <structfield>edid</structfield> points to. The <structfield>edid</structfield>
pointer must point to memory at least <structfield>blocks</structfield>&nbsp;*&nbsp;128 bytes
large (the size of one block is 128 bytes).</para>
<para>If there are fewer blocks than specified, then the driver will set <structfield>blocks</structfield>
to the actual number of blocks. If there are no EDID blocks available at all, then the error code
ENODATA is set.</para>
<para>If blocks have to be retrieved from the sink, then this call will block until they
have been read.</para>
<para>To set the EDID blocks of a receiver the application has to fill in the <structfield>pad</structfield>,
<structfield>blocks</structfield> and <structfield>edid</structfield> fields and set
<structfield>start_block</structfield> to 0. It is not possible to set part of an EDID,
it is always all or nothing. Setting the EDID data is only valid for receivers as it makes
no sense for a transmitter.</para>
<para>The driver assumes that the full EDID is passed in. If there are more EDID blocks than
the hardware can handle then the EDID is not written, but instead the error code E2BIG is set
and <structfield>blocks</structfield> is set to the maximum that the hardware supports.
If <structfield>start_block</structfield> is any
value other than 0 then the error code EINVAL is set.</para>
<para>To disable an EDID you set <structfield>blocks</structfield> to 0. Depending on the
hardware this will drive the hotplug pin low and/or block the source from reading the EDID
data in some way. In any case, the end result is the same: the EDID is no longer available.
</para>
<table pgwide="1" frame="none" id="v4l2-subdev-edid">
<title>struct <structname>v4l2_subdev_edid</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>pad</structfield></entry>
<entry>Pad for which to get/set the EDID blocks.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>start_block</structfield></entry>
<entry>Read the EDID from starting with this block. Must be 0 when setting
the EDID.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>blocks</structfield></entry>
<entry>The number of blocks to get or set. Must be less or equal to 256 (the
maximum number of blocks as defined by the standard). When you set the EDID and
<structfield>blocks</structfield> is 0, then the EDID is disabled or erased.</entry>
</row>
<row>
<entry>__u8&nbsp;*</entry>
<entry><structfield>edid</structfield></entry>
<entry>Pointer to memory that contains the EDID. The minimum size is
<structfield>blocks</structfield>&nbsp;*&nbsp;128.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[5]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>ENODATA</errorcode></term>
<listitem>
<para>The EDID data is not available.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>E2BIG</errorcode></term>
<listitem>
<para>The EDID data you provided is more than the hardware can handle.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
Documentation/DocBook/media_api.tmpl
浏览文件 @ af5666e0
......@@ -34,22 +34,20 @@
<book id="media_api">
<bookinfo>
<title>LINUX MEDIA INFRASTRUCTURE API</title>
<copyright>
<year>2009-2012</year>
<holder>LinuxTV Developers</holder>
</copyright>
<legalnotice>
<para>Permission is granted to copy, distribute and/or modify
this document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
Foundation. A copy of the license is included in the chapter entitled
"GNU Free Documentation License"</para>
</legalnotice>
<title>LINUX MEDIA INFRASTRUCTURE API</title>
<copyright>
<year>2009-2014</year>
<holder>LinuxTV Developers</holder>
</copyright>
<legalnotice>
<para>Permission is granted to copy, distribute and/or modify
this document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
Foundation. A copy of the license is included in the chapter entitled
"GNU Free Documentation License"</para>
</legalnotice>
</bookinfo>
<toc></toc> <!-- autogenerated -->
......@@ -60,10 +58,11 @@ Foundation. A copy of the license is included in the chapter entitled
<para>This document covers the Linux Kernel to Userspace API's used by
video and radio streaming devices, including video cameras,
analog and digital TV receiver cards, AM/FM receiver cards,
streaming capture devices.</para>
streaming capture and output devices, codec devices and remote
controllers.</para>
<para>It is divided into four parts.</para>
<para>The first part covers radio, capture,
cameras and analog TV devices.</para>
<para>The first part covers radio, video capture and output,
cameras, analog TV devices and codecs.</para>
<para>The second part covers the
API used for digital TV and Internet reception via one of the
several digital tv standards. While it is called as DVB API,
......@@ -75,55 +74,14 @@ Foundation. A copy of the license is included in the chapter entitled
<para>For additional information and for the latest development code,
see: <ulink url="http://linuxtv.org">http://linuxtv.org</ulink>.</para>
<para>For discussing improvements, reporting troubles, sending new drivers, etc, please mail to: <ulink url="http://vger.kernel.org/vger-lists.html#linux-media">Linux Media Mailing List (LMML).</ulink>.</para>
</preface>
<part id="v4l2spec">
&sub-v4l2;
</part>
<part id="dvbapi">
&sub-dvbapi;
</part>
<part id="v4ldvb_common">
<partinfo>
<authorgroup>
<author>
<firstname>Mauro</firstname>
<surname>Chehab</surname>
<othername role="mi">Carvalho</othername>
<affiliation><address><email>mchehab@redhat.com</email></address></affiliation>
<contrib>Initial version.</contrib>
</author>
</authorgroup>
<copyright>
<year>2009-2012</year>
<holder>Mauro Carvalho Chehab</holder>
</copyright>
<revhistory>
<!-- Put document revisions here, newest first. -->
<revision>
<revnumber>1.0.0</revnumber>
<date>2009-09-06</date>
<authorinitials>mcc</authorinitials>
<revremark>Initial revision</revremark>
</revision>
</revhistory>
</partinfo>
<title>Remote Controller API</title>
<chapter id="remote_controllers">
&sub-remote_controllers;
</chapter>
</part>
<part id="media_common">
&sub-media-controller;
</part>
<chapter id="gen_errors">
&sub-gen-errors;
</chapter>
<part id="v4l2spec">&sub-v4l2;</part>
<part id="dvbapi">&sub-dvbapi;</part>
<part id="remotes">&sub-remote_controllers;</part>
<part id="media_common">&sub-media-controller;</part>
<chapter id="gen_errors">&sub-gen-errors;</chapter>
&sub-fdl-appendix;
......
Documentation/SubmittingPatches
浏览文件 @ af5666e0
......@@ -14,7 +14,10 @@ Read Documentation/SubmitChecklist for a list of items to check
before submitting code. If you are submitting a driver, also read
Documentation/SubmittingDrivers.
Many of these steps describe the default behavior of the git version
control system; if you use git to prepare your patches, you'll find much
of the mechanical work done for you, though you'll still need to prepare
and document a sensible set of patches.
--------------------------------------------
SECTION 1 - CREATING AND SENDING YOUR CHANGE
......@@ -25,7 +28,9 @@ SECTION 1 - CREATING AND SENDING YOUR CHANGE
1) "diff -up"
------------
Use "diff -up" or "diff -uprN" to create patches.
Use "diff -up" or "diff -uprN" to create patches. git generates patches
in this form by default; if you're using git, you can skip this section
entirely.
All changes to the Linux kernel occur in the form of patches, as
generated by diff(1). When creating your patch, make sure to create it
......@@ -66,19 +71,14 @@ Make sure your patch does not include any extra files which do not
belong in a patch submission. Make sure to review your patch -after-
generated it with diff(1), to ensure accuracy.
If your changes produce a lot of deltas, you may want to look into
splitting them into individual patches which modify things in
logical stages. This will facilitate easier reviewing by other
kernel developers, very important if you want your patch accepted.
There are a number of scripts which can aid in this:
Quilt:
http://savannah.nongnu.org/projects/quilt
If your changes produce a lot of deltas, you need to split them into
individual patches which modify things in logical stages; see section
#3. This will facilitate easier reviewing by other kernel developers,
very important if you want your patch accepted.
Andrew Morton's patch scripts:
http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
Instead of these scripts, quilt is the recommended patch management
tool (see above).
If you're using git, "git rebase -i" can help you with this process. If
you're not using git, quilt <http://savannah.nongnu.org/projects/quilt>
is another popular alternative.
......@@ -106,8 +106,21 @@ I.e., the patch (series) and its description should be self-contained.
This benefits both the patch merger(s) and reviewers. Some reviewers
probably didn't even receive earlier versions of the patch.
Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
to do frotz", as if you are giving orders to the codebase to change
its behaviour.
If the patch fixes a logged bug entry, refer to that bug entry by
number and URL.
number and URL. If the patch follows from a mailing list discussion,
give a URL to the mailing list archive; use the https://lkml.kernel.org/
redirector with a Message-Id, to ensure that the links cannot become
stale.
However, try to make your explanation understandable without external
resources. In addition to giving a URL to a mailing list archive or
bug, summarize the relevant points of the discussion that led to the
patch as submitted.
If you want to refer to a specific commit, don't just refer to the
SHA-1 ID of the commit. Please also include the oneline summary of
......@@ -594,7 +607,8 @@ patch.
If you are going to include a diffstat after the "---" marker, please
use diffstat options "-p 1 -w 70" so that filenames are listed from
the top of the kernel source tree and don't use too much horizontal
space (easily fit in 80 columns, maybe with some indentation).
space (easily fit in 80 columns, maybe with some indentation). (git
generates appropriate diffstats by default.)
See more details on the proper patch format in the following
references.
......@@ -725,7 +739,7 @@ SECTION 3 - REFERENCES
----------------------
Andrew Morton, "The perfect patch" (tpp).
<http://userweb.kernel.org/~akpm/stuff/tpp.txt>
<http://www.ozlabs.org/~akpm/stuff/tpp.txt>
Jeff Garzik, "Linux kernel patch submission format".
<http://linux.yyz.us/patch-format.html>
......@@ -738,7 +752,7 @@ Greg Kroah-Hartman, "How to piss off a kernel subsystem maintainer".
<http://www.kroah.com/log/linux/maintainer-05.html>
NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
<http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
<https://lkml.org/lkml/2005/7/11/336>
Kernel Documentation/CodingStyle:
<http://users.sosdg.org/~qiyong/lxr/source/Documentation/CodingStyle>
......
Documentation/arm/Marvell/README
浏览文件 @ af5666e0
......@@ -83,14 +83,24 @@ EBU Armada family
88F6710
88F6707
88F6W11
Product Brief: http://www.marvell.com/embedded-processors/armada-300/assets/Marvell_ARMADA_370_SoC.pdf
Armada 375 Flavors:
88F6720
Product Brief: http://www.marvell.com/embedded-processors/armada-300/assets/ARMADA_375_SoC-01_product_brief.pdf
Armada 380/385 Flavors:
88F6810
88F6820
88F6828
Armada XP Flavors:
MV78230
MV78260
MV78460
NOTE: not to be confused with the non-SMP 78xx0 SoCs
Product Brief: http://www.marvell.com/embedded-processors/armada-xp/assets/Marvell-ArmadaXP-SoC-product%20brief.pdf
Product Brief: http://www.marvell.com/embedded-processors/armada-xp/assets/Marvell-ArmadaXP-SoC-product%20brief.pdf
No public datasheet available.
Core: Sheeva ARMv7 compatible
......
Documentation/arm64/booting.txt
浏览文件 @ af5666e0
......@@ -111,8 +111,14 @@ Before jumping into the kernel, the following conditions must be met:
- Caches, MMUs
The MMU must be off.
Instruction cache may be on or off.
Data cache must be off and invalidated.
External caches (if present) must be configured and disabled.
The address range corresponding to the loaded kernel image must be
cleaned to the PoC. In the presence of a system cache or other
coherent masters with caches enabled, this will typically require
cache maintenance by VA rather than set/way operations.
System caches which respect the architected cache maintenance by VA
operations must be configured and may be enabled.
System caches which do not respect architected cache maintenance by VA
operations (not recommended) must be configured and disabled.
- Architected timers
CNTFRQ must be programmed with the timer frequency and CNTVOFF must
......
Documentation/arm64/memory.txt
浏览文件 @ af5666e0
......@@ -39,7 +39,7 @@ ffffffbffa000000 ffffffbffaffffff 16MB PCI I/O space
ffffffbffb000000 ffffffbffbbfffff 12MB [guard]
ffffffbffbc00000 ffffffbffbdfffff 2MB earlyprintk device
ffffffbffbc00000 ffffffbffbdfffff 2MB fixed mappings
ffffffbffbe00000 ffffffbffbffffff 2MB [guard]
......@@ -66,7 +66,7 @@ fffffdfffa000000 fffffdfffaffffff 16MB PCI I/O space
fffffdfffb000000 fffffdfffbbfffff 12MB [guard]
fffffdfffbc00000 fffffdfffbdfffff 2MB earlyprintk device
fffffdfffbc00000 fffffdfffbdfffff 2MB fixed mappings
fffffdfffbe00000 fffffdfffbffffff 2MB [guard]
......
Documentation/blockdev/zram.txt
浏览文件 @ af5666e0
......@@ -21,7 +21,43 @@ Following shows a typical sequence of steps for using zram.
This creates 4 devices: /dev/zram{0,1,2,3}
(num_devices parameter is optional. Default: 1)
2) Set Disksize
2) Set max number of compression streams
Compression backend may use up to max_comp_streams compression streams,
thus allowing up to max_comp_streams concurrent compression operations.
By default, compression backend uses single compression stream.
Examples:
#show max compression streams number
cat /sys/block/zram0/max_comp_streams
#set max compression streams number to 3
echo 3 > /sys/block/zram0/max_comp_streams
Note:
In order to enable compression backend's multi stream support max_comp_streams
must be initially set to desired concurrency level before ZRAM device
initialisation. Once the device initialised as a single stream compression
backend (max_comp_streams equals to 1), you will see error if you try to change
the value of max_comp_streams because single stream compression backend
implemented as a special case by lock overhead issue and does not support
dynamic max_comp_streams. Only multi stream backend supports dynamic
max_comp_streams adjustment.
3) Select compression algorithm
Using comp_algorithm device attribute one can see available and
currently selected (shown in square brackets) compression algortithms,
change selected compression algorithm (once the device is initialised
there is no way to change compression algorithm).
Examples:
#show supported compression algorithms
cat /sys/block/zram0/comp_algorithm
lzo [lz4]
#select lzo compression algorithm
echo lzo > /sys/block/zram0/comp_algorithm
4) Set Disksize
Set disk size by writing the value to sysfs node 'disksize'.
The value can be either in bytes or you can use mem suffixes.
Examples:
......@@ -33,32 +69,38 @@ Following shows a typical sequence of steps for using zram.
echo 512M > /sys/block/zram0/disksize
echo 1G > /sys/block/zram0/disksize
3) Activate:
Note:
There is little point creating a zram of greater than twice the size of memory
since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the
size of the disk when not in use so a huge zram is wasteful.
5) Activate:
mkswap /dev/zram0
swapon /dev/zram0
mkfs.ext4 /dev/zram1
mount /dev/zram1 /tmp
4) Stats:
6) Stats:
Per-device statistics are exported as various nodes under
/sys/block/zram<id>/
disksize
num_reads
num_writes
failed_reads
failed_writes
invalid_io
notify_free
discard
zero_pages
orig_data_size
compr_data_size
mem_used_total
5) Deactivate:
7) Deactivate:
swapoff /dev/zram0
umount /dev/zram1
6) Reset:
8) Reset:
Write any positive value to 'reset' sysfs node
echo 1 > /sys/block/zram0/reset
echo 1 > /sys/block/zram1/reset
......
Documentation/cgroups/memcg_test.txt
浏览文件 @ af5666e0
......@@ -24,7 +24,7 @@ Please note that implementation details can be changed.
a page/swp_entry may be charged (usage += PAGE_SIZE) at
mem_cgroup_newpage_charge()
mem_cgroup_charge_anon()
Called at new page fault and Copy-On-Write.
mem_cgroup_try_charge_swapin()
......@@ -32,7 +32,7 @@ Please note that implementation details can be changed.
Followed by charge-commit-cancel protocol. (With swap accounting)
At commit, a charge recorded in swap_cgroup is removed.
mem_cgroup_cache_charge()
mem_cgroup_charge_file()
Called at add_to_page_cache()
mem_cgroup_cache_charge_swapin()
......
Documentation/cgroups/resource_counter.txt
浏览文件 @ af5666e0
......@@ -76,15 +76,7 @@ to work with it.
limit_fail_at parameter is set to the particular res_counter element
where the charging failed.
d. int res_counter_charge_locked
(struct res_counter *rc, unsigned long val, bool force)
The same as res_counter_charge(), but it must not acquire/release the
res_counter->lock internally (it must be called with res_counter->lock
held). The force parameter indicates whether we can bypass the limit.
e. u64 res_counter_uncharge[_locked]
(struct res_counter *rc, unsigned long val)
d. u64 res_counter_uncharge(struct res_counter *rc, unsigned long val)
When a resource is released (freed) it should be de-accounted
from the resource counter it was accounted to. This is called
......@@ -93,7 +85,7 @@ to work with it.
The _locked routines imply that the res_counter->lock is taken.
f. u64 res_counter_uncharge_until
e. u64 res_counter_uncharge_until
(struct res_counter *rc, struct res_counter *top,
unsigned long val)
......
Documentation/clk.txt
浏览文件 @ af5666e0
......@@ -255,3 +255,37 @@ are sorted out.
To bypass this disabling, include "clk_ignore_unused" in the bootargs to the
kernel.
Part 7 - Locking
The common clock framework uses two global locks, the prepare lock and the
enable lock.
The enable lock is a spinlock and is held across calls to the .enable,
.disable and .is_enabled operations. Those operations are thus not allowed to
sleep, and calls to the clk_enable(), clk_disable() and clk_is_enabled() API
functions are allowed in atomic context.
The prepare lock is a mutex and is held across calls to all other operations.
All those operations are allowed to sleep, and calls to the corresponding API
functions are not allowed in atomic context.
This effectively divides operations in two groups from a locking perspective.
Drivers don't need to manually protect resources shared between the operations
of one group, regardless of whether those resources are shared by multiple
clocks or not. However, access to resources that are shared between operations
of the two groups needs to be protected by the drivers. An example of such a
resource would be a register that controls both the clock rate and the clock
enable/disable state.
The clock framework is reentrant, in that a driver is allowed to call clock
framework functions from within its implementation of clock operations. This
can for instance cause a .set_rate operation of one clock being called from
within the .set_rate operation of another clock. This case must be considered
in the driver implementations, but the code flow is usually controlled by the
driver in that case.
Note that locking must also be considered when code outside of the common
clock framework needs to access resources used by the clock operations. This
is considered out of scope of this document.
Documentation/cpu-hotplug.txt
浏览文件 @ af5666e0
......@@ -312,12 +312,57 @@ things will happen if a notifier in path sent a BAD notify code.
Q: I don't see my action being called for all CPUs already up and running?
A: Yes, CPU notifiers are called only when new CPUs are on-lined or offlined.
If you need to perform some action for each cpu already in the system, then
do this:
for_each_online_cpu(i) {
foobar_cpu_callback(&foobar_cpu_notifier, CPU_UP_PREPARE, i);
foobar_cpu_callback(&foobar_cpu_notifier, CPU_ONLINE, i);
}
However, if you want to register a hotplug callback, as well as perform
some initialization for CPUs that are already online, then do this:
Version 1: (Correct)
---------
cpu_notifier_register_begin();
for_each_online_cpu(i) {
foobar_cpu_callback(&foobar_cpu_notifier,
CPU_UP_PREPARE, i);
foobar_cpu_callback(&foobar_cpu_notifier,
CPU_ONLINE, i);
}
/* Note the use of the double underscored version of the API */
__register_cpu_notifier(&foobar_cpu_notifier);
cpu_notifier_register_done();
Note that the following code is *NOT* the right way to achieve this,
because it is prone to an ABBA deadlock between the cpu_add_remove_lock
and the cpu_hotplug.lock.
Version 2: (Wrong!)
---------
get_online_cpus();
for_each_online_cpu(i) {
foobar_cpu_callback(&foobar_cpu_notifier,
CPU_UP_PREPARE, i);
foobar_cpu_callback(&foobar_cpu_notifier,
CPU_ONLINE, i);
}
register_cpu_notifier(&foobar_cpu_notifier);
put_online_cpus();
So always use the first version shown above when you want to register
callbacks as well as initialize the already online CPUs.
Q: If i would like to develop cpu hotplug support for a new architecture,
what do i need at a minimum?
A: The following are what is required for CPU hotplug infrastructure to work
......
Documentation/device-mapper/era.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devices.txt
浏览文件 @ af5666e0
......@@ -353,6 +353,7 @@ Your cooperation is appreciated.
133 = /dev/exttrp External device trap
134 = /dev/apm_bios Advanced Power Management BIOS
135 = /dev/rtc Real Time Clock
137 = /dev/vhci Bluetooth virtual HCI driver
139 = /dev/openprom SPARC OpenBoot PROM
140 = /dev/relay8 Berkshire Products Octal relay card
141 = /dev/relay16 Berkshire Products ISO-16 relay card
......@@ -1493,10 +1494,17 @@ Your cooperation is appreciated.
64 = /dev/radio0 Radio device
...
127 = /dev/radio63 Radio device
128 = /dev/swradio0 Software Defined Radio device
...
191 = /dev/swradio63 Software Defined Radio device
224 = /dev/vbi0 Vertical blank interrupt
...
255 = /dev/vbi31 Vertical blank interrupt
Minor numbers are allocated dynamically unless
CONFIG_VIDEO_FIXED_MINOR_RANGES (default n)
configuration option is set.
81 block I2O hard disk
0 = /dev/i2o/hdq 17th I2O hard disk, whole disk
16 = /dev/i2o/hdr 18th I2O hard disk, whole disk
......
Documentation/devicetree/bindings/arm/armada-375.txt 0 → 100644
浏览文件 @ af5666e0
Marvell Armada 375 Platforms Device Tree Bindings
-------------------------------------------------
Boards with a SoC of the Marvell Armada 375 family shall have the
following property:
Required root node property:
compatible: must contain "marvell,armada375"
Documentation/devicetree/bindings/arm/armada-38x.txt 0 → 100644
浏览文件 @ af5666e0
Marvell Armada 38x Platforms Device Tree Bindings
-------------------------------------------------
Boards with a SoC of the Marvell Armada 38x family shall have the
following property:
Required root node property:
- compatible: must contain either "marvell,armada380" or
"marvell,armada385" depending on the variant of the SoC being used.
Documentation/devicetree/bindings/arm/bcm/bcm21664.txt 0 → 100644
浏览文件 @ af5666e0
Broadcom BCM21664 device tree bindings
--------------------------------------
This document describes the device tree bindings for boards with the BCM21664
SoC.
Required root node property:
- compatible: brcm,bcm21664
Example:
/ {
model = "BCM21664 SoC";
compatible = "brcm,bcm21664";
[...]
}
Documentation/devicetree/bindings/arm/bcm/kona-resetmgr.txt 0 → 100644
浏览文件 @ af5666e0
Broadcom Kona Family Reset Manager
----------------------------------
The reset manager is used on the Broadcom BCM21664 SoC.
Required properties:
- compatible: brcm,bcm21664-resetmgr
- reg: memory address & range
Example:
brcm,resetmgr@35001f00 {
compatible = "brcm,bcm21664-resetmgr";
reg = <0x35001f00 0x24>;
};
Documentation/devicetree/bindings/arm/bcm4708.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/mrvl/feroceon.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/msm/qcom,saw2.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/omap/crossbar.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/omap/dmm.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/rockchip/pmu.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/arm/samsung/pmu.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/dma/fsl-edma.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/dma/qcom_bam_dma.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/dma/sirfsoc-dma.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/drm/i2c/tda998x.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/gpio/gpio-zevio.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-cadence.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-efm32.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/i2c/qcom,i2c-qup.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/iio/adc/at91_adc.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/media/img-ir-rev1.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/mfd/bcm590xx.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/mfd/da9055.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/mfd/qcom,pm8xxx.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/mmc/sdhci-msm.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/mtd/st-fsm.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/altera_tse.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/ethernet.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/micrel.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/nfc/trf7970a.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/samsung-sxgbe.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/sh_eth.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/net/socfpga-dwmac.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/panel/lg,lp129qe.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/reset/sirf,rstc.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/video/exynos_dsim.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/video/ti,omap-dss.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/devicetree/bindings/video/ti,tfp410.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/dontdiff
浏览文件 @ af5666e0
此差异已折叠。
Documentation/dvb/get_dvb_firmware
浏览文件 @ af5666e0
此差异已折叠。
Documentation/dvb/it9137.txt 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
Documentation/edac.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/affs.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/ntfs.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/gpio/consumer.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/gpio/driver.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/hwmon/it87
浏览文件 @ af5666e0
此差异已折叠。
Documentation/hwmon/k10temp
浏览文件 @ af5666e0
此差异已折叠。
Documentation/i2c/busses/i2c-i801
浏览文件 @ af5666e0
此差异已折叠。
Documentation/i2c/functionality
浏览文件 @ af5666e0
此差异已折叠。
Documentation/i2c/i2c-protocol
浏览文件 @ af5666e0
此差异已折叠。
Documentation/irqflags-tracing.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/kmemleak.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/module-signing.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/altera_tse.txt 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/can.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/filter.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/igb.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/phy.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/pktgen.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/rxrpc.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/networking/tcp.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/oops-tracing.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/ptp/testptp.c
浏览文件 @ af5666e0
此差异已折叠。
Documentation/rapidio/sysfs.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/video4linux/fimc.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/video4linux/gspca.txt
浏览文件 @ af5666e0
此差异已折叠。
Documentation/video4linux/v4l2-pci-skeleton.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
MAINTAINERS
浏览文件 @ af5666e0
此差异已折叠。
Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/boot/.gitignore
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/boot/dts/nsimosci.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/boot/dts/skeleton.dts 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arc/configs/nsimosci_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/include/asm/linkage.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/kernel/ctx_sw_asm.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/kernel/entry.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/kernel/head.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/kernel/time.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/memcmp.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/memcpy-700.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/memset.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/strchr-700.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/strcmp.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/strcpy-700.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/lib/strlen.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/mm/cache_arc700.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/mm/init.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/mm/tlbex.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/plat-arcfpga/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arc/plat-arcfpga/platform.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am335x-evmsk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am3517-craneboard.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-380.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-385-db.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-385-rd.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-385.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91-ariag25.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91-cosino.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9261ek.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9rlek.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/atlas6.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm11351-brt.dts 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/boot/dts/bcm11351.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm21664-garnet.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm21664.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm28155-ap.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm2835.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm4708-netgear-r6250.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm4708.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm5301x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/bcm59056.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/dove.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/efm32gg.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos4212.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos5.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx23-evk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx23.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx25-eukrea-cpuimx25.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx25-pinfunc.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx27-apf27.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx27-phytec-phycard-s-som.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx27-phytec-phycore-som.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx27-pinfunc.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-duckbill.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-eukrea-mbmx287lc.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-eukrea-mbmx28lc.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-evk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-m28cu3.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-m28evk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-sps1.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28-tx28.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx35-eukrea-mbimxsd35-baseboard.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx50-evk.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx50-pinfunc.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx50.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx51-apf51.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx51-babbage.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx51-eukrea-cpuimx51.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx51-eukrea-mbimxsd51-baseboard.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-ard.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-evk.dts 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/boot/dts/imx53-m53evk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-mba53.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-qsb-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-qsb.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-qsrb.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-smd.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-tqma53.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-tx53-x03x.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-tx53-x13x.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-tx53.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-voipac-bsb.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-dfi-fs700-m60.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw51xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw52xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw53xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw54xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-nitrogen6x.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-pinfunc.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl-sabrelite.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6dl.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-arm2.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-cm-fx6.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-dfi-fs700-m60.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gk802.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gw51xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gw52xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gw53xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gw5400-a.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-gw54xx.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-nitrogen6x.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-pinfunc.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-sbc6x.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q-udoo.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6q.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw51xx.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw52xx.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw53xx.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw54xx.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl-sabrelite.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6sl-evk.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/integratorap.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/integratorcp.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2e-clocks.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2e-evm.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2e.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2hk-clocks.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2hk-evm.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2hk.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2l-clocks.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2l-evm.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/k2l.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/keystone.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-b3.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds109.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds110jv10.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds111.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds112.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds209.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds210.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds212.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds212j.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds409.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds409slim.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds411.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds411j.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ds411slim.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6192.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-a0.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-a1.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rs212.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rs409.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-rs411.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-synology.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-t5325.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ts419-6281.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ts419-6282.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood-ts419.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/kirkwood.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/marco.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap-gpmc-smsc9221.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap2.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap2420.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap2430.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-beagle.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-cm-t3517.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-cm-t3530.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-cm-t3x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-igep.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-ldp.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-lilly-a83x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-lilly-dbb056.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-n900.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-alto35-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-alto35.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-base.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-chestnut43-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-chestnut43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-common-peripherals.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-gallop43-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-gallop43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-palo43-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-palo43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm-alto35.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm-chestnut43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm-gallop43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm-palo43.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm-summit.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-storm.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-summit-common.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo-summit.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-overo.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-sb-t35.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-sbc-t3517.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3-sbc-t3530.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap3430-sdp.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap36xx.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap4-duovero-parlor.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap4-duovero.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap4-sdp.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap443x.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap4460.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap5-uevm.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/prima2.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/qcom-msm8660.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/qcom-msm8960.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/r7s72100.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/rk3066a.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/rk3188.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/rk3xxx.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sama5d3.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sama5d3xdm.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/socfpga_vt.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/ste-dbx5x0.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/ste-href-ab8500.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/ste-href-ab8505.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/ste-snowball.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/ste-u300.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/stih415.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/stih416.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/stih41x-b2020x.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun4i-a10-inet97fv2.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun4i-a10-pcduino.dts 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun5i-a13.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun6i-a31.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/sunxi-common-regulators.dtsi 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tegra114.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tegra124.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tegra20-paz00.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tegra20.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tegra30.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/tps65910.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/twl4030.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/vf610-cosmic.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/vf610-twr.dts
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/vf610.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/boot/dts/zynq-7000.dtsi
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/common/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/common/scoop.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/common/timer-sp.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/ape6evm_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/at91_dt_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/bcm2835_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/bcm_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/bockw_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/clps711x_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/da8xx_omapl_defconfig 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/configs/dove_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/genmai_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/keystone_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/koelsch_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/kzm9d_defconfig 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/configs/kzm9g_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/lager_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/mackerel_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/marzen_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/multi_v5_defconfig 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/mvebu_defconfig 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/configs/mvebu_v5_defconfig 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/mvebu_v7_defconfig 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/shmobile_defconfig 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/socfpga_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/configs/tegra_defconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/firmware/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/assembler.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/atomic.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/cmpxchg.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/cputype.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/firmware.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/floppy.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/futex.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/hardware/cache-feroceon-l2.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/hwcap.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/jump_label.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/kprobes.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/memory.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/pgtable.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/pmu.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/probes.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/ptrace.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/smp.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/sync_bitops.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/syscall.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/system.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/include/asm/thread_info.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/timex.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/uaccess.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/unistd.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/uprobes.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/asm/xen/page.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/debug/samsung.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/debug/tegra.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/debug/zynq.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/include/uapi/asm/hwcap.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/bios32.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/crash_dump.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/devtree.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/entry-header.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/ftrace.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/hw_breakpoint.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-arm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-test-arm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-test.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-test.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes-thumb.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/kprobes.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/perf_event_cpu.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/perf_event_v7.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/pj4-cp0.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes-arm.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes-arm.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes-thumb.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes-thumb.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/probes.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/sys_oabi-compat.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/unwind.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/uprobes-arm.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/uprobes.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kernel/uprobes.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/kvm/arm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/bitops.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/copy_template.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/io-readsl.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/io-writesl.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/memmove.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/lib/uaccess.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/Kconfig.non_dt
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91rm9200.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9260.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9261.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9263.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9g45.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9n12.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9rl.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91sam9x5.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91x40.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/at91x40_time.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/board-dt-sam9.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/board-gsia18s.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/sam9_smc.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-at91/setup.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/bcm_5301x.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/board_bcm21664.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/board_bcm281xx.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/kona.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm/kona.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-bcm2835/Kconfig 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-bcm2835/Makefile 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-berlin/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-clps711x/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-clps711x/common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-clps711x/common.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-clps711x/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-cns3xxx/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-cns3xxx/cns3420vb.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-cns3xxx/core.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-cns3xxx/pcie.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/Makefile.boot
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/aemif.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/board-tnetv107x-evm.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-davinci/davinci.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/devices-tnetv107x.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-davinci/devices.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/dm355.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/dm365.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/dm644x.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/dm646x.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-davinci/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-davinci/tnetv107x.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-dove/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-dove/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-dove/board-dt.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-dove/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-ebsa110/core.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ebsa110/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-efm32/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ep93xx/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/common.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/common.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/cpuidle.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/exynos.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/include/mach/hardware.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/include/mach/pm-core.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/mach-exynos4-dt.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/mach-exynos5-dt.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-exynos/mfc.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/platsmp.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/pm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/pm_domains.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/regs-pmu.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-exynos/sleep.S 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-footbridge/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-footbridge/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-footbridge/cats-hw.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-footbridge/dc21285.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-footbridge/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-gemini/idle.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-gemini/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-highbank/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-hisi/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-hisi/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-hisi/hotplug.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx21.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx25.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx27.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx51-imx53.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx6q.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-imx6sl.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/clk-vf610.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/common.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6q.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6sl.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/cpuidle.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/devices-imx25.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/devices-imx51.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/devices/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/devices/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/devices/platform-mxc_pwm.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-imx/hardware.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/headsmp.S
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/mach-imx6q.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/mach-imx6sl.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/mach-mx27ads.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/pm-imx6.c 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/pm-imx6q.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-imx/suspend-imx6.S 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/core.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/hardware.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/impd1.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/impd1.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/include/mach/impd1.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-integrator/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-integrator/leds.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/lm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-integrator/pci_v3.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-iop13xx/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-iop32x/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-iop33x/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-ixp4xx/common-pci.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-setup.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ixp4xx/goramo_mlr.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-setup.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ixp4xx/omixp-setup.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-keystone/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-keystone/keystone.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/board-dt.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/common.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-kirkwood/pm.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-kirkwood/pm.h 0 → 100644
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ks8695/board-og.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-ks8695/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-ks8695/time.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-lpc32xx/common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-lpc32xx/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-lpc32xx/timer.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-mmp/aspenite.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-mmp/devices.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-mmp/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-mmp/time.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-mmp/ttc_dkb.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-moxart/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/Makefile
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/board-dt.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/common.h
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/dma.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/headsmp.S 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/hotplug.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/io.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-msm/platsmp.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/scm-boot.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-msm/timer.c 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-mv78xx0/common.c
浏览文件 @ af5666e0
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 1b15d2e5
此差异已折叠。
arch/arm/mach-mvebu/Kconfig
浏览文件 @ af5666e0
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或