Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 76b36fa8 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge tag 'v4.5-rc1' into x86/asm, to refresh the branch before merging new changes 

Signed-off-by: NIngo Molnar <mingo@kernel.org>
上级 14365449 92e963f5
展开全部 隐藏空白更改
内联 并排
Showing with 35867 addition and 13496 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ 76b36fa8
......@@ -534,6 +534,7 @@ N: NeilBrown
E: neil@brown.name
P: 4096R/566281B9 1BC6 29EB D390 D870 7B5F 497A 39EC 9EDD 5662 81B9
D: NFSD Maintainer 2000-2007
D: MD Maintainer 2001-2016
N: Zach Brown
E: zab@zabbo.net
......@@ -1507,6 +1508,14 @@ S: 312/107 Canberra Avenue
S: Griffith, ACT 2603
S: Australia
N: Andreas Herrmann
E: herrmann.der.user@gmail.com
E: herrmann.der.user@googlemail.com
D: Key developer of x86/AMD64
D: Author of AMD family 15h processor power monitoring driver
D: Maintainer of AMD Athlon 64 and Opteron processor frequency driver
S: Germany
N: Sebastian Hetze
E: she@lunetix.de
D: German Linux Documentation,
......@@ -1847,6 +1856,16 @@ S: Korte Heul 95
S: 1403 ND BUSSUM
S: The Netherlands
N: Martin Kepplinger
E: martink@posteo.de
E: martin.kepplinger@theobroma-systems.com
W: http://www.martinkepplinger.com
D: mma8452 accelerators iio driver
D: Kernel cleanups
S: Garnisonstraße 26
S: 4020 Linz
S: Austria
N: Karl Keyte
E: karl@koft.com
D: Disk usage statistics and modifications to line printer driver
......
Documentation/ABI/testing/configfs-iio 0 → 100644
浏览文件 @ 76b36fa8
What: /config/iio
Date: October 2015
KernelVersion: 4.4
Contact: linux-iio@vger.kernel.org
Description:
This represents Industrial IO configuration entry point
directory. It contains sub-groups corresponding to IIO
objects.
What: /config/iio/triggers
Date: October 2015
KernelVersion: 4.4
Description:
Industrial IO software triggers directory.
What: /config/iio/triggers/hrtimers
Date: October 2015
KernelVersion: 4.4
Description:
High resolution timers directory. Creating a directory here
will result in creating a hrtimer trigger in the IIO subsystem.
Documentation/ABI/testing/configfs-rdma_cm 0 → 100644
浏览文件 @ 76b36fa8
What: /config/rdma_cm
Date: November 29, 2015
KernelVersion: 4.4.0
Description: Interface is used to configure RDMA-cable HCAs in respect to
RDMA-CM attributes.
Attributes are visible only when configfs is mounted. To mount
configfs in /config directory use:
# mount -t configfs none /config/
In order to set parameters related to a specific HCA, a directory
for this HCA has to be created:
mkdir -p /config/rdma_cm/<hca>
What: /config/rdma_cm/<hca>/ports/<port-num>/default_roce_mode
Date: November 29, 2015
KernelVersion: 4.4.0
Description: RDMA-CM based connections from HCA <hca> at port <port-num>
will be initiated with this RoCE type as default.
The possible RoCE types are either "IB/RoCE v1" or "RoCE v2".
This parameter has RW access.
Documentation/ABI/testing/configfs-usb-gadget-sourcesink
浏览文件 @ 76b36fa8
......@@ -10,3 +10,5 @@ Description:
isoc_mult - 0..2 (hs/ss only)
isoc_maxburst - 0..15 (ss only)
buflen - buffer length
bulk_qlen - depth of queue for bulk
iso_qlen - depth of queue for iso
Documentation/ABI/testing/configfs-usb-gadget-tcm 0 → 100644
浏览文件 @ 76b36fa8
What: /config/usb-gadget/gadget/functions/tcm.name
Date: Dec 2015
KernelVersion: 4.5
Description:
There are no attributes because all the configuration
is performed in the "target" subsystem of configfs.
Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc 0 → 100644
浏览文件 @ 76b36fa8
What: /sys/bus/iio/devices/iio:deviceX/in_allow_async_readout
Date: December 2015
KernelVersion: 4.4
Contact: linux-iio@vger.kernel.org
Description:
By default (value '0'), the capture thread checks for the Conversion
Ready Flag to being set prior to committing a new value to the sample
buffer. This synchronizes the in-chip conversion rate with the
in-driver readout rate at the cost of an additional register read.
Writing '1' will remove the polling for the Conversion Ready Flags to
save the additional i2c transaction, which will improve the bandwidth
available for reading data. However, samples can be occasionally skipped
or repeated, depending on the beat between the capture and conversion
rates.
What: /sys/bus/iio/devices/iio:deviceX/in_shunt_resistor
Date: December 2015
KernelVersion: 4.4
Contact: linux-iio@vger.kernel.org
Description:
The value of the shunt resistor may be known only at runtime fom an
eeprom content read by a client application. This attribute allows to
set its value in ohms.
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 76b36fa8
......@@ -134,19 +134,21 @@ Description:
enabled for the device. Developer can write y/Y/1 or n/N/0 to
the file to enable/disable the feature.
What: /sys/bus/usb/devices/.../power/usb3_hardware_lpm
Date: June 2015
What: /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u1
/sys/bus/usb/devices/.../power/usb3_hardware_lpm_u2
Date: November 2015
Contact: Kevin Strasser <kevin.strasser@linux.intel.com>
Lu Baolu <baolu.lu@linux.intel.com>
Description:
If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged
in to a xHCI host which supports link PM, it will check if U1
and U2 exit latencies have been set in the BOS descriptor; if
the check is is passed and the host supports USB3 hardware LPM,
the check is passed and the host supports USB3 hardware LPM,
USB3 hardware LPM will be enabled for the device and the USB
device directory will contain a file named
power/usb3_hardware_lpm. The file holds a string value (enable
or disable) indicating whether or not USB3 hardware LPM is
enabled for the device.
device directory will contain two files named
power/usb3_hardware_lpm_u1 and power/usb3_hardware_lpm_u2. These
files hold a string value (enable or disable) indicating whether
or not USB3 hardware LPM U1 or U2 is enabled for the device.
What: /sys/bus/usb/devices/.../removable
Date: February 2012
......@@ -187,6 +189,17 @@ Description:
The file will read "hotplug", "wired" and "not used" if the
information is available, and "unknown" otherwise.
What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
Date: November 2015
Contact: Lu Baolu <baolu.lu@linux.intel.com>
Description:
Some USB3.0 devices are not friendly to USB3 LPM. usb3_lpm_permit
attribute allows enabling/disabling usb3 lpm of a port. It takes
effect both before and after a usb device is enumerated. Supported
values are "0" if both u1 and u2 are NOT permitted, "u1" if only u1
is permitted, "u2" if only u2 is permitted, "u1_u2" if both u1 and
u2 are permitted.
What: /sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout
Date: May 2013
Contact: Mathias Nyman <mathias.nyman@linux.intel.com>
......
Documentation/ABI/testing/sysfs-class-infiniband 0 → 100644
浏览文件 @ 76b36fa8
What: /sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/ndevs/<gid-index>
Date: November 29, 2015
KernelVersion: 4.4.0
Contact: linux-rdma@vger.kernel.org
Description: The net-device's name associated with the GID resides
at index <gid-index>.
What: /sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/types/<gid-index>
Date: November 29, 2015
KernelVersion: 4.4.0
Contact: linux-rdma@vger.kernel.org
Description: The RoCE type of the associated GID resides at index <gid-index>.
This could either be "IB/RoCE v1" for IB and RoCE v1 based GODs
or "RoCE v2" for RoCE v2 based GIDs.
Documentation/ABI/testing/sysfs-class-net-cdc_ncm
浏览文件 @ 76b36fa8
......@@ -19,6 +19,25 @@ Description:
Set to 0 to pad all frames. Set greater than tx_max to
disable all padding.
What: /sys/class/net/<iface>/cdc_ncm/ndp_to_end
Date: Dec 2015
KernelVersion: 4.5
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Boolean attribute showing the status of the "NDP to
end" quirk. Defaults to 'N', except for devices
already known to need it enabled.
The "NDP to end" quirk makes the driver place the NDP
(the packet index table) after the payload. The NCM
specification does not mandate this, but some devices
are known to be more restrictive. Write 'Y' to this
attribute for temporary testing of a suspect device
failing to work with the default driver settings.
A device entry should be added to the driver if this
quirk is found to be required.
What: /sys/class/net/<iface>/cdc_ncm/rx_max
Date: May 2014
KernelVersion: 3.16
......
Documentation/ABI/testing/sysfs-class-net-mesh
浏览文件 @ 76b36fa8
......@@ -8,7 +8,7 @@ Description:
What: /sys/class/net/<mesh_iface>/mesh/<vlan_subdir>/ap_isolation
Date: May 2011
Contact: Antonio Quartulli <antonio@meshcoding.com>
Contact: Antonio Quartulli <a@unstable.cc>
Description:
Indicates whether the data traffic going from a
wireless client to another wireless client will be
......@@ -70,7 +70,7 @@ Description:
What: /sys/class/net/<mesh_iface>/mesh/isolation_mark
Date: Nov 2013
Contact: Antonio Quartulli <antonio@meshcoding.com>
Contact: Antonio Quartulli <a@unstable.cc>
Description:
Defines the isolation mark (and its bitmask) which
is used to classify clients as "isolated" by the
......
Documentation/ABI/testing/sysfs-class-net-qmi 0 → 100644
浏览文件 @ 76b36fa8
What: /sys/class/net/<iface>/qmi/raw_ip
Date: Dec 2015
KernelVersion: 4.4
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Boolean. Default: 'N'
Set this to 'Y' to change the network device link
framing from '802.3' to 'raw-ip'.
The netdev will change to reflect the link framing
mode. The netdev is an ordinary ethernet device in
'802.3' mode, and the driver expects to exchange
frames with an ethernet header over the USB link. The
netdev is a headerless p-t-p device in 'raw-ip' mode,
and the driver expects to echange IPv4 or IPv6 packets
without any L2 header over the USB link.
Userspace is in full control of firmware configuration
through the delegation of the QMI protocol. Userspace
is responsible for coordination of driver and firmware
link framing mode, changing this setting to 'Y' if the
firmware is configured for 'raw-ip' mode.
Documentation/ABI/testing/sysfs-class-watchdog 0 → 100644
浏览文件 @ 76b36fa8
What: /sys/class/watchdog/watchdogn/bootstatus
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It contains status of the watchdog
device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
ioctl interface.
What: /sys/class/watchdog/watchdogn/identity
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It contains identity string of
watchdog device.
What: /sys/class/watchdog/watchdogn/nowayout
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. While reading, it gives '1' if that
device supports nowayout feature else, it gives '0'.
What: /sys/class/watchdog/watchdogn/state
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It gives active/inactive status of
watchdog device.
What: /sys/class/watchdog/watchdogn/status
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It contains watchdog device's
internal status bits. It is equivalent to WDIOC_GETSTATUS
of ioctl interface.
What: /sys/class/watchdog/watchdogn/timeleft
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It contains value of time left for
reset generation. It is equivalent to WDIOC_GETTIMELEFT of
ioctl interface.
What: /sys/class/watchdog/watchdogn/timeout
Date: August 2015
Contact: Wim Van Sebroeck <wim@iguana.be>
Description:
It is a read only file. It is read to know about current
value of timeout programmed.
Documentation/ABI/testing/sysfs-fs-f2fs
浏览文件 @ 76b36fa8
......@@ -87,6 +87,12 @@ Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
Description:
Controls the checkpoint timing.
What: /sys/fs/f2fs/<disk>/idle_interval
Date: January 2016
Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
Description:
Controls the idle timing.
What: /sys/fs/f2fs/<disk>/ra_nid_pages
Date: October 2015
Contact: "Chao Yu" <chao2.yu@samsung.com>
......
Documentation/ABI/testing/sysfs-kernel-livepatch
浏览文件 @ 76b36fa8
......@@ -33,7 +33,7 @@ Description:
The object directory contains subdirectories for each function
that is patched within the object.
What: /sys/kernel/livepatch/<patch>/<object>/<function>
What: /sys/kernel/livepatch/<patch>/<object>/<function,sympos>
Date: Nov 2014
KernelVersion: 3.19.0
Contact: live-patching@vger.kernel.org
......@@ -41,4 +41,8 @@ Description:
The function directory contains attributes regarding the
properties and state of the patched function.
The directory name contains the patched function name and a
sympos number corresponding to the nth occurrence of the symbol
name in kallsyms for the patched object.
There are currently no such attributes.
Documentation/ABI/testing/sysfs-ptp
浏览文件 @ 76b36fa8
......@@ -74,7 +74,7 @@ Description:
assignment may be changed by two writing numbers into
the file.
What: /sys/class/ptp/ptpN/pps_avaiable
What: /sys/class/ptp/ptpN/pps_available
Date: September 2010
Contact: Richard Cochran <richardcochran@gmail.com>
Description:
......
Documentation/CodingStyle
浏览文件 @ 76b36fa8
......@@ -430,7 +430,7 @@ The rationale for using gotos is:
return result;
}
A common type of bug to be aware of it "one err bugs" which look like this:
A common type of bug to be aware of is "one err bugs" which look like this:
err:
kfree(foo->bar);
......
Documentation/DMA-API-HOWTO.txt
浏览文件 @ 76b36fa8
......@@ -951,16 +951,6 @@ to "Closing".
alignment constraints (e.g. the alignment constraints about 64-bit
objects).
3) Supporting multiple types of IOMMUs
If your architecture needs to support multiple types of IOMMUs, you
can use include/linux/asm-generic/dma-mapping-common.h. It's a
library to support the DMA API with multiple types of IOMMUs. Lots
of architectures (x86, powerpc, sh, alpha, ia64, microblaze and
sparc) use it. Choose one to see how it can be used. If you need to
support multiple types of IOMMUs in a single system, the example of
x86 or powerpc helps.
Closing
This document, and the API itself, would not be in its current
......
Documentation/DMA-API.txt
浏览文件 @ 76b36fa8
......@@ -236,7 +236,7 @@ are guaranteed also to be cache line boundaries).
DMA_TO_DEVICE synchronisation must be done after the last modification
of the memory region by the software and before it is handed off to
the driver. Once this primitive is used, memory covered by this
the device. Once this primitive is used, memory covered by this
primitive should be treated as read-only by the device. If the device
may write to it at any point, it should be DMA_BIDIRECTIONAL (see
below).
......
Documentation/DocBook/Makefile
浏览文件 @ 76b36fa8
......@@ -50,8 +50,7 @@ pdfdocs: $(PDF)
HTML := $(sort $(patsubst %.xml, %.html, $(BOOKS)))
htmldocs: $(HTML)
$(call build_main_index)
$(call build_images)
$(call cmd,build_main_index)
$(call install_media_images)
MAN := $(patsubst %.xml, %.9, $(BOOKS))
......@@ -139,7 +138,8 @@ quiet_cmd_db2pdf = PDF $@
index = index.html
main_idx = $(obj)/$(index)
build_main_index = rm -rf $(main_idx); \
quiet_cmd_build_main_index = HTML $(main_idx)
cmd_build_main_index = rm -rf $(main_idx); \
echo '<h1>Linux Kernel HTML Documentation</h1>' >> $(main_idx) && \
echo '<h2>Kernel Version: $(KERNELVERSION)</h2>' >> $(main_idx) && \
cat $(HTML) >> $(main_idx)
......@@ -227,6 +227,10 @@ dochelp:
@echo ' mandocs - man pages'
@echo ' installmandocs - install man pages generated by mandocs'
@echo ' cleandocs - clean all generated DocBook files'
@echo
@echo 'make DOCBOOKS="s1.xml s2.xml" [target] Generate only docs s1.xml s2.xml'
@echo ' valid values for DOCBOOKS are: $(DOCBOOKS)'
###
# Temporary files left by various tools
......
Documentation/DocBook/device-drivers.tmpl
浏览文件 @ 76b36fa8
......@@ -238,83 +238,32 @@ X!Isound/sound_firmware.c
!Iinclude/media/videobuf2-memops.h
</sect1>
<sect1><title>Digital TV (DVB) devices</title>
!Idrivers/media/dvb-core/dvb_ca_en50221.h
!Idrivers/media/dvb-core/dvb_frontend.h
<sect1><title>Digital TV Common functions</title>
!Idrivers/media/dvb-core/dvb_math.h
!Idrivers/media/dvb-core/dvb_ringbuffer.h
!Idrivers/media/dvb-core/dvbdev.h
<sect1><title>Digital TV Demux API</title>
<para>The kernel demux API defines a driver-internal interface for
registering low-level, hardware specific driver to a hardware
independent demux layer. It is only of interest for Digital TV
device driver writers. The header file for this API is named
<constant>demux.h</constant> and located in
<constant>drivers/media/dvb-core</constant>.</para>
<para>The demux API should be implemented for each demux in the
system. It is used to select the TS source of a demux and to manage
the demux resources. When the demux client allocates a resource via
the demux API, it receives a pointer to the API of that
resource.</para>
<para>Each demux receives its TS input from a DVB front-end or from
memory, as set via this demux API. In a system with more than one
front-end, the API can be used to select one of the DVB front-ends
as a TS source for a demux, unless this is fixed in the HW platform.
The demux API only controls front-ends regarding to their connections
with demuxes; the APIs used to set the other front-end parameters,
such as tuning, are not defined in this document.</para>
<para>The functions that implement the abstract interface demux should
be defined static or module private and registered to the Demux
core for external access. It is not necessary to implement every
function in the struct <constant>dmx_demux</constant>. For example,
a demux interface might support Section filtering, but not PES
filtering. The API client is expected to check the value of any
function pointer before calling the function: the value of NULL means
that the &#8220;function is not available&#8221;.</para>
<para>Whenever the functions of the demux API modify shared data,
the possibilities of lost update and race condition problems should
be addressed, e.g. by protecting parts of code with mutexes.</para>
<para>Note that functions called from a bottom half context must not
sleep. Even a simple memory allocation without using GFP_ATOMIC can
result in a kernel thread being put to sleep if swapping is needed.
For example, the Linux kernel calls the functions of a network device
interface from a bottom half context. Thus, if a demux API function
is called from network device code, the function must not sleep.
</para>
</sect1>
<section id="demux_callback_api">
<title>Demux Callback API</title>
<para>This kernel-space API comprises the callback functions that
deliver filtered data to the demux client. Unlike the other DVB
kABIs, these functions are provided by the client and called from
the demux code.</para>
<para>The function pointers of this abstract interface are not
packed into a structure as in the other demux APIs, because the
callback functions are registered and used independent of each
other. As an example, it is possible for the API client to provide
several callback functions for receiving TS packets and no
callbacks for PES packets or sections.</para>
<para>The functions that implement the callback API need not be
re-entrant: when a demux driver calls one of these functions,
the driver is not allowed to call the function again before
the original call returns. If a callback is triggered by a
hardware interrupt, it is recommended to use the Linux
&#8220;bottom half&#8221; mechanism or start a tasklet instead of
making the callback function call directly from a hardware
interrupt.</para>
<para>This mechanism is implemented by
<link linkend='API-dmx-ts-cb'>dmx_ts_cb()</link> and
<link linkend='API-dmx-section-cb'>dmx_section_cb()</link>.</para>
</section>
</sect1>
<sect1><title>Digital TV Frontend kABI</title>
!Pdrivers/media/dvb-core/dvb_frontend.h Digital TV Frontend
!Idrivers/media/dvb-core/dvb_frontend.h
</sect1>
<sect1><title>Digital TV Demux kABI</title>
!Pdrivers/media/dvb-core/demux.h Digital TV Demux
<sect1><title>Demux Callback API</title>
!Pdrivers/media/dvb-core/demux.h Demux Callback
</sect1>
!Idrivers/media/dvb-core/demux.h
</sect1>
</sect1>
<sect1><title>Digital TV Conditional Access kABI</title>
!Idrivers/media/dvb-core/dvb_ca_en50221.h
</sect1>
</sect1>
<sect1><title>Remote Controller devices</title>
!Iinclude/media/rc-core.h
!Iinclude/media/lirc_dev.h
</sect1>
<sect1><title>Media Controller devices</title>
!Pinclude/media/media-device.h Media Controller
!Iinclude/media/media-device.h
!Iinclude/media/media-devnode.h
!Iinclude/media/media-entity.h
......
Documentation/DocBook/gpu.tmpl
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/DocBook/iio.tmpl
浏览文件 @ 76b36fa8
......@@ -458,7 +458,7 @@
.scan_type = {
.sign = 's',
.realbits = 12,
.storgebits = 16,
.storagebits = 16,
.shift = 4,
.endianness = IIO_LE,
},
......
Documentation/DocBook/media/Makefile
浏览文件 @ 76b36fa8
......@@ -199,8 +199,10 @@ DVB_DOCUMENTED = \
#
install_media_images = \
$(Q)-mkdir $(MEDIA_OBJ_DIR)/media_api; \
cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
$(Q)if [ "x$(findstring media_api.xml,$(DOCBOOKS))" != "x" ]; then \
mkdir -p $(MEDIA_OBJ_DIR)/media_api; \
cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api; \
fi
$(MEDIA_OBJ_DIR)/%: $(MEDIA_SRC_DIR)/%.b64
$(Q)base64 -d $< >$@
......
Documentation/DocBook/media/dvb/dvbproperty.xml
浏览文件 @ 76b36fa8
......@@ -76,7 +76,7 @@ int main(void)
<para>NOTE: While it is possible to directly call the Kernel code like the
above example, it is strongly recommended to use
<ulink url="http://linuxtv.org/docs/libdvbv5/index.html">libdvbv5</ulink>,
<ulink url="https://linuxtv.org/docs/libdvbv5/index.html">libdvbv5</ulink>,
as it provides abstraction to work with the supported digital TV standards
and provides methods for usual operations like program scanning and to
read/write channel descriptor files.</para>
......
Documentation/DocBook/media/dvb/examples.xml
浏览文件 @ 76b36fa8
......@@ -3,7 +3,7 @@
</para>
<para>NOTE: This section is out of date, and the code below won't even
compile. Please refer to the
<ulink url="http://linuxtv.org/docs/libdvbv5/index.html">libdvbv5</ulink>
<ulink url="https://linuxtv.org/docs/libdvbv5/index.html">libdvbv5</ulink>
for updated/recommended examples.
</para>
......
Documentation/DocBook/media/dvb/intro.xml
浏览文件 @ 76b36fa8
......@@ -32,7 +32,7 @@ and filtering several section and PES data streams at the same time.
new standard Linux DVB API. As a commitment to the development of
terminals based on open standards, Nokia and Convergence made it
available to all Linux developers and published it on
<ulink url="http://www.linuxtv.org/" /> in September 2000.
<ulink url="https://linuxtv.org" /> in September 2000.
Convergence is the maintainer of the Linux DVB API. Together with the
LinuxTV community (i.e. you, the reader of this document), the Linux DVB
API will be constantly reviewed and improved. With the Linux driver for
......
Documentation/DocBook/media/v4l/capture.c.xml
浏览文件 @ 76b36fa8
......@@ -5,7 +5,7 @@
* This program can be used and distributed without restrictions.
*
* This program is provided with the V4L2 API
* see http://linuxtv.org/docs.php for more information
* see https://linuxtv.org/docs.php for more information
*/
#include &lt;stdio.h&gt;
......
Documentation/DocBook/media/v4l/compat.xml
浏览文件 @ 76b36fa8
......@@ -2666,7 +2666,7 @@ is useful to display images captured with V4L2 devices.</para>
<para>V4L2 does not support digital terrestrial, cable or
satellite broadcast. A separate project aiming at digital receivers
exists. You can find its homepage at <ulink
url="http://linuxtv.org">http://linuxtv.org</ulink>. The Linux DVB API
url="https://linuxtv.org">https://linuxtv.org</ulink>. The Linux DVB API
has no connection to the V4L2 API except that drivers for hybrid
hardware may support both.</para>
</section>
......
Documentation/DocBook/media/v4l/io.xml
浏览文件 @ 76b36fa8
......@@ -699,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 it refers to an output stream.
refers to a capture stream, applications when it refers to an output stream.
If the application sets this to 0 for an output stream, then
<structfield>bytesused</structfield> will be set to the size of the
buffer (see the <structfield>length</structfield> field of this struct) by
......@@ -720,14 +720,14 @@ linkend="buffer-flags" />.</entry>
<entry>Indicates the field order of the image in the
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,
<structfield>type</structfield> refers to a capture stream,
applications when it refers to an output stream.</entry>
</row>
<row>
<entry>struct timeval</entry>
<entry><structfield>timestamp</structfield></entry>
<entry></entry>
<entry><para>For input streams this is time when the first data
<entry><para>For capture streams this is time when the first data
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
......@@ -866,7 +866,7 @@ must set this to 0.</entry>
<entry></entry>
<entry>The number of bytes occupied by data in the plane
(its payload). Drivers must set this field when <structfield>type</structfield>
refers to an input stream, applications when it refers to an output stream.
refers to a capture stream, applications when it refers to an output stream.
If the application sets this to 0 for an output stream, then
<structfield>bytesused</structfield> will be set to the size of the
plane (see the <structfield>length</structfield> field of this struct)
......@@ -919,7 +919,7 @@ must set this to 0.</entry>
<entry></entry>
<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.
refers to a capture stream, applications when it refers to an output stream.
Note that data_offset is included in <structfield>bytesused</structfield>.
So the size of the image in the plane is
<structfield>bytesused</structfield>-<structfield>data_offset</structfield> at
......
Documentation/DocBook/media/v4l/media-controller.xml
浏览文件 @ 76b36fa8
......@@ -58,21 +58,36 @@
<title>Media device model</title>
<para>Discovering a device internal topology, and configuring it at runtime,
is one of the goals of the media controller API. To achieve this, hardware
devices are modelled as an oriented graph of building blocks called entities
connected through pads.</para>
<para>An entity is a basic media hardware or software building block. It can
correspond to a large variety of logical blocks such as physical hardware
devices (CMOS sensor for instance), logical hardware devices (a building
block in a System-on-Chip image processing pipeline), DMA channels or
physical connectors.</para>
<para>A pad is a connection endpoint through which an entity can interact
with other entities. Data (not restricted to video) produced by an entity
flows from the entity's output to one or more entity inputs. Pads should not
be confused with physical pins at chip boundaries.</para>
<para>A link is a point-to-point oriented connection between two pads,
either on the same entity or on different entities. Data flows from a source
pad to a sink pad.</para>
devices and Linux Kernel interfaces are modelled as graph objects on
an oriented graph. The object types that constitute the graph are:</para>
<itemizedlist>
<listitem><para>An <emphasis role="bold">entity</emphasis>
is a basic media hardware or software building block. It can correspond to
a large variety of logical blocks such as physical hardware devices
(CMOS sensor for instance), logical hardware devices (a building block in
a System-on-Chip image processing pipeline), DMA channels or physical
connectors.</para></listitem>
<listitem><para>An <emphasis role="bold">interface</emphasis>
is a graph representation of a Linux Kernel userspace API interface,
like a device node or a sysfs file that controls one or more entities
in the graph.</para></listitem>
<listitem><para>A <emphasis role="bold">pad</emphasis>
is a data connection endpoint through which an entity can interact with
other entities. Data (not restricted to video) produced by an entity
flows from the entity's output to one or more entity inputs. Pads should
not be confused with physical pins at chip boundaries.</para></listitem>
<listitem><para>A <emphasis role="bold">data link</emphasis>
is a point-to-point oriented connection between two pads, either on the
same entity or on different entities. Data flows from a source pad to a
sink pad.</para></listitem>
<listitem><para>An <emphasis role="bold">interface link</emphasis>
is a point-to-point bidirectional control connection between a Linux
Kernel interface and an entity.m</para></listitem>
</itemizedlist>
</section>
<!-- All non-ioctl specific data types go here. -->
&sub-media-types;
</chapter>
<appendix id="media-user-func">
......@@ -83,6 +98,7 @@
&sub-media-func-ioctl;
<!-- All ioctls go here. -->
&sub-media-ioc-device-info;
&sub-media-ioc-g-topology;
&sub-media-ioc-enum-entities;
&sub-media-ioc-enum-links;
&sub-media-ioc-setup-link;
......
Documentation/DocBook/media/v4l/media-ioc-enum-entities.xml
浏览文件 @ 76b36fa8
......@@ -59,15 +59,6 @@
<para>Entity IDs can be non-contiguous. Applications must
<emphasis>not</emphasis> try to enumerate entities by calling
MEDIA_IOC_ENUM_ENTITIES with increasing id's until they get an error.</para>
<para>Two or more entities that share a common non-zero
<structfield>group_id</structfield> value are considered as logically
grouped. Groups are used to report
<itemizedlist>
<listitem><para>ALSA, VBI and video nodes that carry the same media
stream</para></listitem>
<listitem><para>lens and flash controllers associated with a sensor</para></listitem>
</itemizedlist>
</para>
<table pgwide="1" frame="none" id="media-entity-desc">
<title>struct <structname>media_entity_desc</structname></title>
......@@ -106,7 +97,7 @@
<entry><structfield>revision</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Entity revision in a driver/hardware specific format.</entry>
<entry>Entity revision. Always zero (obsolete)</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -120,7 +111,7 @@
<entry><structfield>group_id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Entity group ID</entry>
<entry>Entity group ID. Always zero (obsolete)</entry>
</row>
<row>
<entry>__u16</entry>
......@@ -171,97 +162,6 @@
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-entity-type">
<title>Media entity types</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE</constant></entry>
<entry>Unknown device node</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_V4L</constant></entry>
<entry>V4L video, radio or vbi device node</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_FB</constant></entry>
<entry>Frame buffer device node</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_ALSA</constant></entry>
<entry>ALSA card</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_FE</constant></entry>
<entry>DVB frontend devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DEMUX</constant></entry>
<entry>DVB demux devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DVR</constant></entry>
<entry>DVB DVR devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_CA</constant></entry>
<entry>DVB CAM devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_NET</constant></entry>
<entry>DVB network devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV</constant></entry>
<entry>Unknown V4L sub-device</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_SENSOR</constant></entry>
<entry>Video sensor</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_FLASH</constant></entry>
<entry>Flash controller</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_LENS</constant></entry>
<entry>Lens controller</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_DECODER</constant></entry>
<entry>Video decoder, the basic function of the video decoder is to
accept analogue video from a wide variety of sources such as
broadcast, DVD players, cameras and video cassette recorders, in
either NTSC, PAL or HD format and still occasionally SECAM, separate
it into its component parts, luminance and chrominance, and output
it in some digital video standard, with appropriate embedded timing
signals.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_TUNER</constant></entry>
<entry>TV and/or radio tuner</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-entity-flag">
<title>Media entity flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_ENT_FL_DEFAULT</constant></entry>
<entry>Default entity for its type. Used to discover the default
audio, VBI and video devices, the default camera sensor, ...</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
......
Documentation/DocBook/media/v4l/media-ioc-enum-links.xml
浏览文件 @ 76b36fa8
......@@ -118,35 +118,6 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-pad-flag">
<title>Media pad flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_PAD_FL_SINK</constant></entry>
<entry>Input pad, relative to the entity. Input pads sink data and
are targets of links.</entry>
</row>
<row>
<entry><constant>MEDIA_PAD_FL_SOURCE</constant></entry>
<entry>Output pad, relative to the entity. Output pads source data
and are origins of links.</entry>
</row>
<row>
<entry><constant>MEDIA_PAD_FL_MUST_CONNECT</constant></entry>
<entry>If this flag is set and the pad is linked to any other
pad, then at least one of those links must be enabled for the
entity to be able to stream. There could be temporary reasons
(e.g. device configuration dependent) for the pad to need
enabled links even when this flag isn't set; the absence of the
flag doesn't imply there is none.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-link-desc">
<title>struct <structname>media_link_desc</structname></title>
<tgroup cols="3">
......@@ -171,33 +142,6 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-link-flag">
<title>Media link flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_LNK_FL_ENABLED</constant></entry>
<entry>The link is enabled and can be used to transfer media data.
When two or more links target a sink pad, only one of them can be
enabled at a time.</entry>
</row>
<row>
<entry><constant>MEDIA_LNK_FL_IMMUTABLE</constant></entry>
<entry>The link enabled state can't be modified at runtime. An
immutable link is always enabled.</entry>
</row>
<row>
<entry><constant>MEDIA_LNK_FL_DYNAMIC</constant></entry>
<entry>The link enabled state can be modified during streaming. This
flag is set by drivers and is read-only for applications.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>One and only one of <constant>MEDIA_PAD_FL_SINK</constant> and
<constant>MEDIA_PAD_FL_SOURCE</constant> must be set for every pad.</para>
</refsect1>
<refsect1>
......
Documentation/DocBook/media/v4l/media-ioc-g-topology.xml 0 → 100644
浏览文件 @ 76b36fa8
<refentry id="media-g-topology">
<refmeta>
<refentrytitle>ioctl MEDIA_IOC_G_TOPOLOGY</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>MEDIA_IOC_G_TOPOLOGY</refname>
<refpurpose>Enumerate the graph topology and graph element properties</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct media_v2_topology *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>File descriptor returned by
<link linkend='media-func-open'><function>open()</function></link>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>MEDIA_IOC_G_TOPOLOGY</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para><emphasis role="bold">NOTE:</emphasis> This new ioctl is programmed to be added on Kernel 4.6. Its definition/arguments may change until its final version.</para>
<para>The typical usage of this ioctl is to call it twice.
On the first call, the structure defined at &media-v2-topology; should
be zeroed. At return, if no errors happen, this ioctl will return the
<constant>topology_version</constant> and the total number of entities,
interfaces, pads and links.</para>
<para>Before the second call, the userspace should allocate arrays to
store the graph elements that are desired, putting the pointers to them
at the ptr_entities, ptr_interfaces, ptr_links and/or ptr_pads, keeping
the other values untouched.</para>
<para>If the <constant>topology_version</constant> remains the same, the
ioctl should fill the desired arrays with the media graph elements.</para>
<table pgwide="1" frame="none" id="media-v2-topology">
<title>struct <structname>media_v2_topology</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u64</entry>
<entry><structfield>topology_version</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Version of the media graph topology. When the graph is
created, this field starts with zero. Every time a graph
element is added or removed, this field is
incremented.</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>num_entities</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Number of entities in the graph</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>ptr_entities</structfield></entry>
<entry></entry>
<entry></entry>
<entry>A pointer to a memory area where the entities array
will be stored, converted to a 64-bits integer.
It can be zero. if zero, the ioctl won't store the
entities. It will just update
<constant>num_entities</constant></entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>num_interfaces</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Number of interfaces in the graph</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>ptr_interfaces</structfield></entry>
<entry></entry>
<entry></entry>
<entry>A pointer to a memory area where the interfaces array
will be stored, converted to a 64-bits integer.
It can be zero. if zero, the ioctl won't store the
interfaces. It will just update
<constant>num_interfaces</constant></entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>num_pads</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Total number of pads in the graph</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>ptr_pads</structfield></entry>
<entry></entry>
<entry></entry>
<entry>A pointer to a memory area where the pads array
will be stored, converted to a 64-bits integer.
It can be zero. if zero, the ioctl won't store the
pads. It will just update
<constant>num_pads</constant></entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>num_links</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Total number of data and interface links in the graph</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>ptr_links</structfield></entry>
<entry></entry>
<entry></entry>
<entry>A pointer to a memory area where the links array
will be stored, converted to a 64-bits integer.
It can be zero. if zero, the ioctl won't store the
links. It will just update
<constant>num_links</constant></entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-v2-entity">
<title>struct <structname>media_v2_entity</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Unique ID for the entity.</entry>
</row>
<row>
<entry>char</entry>
<entry><structfield>name</structfield>[64]</entry>
<entry></entry>
<entry></entry>
<entry>Entity name as an UTF-8 NULL-terminated string.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>function</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Entity main function, see <xref linkend="media-entity-type" /> for details.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[12]</entry>
<entry>Reserved for future extensions. Drivers and applications must
set this array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-v2-interface">
<title>struct <structname>media_v2_interface</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Unique ID for the interface.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>intf_type</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Interface type, see <xref linkend="media-intf-type" /> for details.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>flags</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Interface flags. Currently unused.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry></entry>
<entry></entry>
<entry>Reserved for future extensions. Drivers and applications must
set this array to zero.</entry>
</row>
<row>
<entry>struct media_v2_intf_devnode</entry>
<entry><structfield>devnode</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Used only for device node interfaces. See <xref linkend="media-v2-intf-devnode" /> for details..</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-v2-intf-devnode">
<title>struct <structname>media_v2_interface</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>major</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Device node major number.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>minor</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Device node minor number.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-v2-pad">
<title>struct <structname>media_v2_pad</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Unique ID for the pad.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>entity_id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Unique ID for the entity where this pad belongs.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>flags</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Pad flags, see <xref linkend="media-pad-flag" /> for more details.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry></entry>
<entry></entry>
<entry>Reserved for future extensions. Drivers and applications must
set this array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="media-v2-link">
<title>struct <structname>media_v2_pad</structname></title>
<tgroup cols="5">
<colspec colname="c1" />
<colspec colname="c2" />
<colspec colname="c3" />
<colspec colname="c4" />
<colspec colname="c5" />
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Unique ID for the pad.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>source_id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>
<para>On pad to pad links: unique ID for the source pad.</para>
<para>On interface to entity links: unique ID for the interface.</para>
</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>sink_id</structfield></entry>
<entry></entry>
<entry></entry>
<entry>
<para>On pad to pad links: unique ID for the sink pad.</para>
<para>On interface to entity links: unique ID for the entity.</para>
</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>flags</structfield></entry>
<entry></entry>
<entry></entry>
<entry>Link flags, see <xref linkend="media-link-flag" /> for more details.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[5]</entry>
<entry></entry>
<entry></entry>
<entry>Reserved for future extensions. Drivers and applications must
set this array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>ENOSPC</errorcode></term>
<listitem>
<para>This is returned when either one or more of the num_entities,
num_interfaces, num_links or num_pads are non-zero and are smaller
than the actual number of elements inside the graph. This may happen
if the <constant>topology_version</constant> changed when compared
to the last time this ioctl was called. Userspace should usually
free the area for the pointers, zero the struct elements and call
this ioctl again.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
Documentation/DocBook/media/v4l/media-types.xml 0 → 100644
浏览文件 @ 76b36fa8
<section id="media-controller-types">
<title>Types and flags used to represent the media graph elements</title>
<table frame="none" pgwide="1" id="media-entity-type">
<title>Media entity types</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_ENT_F_UNKNOWN</constant> and <constant>MEDIA_ENT_F_V4L2_SUBDEV_UNKNOWN</constant></entry>
<entry>Unknown entity. That generally indicates that
a driver didn't initialize properly the entity, with is a Kernel bug</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_IO_V4L</constant></entry>
<entry>Data streaming input and/or output entity.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_IO_VBI</constant></entry>
<entry>V4L VBI streaming input or output entity</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_IO_SWRADIO</constant></entry>
<entry>V4L Software Digital Radio (SDR) streaming input or output entity</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_IO_DTV</constant></entry>
<entry>DVB Digital TV streaming input or output entity</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_DTV_DEMOD</constant></entry>
<entry>Digital TV demodulator entity.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_TS_DEMUX</constant></entry>
<entry>MPEG Transport stream demux entity. Could be implemented on hardware or in Kernelspace by the Linux DVB subsystem.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_DTV_CA</constant></entry>
<entry>Digital TV Conditional Access module (CAM) entity</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_DTV_NET_DECAP</constant></entry>
<entry>Digital TV network ULE/MLE desencapsulation entity. Could be implemented on hardware or in Kernelspace</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_RF</constant></entry>
<entry>Connector for a Radio Frequency (RF) signal.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_SVIDEO</constant></entry>
<entry>Connector for a S-Video signal.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_COMPOSITE</constant></entry>
<entry>Connector for a RGB composite signal.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_TEST</constant></entry>
<entry>Connector for a test generator.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CAM_SENSOR</constant></entry>
<entry>Camera video sensor entity.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_FLASH</constant></entry>
<entry>Flash controller entity.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_LENS</constant></entry>
<entry>Lens controller entity.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_ATV_DECODER</constant></entry>
<entry>Analog video decoder, the basic function of the video decoder
is to accept analogue video from a wide variety of sources such as
broadcast, DVD players, cameras and video cassette recorders, in
either NTSC, PAL, SECAM or HD format, separating the stream
into its component parts, luminance and chrominance, and output
it in some digital video standard, with appropriate timing
signals.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_TUNER</constant></entry>
<entry>Digital TV, analog TV, radio and/or software radio tuner.</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-entity-flag">
<title>Media entity flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_ENT_FL_DEFAULT</constant></entry>
<entry>Default entity for its type. Used to discover the default
audio, VBI and video devices, the default camera sensor, ...</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_FL_CONNECTOR</constant></entry>
<entry>The entity represents a data conector</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-intf-type">
<title>Media interface types</title>
<tgroup cols="3">
<colspec colname="c1"/>
<colspec colname="c2"/>
<colspec colname="c3"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_INTF_T_DVB_FE</constant></entry>
<entry>Device node interface for the Digital TV frontend</entry>
<entry>typically, /dev/dvb/adapter?/frontend?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_DVB_DEMUX</constant></entry>
<entry>Device node interface for the Digital TV demux</entry>
<entry>typically, /dev/dvb/adapter?/demux?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_DVB_DVR</constant></entry>
<entry>Device node interface for the Digital TV DVR</entry>
<entry>typically, /dev/dvb/adapter?/dvr?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_DVB_CA</constant></entry>
<entry>Device node interface for the Digital TV Conditional Access</entry>
<entry>typically, /dev/dvb/adapter?/ca?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_DVB_FE</constant></entry>
<entry>Device node interface for the Digital TV network control</entry>
<entry>typically, /dev/dvb/adapter?/net?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_V4L_VIDEO</constant></entry>
<entry>Device node interface for video (V4L)</entry>
<entry>typically, /dev/video?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_V4L_VBI</constant></entry>
<entry>Device node interface for VBI (V4L)</entry>
<entry>typically, /dev/vbi?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_V4L_RADIO</constant></entry>
<entry>Device node interface for radio (V4L)</entry>
<entry>typically, /dev/vbi?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_V4L_SUBDEV</constant></entry>
<entry>Device node interface for a V4L subdevice</entry>
<entry>typically, /dev/v4l-subdev?</entry>
</row>
<row>
<entry><constant>MEDIA_INTF_T_V4L_SWRADIO</constant></entry>
<entry>Device node interface for Software Defined Radio (V4L)</entry>
<entry>typically, /dev/swradio?</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="media-pad-flag">
<title>Media pad flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_PAD_FL_SINK</constant></entry>
<entry>Input pad, relative to the entity. Input pads sink data and
are targets of links.</entry>
</row>
<row>
<entry><constant>MEDIA_PAD_FL_SOURCE</constant></entry>
<entry>Output pad, relative to the entity. Output pads source data
and are origins of links.</entry>
</row>
<row>
<entry><constant>MEDIA_PAD_FL_MUST_CONNECT</constant></entry>
<entry>If this flag is set and the pad is linked to any other
pad, then at least one of those links must be enabled for the
entity to be able to stream. There could be temporary reasons
(e.g. device configuration dependent) for the pad to need
enabled links even when this flag isn't set; the absence of the
flag doesn't imply there is none.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>One and only one of <constant>MEDIA_PAD_FL_SINK</constant> and
<constant>MEDIA_PAD_FL_SOURCE</constant> must be set for every pad.</para>
<table frame="none" pgwide="1" id="media-link-flag">
<title>Media link flags</title>
<tgroup cols="2">
<colspec colname="c1"/>
<colspec colname="c2"/>
<tbody valign="top">
<row>
<entry><constant>MEDIA_LNK_FL_ENABLED</constant></entry>
<entry>The link is enabled and can be used to transfer media data.
When two or more links target a sink pad, only one of them can be
enabled at a time.</entry>
</row>
<row>
<entry><constant>MEDIA_LNK_FL_IMMUTABLE</constant></entry>
<entry>The link enabled state can't be modified at runtime. An
immutable link is always enabled.</entry>
</row>
<row>
<entry><constant>MEDIA_LNK_FL_DYNAMIC</constant></entry>
<entry>The link enabled state can be modified during streaming. This
flag is set by drivers and is read-only for applications.</entry>
</row>
<row>
<entry><constant>MEDIA_LNK_FL_LINK_TYPE</constant></entry>
<entry><para>This is a bitmask that defines the type of the link.
Currently, two types of links are supported:</para>
<para><constant>MEDIA_LNK_FL_DATA_LINK</constant>
if the link is between two pads</para>
<para><constant>MEDIA_LNK_FL_INTERFACE_LINK</constant>
if the link is between an interface and an entity</para></entry>
</row>
</tbody>
</tgroup>
</table>
</section>
Documentation/DocBook/media/v4l/v4l2.xml
浏览文件 @ 76b36fa8
......@@ -151,6 +151,16 @@ Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab,
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>4.5</revnumber>
<date>2015-10-29</date>
<authorinitials>rr</authorinitials>
<revremark>Extend vidioc-g-ext-ctrls;. Replace ctrl_class with a new
union with ctrl_class and which. Which is used to select the current value of
the control or the default value.
</revremark>
</revision>
<revision>
<revnumber>4.4</revnumber>
<date>2015-05-26</date>
......
Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
浏览文件 @ 76b36fa8
......@@ -58,7 +58,7 @@
<para>This ioctl is used to create buffers for <link linkend="mmap">memory
mapped</link> or <link linkend="userp">user pointer</link> or <link
linkend="dmabuf">DMA buffer</link> I/O. It can be used as an alternative or in
addition to the <constant>VIDIOC_REQBUFS</constant> ioctl, when a tighter
addition to the &VIDIOC-REQBUFS; ioctl, when a tighter
control over buffers is required. This ioctl can be called multiple times to
create buffers of different sizes.</para>
......@@ -71,30 +71,28 @@ zeroed.</para>
<para>The <structfield>format</structfield> field specifies the image format
that the buffers must be able to handle. The application has to fill in this
&v4l2-format;. Usually this will be done using the
<constant>VIDIOC_TRY_FMT</constant> or <constant>VIDIOC_G_FMT</constant> ioctl()
to ensure that the requested format is supported by the driver. Unsupported
formats will result in an error.</para>
&v4l2-format;. Usually this will be done using the &VIDIOC-TRY-FMT; or &VIDIOC-G-FMT; ioctls
to ensure that the requested format is supported by the driver.
Based on the format's <structfield>type</structfield> field the requested buffer
size (for single-planar) or plane sizes (for multi-planar formats) will be
used for the allocated buffers. The driver may return an error if the size(s)
are not supported by the hardware (usually because they are too small).</para>
<para>The buffers created by this ioctl will have as minimum size the size
defined by the <structfield>format.pix.sizeimage</structfield> field. If the
defined by the <structfield>format.pix.sizeimage</structfield> field (or the
corresponding fields for other format types). Usually if the
<structfield>format.pix.sizeimage</structfield> field is less than the minimum
required for the given format, then <structfield>sizeimage</structfield> will be
increased by the driver to that minimum to allocate the buffers. If it is
larger, then the value will be used as-is. The same applies to the
<structfield>sizeimage</structfield> field of the
<structname>v4l2_plane_pix_format</structname> structure in the case of
multiplanar formats.</para>
required for the given format, then an error will be returned since drivers will
typically not allow this. If it is larger, then the value will be used as-is.
In other words, the driver may reject the requested size, but if it is accepted
the driver will use it unchanged.</para>
<para>When the ioctl is called with a pointer to this structure the driver
will attempt to allocate up to the requested number of buffers and store the
actual number allocated and the starting index in the
<structfield>count</structfield> and the <structfield>index</structfield> fields
respectively. On return <structfield>count</structfield> can be smaller than
the number requested. The driver may also increase buffer sizes if required,
however, it will not update <structfield>sizeimage</structfield> field values.
The user has to use <constant>VIDIOC_QUERYBUF</constant> to retrieve that
information.</para>
the number requested.</para>
<table pgwide="1" frame="none" id="v4l2-create-buffers">
<title>struct <structname>v4l2_create_buffers</structname></title>
......
Documentation/DocBook/media/v4l/vidioc-dbg-g-chip-info.xml
浏览文件 @ 76b36fa8
......@@ -99,7 +99,7 @@ if the driver supports writing registers to the device.</para>
<para>We recommended the <application>v4l2-dbg</application>
utility over calling this ioctl directly. It is available from the
LinuxTV v4l-dvb repository; see <ulink
url="http://linuxtv.org/repo/">http://linuxtv.org/repo/</ulink> for
url="https://linuxtv.org/repo/">https://linuxtv.org/repo/</ulink> for
access instructions.</para>
<!-- Note for convenience vidioc-dbg-g-register.sgml
......
Documentation/DocBook/media/v4l/vidioc-dbg-g-register.xml
浏览文件 @ 76b36fa8
......@@ -117,7 +117,7 @@ However when a driver supports these ioctls it must also support
<para>We recommended the <application>v4l2-dbg</application>
utility over calling these ioctls directly. It is available from the
LinuxTV v4l-dvb repository; see <ulink
url="http://linuxtv.org/repo/">http://linuxtv.org/repo/</ulink> for
url="https://linuxtv.org/repo/">https://linuxtv.org/repo/</ulink> for
access instructions.</para>
<!-- Note for convenience vidioc-dbg-g-chip-info.sgml
......
Documentation/DocBook/media/v4l/vidioc-enumstd.xml
浏览文件 @ 76b36fa8
......@@ -198,7 +198,7 @@ video4linux-list@redhat.com on 17 Oct 2002
<constant>V4L2_STD_ATSC_16_VSB</constant> are U.S. terrestrial digital
TV standards. Presently the V4L2 API does not support digital TV. See
also the Linux DVB API at <ulink
url="http://linuxtv.org">http://linuxtv.org</ulink>.</para>
url="https://linuxtv.org">https://linuxtv.org</ulink>.</para>
<para><programlisting>
#define V4L2_STD_PAL_BG (V4L2_STD_PAL_B |\
V4L2_STD_PAL_B1 |\
......
Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml
浏览文件 @ 76b36fa8
......@@ -61,7 +61,7 @@ must belong to the same control class.</para>
<para>Applications must always fill in the
<structfield>count</structfield>,
<structfield>ctrl_class</structfield>,
<structfield>which</structfield>,
<structfield>controls</structfield> and
<structfield>reserved</structfield> fields of &v4l2-ext-controls;, and
initialize the &v4l2-ext-control; array pointed to by the
......@@ -109,7 +109,7 @@ the driver whether wrong values are automatically adjusted to a valid
value or if an error is returned.</para>
<para>When the <structfield>id</structfield> or
<structfield>ctrl_class</structfield> is invalid drivers return an
<structfield>which</structfield> is invalid drivers return an
&EINVAL;. When the value is out of bounds drivers can choose to take
the closest valid value or return an &ERANGE;, whatever seems more
appropriate. In the first case the new value is set in
......@@ -223,7 +223,12 @@ Valid if <constant>V4L2_CTRL_FLAG_HAS_PAYLOAD</constant> is set for this control
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>union</entry>
<entry>(anonymous)</entry>
</row>
<row>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>ctrl_class</structfield></entry>
<entry>The control class to which all controls belong, see
......@@ -233,6 +238,23 @@ belong to any control class. Whether drivers support this can be tested by setti
<structfield>ctrl_class</structfield> to 0 and calling <constant>VIDIOC_TRY_EXT_CTRLS</constant>
with a <structfield>count</structfield> of 0. If that succeeds, then the driver
supports this feature.</entry>
</row>
<row>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>which</structfield></entry>
<entry><para>Which value of the control to get/set/try. <constant>V4L2_CTRL_WHICH_CUR_VAL</constant>
will return the current value of the control and <constant>V4L2_CTRL_WHICH_DEF_VAL</constant> will
return the default value of the control. Please note that you can only get the default value of the
control, you cannot set or try it.</para>
<para>For backwards compatibility you can also use a control class here (see
<xref linkend="ctrl-class" />). In that case all controls have to belong to that
control class. This usage is deprecated, instead just use <constant>V4L2_CTRL_WHICH_CUR_VAL</constant>.
There are some very old drivers that do not yet support <constant>V4L2_CTRL_WHICH_CUR_VAL</constant>
and that require a control class here. You can test for such drivers by setting ctrl_class to
<constant>V4L2_CTRL_WHICH_CUR_VAL</constant> and calling VIDIOC_TRY_EXT_CTRLS with a count of 0.
If that fails, then the driver does not support <constant>V4L2_CTRL_WHICH_CUR_VAL</constant>.</para>
</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -390,7 +412,7 @@ These controls are described in <xref linkend="rf-tuner-controls" />.</entry>
<listitem>
<para>The &v4l2-ext-control; <structfield>id</structfield>
is invalid, the &v4l2-ext-controls;
<structfield>ctrl_class</structfield> is invalid, or the &v4l2-ext-control;
<structfield>which</structfield> is invalid, or the &v4l2-ext-control;
<structfield>value</structfield> was inappropriate (e.g. the given menu
index is not supported by the driver). This error code is
also returned by the <constant>VIDIOC_S_EXT_CTRLS</constant> and
......
Documentation/DocBook/media_api.tmpl
浏览文件 @ 76b36fa8
......@@ -19,10 +19,10 @@
<!ENTITY cs-def "<colspec colname='c1' colwidth='3*' /><colspec colname='c2' colwidth='1*' /><colspec colname='c3' colwidth='4*' /><spanspec spanname='hspan' namest='c1' nameend='c3' />">
<!-- Video for Linux mailing list address. -->
<!ENTITY v4l-ml "<ulink url='http://www.linuxtv.org/lists.php'>http://www.linuxtv.org/lists.php</ulink>">
<!ENTITY v4l-ml "<ulink url='https://linuxtv.org/lists.php'>https://linuxtv.org/lists.php</ulink>">
<!-- LinuxTV v4l-dvb repository. -->
<!ENTITY v4l-dvb "<ulink url='http://linuxtv.org/repo/'>http://linuxtv.org/repo/</ulink>">
<!ENTITY v4l-dvb "<ulink url='https://linuxtv.org/repo/'>https://linuxtv.org/repo/</ulink>">
<!ENTITY dash-ent-8 "<entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry>">
<!ENTITY dash-ent-10 "<entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry>">
<!ENTITY dash-ent-12 "<entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry>">
......@@ -91,7 +91,7 @@
components, like mixers, PCM capture, PCM playback, etc, which
are controlled via ALSA API.</para>
<para>For additional information and for the latest development code,
see: <ulink url="http://linuxtv.org">http://linuxtv.org</ulink>.</para>
see: <ulink url="https://linuxtv.org">https://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>
......
Documentation/DocBook/mtdnand.tmpl
浏览文件 @ 76b36fa8
......@@ -162,12 +162,15 @@
<sect1 id="Basic_defines">
<title>Basic defines</title>
<para>
At least you have to provide a mtd structure and
a storage for the ioremap'ed chip address.
You can allocate the mtd structure using kmalloc
or you can allocate it statically.
In case of static allocation you have to allocate
a nand_chip structure too.
At least you have to provide a nand_chip structure
and a storage for the ioremap'ed chip address.
You can allocate the nand_chip structure using
kmalloc or you can allocate it statically.
The NAND chip structure embeds an mtd structure
which will be registered to the MTD subsystem.
You can extract a pointer to the mtd structure
from a nand_chip pointer using the nand_to_mtd()
helper.
</para>
<para>
Kmalloc based example
......@@ -180,7 +183,6 @@ static void __iomem *baseaddr;
Static example
</para>
<programlisting>
static struct mtd_info board_mtd;
static struct nand_chip board_chip;
static void __iomem *baseaddr;
</programlisting>
......@@ -235,7 +237,7 @@ static void board_hwcontrol(struct mtd_info *mtd, int cmd)
<programlisting>
static void board_hwcontrol(struct mtd_info *mtd, int cmd)
{
struct nand_chip *this = (struct nand_chip *) mtd->priv;
struct nand_chip *this = mtd_to_nand(mtd);
switch(cmd){
case NAND_CTL_SETCLE: this->IO_ADDR_W |= CLE_ADRR_BIT; break;
case NAND_CTL_CLRCLE: this->IO_ADDR_W &amp;= ~CLE_ADRR_BIT; break;
......@@ -274,13 +276,15 @@ static int __init board_init (void)
int err = 0;
/* Allocate memory for MTD device structure and private data */
board_mtd = kzalloc(sizeof(struct mtd_info) + sizeof(struct nand_chip), GFP_KERNEL);
if (!board_mtd) {
this = kzalloc(sizeof(struct nand_chip), GFP_KERNEL);
if (!this) {
printk ("Unable to allocate NAND MTD device structure.\n");
err = -ENOMEM;
goto out;
}
board_mtd = nand_to_mtd(this);
/* map physical address */
baseaddr = ioremap(CHIP_PHYSICAL_ADDRESS, 1024);
if (!baseaddr) {
......@@ -289,11 +293,6 @@ static int __init board_init (void)
goto out_mtd;
}
/* Get pointer to private data */
this = (struct nand_chip *) ();
/* Link the private data with the MTD structure */
board_mtd->priv = this;
/* Set address of NAND IO lines */
this->IO_ADDR_R = baseaddr;
this->IO_ADDR_W = baseaddr;
......@@ -317,7 +316,7 @@ static int __init board_init (void)
out_ior:
iounmap(baseaddr);
out_mtd:
kfree (board_mtd);
kfree (this);
out:
return err;
}
......@@ -343,7 +342,7 @@ static void __exit board_cleanup (void)
iounmap(baseaddr);
/* Free the MTD device structure */
kfree (board_mtd);
kfree (mtd_to_nand(board_mtd));
}
module_exit(board_cleanup);
#endif
......@@ -399,7 +398,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip)
<programlisting>
static void board_select_chip (struct mtd_info *mtd, int chip)
{
struct nand_chip *this = (struct nand_chip *) mtd->priv;
struct nand_chip *this = mtd_to_nand(mtd);
/* Deselect all chips */
this->IO_ADDR_R &amp;= ~BOARD_NAND_ADDR_MASK;
......
Documentation/HOWTO
浏览文件 @ 76b36fa8
......@@ -209,7 +209,7 @@ tools. One such tool that is particularly recommended is the Linux
Cross-Reference project, which is able to present source code in a
self-referential, indexed webpage format. An excellent up-to-date
repository of the kernel code may be found at:
http://lxr.linux.no/+trees
http://lxr.free-electrons.com/
The development process
......
Documentation/Makefile
浏览文件 @ 76b36fa8
subdir-y := accounting auxdisplay blackfin connector \
filesystems filesystems ia64 laptops mic misc-devices \
networking pcmcia prctl ptp spi timers vDSO video4linux \
networking pcmcia prctl ptp timers vDSO video4linux \
watchdog
Documentation/accounting/getdelays.c
浏览文件 @ 76b36fa8
......@@ -375,7 +375,8 @@ int main(int argc, char *argv[])
}
}
if ((nl_sd = create_nl_socket(NETLINK_GENERIC)) < 0)
nl_sd = create_nl_socket(NETLINK_GENERIC);
if (nl_sd < 0)
err(1, "error creating Netlink socket\n");
......
Documentation/arm/Marvell/README
浏览文件 @ 76b36fa8
......@@ -233,29 +233,30 @@ MMP/MMP2 family (communication processor)
Linux kernel mach directory: arch/arm/mach-mmp
Linux kernel plat directory: arch/arm/plat-pxa
Berlin family (Digital Entertainment)
Berlin family (Multimedia Solutions)
-------------------------------------
Flavors:
88DE3005, Armada 1500-mini
88DE3005, Armada 1500 Mini
Design name: BG2CD
Core: ARM Cortex-A9, PL310 L2CC
Homepage: http://www.marvell.com/digital-entertainment/armada-1500-mini/
Homepage: http://www.marvell.com/multimedia-solutions/armada-1500-mini/
88DE3006, Armada 1500 Mini Plus
Design name: BG2CDP
Core: Dual Core ARM Cortex-A7
Homepage: http://www.marvell.com/multimedia-solutions/armada-1500-mini-plus/
88DE3100, Armada 1500
Design name: BG2
Core: Marvell PJ4B (ARMv7), Tauros3 L2CC
Homepage: http://www.marvell.com/digital-entertainment/armada-1500/
Product Brief: http://www.marvell.com/digital-entertainment/armada-1500/assets/Marvell-ARMADA-1500-Product-Brief.pdf
Product Brief: http://www.marvell.com/multimedia-solutions/armada-1500/assets/Marvell-ARMADA-1500-Product-Brief.pdf
88DE3114, Armada 1500 Pro
Design name: BG2-Q
Design name: BG2Q
Core: Quad Core ARM Cortex-A9, PL310 L2CC
Homepage: http://www.marvell.com/digital-entertainment/armada-1500-pro/
Product Brief: http://www.marvell.com/digital-entertainment/armada-1500-pro/assets/Marvell_ARMADA_1500_PRO-01_product_brief.pdf
88DE????
Design name: BG3
Core: ARM Cortex-A15, CA15 integrated L2CC
Homepage: http://www.marvell.com/digital-entertainment/
Homepage: http://www.marvell.com/multimedia-solutions/
Directory: arch/arm/mach-berlin
Comments:
......
Documentation/arm/pxa/mfp.txt
浏览文件 @ 76b36fa8
......@@ -49,7 +49,7 @@ to this new MFP mechanism, here are several key points:
internal controllers like PWM, SSP and UART, with 128 internal signals
which can be routed to external through one or more MFPs (e.g. GPIO<0>
can be routed through either MFP_PIN_GPIO0 as well as MFP_PIN_GPIO0_2,
see arch/arm/mach-pxa/mach/include/mfp-pxa300.h)
see arch/arm/mach-pxa/mfp-pxa300.h)
2. Alternate function configuration is removed from this GPIO controller,
the remaining functions are pure GPIO-specific, i.e.
......@@ -76,11 +76,11 @@ For board code writers, here are some guidelines:
1. include ONE of the following header files in your <board>.c:
- #include <mach/mfp-pxa25x.h>
- #include <mach/mfp-pxa27x.h>
- #include <mach/mfp-pxa300.h>
- #include <mach/mfp-pxa320.h>
- #include <mach/mfp-pxa930.h>
- #include "mfp-pxa25x.h"
- #include "mfp-pxa27x.h"
- #include "mfp-pxa300.h"
- #include "mfp-pxa320.h"
- #include "mfp-pxa930.h"
NOTE: only one file in your <board>.c, depending on the processors used,
because pin configuration definitions may conflict in these file (i.e.
......@@ -203,20 +203,20 @@ make them effective there-after.
1. Unified pin definitions - enum constants for all configurable pins
2. processor-neutral bit definitions for a possible MFP configuration
- arch/arm/mach-pxa/include/mach/mfp-pxa3xx.h
- arch/arm/mach-pxa/mfp-pxa3xx.h
for PXA3xx specific MFPR register bit definitions and PXA3xx common pin
configurations
- arch/arm/mach-pxa/include/mach/mfp-pxa2xx.h
- arch/arm/mach-pxa/mfp-pxa2xx.h
for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
- arch/arm/mach-pxa/include/mach/mfp-pxa25x.h
arch/arm/mach-pxa/include/mach/mfp-pxa27x.h
arch/arm/mach-pxa/include/mach/mfp-pxa300.h
arch/arm/mach-pxa/include/mach/mfp-pxa320.h
arch/arm/mach-pxa/include/mach/mfp-pxa930.h
- arch/arm/mach-pxa/mfp-pxa25x.h
arch/arm/mach-pxa/mfp-pxa27x.h
arch/arm/mach-pxa/mfp-pxa300.h
arch/arm/mach-pxa/mfp-pxa320.h
arch/arm/mach-pxa/mfp-pxa930.h
for processor specific definitions
......
Documentation/arm64/silicon-errata.txt 0 → 100644
浏览文件 @ 76b36fa8
Silicon Errata and Software Workarounds
=======================================
Author: Will Deacon <will.deacon@arm.com>
Date : 27 November 2015
It is an unfortunate fact of life that hardware is often produced with
so-called "errata", which can cause it to deviate from the architecture
under specific circumstances. For hardware produced by ARM, these
errata are broadly classified into the following categories:
Category A: A critical error without a viable workaround.
Category B: A significant or critical error with an acceptable
workaround.
Category C: A minor error that is not expected to occur under normal
operation.
For more information, consult one of the "Software Developers Errata
Notice" documents available on infocenter.arm.com (registration
required).
As far as Linux is concerned, Category B errata may require some special
treatment in the operating system. For example, avoiding a particular
sequence of code, or configuring the processor in a particular way. A
less common situation may require similar actions in order to declassify
a Category A erratum into a Category C erratum. These are collectively
known as "software workarounds" and are only required in the minority of
cases (e.g. those cases that both require a non-secure workaround *and*
can be triggered by Linux).
For software workarounds that may adversely impact systems unaffected by
the erratum in question, a Kconfig entry is added under "Kernel
Features" -> "ARM errata workarounds via the alternatives framework".
These are enabled by default and patched in at runtime when an affected
CPU is detected. For less-intrusive workarounds, a Kconfig option is not
available and the code is structured (preferably with a comment) in such
a way that the erratum will not be hit.
This approach can make it slightly onerous to determine exactly which
errata are worked around in an arbitrary kernel source tree, so this
file acts as a registry of software workarounds in the Linux Kernel and
will be updated when new workarounds are committed and backported to
stable kernels.
| Implementor | Component | Erratum ID | Kconfig |
+----------------+-----------------+-----------------+-------------------------+
| ARM | Cortex-A53 | #826319 | ARM64_ERRATUM_826319 |
| ARM | Cortex-A53 | #827319 | ARM64_ERRATUM_827319 |
| ARM | Cortex-A53 | #824069 | ARM64_ERRATUM_824069 |
| ARM | Cortex-A53 | #819472 | ARM64_ERRATUM_819472 |
| ARM | Cortex-A53 | #845719 | ARM64_ERRATUM_845719 |
| ARM | Cortex-A53 | #843419 | ARM64_ERRATUM_843419 |
| ARM | Cortex-A57 | #832075 | ARM64_ERRATUM_832075 |
| ARM | Cortex-A57 | #852523 | N/A |
| ARM | Cortex-A57 | #834220 | ARM64_ERRATUM_834220 |
| | | | |
| Cavium | ThunderX ITS | #22375, #24313 | CAVIUM_ERRATUM_22375 |
| Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
Documentation/block/cfq-iosched.txt
浏览文件 @ 76b36fa8
......@@ -81,14 +81,13 @@ on higher end storage.
Default value for this parameter is 8ms.
latency
-------
This parameter is used to enable/disable the latency mode of the CFQ
scheduler. If latency mode (called low_latency) is enabled, CFQ tries
to recompute the slice time for each process based on the target_latency set
for the system. This favors fairness over throughput. Disabling low
latency (setting it to 0) ignores target latency, allowing each process in the
system to get a full time slice.
low_latency
-----------
This parameter is used to enable/disable the low latency mode of the CFQ
scheduler. If enabled, CFQ tries to recompute the slice time for each process
based on the target_latency set for the system. This favors fairness over
throughput. Disabling low latency (setting it to 0) ignores target latency,
allowing each process in the system to get a full time slice.
By default low latency mode is enabled.
......
Documentation/cgroup-v1/00-INDEX 0 → 100644
浏览文件 @ 76b36fa8
00-INDEX
- this file
blkio-controller.txt
- Description for Block IO Controller, implementation and usage details.
cgroups.txt
- Control Groups definition, implementation details, examples and API.
cpuacct.txt
- CPU Accounting Controller; account CPU usage for groups of tasks.
cpusets.txt
- documents the cpusets feature; assign CPUs and Mem to a set of tasks.
devices.txt
- Device Whitelist Controller; description, interface and security.
freezer-subsystem.txt
- checkpointing; rationale to not use signals, interface.
hugetlb.txt
- HugeTLB Controller implementation and usage details.
memcg_test.txt
- Memory Resource Controller; implementation details.
memory.txt
- Memory Resource Controller; design, accounting, interface, testing.
net_cls.txt
- Network classifier cgroups details and usages.
net_prio.txt
- Network priority cgroups details and usages.
pids.txt
- Process number cgroups details and usages.
unified-hierarchy.txt
- Description the new/next cgroup interface.
Documentation/cgroup-v1/blkio-controller.txt 0 → 100644
浏览文件 @ 76b36fa8
Block IO Controller
===================
Overview
========
cgroup subsys "blkio" implements the block io controller. There seems to be
a need of various kinds of IO control policies (like proportional BW, max BW)
both at leaf nodes as well as at intermediate nodes in a storage hierarchy.
Plan is to use the same cgroup based management interface for blkio controller
and based on user options switch IO policies in the background.
Currently two IO control policies are implemented. First one is proportional
weight time based division of disk policy. It is implemented in CFQ. Hence
this policy takes effect only on leaf nodes when CFQ is being used. The second
one is throttling policy which can be used to specify upper IO rate limits
on devices. This policy is implemented in generic block layer and can be
used on leaf nodes as well as higher level logical devices like device mapper.
HOWTO
=====
Proportional Weight division of bandwidth
-----------------------------------------
You can do a very simple testing of running two dd threads in two different
cgroups. Here is what you can do.
- Enable Block IO controller
CONFIG_BLK_CGROUP=y
- Enable group scheduling in CFQ
CONFIG_CFQ_GROUP_IOSCHED=y
- Compile and boot into kernel and mount IO controller (blkio); see
cgroups.txt, Why are cgroups needed?.
mount -t tmpfs cgroup_root /sys/fs/cgroup
mkdir /sys/fs/cgroup/blkio
mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
- Create two cgroups
mkdir -p /sys/fs/cgroup/blkio/test1/ /sys/fs/cgroup/blkio/test2
- Set weights of group test1 and test2
echo 1000 > /sys/fs/cgroup/blkio/test1/blkio.weight
echo 500 > /sys/fs/cgroup/blkio/test2/blkio.weight
- Create two same size files (say 512MB each) on same disk (file1, file2) and
launch two dd threads in different cgroup to read those files.
sync
echo 3 > /proc/sys/vm/drop_caches
dd if=/mnt/sdb/zerofile1 of=/dev/null &
echo $! > /sys/fs/cgroup/blkio/test1/tasks
cat /sys/fs/cgroup/blkio/test1/tasks
dd if=/mnt/sdb/zerofile2 of=/dev/null &
echo $! > /sys/fs/cgroup/blkio/test2/tasks
cat /sys/fs/cgroup/blkio/test2/tasks
- At macro level, first dd should finish first. To get more precise data, keep
on looking at (with the help of script), at blkio.disk_time and
blkio.disk_sectors files of both test1 and test2 groups. This will tell how
much disk time (in milliseconds), each group got and how many sectors each
group dispatched to the disk. We provide fairness in terms of disk time, so
ideally io.disk_time of cgroups should be in proportion to the weight.
Throttling/Upper Limit policy
-----------------------------
- Enable Block IO controller
CONFIG_BLK_CGROUP=y
- Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y
- Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
- Specify a bandwidth rate on particular device for root group. The format
for policy is "<major>:<minor> <bytes_per_second>".
echo "8:16 1048576" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device
Above will put a limit of 1MB/second on reads happening for root group
on device having major/minor number 8:16.
- Run dd to read a file and see if rate is throttled to 1MB/s or not.
# dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K count=1024
1024+0 records in
1024+0 records out
4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s
Limits for writes can be put using blkio.throttle.write_bps_device file.
Hierarchical Cgroups
====================
Both CFQ and throttling implement hierarchy support; however,
throttling's hierarchy support is enabled iff "sane_behavior" is
enabled from cgroup side, which currently is a development option and
not publicly available.
If somebody created a hierarchy like as follows.
root
/ \
test1 test2
|
test3
CFQ by default and throttling with "sane_behavior" will handle the
hierarchy correctly. For details on CFQ hierarchy support, refer to
Documentation/block/cfq-iosched.txt. For throttling, all limits apply
to the whole subtree while all statistics are local to the IOs
directly generated by tasks in that cgroup.
Throttling without "sane_behavior" enabled from cgroup side will
practically treat all groups at same level as if it looks like the
following.
pivot
/ / \ \
root test1 test2 test3
Various user visible config options
===================================
CONFIG_BLK_CGROUP
- Block IO controller.
CONFIG_DEBUG_BLK_CGROUP
- Debug help. Right now some additional stats file show up in cgroup
if this option is enabled.
CONFIG_CFQ_GROUP_IOSCHED
- Enables group scheduling in CFQ. Currently only 1 level of group
creation is allowed.
CONFIG_BLK_DEV_THROTTLING
- Enable block device throttling support in block layer.
Details of cgroup files
=======================
Proportional weight policy files
--------------------------------
- blkio.weight
- Specifies per cgroup weight. This is default weight of the group
on all the devices until and unless overridden by per device rule.
(See blkio.weight_device).
Currently allowed range of weights is from 10 to 1000.
- blkio.weight_device
- One can specify per cgroup per device rules using this interface.
These rules override the default value of group weight as specified
by blkio.weight.
Following is the format.
# echo dev_maj:dev_minor weight > blkio.weight_device
Configure weight=300 on /dev/sdb (8:16) in this cgroup
# echo 8:16 300 > blkio.weight_device
# cat blkio.weight_device
dev weight
8:16 300
Configure weight=500 on /dev/sda (8:0) in this cgroup
# echo 8:0 500 > blkio.weight_device
# cat blkio.weight_device
dev weight
8:0 500
8:16 300
Remove specific weight for /dev/sda in this cgroup
# echo 8:0 0 > blkio.weight_device
# cat blkio.weight_device
dev weight
8:16 300
- blkio.leaf_weight[_device]
- Equivalents of blkio.weight[_device] for the purpose of
deciding how much weight tasks in the given cgroup has while
competing with the cgroup's child cgroups. For details,
please refer to Documentation/block/cfq-iosched.txt.
- blkio.time
- disk time allocated to cgroup per device in milliseconds. First
two fields specify the major and minor number of the device and
third field specifies the disk time allocated to group in
milliseconds.
- blkio.sectors
- number of sectors transferred to/from disk by the group. First
two fields specify the major and minor number of the device and
third field specifies the number of sectors transferred by the
group to/from the device.
- blkio.io_service_bytes
- Number of bytes transferred to/from the disk by the group. These
are further divided by the type of operation - read or write, sync
or async. First two fields specify the major and minor number of the
device, third field specifies the operation type and the fourth field
specifies the number of bytes.
- blkio.io_serviced
- Number of IOs (bio) issued to the disk by the group. These
are further divided by the type of operation - read or write, sync
or async. First two fields specify the major and minor number of the
device, third field specifies the operation type and the fourth field
specifies the number of IOs.
- blkio.io_service_time
- Total amount of time between request dispatch and request completion
for the IOs done by this cgroup. This is in nanoseconds to make it
meaningful for flash devices too. For devices with queue depth of 1,
this time represents the actual service time. When queue_depth > 1,
that is no longer true as requests may be served out of order. This
may cause the service time for a given IO to include the service time
of multiple IOs when served out of order which may result in total
io_service_time > actual time elapsed. This time is further divided by
the type of operation - read or write, sync or async. First two fields
specify the major and minor number of the device, third field
specifies the operation type and the fourth field specifies the
io_service_time in ns.
- blkio.io_wait_time
- Total amount of time the IOs for this cgroup spent waiting in the
scheduler queues for service. This can be greater than the total time
elapsed since it is cumulative io_wait_time for all IOs. It is not a
measure of total time the cgroup spent waiting but rather a measure of
the wait_time for its individual IOs. For devices with queue_depth > 1
this metric does not include the time spent waiting for service once
the IO is dispatched to the device but till it actually gets serviced
(there might be a time lag here due to re-ordering of requests by the
device). This is in nanoseconds to make it meaningful for flash
devices too. This time is further divided by the type of operation -
read or write, sync or async. First two fields specify the major and
minor number of the device, third field specifies the operation type
and the fourth field specifies the io_wait_time in ns.
- blkio.io_merged
- Total number of bios/requests merged into requests belonging to this
cgroup. This is further divided by the type of operation - read or
write, sync or async.
- blkio.io_queued
- Total number of requests queued up at any given instant for this
cgroup. This is further divided by the type of operation - read or
write, sync or async.
- blkio.avg_queue_size
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
The average queue size for this cgroup over the entire time of this
cgroup's existence. Queue size samples are taken each time one of the
queues of this cgroup gets a timeslice.
- blkio.group_wait_time
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
This is the amount of time the cgroup had to wait since it became busy
(i.e., went from 0 to 1 request queued) to get a timeslice for one of
its queues. This is different from the io_wait_time which is the
cumulative total of the amount of time spent by each IO in that cgroup
waiting in the scheduler queue. This is in nanoseconds. If this is
read when the cgroup is in a waiting (for timeslice) state, the stat
will only report the group_wait_time accumulated till the last time it
got a timeslice and will not include the current delta.
- blkio.empty_time
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
This is the amount of time a cgroup spends without any pending
requests when not being served, i.e., it does not include any time
spent idling for one of the queues of the cgroup. This is in
nanoseconds. If this is read when the cgroup is in an empty state,
the stat will only report the empty_time accumulated till the last
time it had a pending request and will not include the current delta.
- blkio.idle_time
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
This is the amount of time spent by the IO scheduler idling for a
given cgroup in anticipation of a better request than the existing ones
from other queues/cgroups. This is in nanoseconds. If this is read
when the cgroup is in an idling state, the stat will only report the
idle_time accumulated till the last idle period and will not include
the current delta.
- blkio.dequeue
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y. This
gives the statistics about how many a times a group was dequeued
from service tree of the device. First two fields specify the major
and minor number of the device and third field specifies the number
of times a group was dequeued from a particular device.
- blkio.*_recursive
- Recursive version of various stats. These files show the
same information as their non-recursive counterparts but
include stats from all the descendant cgroups.
Throttling/Upper limit policy files
-----------------------------------
- blkio.throttle.read_bps_device
- Specifies upper limit on READ rate from the device. IO rate is
specified in bytes per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
- blkio.throttle.write_bps_device
- Specifies upper limit on WRITE rate to the device. IO rate is
specified in bytes per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
- blkio.throttle.read_iops_device
- Specifies upper limit on READ rate from the device. IO rate is
specified in IO per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
- blkio.throttle.write_iops_device
- Specifies upper limit on WRITE rate to the device. IO rate is
specified in io per second. Rules are per device. Following is
the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
Note: If both BW and IOPS rules are specified for a device, then IO is
subjected to both the constraints.
- blkio.throttle.io_serviced
- Number of IOs (bio) issued to the disk by the group. These
are further divided by the type of operation - read or write, sync
or async. First two fields specify the major and minor number of the
device, third field specifies the operation type and the fourth field
specifies the number of IOs.
- blkio.throttle.io_service_bytes
- Number of bytes transferred to/from the disk by the group. These
are further divided by the type of operation - read or write, sync
or async. First two fields specify the major and minor number of the
device, third field specifies the operation type and the fourth field
specifies the number of bytes.
Common files among various policies
-----------------------------------
- blkio.reset_stats
- Writing an int to this file will result in resetting all the stats
for that cgroup.
CFQ sysfs tunable
=================
/sys/block/<disk>/queue/iosched/slice_idle
------------------------------------------
On a faster hardware CFQ can be slow, especially with sequential workload.
This happens because CFQ idles on a single queue and single queue might not
drive deeper request queue depths to keep the storage busy. In such scenarios
one can try setting slice_idle=0 and that would switch CFQ to IOPS
(IO operations per second) mode on NCQ supporting hardware.
That means CFQ will not idle between cfq queues of a cfq group and hence be
able to driver higher queue depth and achieve better throughput. That also
means that cfq provides fairness among groups in terms of IOPS and not in
terms of disk time.
/sys/block/<disk>/queue/iosched/group_idle
------------------------------------------
If one disables idling on individual cfq queues and cfq service trees by
setting slice_idle=0, group_idle kicks in. That means CFQ will still idle
on the group in an attempt to provide fairness among groups.
By default group_idle is same as slice_idle and does not do anything if
slice_idle is enabled.
One can experience an overall throughput drop if you have created multiple
groups and put applications in that group which are not driving enough
IO to keep disk busy. In that case set group_idle=0, and CFQ will not idle
on individual groups and throughput should improve.
Documentation/cgroup-v2.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/cgroups/00-INDEX 已删除 100644 → 0
浏览文件 @ 14365449
00-INDEX
- this file
blkio-controller.txt
- Description for Block IO Controller, implementation and usage details.
cgroups.txt
- Control Groups definition, implementation details, examples and API.
cpuacct.txt
- CPU Accounting Controller; account CPU usage for groups of tasks.
cpusets.txt
- documents the cpusets feature; assign CPUs and Mem to a set of tasks.
devices.txt
- Device Whitelist Controller; description, interface and security.
freezer-subsystem.txt
- checkpointing; rationale to not use signals, interface.
hugetlb.txt
- HugeTLB Controller implementation and usage details.
memcg_test.txt
- Memory Resource Controller; implementation details.
memory.txt
- Memory Resource Controller; design, accounting, interface, testing.
net_cls.txt
- Network classifier cgroups details and usages.
net_prio.txt
- Network priority cgroups details and usages.
pids.txt
- Process number cgroups details and usages.
resource_counter.txt
- Resource Counter API.
unified-hierarchy.txt
- Description the new/next cgroup interface.
Documentation/cgroups/blkio-controller.txt 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/cgroups/unified-hierarchy.txt 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/cpu-freq/pcc-cpufreq.txt
浏览文件 @ 76b36fa8
......@@ -159,8 +159,8 @@ to be strictly associated with a P-state.
2.2 cpuinfo_transition_latency:
-------------------------------
The cpuinfo_transition_latency field is 0. The PCC specification does
not include a field to expose this value currently.
The cpuinfo_transition_latency field is CPUFREQ_ETERNAL. The PCC specification
does not include a field to expose this value currently.
2.3 cpuinfo_cur_freq:
---------------------
......
Documentation/cpu-hotplug.txt
浏览文件 @ 76b36fa8
......@@ -150,7 +150,7 @@ an entry as shown below in the output.
If this is not mounted, do the following.
#mkdir /sysfs
#mkdir /sys
#mount -t sysfs sys /sys
Now you should see entries for all present cpu, the following is an example
......
Documentation/device-mapper/verity.txt
浏览文件 @ 76b36fa8
......@@ -18,11 +18,11 @@ Construction Parameters
0 is the original format used in the Chromium OS.
The salt is appended when hashing, digests are stored continuously and
the rest of the block is padded with zeros.
the rest of the block is padded with zeroes.
1 is the current format that should be used for new devices.
The salt is prepended when hashing and each digest is
padded with zeros to the power of two.
padded with zeroes to the power of two.
<dev>
This is the device containing data, the integrity of which needs to be
......@@ -79,6 +79,37 @@ restart_on_corruption
not compatible with ignore_corruption and requires user space support to
avoid restart loops.
ignore_zero_blocks
Do not verify blocks that are expected to contain zeroes and always return
zeroes instead. This may be useful if the partition contains unused blocks
that are not guaranteed to contain zeroes.
use_fec_from_device <fec_dev>
Use forward error correction (FEC) to recover from corruption if hash
verification fails. Use encoding data from the specified device. This
may be the same device where data and hash blocks reside, in which case
fec_start must be outside data and hash areas.
If the encoding data covers additional metadata, it must be accessible
on the hash device after the hash blocks.
Note: block sizes for data and hash devices must match. Also, if the
verity <dev> is encrypted the <fec_dev> should be too.
fec_roots <num>
Number of generator roots. This equals to the number of parity bytes in
the encoding data. For example, in RS(M, N) encoding, the number of roots
is M-N.
fec_blocks <num>
The number of encoding data blocks on the FEC device. The block size for
the FEC device is <data_block_size>.
fec_start <offset>
This is the offset, in <data_block_size> blocks, from the start of the
FEC device to the beginning of the encoding data.
Theory of operation
===================
......@@ -98,6 +129,11 @@ per-block basis. This allows for a lightweight hash computation on first read
into the page cache. Block hashes are stored linearly, aligned to the nearest
block size.
If forward error correction (FEC) support is enabled any recovery of
corrupted data will be verified using the cryptographic hash of the
corresponding data. This is why combining error correction with
integrity checking is essential.
Hash Tree
---------
......
Documentation/devicetree/bindings/arm/arm,scpi.txt
浏览文件 @ 76b36fa8
......@@ -63,7 +63,7 @@ Required properties:
- compatible : should be "arm,juno-sram-ns" for Non-secure SRAM on Juno
The rest of the properties should follow the generic mmio-sram description
found in ../../misc/sysram.txt
found in ../../sram/sram.txt
Each sub-node represents the reserved area for SCPI.
......
Documentation/devicetree/bindings/arm/bcm/brcm,bcm2835.txt
浏览文件 @ 76b36fa8
......@@ -26,6 +26,10 @@ Raspberry Pi Model B+
Required root node properties:
compatible = "raspberrypi,model-b-plus", "brcm,bcm2835";
Raspberry Pi 2 Model B
Required root node properties:
compatible = "raspberrypi,2-model-b", "brcm,bcm2836";
Raspberry Pi Compute Module
Required root node properties:
compatible = "raspberrypi,compute-module", "brcm,bcm2835";
......
Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt
浏览文件 @ 76b36fa8
......@@ -5,4 +5,11 @@ Boards with the BCM4708 SoC shall have the following properties:
Required root node property:
bcm4708
compatible = "brcm,bcm4708";
bcm4709
compatible = "brcm,bcm4709";
bcm53012
compatible = "brcm,bcm53012";
Documentation/devicetree/bindings/arm/fsl.txt
浏览文件 @ 76b36fa8
......@@ -131,6 +131,10 @@ Example:
Freescale ARMv8 based Layerscape SoC family Device Tree Bindings
----------------------------------------------------------------
LS1043A ARMv8 based RDB Board
Required root node properties:
- compatible = "fsl,ls1043a-rdb", "fsl,ls1043a";
LS2080A ARMv8 based Simulator model
Required root node properties:
- compatible = "fsl,ls2080a-simu", "fsl,ls2080a";
......
Documentation/devicetree/bindings/arm/l2c2x0.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/arm/secure.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/arm/technologic.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/clock/cs2000-cp.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/dma/stm32-dma.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/iio/adc/imx7d-adc.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/net/nfc/st95hf.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/pci/qcom,pcie.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/phy/phy-ath79-usb.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/regulator/pv88060.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/regulator/pv88090.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/soc/dove/pmu.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/atmel-pdmic.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/da7218.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/img,i2s-in.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/img,i2s-out.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/inno-rk3036.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/pcm179x.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/rt5616.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/rt5651.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/rt5659.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/ti,pcm3168a.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sound/wlf,wm8974.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sram/samsung-sram.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/sram/sunxi-sram.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/usb/dwc3-xilinx.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/usb/mt8173-xhci.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/usb/octeon-usb.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/devicetree/bindings/usb/renesas_usb3.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/dmaengine/client.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/dvb/README.dvb-usb
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/dvb/faq.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/dvb/get_dvb_firmware
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/dvb/readme.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/edac.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/filesystems/tmpfs.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/filesystems/vfat.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/gpio/consumer.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/gpio/driver.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/hwmon/htu21 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/hwmon/ltc3815 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/iio/iio_configfs.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/ja_JP/HOWTO
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/kernel-docs.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/ko_KR/HOWTO
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/leds/leds-class.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/md-cluster.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/media-framework.txt 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/memory-barriers.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/mtd/nand_ecc.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/networking/can.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/power/pci.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/power/runtime_pm.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/printk-formats.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/s390/zfcpdump.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/sound/alsa/img,spdif-in.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/spi/00-INDEX
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/spi/Makefile 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/spi/spidev_test.c 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
Documentation/sysctl/fs.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/thermal/sysfs-api.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/ubsan.txt 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/usb/chipidea.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/video4linux/API.html
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/video4linux/fimc.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/virtual/kvm/mmu.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/vm/slub.txt
浏览文件 @ 76b36fa8
此差异已折叠。
Documentation/vm/transhuge.txt
浏览文件 @ 76b36fa8
此差异已折叠。
MAINTAINERS
浏览文件 @ 76b36fa8
此差异已折叠。
Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/alpha/include/uapi/asm/mman.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/alpha/kernel/module.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arc/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arc/include/asm/dma-mapping.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arc/kernel/unwind.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arc/mm/cache.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arc/mm/dma.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/compressed/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/compressed/efi-header.S 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/compressed/head.S
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-cm-t335.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-evmsk.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-lxm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-nano.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-pepper.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-sbc-t335.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-shc.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-sl50.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am335x-wega.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am437x-cm-t43.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am437x-sbc-t43.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am437x-sk-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am57xx-cl-som-am57x.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/am57xx-sbc-am57x.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/arm-realview-pb11mp.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/armada-388-clearfog.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/armada-388-gp.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/armada-38x-solidrun-microsom.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/at91-sama5d4_ma5d4.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/at91-sama5d4_ma5d4evk.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/at91-vinco.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm-cygnus.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm-nsp.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm11351.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm21664.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi-b.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm2835.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm2836-rpi-2-b.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm2836.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm283x.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm4708.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm5301x.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm63138.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm94708.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm94709.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm953012k.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/bcm958625k.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/berlin2.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/berlin2cd.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/berlin2q.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/compulab-sb-som.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/da850-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/da850.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dm8148-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dm8148-t410.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dm814x.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dm816x.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dove-cubox.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dove.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra62x-clocks.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra62x-j5eco-evm.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra62x.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ea3250.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/emev2.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos5.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos5410.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx25-pinfunc.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx51-ts4800.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6dl.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6q-novena.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6q.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6sx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx6ul.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx7d-cl-som-imx7.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx7d-sbc-imx7.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx7d-sdb.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/imx7d.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/kirkwood-nsa325.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/kirkwood-pogoplug-series-4.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/lpc18xx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/lpc32xx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/lpc4337-ciaa.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/lpc4357.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ls1021a-qds.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ls1021a-twr.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ls1021a.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/meson8b.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/mt2701-evb.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/mt2701.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/mt8135.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-beagle.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-cm-t3x.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-ldp.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-n900.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3-zoom3.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap4-sdp.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap5-cm-t54.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap5-uevm.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/phy3250.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064-sony-xperia-yuga.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-msm8960.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-pm8841.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-pm8941.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/qcom-pma8084.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r7s72100.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7740.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7778-bockw.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7791-henninger.dts 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7793-gose.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7793.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7794-alt.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7794-silk.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/r8a7794.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3036-evb.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3036-kylin.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3036.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3066a.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3188.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3228-evb.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3228.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3288-evb.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3288-r89.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3288-veyron-brain.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3288-veyron-mickey.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3288.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/rk3xxx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sama5d2.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sama5d4.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sh73a0-kzm9g.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sh73a0.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/socfpga_cyclone5_mcv.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/socfpga_cyclone5_mcvevk.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ste-dbx5x0.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ste-snowball.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/ste-u300.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun5i-a13-empire-electronix-d709.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-icnova-swac.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun8i-h3-orangepi-plus.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun8i-h3.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/sun9i-a80.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/tango4-common.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/tango4-smp8758.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/tango4-vantage-1172.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/tps65217.dtsi 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/boot/dts/uniphier-common32.dtsi 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/versatile-ab.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/vf-colibri.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/vf610m4-cosmic.dts 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/vfxxx.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/wm8505.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/zynq-7000.dtsi
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/boot/dts/zynq-zc702.dts
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/common/mcpm_platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/common/scoop.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/bcm2835_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/ep93xx_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/lpc18xx_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/lpc32xx_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/multi_v5_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/mv78xx0_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/mvebu_v5_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/orion5x_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/pxa_defconfig 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/qcom_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/realview_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/s3c6400_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/sama5_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/shmobile_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/socfpga_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/stm32_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/configs/zx_defconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/Kbuild
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/barrier.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/bug.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/cpuidle.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/cputype.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/div64.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/dma-mapping.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/efi.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/fixmap.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/hardirq.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/kvm_arm.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/kvm_host.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/kvm_mmu.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/mach/map.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/mmu_context.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/paravirt.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/psci.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/include/asm/setup.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/atags.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/cpuidle.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/devtree.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/efi.c 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/entry-v7m.S
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/module-plts.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/paravirt.c 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/perf_event_v7.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/pj4-cp0.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/psci-call.S 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/kernel/psci_smp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/smccc-call.S 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/vdso.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kernel/xscale-cp0.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/arm.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/emulate.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/guest.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/handle_exit.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/mmio.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/kvm/mmu.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/lib/lib1funcs.S
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/lib/uaccess_with_memcpy.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-alpine/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-alpine/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-axxia/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-axxia/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/bcm63xx_smp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/bcm_5301x.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/board_bcm2835.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/kona_smp.c 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-bcm/platsmp-brcmstb.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-bcm/platsmp.c 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-berlin/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-berlin/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-cns3xxx/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/clock.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/cp_intc.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/cpuidle.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/da830.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/da850.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/da8xx-dt.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/dm355.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/dm365.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/dm644x.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/dm646x.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/pm.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/psc.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/sleep.S
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-davinci/sram.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-dove/cm-a510.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-dove/common.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-dove/dove-db-setup.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-dove/include/mach/entry-macro.S 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-dove/irq.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ep93xx/snappercl15.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ep93xx/ts72xx.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-exynos/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-exynos/common.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-exynos/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-exynos/pmu.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-exynos/regs-pmu.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-highbank/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-hisi/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-hisi/core.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-hisi/platmcpm.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-hisi/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/common.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/iomux-imx31.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/mach-imx6ul.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/mach-imx7d.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/mach-mx21ads.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/mach-qong.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-imx/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-integrator/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-iop13xx/include/mach/pci.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-iop13xx/iq81340mc.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-iop13xx/iq81340sc.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-iop13xx/irq.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-iop13xx/pci.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-iop13xx/pci.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-keystone/keystone.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-keystone/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/board-acs5k.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/board-dsm320.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/board-micrel.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/board-og.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/board-sg.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/cpu.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/devices.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-ks8695/pci.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mediatek/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mediatek/mediatek.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mediatek/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-meson/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/addr-map.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/aspenite.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/avengers_lite.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/brownstone.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/clock-mmp2.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/clock-pxa168.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/clock-pxa910.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/clock.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/clock.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/common.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/common.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/devices.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/flint.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/gplugd.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/include/mach/addr-map.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/hardware.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/mfp-mmp2.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/mfp-pxa168.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/mfp-pxa910.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/mmp2.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/pm-mmp2.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/pxa168.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/pxa910.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/regs-apbc.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/regs-apmu.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/regs-icu.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/regs-smc.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/regs-timers.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/teton_bga.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/include/mach/uncompress.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mmp/jasper.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/mfp-mmp2.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/mfp-pxa168.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/mfp-pxa910.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/mmp2.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/mmp2.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pm-mmp2.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pm-mmp2.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pm-pxa910.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pxa168.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pxa168.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pxa910.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/pxa910.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/regs-apbc.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/regs-apmu.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/regs-icu.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/regs-timers.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/tavorevb.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/teton_bga.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/teton_bga.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/time.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mmp/ttc_dkb.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-moxart/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/bridge-regs.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/common.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/hardware.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/irqs.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/mv78xx0.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mv78xx0/irq.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/irqs.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/mpp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/mv78xx0.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mv78xx0/pcie.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mvebu/Kconfig
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mvebu/armada-370-xp.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mvebu/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-mvebu/platsmp-a9.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-mvebu/platsmp.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-netx/include/mach/param.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-omap1/board-fsample.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-nand.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-palmte.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-palmtt.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-palmz71.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-sx1-mmc.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/board-sx1.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/camera.h 0 → 100644
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/devices.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/flash.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap1/include/mach/camera.h 已删除 100644 → 0
浏览文件 @ 14365449
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap2/board-generic.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap2/cm81xx.h
浏览文件 @ 76b36fa8
此差异已折叠。
arch/arm/mach-omap2/common.h
浏览文件 @ 76b36fa8
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或