Skip to content

K
Kernel

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

通知 8
Star 0
Fork 0
K
Kernel
提交 67cbf8a2 编写于 作者: T Takashi Iwai
浏览文件
操作

Merge branch 'fix/misc' into topic/misc

上级 6c941c85 2fbe74b9
展开全部 隐藏空白更改
内联 并排
Showing with 64558 addition and 29851 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 67cbf8a2
......@@ -144,3 +144,16 @@ Description:
Write a 1 to force the device to disconnect
(equivalent to unplugging a wired USB device).
What: /sys/bus/usb/drivers/.../remove_id
Date: November 2009
Contact: CHENG Renquan <rqcheng@smu.edu.sg>
Description:
Writing a device ID to this file will remove an ID
that was dynamically added via the new_id sysfs entry.
The format for the device ID is:
idVendor idProduct. After successfully
removing an ID, the driver will no longer support the
device. This is useful to ensure auto probing won't
match the driver to the device. For example:
# echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc
浏览文件 @ 67cbf8a2
......@@ -23,3 +23,16 @@ Description:
Since this relates to security (specifically, the
lifetime of PTKs and GTKs) it should not be changed
from the default.
What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_phy_rate
Date: August 2009
KernelVersion: 2.6.32
Contact: David Vrabel <david.vrabel@csr.com>
Description:
The maximum PHY rate to use for all connected devices.
This is only of limited use for testing and
development as the hardware's automatic rate
adaptation is better then this simple control.
Refer to [ECMA-368] section 10.3.1.1 for the value to
use.
Documentation/ABI/testing/sysfs-devices-memory
浏览文件 @ 67cbf8a2
......@@ -60,6 +60,19 @@ Description:
Users: hotplug memory remove tools
https://w3.opensource.ibm.com/projects/powerpc-utils/
What: /sys/devices/system/memoryX/nodeY
Date: October 2009
Contact: Linux Memory Management list <linux-mm@kvack.org>
Description:
When CONFIG_NUMA is enabled, a symbolic link that
points to the corresponding NUMA node directory.
For example, the following symbolic link is created for
memory section 9 on node0:
/sys/devices/system/memory/memory9/node0 -> ../../node/node0
What: /sys/devices/system/node/nodeX/memoryY
Date: September 2008
Contact: Gary Hade <garyhade@us.ibm.com>
......@@ -70,4 +83,3 @@ Description:
memory section directory. For example, the following symbolic
link is created for memory section 9 on node0.
/sys/devices/system/node/node0/memory9 -> ../../memory/memory9
Documentation/ABI/testing/sysfs-devices-system-cpu
浏览文件 @ 67cbf8a2
......@@ -62,6 +62,35 @@ Description: CPU topology files that describe kernel limits related to
See Documentation/cputopology.txt for more information.
What: /sys/devices/system/cpu/probe
/sys/devices/system/cpu/release
Date: November 2009
Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Description: Dynamic addition and removal of CPU's. This is not hotplug
removal, this is meant complete removal/addition of the CPU
from the system.
probe: writes to this file will dynamically add a CPU to the
system. Information written to the file to add CPU's is
architecture specific.
release: writes to this file dynamically remove a CPU from
the system. Information writtento the file to remove CPU's
is architecture specific.
What: /sys/devices/system/cpu/cpu#/node
Date: October 2009
Contact: Linux memory management mailing list <linux-mm@kvack.org>
Description: Discover NUMA node a CPU belongs to
When CONFIG_NUMA is enabled, a symbolic link that points
to the corresponding NUMA node directory.
For example, the following symlink is created for cpu42
in NUMA node 2:
/sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
What: /sys/devices/system/cpu/cpu#/node
Date: October 2009
......@@ -136,6 +165,24 @@ Description: Discover cpuidle policy and mechanism
See files in Documentation/cpuidle/ for more information.
What: /sys/devices/system/cpu/cpu#/cpufreq/*
Date: pre-git history
Contact: cpufreq@vger.kernel.org
Description: Discover and change clock speed of CPUs
Clock scaling allows you to change the clock speed of the
CPUs on the fly. This is a nice method to save battery
power, because the lower the clock speed, the less power
the CPU consumes.
There are many knobs to tweak in this directory.
See files in Documentation/cpu-freq/ for more information.
In particular, read Documentation/cpu-freq/user-guide.txt
to learn how to control the knobs.
What: /sys/devices/system/cpu/cpu*/cache/index*/cache_disable_X
Date: August 2008
KernelVersion: 2.6.27
......
Documentation/ABI/testing/sysfs-kernel-slab
浏览文件 @ 67cbf8a2
......@@ -45,8 +45,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The alloc_fastpath file is read-only and specifies how many
objects have been allocated using the fast path.
The alloc_fastpath file shows how many objects have been
allocated using the fast path. It can be written to clear the
current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/alloc_from_partial
......@@ -55,9 +56,10 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The alloc_from_partial file is read-only and specifies how
many times a cpu slab has been full and it has been refilled
by using a slab from the list of partially used slabs.
The alloc_from_partial file shows how many times a cpu slab has
been full and it has been refilled by using a slab from the list
of partially used slabs. It can be written to clear the current
count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/alloc_refill
......@@ -66,9 +68,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The alloc_refill file is read-only and specifies how many
times the per-cpu freelist was empty but there were objects
available as the result of remote cpu frees.
The alloc_refill file shows how many times the per-cpu freelist
was empty but there were objects available as the result of
remote cpu frees. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/alloc_slab
......@@ -77,8 +79,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The alloc_slab file is read-only and specifies how many times
a new slab had to be allocated from the page allocator.
The alloc_slab file is shows how many times a new slab had to
be allocated from the page allocator. It can be written to
clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/alloc_slowpath
......@@ -87,9 +90,10 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The alloc_slowpath file is read-only and specifies how many
objects have been allocated using the slow path because of a
refill or allocation from a partial or new slab.
The alloc_slowpath file shows how many objects have been
allocated using the slow path because of a refill or
allocation from a partial or new slab. It can be written to
clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/cache_dma
......@@ -117,10 +121,11 @@ KernelVersion: 2.6.31
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file cpuslab_flush is read-only and specifies how many
times a cache's cpu slabs have been flushed as the result of
destroying or shrinking a cache, a cpu going offline, or as
the result of forcing an allocation from a certain node.
The file cpuslab_flush shows how many times a cache's cpu slabs
have been flushed as the result of destroying or shrinking a
cache, a cpu going offline, or as the result of forcing an
allocation from a certain node. It can be written to clear the
current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/ctor
......@@ -139,8 +144,8 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file deactivate_empty is read-only and specifies how many
times an empty cpu slab was deactivated.
The deactivate_empty file shows how many times an empty cpu slab
was deactivated. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/deactivate_full
......@@ -149,8 +154,8 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file deactivate_full is read-only and specifies how many
times a full cpu slab was deactivated.
The deactivate_full file shows how many times a full cpu slab
was deactivated. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/deactivate_remote_frees
......@@ -159,9 +164,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file deactivate_remote_frees is read-only and specifies how
many times a cpu slab has been deactivated and contained free
objects that were freed remotely.
The deactivate_remote_frees file shows how many times a cpu slab
has been deactivated and contained free objects that were freed
remotely. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/deactivate_to_head
......@@ -170,9 +175,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file deactivate_to_head is read-only and specifies how
many times a partial cpu slab was deactivated and added to the
head of its node's partial list.
The deactivate_to_head file shows how many times a partial cpu
slab was deactivated and added to the head of its node's partial
list. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/deactivate_to_tail
......@@ -181,9 +186,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file deactivate_to_tail is read-only and specifies how
many times a partial cpu slab was deactivated and added to the
tail of its node's partial list.
The deactivate_to_tail file shows how many times a partial cpu
slab was deactivated and added to the tail of its node's partial
list. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/destroy_by_rcu
......@@ -201,9 +206,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file free_add_partial is read-only and specifies how many
times an object has been freed in a full slab so that it had to
added to its node's partial list.
The free_add_partial file shows how many times an object has
been freed in a full slab so that it had to added to its node's
partial list. It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/free_calls
......@@ -222,9 +227,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The free_fastpath file is read-only and specifies how many
objects have been freed using the fast path because it was an
object from the cpu slab.
The free_fastpath file shows how many objects have been freed
using the fast path because it was an object from the cpu slab.
It can be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/free_frozen
......@@ -233,9 +238,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The free_frozen file is read-only and specifies how many
objects have been freed to a frozen slab (i.e. a remote cpu
slab).
The free_frozen file shows how many objects have been freed to
a frozen slab (i.e. a remote cpu slab). It can be written to
clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/free_remove_partial
......@@ -244,9 +249,10 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file free_remove_partial is read-only and specifies how
many times an object has been freed to a now-empty slab so
that it had to be removed from its node's partial list.
The free_remove_partial file shows how many times an object has
been freed to a now-empty slab so that it had to be removed from
its node's partial list. It can be written to clear the current
count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/free_slab
......@@ -255,8 +261,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The free_slab file is read-only and specifies how many times an
empty slab has been freed back to the page allocator.
The free_slab file shows how many times an empty slab has been
freed back to the page allocator. It can be written to clear
the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/free_slowpath
......@@ -265,9 +272,9 @@ KernelVersion: 2.6.25
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The free_slowpath file is read-only and specifies how many
objects have been freed using the slow path (i.e. to a full or
partial slab).
The free_slowpath file shows how many objects have been freed
using the slow path (i.e. to a full or partial slab). It can
be written to clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/hwcache_align
......@@ -346,10 +353,10 @@ KernelVersion: 2.6.26
Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>
Description:
The file order_fallback is read-only and specifies how many
times an allocation of a new slab has not been possible at the
cache's order and instead fallen back to its minimum possible
order.
The order_fallback file shows how many times an allocation of a
new slab has not been possible at the cache's order and instead
fallen back to its minimum possible order. It can be written to
clear the current count.
Available when CONFIG_SLUB_STATS is enabled.
What: /sys/kernel/slab/cache/partial
......
Documentation/ABI/testing/sysfs-memory-page-offline 0 → 100644
浏览文件 @ 67cbf8a2
What: /sys/devices/system/memory/soft_offline_page
Date: Sep 2009
KernelVersion: 2.6.33
Contact: andi@firstfloor.org
Description:
Soft-offline the memory page containing the physical address
written into this file. Input is a hex number specifying the
physical address of the page. The kernel will then attempt
to soft-offline it, by moving the contents elsewhere or
dropping it if possible. The kernel will then be placed
on the bad page list and never be reused.
The offlining is done in kernel specific granuality.
Normally it's the base page size of the kernel, but
this might change.
The page must be still accessible, not poisoned. The
kernel will never kill anything for this, but rather
fail the offline. Return value is the size of the
number, or a error when the offlining failed. Reading
the file is not allowed.
What: /sys/devices/system/memory/hard_offline_page
Date: Sep 2009
KernelVersion: 2.6.33
Contact: andi@firstfloor.org
Description:
Hard-offline the memory page containing the physical
address written into this file. Input is a hex number
specifying the physical address of the page. The
kernel will then attempt to hard-offline the page, by
trying to drop the page or killing any owner or
triggering IO errors if needed. Note this may kill
any processes owning the page. The kernel will avoid
to access this page assuming it's poisoned by the
hardware.
The offlining is done in kernel specific granuality.
Normally it's the base page size of the kernel, but
this might change.
Return value is the size of the number, or a error when
the offlining failed.
Reading the file is not allowed.
Documentation/Changes
浏览文件 @ 67cbf8a2
......@@ -49,6 +49,8 @@ o oprofile 0.9 # oprofiled --version
o udev 081 # udevinfo -V
o grub 0.93 # grub --version
o mcelog 0.6
o iptables 1.4.1 # iptables -V
Kernel compilation
==================
......
Documentation/DocBook/Makefile
浏览文件 @ 67cbf8a2
......@@ -8,7 +8,7 @@
DOCBOOKS := z8530book.xml mcabook.xml device-drivers.xml \
kernel-hacking.xml kernel-locking.xml deviceiobook.xml \
procfs-guide.xml writing_usb_driver.xml networking.xml \
writing_usb_driver.xml networking.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml kgdb.xml \
gadget.xml libata.xml mtdnand.xml librs.xml rapidio.xml \
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
......@@ -32,10 +32,10 @@ PS_METHOD = $(prefer-db2x)
###
# The targets that may be used.
PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs media
PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs xmldoclinks
BOOKS := $(addprefix $(obj)/,$(DOCBOOKS))
xmldocs: $(BOOKS)
xmldocs: $(BOOKS) xmldoclinks
sgmldocs: xmldocs
PS := $(patsubst %.xml, %.ps, $(BOOKS))
......@@ -45,15 +45,24 @@ PDF := $(patsubst %.xml, %.pdf, $(BOOKS))
pdfdocs: $(PDF)
HTML := $(sort $(patsubst %.xml, %.html, $(BOOKS)))
htmldocs: media $(HTML)
htmldocs: $(HTML)
$(call build_main_index)
$(call build_images)
MAN := $(patsubst %.xml, %.9, $(BOOKS))
mandocs: $(MAN)
media:
mkdir -p $(srctree)/Documentation/DocBook/media/
cp $(srctree)/Documentation/DocBook/dvb/*.png $(srctree)/Documentation/DocBook/v4l/*.gif $(srctree)/Documentation/DocBook/media/
build_images = mkdir -p $(objtree)/Documentation/DocBook/media/ && \
cp $(srctree)/Documentation/DocBook/dvb/*.png $(srctree)/Documentation/DocBook/v4l/*.gif $(objtree)/Documentation/DocBook/media/
xmldoclinks:
ifneq ($(objtree),$(srctree))
for dep in dvb media-entities.tmpl media-indices.tmpl v4l; do \
rm -f $(objtree)/Documentation/DocBook/$$dep \
&& ln -s $(srctree)/Documentation/DocBook/$$dep $(objtree)/Documentation/DocBook/ \
|| exit; \
done
endif
installmandocs: mandocs
mkdir -p /usr/local/man/man9/
......@@ -65,7 +74,7 @@ KERNELDOC = $(srctree)/scripts/kernel-doc
DOCPROC = $(objtree)/scripts/basic/docproc
XMLTOFLAGS = -m $(srctree)/Documentation/DocBook/stylesheet.xsl
#XMLTOFLAGS += --skip-validation
XMLTOFLAGS += --skip-validation
###
# DOCPROC is used for two purposes:
......@@ -101,17 +110,6 @@ endif
# Changes in kernel-doc force a rebuild of all documentation
$(BOOKS): $(KERNELDOC)
###
# procfs guide uses a .c file as example code.
# This requires an explicit dependency
C-procfs-example = procfs_example.xml
C-procfs-example2 = $(addprefix $(obj)/,$(C-procfs-example))
$(obj)/procfs-guide.xml: $(C-procfs-example2)
# List of programs to build
##oops, this is a kernel module::hostprogs-y := procfs_example
obj-m += procfs_example.o
# Tell kbuild to always build the programs
always := $(hostprogs-y)
......@@ -238,7 +236,7 @@ clean-files := $(DOCBOOKS) \
$(patsubst %.xml, %.pdf, $(DOCBOOKS)) \
$(patsubst %.xml, %.html, $(DOCBOOKS)) \
$(patsubst %.xml, %.9, $(DOCBOOKS)) \
$(C-procfs-example) $(index)
$(index)
clean-dirs := $(patsubst %.xml,%,$(DOCBOOKS)) man
......
Documentation/DocBook/media-entities.tmpl
浏览文件 @ 67cbf8a2
......@@ -23,6 +23,7 @@
<!ENTITY VIDIOC-ENUMINPUT "<link linkend='vidioc-enuminput'><constant>VIDIOC_ENUMINPUT</constant></link>">
<!ENTITY VIDIOC-ENUMOUTPUT "<link linkend='vidioc-enumoutput'><constant>VIDIOC_ENUMOUTPUT</constant></link>">
<!ENTITY VIDIOC-ENUMSTD "<link linkend='vidioc-enumstd'><constant>VIDIOC_ENUMSTD</constant></link>">
<!ENTITY VIDIOC-ENUM-DV-PRESETS "<link linkend='vidioc-enum-dv-presets'><constant>VIDIOC_ENUM_DV_PRESETS</constant></link>">
<!ENTITY VIDIOC-ENUM-FMT "<link linkend='vidioc-enum-fmt'><constant>VIDIOC_ENUM_FMT</constant></link>">
<!ENTITY VIDIOC-ENUM-FRAMEINTERVALS "<link linkend='vidioc-enum-frameintervals'><constant>VIDIOC_ENUM_FRAMEINTERVALS</constant></link>">
<!ENTITY VIDIOC-ENUM-FRAMESIZES "<link linkend='vidioc-enum-framesizes'><constant>VIDIOC_ENUM_FRAMESIZES</constant></link>">
......@@ -30,6 +31,8 @@
<!ENTITY VIDIOC-G-AUDOUT "<link linkend='vidioc-g-audioout'><constant>VIDIOC_G_AUDOUT</constant></link>">
<!ENTITY VIDIOC-G-CROP "<link linkend='vidioc-g-crop'><constant>VIDIOC_G_CROP</constant></link>">
<!ENTITY VIDIOC-G-CTRL "<link linkend='vidioc-g-ctrl'><constant>VIDIOC_G_CTRL</constant></link>">
<!ENTITY VIDIOC-G-DV-PRESET "<link linkend='vidioc-g-dv-preset'><constant>VIDIOC_G_DV_PRESET</constant></link>">
<!ENTITY VIDIOC-G-DV-TIMINGS "<link linkend='vidioc-g-dv-timings'><constant>VIDIOC_G_DV_TIMINGS</constant></link>">
<!ENTITY VIDIOC-G-ENC-INDEX "<link linkend='vidioc-g-enc-index'><constant>VIDIOC_G_ENC_INDEX</constant></link>">
<!ENTITY VIDIOC-G-EXT-CTRLS "<link linkend='vidioc-g-ext-ctrls'><constant>VIDIOC_G_EXT_CTRLS</constant></link>">
<!ENTITY VIDIOC-G-FBUF "<link linkend='vidioc-g-fbuf'><constant>VIDIOC_G_FBUF</constant></link>">
......@@ -53,6 +56,7 @@
<!ENTITY VIDIOC-QUERYCTRL "<link linkend='vidioc-queryctrl'><constant>VIDIOC_QUERYCTRL</constant></link>">
<!ENTITY VIDIOC-QUERYMENU "<link linkend='vidioc-queryctrl'><constant>VIDIOC_QUERYMENU</constant></link>">
<!ENTITY VIDIOC-QUERYSTD "<link linkend='vidioc-querystd'><constant>VIDIOC_QUERYSTD</constant></link>">
<!ENTITY VIDIOC-QUERY-DV-PRESET "<link linkend='vidioc-query-dv-preset'><constant>VIDIOC_QUERY_DV_PRESET</constant></link>">
<!ENTITY VIDIOC-REQBUFS "<link linkend='vidioc-reqbufs'><constant>VIDIOC_REQBUFS</constant></link>">
<!ENTITY VIDIOC-STREAMOFF "<link linkend='vidioc-streamon'><constant>VIDIOC_STREAMOFF</constant></link>">
<!ENTITY VIDIOC-STREAMON "<link linkend='vidioc-streamon'><constant>VIDIOC_STREAMON</constant></link>">
......@@ -60,6 +64,8 @@
<!ENTITY VIDIOC-S-AUDOUT "<link linkend='vidioc-g-audioout'><constant>VIDIOC_S_AUDOUT</constant></link>">
<!ENTITY VIDIOC-S-CROP "<link linkend='vidioc-g-crop'><constant>VIDIOC_S_CROP</constant></link>">
<!ENTITY VIDIOC-S-CTRL "<link linkend='vidioc-g-ctrl'><constant>VIDIOC_S_CTRL</constant></link>">
<!ENTITY VIDIOC-S-DV-PRESET "<link linkend='vidioc-g-dv-preset'><constant>VIDIOC_S_DV_PRESET</constant></link>">
<!ENTITY VIDIOC-S-DV-TIMINGS "<link linkend='vidioc-g-dv-timings'><constant>VIDIOC_S_DV_TIMINGS</constant></link>">
<!ENTITY VIDIOC-S-EXT-CTRLS "<link linkend='vidioc-g-ext-ctrls'><constant>VIDIOC_S_EXT_CTRLS</constant></link>">
<!ENTITY VIDIOC-S-FBUF "<link linkend='vidioc-g-fbuf'><constant>VIDIOC_S_FBUF</constant></link>">
<!ENTITY VIDIOC-S-FMT "<link linkend='vidioc-g-fmt'><constant>VIDIOC_S_FMT</constant></link>">
......@@ -118,6 +124,7 @@
<!-- Structures -->
<!ENTITY v4l2-audio "struct&nbsp;<link linkend='v4l2-audio'>v4l2_audio</link>">
<!ENTITY v4l2-audioout "struct&nbsp;<link linkend='v4l2-audioout'>v4l2_audioout</link>">
<!ENTITY v4l2-bt-timings "struct&nbsp;<link linkend='v4l2-bt-timings'>v4l2_bt_timings</link>">
<!ENTITY v4l2-buffer "struct&nbsp;<link linkend='v4l2-buffer'>v4l2_buffer</link>">
<!ENTITY v4l2-capability "struct&nbsp;<link linkend='v4l2-capability'>v4l2_capability</link>">
<!ENTITY v4l2-captureparm "struct&nbsp;<link linkend='v4l2-captureparm'>v4l2_captureparm</link>">
......@@ -128,6 +135,9 @@
<!ENTITY v4l2-dbg-chip-ident "struct&nbsp;<link linkend='v4l2-dbg-chip-ident'>v4l2_dbg_chip_ident</link>">
<!ENTITY v4l2-dbg-match "struct&nbsp;<link linkend='v4l2-dbg-match'>v4l2_dbg_match</link>">
<!ENTITY v4l2-dbg-register "struct&nbsp;<link linkend='v4l2-dbg-register'>v4l2_dbg_register</link>">
<!ENTITY v4l2-dv-enum-preset "struct&nbsp;<link linkend='v4l2-dv-enum-preset'>v4l2_dv_enum_preset</link>">
<!ENTITY v4l2-dv-preset "struct&nbsp;<link linkend='v4l2-dv-preset'>v4l2_dv_preset</link>">
<!ENTITY v4l2-dv-timings "struct&nbsp;<link linkend='v4l2-dv-timings'>v4l2_dv_timings</link>">
<!ENTITY v4l2-enc-idx "struct&nbsp;<link linkend='v4l2-enc-idx'>v4l2_enc_idx</link>">
<!ENTITY v4l2-enc-idx-entry "struct&nbsp;<link linkend='v4l2-enc-idx-entry'>v4l2_enc_idx_entry</link>">
<!ENTITY v4l2-encoder-cmd "struct&nbsp;<link linkend='v4l2-encoder-cmd'>v4l2_encoder_cmd</link>">
......@@ -243,6 +253,10 @@
<!ENTITY sub-enumaudioout SYSTEM "v4l/vidioc-enumaudioout.xml">
<!ENTITY sub-enuminput SYSTEM "v4l/vidioc-enuminput.xml">
<!ENTITY sub-enumoutput SYSTEM "v4l/vidioc-enumoutput.xml">
<!ENTITY sub-enum-dv-presets SYSTEM "v4l/vidioc-enum-dv-presets.xml">
<!ENTITY sub-g-dv-preset SYSTEM "v4l/vidioc-g-dv-preset.xml">
<!ENTITY sub-query-dv-preset SYSTEM "v4l/vidioc-query-dv-preset.xml">
<!ENTITY sub-g-dv-timings SYSTEM "v4l/vidioc-g-dv-timings.xml">
<!ENTITY sub-enumstd SYSTEM "v4l/vidioc-enumstd.xml">
<!ENTITY sub-g-audio SYSTEM "v4l/vidioc-g-audio.xml">
<!ENTITY sub-g-audioout SYSTEM "v4l/vidioc-g-audioout.xml">
......@@ -333,6 +347,10 @@
<!ENTITY enumaudioout SYSTEM "v4l/vidioc-enumaudioout.xml">
<!ENTITY enuminput SYSTEM "v4l/vidioc-enuminput.xml">
<!ENTITY enumoutput SYSTEM "v4l/vidioc-enumoutput.xml">
<!ENTITY enum-dv-presets SYSTEM "v4l/vidioc-enum-dv-presets.xml">
<!ENTITY g-dv-preset SYSTEM "v4l/vidioc-g-dv-preset.xml">
<!ENTITY query-dv-preset SYSTEM "v4l/vidioc-query-dv-preset.xml">
<!ENTITY g-dv-timings SYSTEM "v4l/vidioc-g-dv-timings.xml">
<!ENTITY enumstd SYSTEM "v4l/vidioc-enumstd.xml">
<!ENTITY g-audio SYSTEM "v4l/vidioc-g-audio.xml">
<!ENTITY g-audioout SYSTEM "v4l/vidioc-g-audioout.xml">
......
Documentation/DocBook/media-indices.tmpl
浏览文件 @ 67cbf8a2
......@@ -36,6 +36,7 @@
<indexentry><primaryie>enum&nbsp;<link linkend='v4l2-preemphasis'>v4l2_preemphasis</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-audio'>v4l2_audio</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-audioout'>v4l2_audioout</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-bt-timings'>v4l2_bt_timings</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-buffer'>v4l2_buffer</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-capability'>v4l2_capability</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-captureparm'>v4l2_captureparm</link></primaryie></indexentry>
......@@ -46,6 +47,9 @@
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dbg-chip-ident'>v4l2_dbg_chip_ident</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dbg-match'>v4l2_dbg_match</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dbg-register'>v4l2_dbg_register</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dv-enum-preset'>v4l2_dv_enum_preset</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dv-preset'>v4l2_dv_preset</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-dv-timings'>v4l2_dv_timings</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-enc-idx'>v4l2_enc_idx</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-enc-idx-entry'>v4l2_enc_idx_entry</link></primaryie></indexentry>
<indexentry><primaryie>struct&nbsp;<link linkend='v4l2-encoder-cmd'>v4l2_encoder_cmd</link></primaryie></indexentry>
......
Documentation/DocBook/procfs-guide.tmpl 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
Documentation/DocBook/procfs_example.c 已删除 100644 → 0
浏览文件 @ 6c941c85
/*
* procfs_example.c: an example proc interface
*
* Copyright (C) 2001, Erik Mouw (mouw@nl.linux.org)
*
* This file accompanies the procfs-guide in the Linux kernel
* source. Its main use is to demonstrate the concepts and
* functions described in the guide.
*
* This software has been developed while working on the LART
* computing board (http://www.lartmaker.nl), which was sponsored
* by the Delt University of Technology projects Mobile Multi-media
* Communications and Ubiquitous Communications.
*
* This program is free software; you can redistribute
* it and/or modify it under the terms of the GNU General
* Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your
* option) any later version.
*
* This program is distributed in the hope that it will be
* useful, but WITHOUT ANY WARRANTY; without even the implied
* warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
* PURPOSE. See the GNU General Public License for more
* details.
*
* You should have received a copy of the GNU General Public
* License along with this program; if not, write to the
* Free Software Foundation, Inc., 59 Temple Place,
* Suite 330, Boston, MA 02111-1307 USA
*
*/
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/init.h>
#include <linux/proc_fs.h>
#include <linux/jiffies.h>
#include <asm/uaccess.h>
#define MODULE_VERS "1.0"
#define MODULE_NAME "procfs_example"
#define FOOBAR_LEN 8
struct fb_data_t {
char name[FOOBAR_LEN + 1];
char value[FOOBAR_LEN + 1];
};
static struct proc_dir_entry *example_dir, *foo_file,
*bar_file, *jiffies_file, *symlink;
struct fb_data_t foo_data, bar_data;
static int proc_read_jiffies(char *page, char **start,
off_t off, int count,
int *eof, void *data)
{
int len;
len = sprintf(page, "jiffies = %ld\n",
jiffies);
return len;
}
static int proc_read_foobar(char *page, char **start,
off_t off, int count,
int *eof, void *data)
{
int len;
struct fb_data_t *fb_data = (struct fb_data_t *)data;
/* DON'T DO THAT - buffer overruns are bad */
len = sprintf(page, "%s = '%s'\n",
fb_data->name, fb_data->value);
return len;
}
static int proc_write_foobar(struct file *file,
const char *buffer,
unsigned long count,
void *data)
{
int len;
struct fb_data_t *fb_data = (struct fb_data_t *)data;
if(count > FOOBAR_LEN)
len = FOOBAR_LEN;
else
len = count;
if(copy_from_user(fb_data->value, buffer, len))
return -EFAULT;
fb_data->value[len] = '\0';
return len;
}
static int __init init_procfs_example(void)
{
int rv = 0;
/* create directory */
example_dir = proc_mkdir(MODULE_NAME, NULL);
if(example_dir == NULL) {
rv = -ENOMEM;
goto out;
}
/* create jiffies using convenience function */
jiffies_file = create_proc_read_entry("jiffies",
0444, example_dir,
proc_read_jiffies,
NULL);
if(jiffies_file == NULL) {
rv = -ENOMEM;
goto no_jiffies;
}
/* create foo and bar files using same callback
* functions
*/
foo_file = create_proc_entry("foo", 0644, example_dir);
if(foo_file == NULL) {
rv = -ENOMEM;
goto no_foo;
}
strcpy(foo_data.name, "foo");
strcpy(foo_data.value, "foo");
foo_file->data = &foo_data;
foo_file->read_proc = proc_read_foobar;
foo_file->write_proc = proc_write_foobar;
bar_file = create_proc_entry("bar", 0644, example_dir);
if(bar_file == NULL) {
rv = -ENOMEM;
goto no_bar;
}
strcpy(bar_data.name, "bar");
strcpy(bar_data.value, "bar");
bar_file->data = &bar_data;
bar_file->read_proc = proc_read_foobar;
bar_file->write_proc = proc_write_foobar;
/* create symlink */
symlink = proc_symlink("jiffies_too", example_dir,
"jiffies");
if(symlink == NULL) {
rv = -ENOMEM;
goto no_symlink;
}
/* everything OK */
printk(KERN_INFO "%s %s initialised\n",
MODULE_NAME, MODULE_VERS);
return 0;
no_symlink:
remove_proc_entry("bar", example_dir);
no_bar:
remove_proc_entry("foo", example_dir);
no_foo:
remove_proc_entry("jiffies", example_dir);
no_jiffies:
remove_proc_entry(MODULE_NAME, NULL);
out:
return rv;
}
static void __exit cleanup_procfs_example(void)
{
remove_proc_entry("jiffies_too", example_dir);
remove_proc_entry("bar", example_dir);
remove_proc_entry("foo", example_dir);
remove_proc_entry("jiffies", example_dir);
remove_proc_entry(MODULE_NAME, NULL);
printk(KERN_INFO "%s %s removed\n",
MODULE_NAME, MODULE_VERS);
}
module_init(init_procfs_example);
module_exit(cleanup_procfs_example);
MODULE_AUTHOR("Erik Mouw");
MODULE_DESCRIPTION("procfs examples");
MODULE_LICENSE("GPL");
Documentation/DocBook/v4l/common.xml
浏览文件 @ 67cbf8a2
......@@ -716,6 +716,41 @@ if (-1 == ioctl (fd, &VIDIOC-S-STD;, &amp;std_id)) {
}
</programlisting>
</example>
<section id="dv-timings">
<title>Digital Video (DV) Timings</title>
<para>
The video standards discussed so far has been dealing with Analog TV and the
corresponding video timings. Today there are many more different hardware interfaces
such as High Definition TV interfaces (HDMI), VGA, DVI connectors etc., that carry
video signals and there is a need to extend the API to select the video timings
for these interfaces. Since it is not possible to extend the &v4l2-std-id; due to
the limited bits available, a new set of IOCTLs is added to set/get video timings at
the input and output: </para><itemizedlist>
<listitem>
<para>DV Presets: Digital Video (DV) presets. These are IDs representing a
video timing at the input/output. Presets are pre-defined timings implemented
by the hardware according to video standards. A __u32 data type is used to represent
a preset unlike the bit mask that is used in &v4l2-std-id; allowing future extensions
to support as many different presets as needed.</para>
</listitem>
<listitem>
<para>Custom DV Timings: This will allow applications to define more detailed
custom video timings for the interface. This includes parameters such as width, height,
polarities, frontporch, backporch etc.
</para>
</listitem>
</itemizedlist>
<para>To enumerate and query the attributes of DV presets supported by a device,
applications use the &VIDIOC-ENUM-DV-PRESETS; ioctl. To get the current DV preset,
applications use the &VIDIOC-G-DV-PRESET; ioctl and to set a preset they use the
&VIDIOC-S-DV-PRESET; ioctl.</para>
<para>To set custom DV timings for the device, applications use the
&VIDIOC-S-DV-TIMINGS; ioctl and to get current custom DV timings they use the
&VIDIOC-G-DV-TIMINGS; ioctl.</para>
<para>Applications can make use of the <xref linkend="input-capabilities" /> and
<xref linkend="output-capabilities"/> flags to decide what ioctls are available to set the
video timings for the device.</para>
</section>
</section>
&sub-controls;
......
Documentation/DocBook/v4l/compat.xml
浏览文件 @ 67cbf8a2
......@@ -2291,8 +2291,8 @@ was renamed to <structname id="v4l2-chip-ident-old">v4l2_chip_ident_old</structn
<listitem>
<para>New control <constant>V4L2_CID_COLORFX</constant> was added.</para>
</listitem>
</orderedlist>
</section>
</orderedlist>
</section>
<section>
<title>V4L2 in Linux 2.6.32</title>
<orderedlist>
......@@ -2322,8 +2322,16 @@ more information.</para>
<listitem>
<para>Added Remote Controller chapter, describing the default Remote Controller mapping for media devices.</para>
</listitem>
</orderedlist>
</section>
</orderedlist>
</section>
<section>
<title>V4L2 in Linux 2.6.33</title>
<orderedlist>
<listitem>
<para>Added support for Digital Video timings in order to support HDTV receivers and transmitters.</para>
</listitem>
</orderedlist>
</section>
</section>
<section id="other">
......
Documentation/DocBook/v4l/v4l2.xml
浏览文件 @ 67cbf8a2
......@@ -74,6 +74,17 @@ Remote Controller chapter.</contrib>
</address>
</affiliation>
</author>
<author>
<firstname>Muralidharan</firstname>
<surname>Karicheri</surname>
<contrib>Documented the Digital Video timings API.</contrib>
<affiliation>
<address>
<email>m-karicheri2@ti.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<copyright>
......@@ -89,7 +100,7 @@ Remote Controller chapter.</contrib>
<year>2008</year>
<year>2009</year>
<holder>Bill Dirks, Michael H. Schimek, Hans Verkuil, Martin
Rubli, Andy Walls, Mauro Carvalho Chehab</holder>
Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab</holder>
</copyright>
<legalnotice>
<para>Except when explicitly stated as GPL, programming examples within
......@@ -102,6 +113,13 @@ structs, ioctls) must be noted in more detail in the history chapter
(compat.sgml), along with the possible impact on existing drivers and
applications. -->
<revision>
<revnumber>2.6.33</revnumber>
<date>2009-12-03</date>
<authorinitials>mk</authorinitials>
<revremark>Added documentation for the Digital Video timings API.</revremark>
</revision>
<revision>
<revnumber>2.6.32</revnumber>
<date>2009-08-31</date>
......@@ -355,7 +373,7 @@ and discussions on the V4L mailing list.</revremark>
</partinfo>
<title>Video for Linux Two API Specification</title>
<subtitle>Revision 2.6.32</subtitle>
<subtitle>Revision 2.6.33</subtitle>
<chapter id="common">
&sub-common;
......@@ -411,6 +429,7 @@ and discussions on the V4L mailing list.</revremark>
&sub-encoder-cmd;
&sub-enumaudio;
&sub-enumaudioout;
&sub-enum-dv-presets;
&sub-enum-fmt;
&sub-enum-framesizes;
&sub-enum-frameintervals;
......@@ -421,6 +440,8 @@ and discussions on the V4L mailing list.</revremark>
&sub-g-audioout;
&sub-g-crop;
&sub-g-ctrl;
&sub-g-dv-preset;
&sub-g-dv-timings;
&sub-g-enc-index;
&sub-g-ext-ctrls;
&sub-g-fbuf;
......@@ -441,6 +462,7 @@ and discussions on the V4L mailing list.</revremark>
&sub-querybuf;
&sub-querycap;
&sub-queryctrl;
&sub-query-dv-preset;
&sub-querystd;
&sub-reqbufs;
&sub-s-hw-freq-seek;
......
Documentation/DocBook/v4l/videodev2.h.xml
浏览文件 @ 67cbf8a2
......@@ -733,6 +733,99 @@ struct <link linkend="v4l2-standard">v4l2_standard</link> {
__u32 reserved[4];
};
/*
* V I D E O T I M I N G S D V P R E S E T
*/
struct <link linkend="v4l2-dv-preset">v4l2_dv_preset</link> {
__u32 preset;
__u32 reserved[4];
};
/*
* D V P R E S E T S E N U M E R A T I O N
*/
struct <link linkend="v4l2-dv-enum-preset">v4l2_dv_enum_preset</link> {
__u32 index;
__u32 preset;
__u8 name[32]; /* Name of the preset timing */
__u32 width;
__u32 height;
__u32 reserved[4];
};
/*
* D V P R E S E T V A L U E S
*/
#define V4L2_DV_INVALID 0
#define V4L2_DV_480P59_94 1 /* BT.1362 */
#define V4L2_DV_576P50 2 /* BT.1362 */
#define V4L2_DV_720P24 3 /* SMPTE 296M */
#define V4L2_DV_720P25 4 /* SMPTE 296M */
#define V4L2_DV_720P30 5 /* SMPTE 296M */
#define V4L2_DV_720P50 6 /* SMPTE 296M */
#define V4L2_DV_720P59_94 7 /* SMPTE 274M */
#define V4L2_DV_720P60 8 /* SMPTE 274M/296M */
#define V4L2_DV_1080I29_97 9 /* BT.1120/ SMPTE 274M */
#define V4L2_DV_1080I30 10 /* BT.1120/ SMPTE 274M */
#define V4L2_DV_1080I25 11 /* BT.1120 */
#define V4L2_DV_1080I50 12 /* SMPTE 296M */
#define V4L2_DV_1080I60 13 /* SMPTE 296M */
#define V4L2_DV_1080P24 14 /* SMPTE 296M */
#define V4L2_DV_1080P25 15 /* SMPTE 296M */
#define V4L2_DV_1080P30 16 /* SMPTE 296M */
#define V4L2_DV_1080P50 17 /* BT.1120 */
#define V4L2_DV_1080P60 18 /* BT.1120 */
/*
* D V B T T I M I N G S
*/
/* BT.656/BT.1120 timing data */
struct <link linkend="v4l2-bt-timings">v4l2_bt_timings</link> {
__u32 width; /* width in pixels */
__u32 height; /* height in lines */
__u32 interlaced; /* Interlaced or progressive */
__u32 polarities; /* Positive or negative polarity */
__u64 pixelclock; /* Pixel clock in HZ. Ex. 74.25MHz-&gt;74250000 */
__u32 hfrontporch; /* Horizpontal front porch in pixels */
__u32 hsync; /* Horizontal Sync length in pixels */
__u32 hbackporch; /* Horizontal back porch in pixels */
__u32 vfrontporch; /* Vertical front porch in pixels */
__u32 vsync; /* Vertical Sync length in lines */
__u32 vbackporch; /* Vertical back porch in lines */
__u32 il_vfrontporch; /* Vertical front porch for bottom field of
* interlaced field formats
*/
__u32 il_vsync; /* Vertical sync length for bottom field of
* interlaced field formats
*/
__u32 il_vbackporch; /* Vertical back porch for bottom field of
* interlaced field formats
*/
__u32 reserved[16];
} __attribute__ ((packed));
/* Interlaced or progressive format */
#define V4L2_DV_PROGRESSIVE 0
#define V4L2_DV_INTERLACED 1
/* Polarities. If bit is not set, it is assumed to be negative polarity */
#define V4L2_DV_VSYNC_POS_POL 0x00000001
#define V4L2_DV_HSYNC_POS_POL 0x00000002
/* DV timings */
struct <link linkend="v4l2-dv-timings">v4l2_dv_timings</link> {
__u32 type;
union {
struct <link linkend="v4l2-bt-timings">v4l2_bt_timings</link> bt;
__u32 reserved[32];
};
} __attribute__ ((packed));
/* Values for the type field */
#define V4L2_DV_BT_656_1120 0 /* BT.656/1120 timing type */
/*
* V I D E O I N P U T S
*/
......@@ -744,7 +837,8 @@ struct <link linkend="v4l2-input">v4l2_input</link> {
__u32 tuner; /* Associated tuner */
v4l2_std_id std;
__u32 status;
__u32 reserved[4];
__u32 capabilities;
__u32 reserved[3];
};
/* Values for the 'type' field */
......@@ -775,6 +869,11 @@ struct <link linkend="v4l2-input">v4l2_input</link> {
#define V4L2_IN_ST_NO_ACCESS 0x02000000 /* Conditional access denied */
#define V4L2_IN_ST_VTR 0x04000000 /* VTR time constant */
/* capabilities flags */
#define V4L2_IN_CAP_PRESETS 0x00000001 /* Supports S_DV_PRESET */
#define V4L2_IN_CAP_CUSTOM_TIMINGS 0x00000002 /* Supports S_DV_TIMINGS */
#define V4L2_IN_CAP_STD 0x00000004 /* Supports S_STD */
/*
* V I D E O O U T P U T S
*/
......@@ -785,13 +884,19 @@ struct <link linkend="v4l2-output">v4l2_output</link> {
__u32 audioset; /* Associated audios (bitfield) */
__u32 modulator; /* Associated modulator */
v4l2_std_id std;
__u32 reserved[4];
__u32 capabilities;
__u32 reserved[3];
};
/* Values for the 'type' field */
#define V4L2_OUTPUT_TYPE_MODULATOR 1
#define V4L2_OUTPUT_TYPE_ANALOG 2
#define V4L2_OUTPUT_TYPE_ANALOGVGAOVERLAY 3
/* capabilities flags */
#define V4L2_OUT_CAP_PRESETS 0x00000001 /* Supports S_DV_PRESET */
#define V4L2_OUT_CAP_CUSTOM_TIMINGS 0x00000002 /* Supports S_DV_TIMINGS */
#define V4L2_OUT_CAP_STD 0x00000004 /* Supports S_STD */
/*
* C O N T R O L S
*/
......@@ -1626,6 +1731,13 @@ struct <link linkend="v4l2-dbg-chip-ident">v4l2_dbg_chip_ident</link> {
#endif
#define VIDIOC_S_HW_FREQ_SEEK _IOW('V', 82, struct <link linkend="v4l2-hw-freq-seek">v4l2_hw_freq_seek</link>)
#define VIDIOC_ENUM_DV_PRESETS _IOWR('V', 83, struct <link linkend="v4l2-dv-enum-preset">v4l2_dv_enum_preset</link>)
#define VIDIOC_S_DV_PRESET _IOWR('V', 84, struct <link linkend="v4l2-dv-preset">v4l2_dv_preset</link>)
#define VIDIOC_G_DV_PRESET _IOWR('V', 85, struct <link linkend="v4l2-dv-preset">v4l2_dv_preset</link>)
#define VIDIOC_QUERY_DV_PRESET _IOR('V', 86, struct <link linkend="v4l2-dv-preset">v4l2_dv_preset</link>)
#define VIDIOC_S_DV_TIMINGS _IOWR('V', 87, struct <link linkend="v4l2-dv-timings">v4l2_dv_timings</link>)
#define VIDIOC_G_DV_TIMINGS _IOWR('V', 88, struct <link linkend="v4l2-dv-timings">v4l2_dv_timings</link>)
/* Reminder: when adding new ioctls please add support for them to
drivers/media/video/v4l2-compat-ioctl32.c as well! */
......
Documentation/DocBook/v4l/vidioc-enum-dv-presets.xml 0 → 100644
浏览文件 @ 67cbf8a2
<refentry id="vidioc-enum-dv-presets">
<refmeta>
<refentrytitle>ioctl VIDIOC_ENUM_DV_PRESETS</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_ENUM_DV_PRESETS</refname>
<refpurpose>Enumerate supported Digital Video presets</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>struct v4l2_dv_enum_preset *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_ENUM_DV_PRESETS</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>To query the attributes of a DV preset, applications initialize the
<structfield>index</structfield> field and zero the reserved array of &v4l2-dv-enum-preset;
and call the <constant>VIDIOC_ENUM_DV_PRESETS</constant> ioctl with a pointer to this
structure. Drivers fill the rest of the structure or return an
&EINVAL; when the index is out of bounds. To enumerate all DV Presets supported,
applications shall begin at index zero, incrementing by one until the
driver returns <errorcode>EINVAL</errorcode>. Drivers may enumerate a
different set of DV presets after switching the video input or
output.</para>
<table pgwide="1" frame="none" id="v4l2-dv-enum-preset">
<title>struct <structname>v4l2_dv_enum_presets</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>index</structfield></entry>
<entry>Number of the DV preset, set by the
application.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>preset</structfield></entry>
<entry>This field identifies one of the DV preset values listed in <xref linkend="v4l2-dv-presets-vals"/>.</entry>
</row>
<row>
<entry>__u8</entry>
<entry><structfield>name</structfield>[24]</entry>
<entry>Name of the preset, a NUL-terminated ASCII string, for example: "720P-60", "1080I-60". This information is
intended for the user.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>width</structfield></entry>
<entry>Width of the active video in pixels for the DV preset.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>height</structfield></entry>
<entry>Height of the active video in lines for the DV preset.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[4]</entry>
<entry>Reserved for future extensions. Drivers must set the array to zero.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="v4l2-dv-presets-vals">
<title>struct <structname>DV Presets</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>Preset</entry>
<entry>Preset value</entry>
<entry>Description</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry></entry>
</row>
<row>
<entry>V4L2_DV_INVALID</entry>
<entry>0</entry>
<entry>Invalid preset value.</entry>
</row>
<row>
<entry>V4L2_DV_480P59_94</entry>
<entry>1</entry>
<entry>720x480 progressive video at 59.94 fps as per BT.1362.</entry>
</row>
<row>
<entry>V4L2_DV_576P50</entry>
<entry>2</entry>
<entry>720x576 progressive video at 50 fps as per BT.1362.</entry>
</row>
<row>
<entry>V4L2_DV_720P24</entry>
<entry>3</entry>
<entry>1280x720 progressive video at 24 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_720P25</entry>
<entry>4</entry>
<entry>1280x720 progressive video at 25 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_720P30</entry>
<entry>5</entry>
<entry>1280x720 progressive video at 30 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_720P50</entry>
<entry>6</entry>
<entry>1280x720 progressive video at 50 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_720P59_94</entry>
<entry>7</entry>
<entry>1280x720 progressive video at 59.94 fps as per SMPTE 274M.</entry>
</row>
<row>
<entry>V4L2_DV_720P60</entry>
<entry>8</entry>
<entry>1280x720 progressive video at 60 fps as per SMPTE 274M/296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080I29_97</entry>
<entry>9</entry>
<entry>1920x1080 interlaced video at 29.97 fps as per BT.1120/SMPTE 274M.</entry>
</row>
<row>
<entry>V4L2_DV_1080I30</entry>
<entry>10</entry>
<entry>1920x1080 interlaced video at 30 fps as per BT.1120/SMPTE 274M.</entry>
</row>
<row>
<entry>V4L2_DV_1080I25</entry>
<entry>11</entry>
<entry>1920x1080 interlaced video at 25 fps as per BT.1120.</entry>
</row>
<row>
<entry>V4L2_DV_1080I50</entry>
<entry>12</entry>
<entry>1920x1080 interlaced video at 50 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080I60</entry>
<entry>13</entry>
<entry>1920x1080 interlaced video at 60 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080P24</entry>
<entry>14</entry>
<entry>1920x1080 progressive video at 24 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080P25</entry>
<entry>15</entry>
<entry>1920x1080 progressive video at 25 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080P30</entry>
<entry>16</entry>
<entry>1920x1080 progressive video at 30 fps as per SMPTE 296M.</entry>
</row>
<row>
<entry>V4L2_DV_1080P50</entry>
<entry>17</entry>
<entry>1920x1080 progressive video at 50 fps as per BT.1120.</entry>
</row>
<row>
<entry>V4L2_DV_1080P60</entry>
<entry>18</entry>
<entry>1920x1080 progressive video at 60 fps as per BT.1120.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>EINVAL</errorcode></term>
<listitem>
<para>The &v4l2-dv-enum-preset; <structfield>index</structfield>
is out of bounds.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
<!--
Local Variables:
mode: sgml
sgml-parent-document: "v4l2.sgml"
indent-tabs-mode: nil
End:
-->
Documentation/DocBook/v4l/vidioc-enuminput.xml
浏览文件 @ 67cbf8a2
......@@ -124,7 +124,13 @@ current input.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[4]</entry>
<entry><structfield>capabilities</structfield></entry>
<entry>This field provides capabilities for the
input. See <xref linkend="input-capabilities" /> for flags.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[3]</entry>
<entry>Reserved for future extensions. Drivers must set
the array to zero.</entry>
</row>
......@@ -261,6 +267,34 @@ flag is set Macrovision has been detected.</entry>
</tbody>
</tgroup>
</table>
<!-- Capability flags based on video timings RFC by Muralidharan
Karicheri, titled RFC (v1.2): V4L - Support for video timings at the
input/output interface to linux-media@vger.kernel.org on 19 Oct 2009.
-->
<table frame="none" pgwide="1" id="input-capabilities">
<title>Input capabilities</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_IN_CAP_PRESETS</constant></entry>
<entry>0x00000001</entry>
<entry>This input supports setting DV presets by using VIDIOC_S_DV_PRESET.</entry>
</row>
<row>
<entry><constant>V4L2_OUT_CAP_CUSTOM_TIMINGS</constant></entry>
<entry>0x00000002</entry>
<entry>This input supports setting custom video timings by using VIDIOC_S_DV_TIMINGS.</entry>
</row>
<row>
<entry><constant>V4L2_IN_CAP_STD</constant></entry>
<entry>0x00000004</entry>
<entry>This input supports setting the TV standard by using VIDIOC_S_STD.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
......
Documentation/DocBook/v4l/vidioc-enumoutput.xml
浏览文件 @ 67cbf8a2
......@@ -114,7 +114,13 @@ details on video standards and how to switch see <xref
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[4]</entry>
<entry><structfield>capabilities</structfield></entry>
<entry>This field provides capabilities for the
output. See <xref linkend="output-capabilities" /> for flags.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[3]</entry>
<entry>Reserved for future extensions. Drivers must set
the array to zero.</entry>
</row>
......@@ -147,6 +153,34 @@ CVBS, S-Video, RGB.</entry>
</tgroup>
</table>
<!-- Capabilities flags based on video timings RFC by Muralidharan
Karicheri, titled RFC (v1.2): V4L - Support for video timings at the
input/output interface to linux-media@vger.kernel.org on 19 Oct 2009.
-->
<table frame="none" pgwide="1" id="output-capabilities">
<title>Output capabilities</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_OUT_CAP_PRESETS</constant></entry>
<entry>0x00000001</entry>
<entry>This output supports setting DV presets by using VIDIOC_S_DV_PRESET.</entry>
</row>
<row>
<entry><constant>V4L2_OUT_CAP_CUSTOM_TIMINGS</constant></entry>
<entry>0x00000002</entry>
<entry>This output supports setting custom video timings by using VIDIOC_S_DV_TIMINGS.</entry>
</row>
<row>
<entry><constant>V4L2_OUT_CAP_STD</constant></entry>
<entry>0x00000004</entry>
<entry>This output supports setting the TV standard by using VIDIOC_S_STD.</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1>
&return-value;
......
Documentation/DocBook/v4l/vidioc-g-dv-preset.xml 0 → 100644
浏览文件 @ 67cbf8a2
<refentry id="vidioc-g-dv-preset">
<refmeta>
<refentrytitle>ioctl VIDIOC_G_DV_PRESET, VIDIOC_S_DV_PRESET</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_G_DV_PRESET</refname>
<refname>VIDIOC_S_DV_PRESET</refname>
<refpurpose>Query or select the DV preset of the current input or output</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>&v4l2-dv-preset;
*<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_G_DV_PRESET, VIDIOC_S_DV_PRESET</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>To query and select the current DV preset, applications
use the <constant>VIDIOC_G_DV_PRESET</constant> and <constant>VIDIOC_S_DV_PRESET</constant>
ioctls which take a pointer to a &v4l2-dv-preset; type as argument.
Applications must zero the reserved array in &v4l2-dv-preset;.
<constant>VIDIOC_G_DV_PRESET</constant> returns a dv preset in the field
<structfield>preset</structfield> of &v4l2-dv-preset;.</para>
<para><constant>VIDIOC_S_DV_PRESET</constant> accepts a pointer to a &v4l2-dv-preset;
that has the preset value to be set. Applications must zero the reserved array in &v4l2-dv-preset;.
If the preset is not supported, it returns an &EINVAL; </para>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>EINVAL</errorcode></term>
<listitem>
<para>This ioctl is not supported, or the
<constant>VIDIOC_S_DV_PRESET</constant>,<constant>VIDIOC_S_DV_PRESET</constant> parameter was unsuitable.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>EBUSY</errorcode></term>
<listitem>
<para>The device is busy and therefore can not change the preset.</para>
</listitem>
</varlistentry>
</variablelist>
<table pgwide="1" frame="none" id="v4l2-dv-preset">
<title>struct <structname>v4l2_dv_preset</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>preset</structfield></entry>
<entry>Preset value to represent the digital video timings</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved[4]</structfield></entry>
<entry>Reserved fields for future use</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
<!--
Local Variables:
mode: sgml
sgml-parent-document: "v4l2.sgml"
indent-tabs-mode: nil
End:
-->
Documentation/DocBook/v4l/vidioc-g-dv-timings.xml 0 → 100644
浏览文件 @ 67cbf8a2
<refentry id="vidioc-g-dv-timings">
<refmeta>
<refentrytitle>ioctl VIDIOC_G_DV_TIMINGS, VIDIOC_S_DV_TIMINGS</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_G_DV_TIMINGS</refname>
<refname>VIDIOC_S_DV_TIMINGS</refname>
<refpurpose>Get or set custom DV timings for input or output</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>&v4l2-dv-timings;
*<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_G_DV_TIMINGS, VIDIOC_S_DV_TIMINGS</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>To set custom DV timings for the input or output, applications use the
<constant>VIDIOC_S_DV_TIMINGS</constant> ioctl and to get the current custom timings,
applications use the <constant>VIDIOC_G_DV_TIMINGS</constant> ioctl. The detailed timing
information is filled in using the structure &v4l2-dv-timings;. These ioctls take
a pointer to the &v4l2-dv-timings; structure as argument. If the ioctl is not supported
or the timing values are not correct, the driver returns &EINVAL;.</para>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>EINVAL</errorcode></term>
<listitem>
<para>This ioctl is not supported, or the
<constant>VIDIOC_S_DV_TIMINGS</constant> parameter was unsuitable.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>EBUSY</errorcode></term>
<listitem>
<para>The device is busy and therefore can not change the timings.</para>
</listitem>
</varlistentry>
</variablelist>
<table pgwide="1" frame="none" id="v4l2-bt-timings">
<title>struct <structname>v4l2_bt_timings</structname></title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>width</structfield></entry>
<entry>Width of the active video in pixels</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>height</structfield></entry>
<entry>Height of the active video in lines</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>interlaced</structfield></entry>
<entry>Progressive (0) or interlaced (1)</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>polarities</structfield></entry>
<entry>This is a bit mask that defines polarities of sync signals.
bit 0 (V4L2_DV_VSYNC_POS_POL) is for vertical sync polarity and bit 1 (V4L2_DV_HSYNC_POS_POL) is for horizontal sync polarity. If the bit is set
(1) it is positive polarity and if is cleared (0), it is negative polarity.</entry>
</row>
<row>
<entry>__u64</entry>
<entry><structfield>pixelclock</structfield></entry>
<entry>Pixel clock in Hz. Ex. 74.25MHz->74250000</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>hfrontporch</structfield></entry>
<entry>Horizontal front porch in pixels</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>hsync</structfield></entry>
<entry>Horizontal sync length in pixels</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>hbackporch</structfield></entry>
<entry>Horizontal back porch in pixels</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>vfrontporch</structfield></entry>
<entry>Vertical front porch in lines</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>vsync</structfield></entry>
<entry>Vertical sync length in lines</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>vbackporch</structfield></entry>
<entry>Vertical back porch in lines</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>il_vfrontporch</structfield></entry>
<entry>Vertical front porch in lines for bottom field of interlaced field formats</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>il_vsync</structfield></entry>
<entry>Vertical sync length in lines for bottom field of interlaced field formats</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>il_vbackporch</structfield></entry>
<entry>Vertical back porch in lines for bottom field of interlaced field formats</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="v4l2-dv-timings">
<title>struct <structname>v4l2_dv_timings</structname></title>
<tgroup cols="4">
&cs-str;
<tbody valign="top">
<row>
<entry>__u32</entry>
<entry><structfield>type</structfield></entry>
<entry></entry>
<entry>Type of DV timings as listed in <xref linkend="dv-timing-types"/>.</entry>
</row>
<row>
<entry>union</entry>
<entry><structfield></structfield></entry>
<entry></entry>
</row>
<row>
<entry></entry>
<entry>&v4l2-bt-timings;</entry>
<entry><structfield>bt</structfield></entry>
<entry>Timings defined by BT.656/1120 specifications</entry>
</row>
<row>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[32]</entry>
<entry></entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="dv-timing-types">
<title>DV Timing types</title>
<tgroup cols="3">
&cs-str;
<tbody valign="top">
<row>
<entry>Timing type</entry>
<entry>value</entry>
<entry>Description</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry></entry>
</row>
<row>
<entry>V4L2_DV_BT_656_1120</entry>
<entry>0</entry>
<entry>BT.656/1120 timings</entry>
</row>
</tbody>
</tgroup>
</table>
</refsect1>
</refentry>
<!--
Local Variables:
mode: sgml
sgml-parent-document: "v4l2.sgml"
indent-tabs-mode: nil
End:
-->
Documentation/DocBook/v4l/vidioc-g-std.xml
浏览文件 @ 67cbf8a2
......@@ -86,6 +86,12 @@ standards.</para>
<constant>VIDIOC_S_STD</constant> parameter was unsuitable.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>EBUSY</errorcode></term>
<listitem>
<para>The device is busy and therefore can not change the standard</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
......
Documentation/DocBook/v4l/vidioc-query-dv-preset.xml 0 → 100644
浏览文件 @ 67cbf8a2
<refentry id="vidioc-query-dv-preset">
<refmeta>
<refentrytitle>ioctl VIDIOC_QUERY_DV_PRESET</refentrytitle>
&manvol;
</refmeta>
<refnamediv>
<refname>VIDIOC_QUERY_DV_PRESET</refname>
<refpurpose>Sense the DV preset received by the current
input</refpurpose>
</refnamediv>
<refsynopsisdiv>
<funcsynopsis>
<funcprototype>
<funcdef>int <function>ioctl</function></funcdef>
<paramdef>int <parameter>fd</parameter></paramdef>
<paramdef>int <parameter>request</parameter></paramdef>
<paramdef>&v4l2-dv-preset; *<parameter>argp</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Arguments</title>
<variablelist>
<varlistentry>
<term><parameter>fd</parameter></term>
<listitem>
<para>&fd;</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>request</parameter></term>
<listitem>
<para>VIDIOC_QUERY_DV_PRESET</para>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>argp</parameter></term>
<listitem>
<para></para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Description</title>
<para>The hardware may be able to detect the current DV preset
automatically, similar to sensing the video standard. To do so, applications
call <constant> VIDIOC_QUERY_DV_PRESET</constant> with a pointer to a
&v4l2-dv-preset; type. Once the hardware detects a preset, that preset is
returned in the preset field of &v4l2-dv-preset;. When detection is not
possible or fails, the value V4L2_DV_INVALID is returned.</para>
</refsect1>
<refsect1>
&return-value;
<variablelist>
<varlistentry>
<term><errorcode>EINVAL</errorcode></term>
<listitem>
<para>This ioctl is not supported.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>EBUSY</errorcode></term>
<listitem>
<para>The device is busy and therefore can not sense the preset</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
<!--
Local Variables:
mode: sgml
sgml-parent-document: "v4l2.sgml"
indent-tabs-mode: nil
End:
-->
Documentation/DocBook/v4l/vidioc-querystd.xml
浏览文件 @ 67cbf8a2
......@@ -70,6 +70,12 @@ current video input or output.</para>
<para>This ioctl is not supported.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><errorcode>EBUSY</errorcode></term>
<listitem>
<para>The device is busy and therefore can not detect the standard</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
</refentry>
......
Documentation/SubmitChecklist
浏览文件 @ 67cbf8a2
......@@ -15,7 +15,7 @@ kernel patches.
2: Passes allnoconfig, allmodconfig
3: Builds on multiple CPU architectures by using local cross-compile tools
or something like PLM at OSDL.
or some other build farm.
4: ppc64 is a good architecture for cross-compilation checking because it
tends to use `unsigned long' for 64-bit quantities.
......@@ -88,3 +88,6 @@ kernel patches.
24: All memory barriers {e.g., barrier(), rmb(), wmb()} need a comment in the
source code that explains the logic of what they are doing and why.
25: If any ioctl's are added by the patch, then also update
Documentation/ioctl/ioctl-number.txt.
Documentation/acpi/method-customizing.txt 0 → 100644
浏览文件 @ 67cbf8a2
Linux ACPI Custom Control Method How To
=======================================
Written by Zhang Rui <rui.zhang@intel.com>
Linux supports customizing ACPI control methods at runtime.
Users can use this to
1. override an existing method which may not work correctly,
or just for debugging purposes.
2. insert a completely new method in order to create a missing
method such as _OFF, _ON, _STA, _INI, etc.
For these cases, it is far simpler to dynamically install a single
control method rather than override the entire DSDT, because kernel
rebuild/reboot is not needed and test result can be got in minutes.
Note: Only ACPI METHOD can be overridden, any other object types like
"Device", "OperationRegion", are not recognized.
Note: The same ACPI control method can be overridden for many times,
and it's always the latest one that used by Linux/kernel.
1. override an existing method
a) get the ACPI table via ACPI sysfs I/F. e.g. to get the DSDT,
just run "cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat"
b) disassemble the table by running "iasl -d dsdt.dat".
c) rewrite the ASL code of the method and save it in a new file,
d) package the new file (psr.asl) to an ACPI table format.
Here is an example of a customized \_SB._AC._PSR method,
DefinitionBlock ("", "SSDT", 1, "", "", 0x20080715)
{
External (ACON)
Method (\_SB_.AC._PSR, 0, NotSerialized)
{
Store ("In AC _PSR", Debug)
Return (ACON)
}
}
Note that the full pathname of the method in ACPI namespace
should be used.
And remember to use "External" to declare external objects.
e) assemble the file to generate the AML code of the method.
e.g. "iasl psr.asl" (psr.aml is generated as a result)
f) mount debugfs by "mount -t debugfs none /sys/kernel/debug"
g) override the old method via the debugfs by running
"cat /tmp/psr.aml > /sys/kernel/debug/acpi/custom_method"
2. insert a new method
This is easier than overriding an existing method.
We just need to create the ASL code of the method we want to
insert and then follow the step c) ~ g) in section 1.
3. undo your changes
The "undo" operation is not supported for a new inserted method
right now, i.e. we can not remove a method currently.
For an overrided method, in order to undo your changes, please
save a copy of the method original ASL code in step c) section 1,
and redo step c) ~ g) to override the method with the original one.
Note: We can use a kernel with multiple custom ACPI method running,
But each individual write to debugfs can implement a SINGLE
method override. i.e. if we want to insert/override multiple
ACPI methods, we need to redo step c) ~ g) for multiple times.
Documentation/arm/OMAP/DSS 0 → 100644
浏览文件 @ 67cbf8a2
OMAP2/3 Display Subsystem
-------------------------
This is an almost total rewrite of the OMAP FB driver in drivers/video/omap
(let's call it DSS1). The main differences between DSS1 and DSS2 are DSI,
TV-out and multiple display support, but there are lots of small improvements
also.
The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
panel and controller drivers are in drivers/video/omap2/. DSS1 and DSS2 live
currently side by side, you can choose which one to use.
Features
--------
Working and tested features include:
- MIPI DPI (parallel) output
- MIPI DSI output in command mode
- MIPI DBI (RFBI) output
- SDI output
- TV output
- All pieces can be compiled as a module or inside kernel
- Use DISPC to update any of the outputs
- Use CPU to update RFBI or DSI output
- OMAP DISPC planes
- RGB16, RGB24 packed, RGB24 unpacked
- YUV2, UYVY
- Scaling
- Adjusting DSS FCK to find a good pixel clock
- Use DSI DPLL to create DSS FCK
Tested boards include:
- OMAP3 SDP board
- Beagle board
- N810
omapdss driver
--------------
The DSS driver does not itself have any support for Linux framebuffer, V4L or
such like the current ones, but it has an internal kernel API that upper level
drivers can use.
The DSS driver models OMAP's overlays, overlay managers and displays in a
flexible way to enable non-common multi-display configuration. In addition to
modelling the hardware overlays, omapdss supports virtual overlays and overlay
managers. These can be used when updating a display with CPU or system DMA.
Panel and controller drivers
----------------------------
The drivers implement panel or controller specific functionality and are not
usually visible to users except through omapfb driver. They register
themselves to the DSS driver.
omapfb driver
-------------
The omapfb driver implements arbitrary number of standard linux framebuffers.
These framebuffers can be routed flexibly to any overlays, thus allowing very
dynamic display architecture.
The driver exports some omapfb specific ioctls, which are compatible with the
ioctls in the old driver.
The rest of the non standard features are exported via sysfs. Whether the final
implementation will use sysfs, or ioctls, is still open.
V4L2 drivers
------------
V4L2 is being implemented in TI.
From omapdss point of view the V4L2 drivers should be similar to framebuffer
driver.
Architecture
--------------------
Some clarification what the different components do:
- Framebuffer is a memory area inside OMAP's SRAM/SDRAM that contains the
pixel data for the image. Framebuffer has width and height and color
depth.
- Overlay defines where the pixels are read from and where they go on the
screen. The overlay may be smaller than framebuffer, thus displaying only
part of the framebuffer. The position of the overlay may be changed if
the overlay is smaller than the display.
- Overlay manager combines the overlays in to one image and feeds them to
display.
- Display is the actual physical display device.
A framebuffer can be connected to multiple overlays to show the same pixel data
on all of the overlays. Note that in this case the overlay input sizes must be
the same, but, in case of video overlays, the output size can be different. Any
framebuffer can be connected to any overlay.
An overlay can be connected to one overlay manager. Also DISPC overlays can be
connected only to DISPC overlay managers, and virtual overlays can be only
connected to virtual overlays.
An overlay manager can be connected to one display. There are certain
restrictions which kinds of displays an overlay manager can be connected:
- DISPC TV overlay manager can be only connected to TV display.
- Virtual overlay managers can only be connected to DBI or DSI displays.
- DISPC LCD overlay manager can be connected to all displays, except TV
display.
Sysfs
-----
The sysfs interface is mainly used for testing. I don't think sysfs
interface is the best for this in the final version, but I don't quite know
what would be the best interfaces for these things.
The sysfs interface is divided to two parts: DSS and FB.
/sys/class/graphics/fb? directory:
mirror 0=off, 1=on
rotate Rotation 0-3 for 0, 90, 180, 270 degrees
rotate_type 0 = DMA rotation, 1 = VRFB rotation
overlays List of overlay numbers to which framebuffer pixels go
phys_addr Physical address of the framebuffer
virt_addr Virtual address of the framebuffer
size Size of the framebuffer
/sys/devices/platform/omapdss/overlay? directory:
enabled 0=off, 1=on
input_size width,height (ie. the framebuffer size)
manager Destination overlay manager name
name
output_size width,height
position x,y
screen_width width
global_alpha global alpha 0-255 0=transparent 255=opaque
/sys/devices/platform/omapdss/manager? directory:
display Destination display
name
alpha_blending_enabled 0=off, 1=on
trans_key_enabled 0=off, 1=on
trans_key_type gfx-destination, video-source
trans_key_value transparency color key (RGB24)
default_color default background color (RGB24)
/sys/devices/platform/omapdss/display? directory:
ctrl_name Controller name
mirror 0=off, 1=on
update_mode 0=off, 1=auto, 2=manual
enabled 0=off, 1=on
name
rotate Rotation 0-3 for 0, 90, 180, 270 degrees
timings Display timings (pixclock,xres/hfp/hbp/hsw,yres/vfp/vbp/vsw)
When writing, two special timings are accepted for tv-out:
"pal" and "ntsc"
panel_name
tear_elim Tearing elimination 0=off, 1=on
There are also some debugfs files at <debugfs>/omapdss/ which show information
about clocks and registers.
Examples
--------
The following definitions have been made for the examples below:
ovl0=/sys/devices/platform/omapdss/overlay0
ovl1=/sys/devices/platform/omapdss/overlay1
ovl2=/sys/devices/platform/omapdss/overlay2
mgr0=/sys/devices/platform/omapdss/manager0
mgr1=/sys/devices/platform/omapdss/manager1
lcd=/sys/devices/platform/omapdss/display0
dvi=/sys/devices/platform/omapdss/display1
tv=/sys/devices/platform/omapdss/display2
fb0=/sys/class/graphics/fb0
fb1=/sys/class/graphics/fb1
fb2=/sys/class/graphics/fb2
Default setup on OMAP3 SDP
--------------------------
Here's the default setup on OMAP3 SDP board. All planes go to LCD. DVI
and TV-out are not in use. The columns from left to right are:
framebuffers, overlays, overlay managers, displays. Framebuffers are
handled by omapfb, and the rest by the DSS.
FB0 --- GFX -\ DVI
FB1 --- VID1 --+- LCD ---- LCD
FB2 --- VID2 -/ TV ----- TV
Example: Switch from LCD to DVI
----------------------
w=`cat $dvi/timings | cut -d "," -f 2 | cut -d "/" -f 1`
h=`cat $dvi/timings | cut -d "," -f 3 | cut -d "/" -f 1`
echo "0" > $lcd/enabled
echo "" > $mgr0/display
fbset -fb /dev/fb0 -xres $w -yres $h -vxres $w -vyres $h
# at this point you have to switch the dvi/lcd dip-switch from the omap board
echo "dvi" > $mgr0/display
echo "1" > $dvi/enabled
After this the configuration looks like:
FB0 --- GFX -\ -- DVI
FB1 --- VID1 --+- LCD -/ LCD
FB2 --- VID2 -/ TV ----- TV
Example: Clone GFX overlay to LCD and TV
-------------------------------
w=`cat $tv/timings | cut -d "," -f 2 | cut -d "/" -f 1`
h=`cat $tv/timings | cut -d "," -f 3 | cut -d "/" -f 1`
echo "0" > $ovl0/enabled
echo "0" > $ovl1/enabled
echo "" > $fb1/overlays
echo "0,1" > $fb0/overlays
echo "$w,$h" > $ovl1/output_size
echo "tv" > $ovl1/manager
echo "1" > $ovl0/enabled
echo "1" > $ovl1/enabled
echo "1" > $tv/enabled
After this the configuration looks like (only relevant parts shown):
FB0 +-- GFX ---- LCD ---- LCD
\- VID1 ---- TV ---- TV
Misc notes
----------
OMAP FB allocates the framebuffer memory using the OMAP VRAM allocator.
Using DSI DPLL to generate pixel clock it is possible produce the pixel clock
of 86.5MHz (max possible), and with that you get 1280x1024@57 output from DVI.
Rotation and mirroring currently only supports RGB565 and RGB8888 modes. VRFB
does not support mirroring.
VRFB rotation requires much more memory than non-rotated framebuffer, so you
probably need to increase your vram setting before using VRFB rotation. Also,
many applications may not work with VRFB if they do not pay attention to all
framebuffer parameters.
Kernel boot arguments
---------------------
vram=<size>
- Amount of total VRAM to preallocate. For example, "10M". omapfb
allocates memory for framebuffers from VRAM.
omapfb.mode=<display>:<mode>[,...]
- Default video mode for specified displays. For example,
"dvi:800x400MR-24@60". See drivers/video/modedb.c.
There are also two special modes: "pal" and "ntsc" that
can be used to tv out.
omapfb.vram=<fbnum>:<size>[@<physaddr>][,...]
- VRAM allocated for a framebuffer. Normally omapfb allocates vram
depending on the display size. With this you can manually allocate
more or define the physical address of each framebuffer. For example,
"1:4M" to allocate 4M for fb1.
omapfb.debug=<y|n>
- Enable debug printing. You have to have OMAPFB debug support enabled
in kernel config.
omapfb.test=<y|n>
- Draw test pattern to framebuffer whenever framebuffer settings change.
You need to have OMAPFB debug support enabled in kernel config.
omapfb.vrfb=<y|n>
- Use VRFB rotation for all framebuffers.
omapfb.rotate=<angle>
- Default rotation applied to all framebuffers.
0 - 0 degree rotation
1 - 90 degree rotation
2 - 180 degree rotation
3 - 270 degree rotation
omapfb.mirror=<y|n>
- Default mirror for all framebuffers. Only works with DMA rotation.
omapdss.def_disp=<display>
- Name of default display, to which all overlays will be connected.
Common examples are "lcd" or "tv".
omapdss.debug=<y|n>
- Enable debug printing. You have to have DSS debug support enabled in
kernel config.
TODO
----
DSS locking
Error checking
- Lots of checks are missing or implemented just as BUG()
System DMA update for DSI
- Can be used for RGB16 and RGB24P modes. Probably not for RGB24U (how
to skip the empty byte?)
OMAP1 support
- Not sure if needed
Documentation/blackfin/00-INDEX
浏览文件 @ 67cbf8a2
00-INDEX
- This file
cache-lock.txt
- HOWTO for blackfin cache locking.
cachefeatures.txt
- Supported cache features.
......
Documentation/blackfin/Makefile 0 → 100644
浏览文件 @ 67cbf8a2
obj-m := gptimers-example.o
all: modules
modules clean:
$(MAKE) -C ../.. SUBDIRS=$(PWD) $@
Documentation/blackfin/cache-lock.txt 已删除 100644 → 0
浏览文件 @ 6c941c85
/*
* File: Documentation/blackfin/cache-lock.txt
* Based on:
* Author:
*
* Created:
* Description: This file contains the simple DMA Implementation for Blackfin
*
* Rev: $Id: cache-lock.txt 2384 2006-11-01 04:12:43Z magicyang $
*
* Modified:
* Copyright 2004-2006 Analog Devices Inc.
*
* Bugs: Enter bugs at http://blackfin.uclinux.org/
*
*/
How to lock your code in cache in uClinux/blackfin
--------------------------------------------------
There are only a few steps required to lock your code into the cache.
Currently you can lock the code by Way.
Below are the interface provided for locking the cache.
1. cache_grab_lock(int Ways);
This function grab the lock for locking your code into the cache specified
by Ways.
2. cache_lock(int Ways);
This function should be called after your critical code has been executed.
Once the critical code exits, the code is now loaded into the cache. This
function locks the code into the cache.
So, the example sequence will be:
cache_grab_lock(WAY0_L); /* Grab the lock */
critical_code(); /* Execute the code of interest */
cache_lock(WAY0_L); /* Lock the cache */
Where WAY0_L signifies WAY0 locking.
Documentation/blackfin/cachefeatures.txt
浏览文件 @ 67cbf8a2
......@@ -41,16 +41,6 @@
icplb_flush();
dcplb_flush();
- Locking the cache.
cache_grab_lock();
cache_lock();
Please refer linux-2.6.x/Documentation/blackfin/cache-lock.txt for how to
lock the cache.
Locking the cache is optional feature.
- Miscellaneous cache functions.
flush_cache_all();
......
Documentation/blackfin/gptimers-example.c 0 → 100644
浏览文件 @ 67cbf8a2
/*
* Simple gptimers example
* http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:gptimers
*
* Copyright 2007-2009 Analog Devices Inc.
*
* Licensed under the GPL-2 or later.
*/
#include <linux/interrupt.h>
#include <linux/module.h>
#include <asm/gptimers.h>
#include <asm/portmux.h>
/* ... random driver includes ... */
#define DRIVER_NAME "gptimer_example"
struct gptimer_data {
uint32_t period, width;
};
static struct gptimer_data data;
/* ... random driver state ... */
static irqreturn_t gptimer_example_irq(int irq, void *dev_id)
{
struct gptimer_data *data = dev_id;
/* make sure it was our timer which caused the interrupt */
if (!get_gptimer_intr(TIMER5_id))
return IRQ_NONE;
/* read the width/period values that were captured for the waveform */
data->width = get_gptimer_pwidth(TIMER5_id);
data->period = get_gptimer_period(TIMER5_id);
/* acknowledge the interrupt */
clear_gptimer_intr(TIMER5_id);
/* tell the upper layers we took care of things */
return IRQ_HANDLED;
}
/* ... random driver code ... */
static int __init gptimer_example_init(void)
{
int ret;
/* grab the peripheral pins */
ret = peripheral_request(P_TMR5, DRIVER_NAME);
if (ret) {
printk(KERN_NOTICE DRIVER_NAME ": peripheral request failed\n");
return ret;
}
/* grab the IRQ for the timer */
ret = request_irq(IRQ_TIMER5, gptimer_example_irq, IRQF_SHARED, DRIVER_NAME, &data);
if (ret) {
printk(KERN_NOTICE DRIVER_NAME ": IRQ request failed\n");
peripheral_free(P_TMR5);
return ret;
}
/* setup the timer and enable it */
set_gptimer_config(TIMER5_id, WDTH_CAP | PULSE_HI | PERIOD_CNT | IRQ_ENA);
enable_gptimers(TIMER5bit);
return 0;
}
module_init(gptimer_example_init);
static void __exit gptimer_example_exit(void)
{
disable_gptimers(TIMER5bit);
free_irq(IRQ_TIMER5, &data);
peripheral_free(P_TMR5);
}
module_exit(gptimer_example_exit);
MODULE_LICENSE("BSD");
Documentation/cpu-freq/cpu-drivers.txt
浏览文件 @ 67cbf8a2
......@@ -92,9 +92,9 @@ policy->cpuinfo.max_freq - the minimum and maximum frequency
(in kHz) which is supported by
this CPU
policy->cpuinfo.transition_latency the time it takes on this CPU to
switch between two frequencies (if
appropriate, else specify
CPUFREQ_ETERNAL)
switch between two frequencies in
nanoseconds (if appropriate, else
specify CPUFREQ_ETERNAL)
policy->cur The current operating frequency of
this CPU (if appropriate)
......
Documentation/cpu-freq/user-guide.txt
浏览文件 @ 67cbf8a2
......@@ -203,6 +203,17 @@ scaling_cur_freq : Current frequency of the CPU as determined by
the frequency the kernel thinks the CPU runs
at.
bios_limit : If the BIOS tells the OS to limit a CPU to
lower frequencies, the user can read out the
maximum available frequency from this file.
This typically can happen through (often not
intended) BIOS settings, restrictions
triggered through a service processor or other
BIOS/HW based implementations.
This does not cover thermal ACPI limitations
which can be detected through the generic
thermal driver.
If you have selected the "userspace" governor which allows you to
set the CPU operating frequency to a specific value, you can read out
the current frequency in
......
Documentation/cpu-hotplug.txt
浏览文件 @ 67cbf8a2
......@@ -49,6 +49,12 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using
additional_cpus=n (*) Use this to limit hotpluggable cpus. This option sets
cpu_possible_map = cpu_present_map + additional_cpus
cede_offline={"off","on"} Use this option to disable/enable putting offlined
processors to an extended H_CEDE state on
supported pseries platforms.
If nothing is specified,
cede_offline is set to "on".
(*) Option valid only for following architectures
- ia64
......
Documentation/device-mapper/snapshot.txt
浏览文件 @ 67cbf8a2
......@@ -8,13 +8,19 @@ the block device which are also writable without interfering with the
original content;
*) To create device "forks", i.e. multiple different versions of the
same data stream.
*) To merge a snapshot of a block device back into the snapshot's origin
device.
In the first two cases, dm copies only the chunks of data that get
changed and uses a separate copy-on-write (COW) block device for
storage.
In both cases, dm copies only the chunks of data that get changed and
uses a separate copy-on-write (COW) block device for storage.
For snapshot merge the contents of the COW storage are merged back into
the origin device.
There are two dm targets available: snapshot and snapshot-origin.
There are three dm targets available:
snapshot, snapshot-origin, and snapshot-merge.
*) snapshot-origin <origin>
......@@ -40,8 +46,25 @@ The difference is that for transient snapshots less metadata must be
saved on disk - they can be kept in memory by the kernel.
How this is used by LVM2
========================
* snapshot-merge <origin> <COW device> <persistent> <chunksize>
takes the same table arguments as the snapshot target except it only
works with persistent snapshots. This target assumes the role of the
"snapshot-origin" target and must not be loaded if the "snapshot-origin"
is still present for <origin>.
Creates a merging snapshot that takes control of the changed chunks
stored in the <COW device> of an existing snapshot, through a handover
procedure, and merges these chunks back into the <origin>. Once merging
has started (in the background) the <origin> may be opened and the merge
will continue while I/O is flowing to it. Changes to the <origin> are
deferred until the merging snapshot's corresponding chunk(s) have been
merged. Once merging has started the snapshot device, associated with
the "snapshot" target, will return -EIO when accessed.
How snapshot is used by LVM2
============================
When you create the first LVM2 snapshot of a volume, four dm devices are used:
1) a device containing the original mapping table of the source volume;
......@@ -72,3 +95,30 @@ brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow
brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap
brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base
How snapshot-merge is used by LVM2
==================================
A merging snapshot assumes the role of the "snapshot-origin" while
merging. As such the "snapshot-origin" is replaced with
"snapshot-merge". The "-real" device is not changed and the "-cow"
device is renamed to <origin name>-cow to aid LVM2's cleanup of the
merging snapshot after it completes. The "snapshot" that hands over its
COW device to the "snapshot-merge" is deactivated (unless using lvchange
--refresh); but if it is left active it will simply return I/O errors.
A snapshot will merge into its origin with the following command:
lvconvert --merge volumeGroup/snap
we'll now have this situation:
# dmsetup table|grep volumeGroup
volumeGroup-base-real: 0 2097152 linear 8:19 384
volumeGroup-base-cow: 0 204800 linear 8:19 2097536
volumeGroup-base: 0 2097152 snapshot-merge 254:11 254:12 P 16
# ls -lL /dev/mapper/volumeGroup-*
brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow
brw------- 1 root root 254, 10 29 ago 18:16 /dev/mapper/volumeGroup-base
Documentation/fb/viafb.txt
浏览文件 @ 67cbf8a2
......@@ -7,7 +7,7 @@
VIA UniChrome Family(CLE266, PM800 / CN400 / CN300,
P4M800CE / P4M800Pro / CN700 / VN800,
CX700 / VX700, K8M890, P4M890,
CN896 / P4M900, VX800)
CN896 / P4M900, VX800, VX855)
[Driver features]
------------------------
......@@ -154,13 +154,6 @@
0 : No Dual Edge Panel (default)
1 : Dual Edge Panel
viafb_video_dev:
This option is used to specify video output devices(CRT, DVI, LCD) for
duoview case.
For example:
To output video on DVI, we should use:
modprobe viafb viafb_video_dev=DVI...
viafb_lcd_port:
This option is used to specify LCD output port,
available values are "DVP0" "DVP1" "DFP_HIGHLOW" "DFP_HIGH" "DFP_LOW".
......@@ -181,9 +174,6 @@ Notes:
and bpp, need to call VIAFB specified ioctl interface VIAFB_SET_DEVICE
instead of calling common ioctl function FBIOPUT_VSCREENINFO since
viafb doesn't support multi-head well, or it will cause screen crush.
4. VX800 2D accelerator hasn't been supported in this driver yet. When
using driver on VX800, the driver will disable the acceleration
function as default.
[Configure viafb with "fbset" tool]
......
Documentation/feature-removal-schedule.txt
浏览文件 @ 67cbf8a2
......@@ -291,22 +291,6 @@ Who: Michael Buesch <mb@bu3sch.de>
---------------------------
What: usedac i386 kernel parameter
When: 2.6.27
Why: replaced by allowdac and no dac combination
Who: Glauber Costa <gcosta@redhat.com>
---------------------------
What: print_fn_descriptor_symbol()
When: October 2009
Why: The %pF vsprintf format provides the same functionality in a
simpler way. print_fn_descriptor_symbol() is deprecated but
still present to give out-of-tree modules time to change.
Who: Bjorn Helgaas <bjorn.helgaas@hp.com>
---------------------------
What: /sys/o2cb symlink
When: January 2010
Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb
......@@ -490,3 +474,22 @@ Why: Obsoleted by the adt7475 driver.
Who: Jean Delvare <khali@linux-fr.org>
---------------------------
What: Support for lcd_switch and display_get in asus-laptop driver
When: March 2010
Why: These two features use non-standard interfaces. There are the
only features that really need multiple path to guess what's
the right method name on a specific laptop.
Removing them will allow to remove a lot of code an significantly
clean the drivers.
This will affect the backlight code which won't be able to know
if the backlight is on or off. The platform display file will also be
write only (like the one in eeepc-laptop).
This should'nt affect a lot of user because they usually know
when their display is on or off.
Who: Corentin Chary <corentin.chary@gmail.com>
----------------------------
Documentation/filesystems/00-INDEX
浏览文件 @ 67cbf8a2
00-INDEX
- this file (info on some of the filesystems supported by linux).
Exporting
- explanation of how to make filesystems exportable.
Locking
- info on locking rules as they pertain to Linux VFS.
9p.txt
......@@ -36,6 +34,8 @@ dnotify.txt
- info about directory notification in Linux.
ecryptfs.txt
- docs on eCryptfs: stacked cryptographic filesystem for Linux.
exofs.txt
- info, usage, mount options, design about EXOFS.
ext2.txt
- info, mount options and specifications for the Ext2 filesystem.
ext3.txt
......@@ -66,12 +66,8 @@ mandatory-locking.txt
- info on the Linux implementation of Sys V mandatory file locking.
ncpfs.txt
- info on Novell Netware(tm) filesystem using NCP protocol.
nfs41-server.txt
- info on the Linux server implementation of NFSv4 minor version 1.
nfs-rdma.txt
- how to install and setup the Linux NFS/RDMA client and server software.
nfsroot.txt
- short guide on setting up a diskless box with NFS root filesystem.
nfs/
- nfs-related documentation.
nilfs2.txt
- info and mount options for the NILFS2 filesystem.
ntfs.txt
......@@ -90,8 +86,6 @@ relay.txt
- info on relay, for efficient streaming from kernel to user space.
romfs.txt
- description of the ROMFS filesystem.
rpc-cache.txt
- introduction to the caching mechanisms in the sunrpc layer.
seq_file.txt
- how to use the seq_file API
sharedsubtree.txt
......
Documentation/filesystems/exofs.txt
浏览文件 @ 67cbf8a2
......@@ -60,13 +60,13 @@ USAGE
mkfs.exofs --pid=65536 --format /dev/osd0
The --format is optional if not specified no OSD_FORMAT will be
preformed and a clean file system will be created in the specified pid,
The --format is optional. If not specified, no OSD_FORMAT will be
performed and a clean file system will be created in the specified pid,
in the available space of the target. (Use --format=size_in_meg to limit
the total LUN space available)
If pid already exist it will be deleted and a new one will be created in it's
place. Be careful.
If pid already exists, it will be deleted and a new one will be created in
its place. Be careful.
An exofs lives inside a single OSD partition. You can create multiple exofs
filesystems on the same device using multiple pids.
......@@ -81,7 +81,7 @@ USAGE
7. For reference (See do-exofs example script):
do-exofs start - an example of how to perform the above steps.
do-exofs stop - an example of how to unmount the file system.
do-exofs stop - an example of how to unmount the file system.
do-exofs format - an example of how to format and mkfs a new exofs.
8. Extra compilation flags (uncomment in fs/exofs/Kbuild):
......@@ -104,8 +104,8 @@ Where:
exofs specific options: Options are separated by commas (,)
pid=<integer> - The partition number to mount/create as
container of the filesystem.
This option is mandatory
to=<integer> - Timeout in ticks for a single command
This option is mandatory.
to=<integer> - Timeout in ticks for a single command.
default is (60 * HZ) [for debugging only]
===============================================================================
......@@ -116,7 +116,7 @@ DESIGN
with a special ID (defined in common.h).
Information included in the file system control block is used to fill the
in-memory superblock structure at mount time. This object is created before
the file system is used by mkexofs.c It contains information such as:
the file system is used by mkexofs.c. It contains information such as:
- The file system's magic number
- The next inode number to be allocated
......@@ -134,8 +134,8 @@ DESIGN
attributes. This applies to both regular files and other types (directories,
device files, symlinks, etc.).
* Credentials are generated per object (inode and superblock) when they is
created in memory (read off disk or created). The credential works for all
* Credentials are generated per object (inode and superblock) when they are
created in memory (read from disk or created). The credential works for all
operations and is used as long as the object remains in memory.
* Async OSD operations are used whenever possible, but the target may execute
......@@ -145,7 +145,8 @@ DESIGN
from executing in reverse order:
- The following are handled with the OBJ_CREATED and OBJ_2BCREATED
flags. OBJ_CREATED is set when we know the object exists on the OSD -
in create's callback function, and when we successfully do a read_inode.
in create's callback function, and when we successfully do a
read_inode.
OBJ_2BCREATED is set in the beginning of the create function, so we
know that we should wait.
- create/delete: delete should wait until the object is created
......
Documentation/filesystems/ext3.txt
浏览文件 @ 67cbf8a2
......@@ -32,8 +32,8 @@ journal_dev=devnum When the external journal device's major/minor numbers
identified through its new major/minor numbers encoded
in devnum.
noload Don't load the journal on mounting. Note that this forces
mount of inconsistent filesystem, which can lead to
norecovery Don't load the journal on mounting. Note that this forces
noload mount of inconsistent filesystem, which can lead to
various problems.
data=journal All data are committed into the journal prior to being
......
Documentation/filesystems/ext4.txt
浏览文件 @ 67cbf8a2
......@@ -153,8 +153,8 @@ journal_dev=devnum When the external journal device's major/minor numbers
identified through its new major/minor numbers encoded
in devnum.
noload Don't load the journal on mounting. Note that
if the filesystem was not unmounted cleanly,
norecovery Don't load the journal on mounting. Note that
noload if the filesystem was not unmounted cleanly,
skipping the journal replay will lead to the
filesystem containing inconsistencies that can
lead to any number of problems.
......@@ -353,6 +353,12 @@ noauto_da_alloc replacing existing files via patterns such as
system crashes before the delayed allocation
blocks are forced to disk.
discard Controls whether ext4 should issue discard/TRIM
nodiscard(*) commands to the underlying block device when
blocks are freed. This is useful for SSD devices
and sparse/thinly-provisioned LUNs, but it is off
by default until sufficient testing has been done.
Data Mode
=========
There are 3 different data modes:
......
Documentation/filesystems/nfs/00-INDEX 0 → 100644
浏览文件 @ 67cbf8a2
00-INDEX
- this file (nfs-related documentation).
Exporting
- explanation of how to make filesystems exportable.
knfsd-stats.txt
- statistics which the NFS server makes available to user space.
nfs.txt
- nfs client, and DNS resolution for fs_locations.
nfs41-server.txt
- info on the Linux server implementation of NFSv4 minor version 1.
nfs-rdma.txt
- how to install and setup the Linux NFS/RDMA client and server software
nfsroot.txt
- short guide on setting up a diskless box with NFS root filesystem.
rpc-cache.txt
- introduction to the caching mechanisms in the sunrpc layer.
Documentation/filesystems/nfs41-server.txt → Documentation/filesystems/nfs/nfs41-server.txt
浏览文件 @ 67cbf8a2
......@@ -41,7 +41,7 @@ interoperability problems with future clients. Known issues:
conformant with the spec (for example, we don't use kerberos
on the backchannel correctly).
- no trunking support: no clients currently take advantage of
trunking, but this is a mandatory failure, and its use is
trunking, but this is a mandatory feature, and its use is
recommended to clients in a number of places. (E.g. to ensure
timely renewal in case an existing connection's retry timeouts
have gotten too long; see section 8.3 of the draft.)
......@@ -213,3 +213,10 @@ The following cases aren't supported yet:
DESTROY_CLIENTID, DESTROY_SESSION, EXCHANGE_ID.
* DESTROY_SESSION MUST be the final operation in the COMPOUND request.
Nonstandard compound limitations:
* No support for a sessions fore channel RPC compound that requires both a
ca_maxrequestsize request and a ca_maxresponsesize reply, so we may
fail to live up to the promise we made in CREATE_SESSION fore channel
negotiation.
* No more than one IO operation (read, write, readdir) allowed per
compound.
Documentation/filesystems/nilfs2.txt
浏览文件 @ 67cbf8a2
......@@ -49,8 +49,7 @@ Mount options
NILFS2 supports the following mount options:
(*) == default
barrier=on(*) This enables/disables barriers. barrier=off disables
it, barrier=on enables it.
nobarrier Disables barriers.
errors=continue(*) Keep going on a filesystem error.
errors=remount-ro Remount the filesystem read-only on an error.
errors=panic Panic and halt the machine if an error occurs.
......@@ -71,6 +70,10 @@ order=strict Apply strict in-order semantics that preserves sequence
blocks. That means, it is guaranteed that no
overtaking of events occurs in the recovered file
system after a crash.
norecovery Disable recovery of the filesystem on mount.
This disables every write access on the device for
read-only mounts or snapshots. This option will fail
for r/w mounts on an unclean volume.
NILFS2 usage
============
......
Documentation/filesystems/porting
浏览文件 @ 67cbf8a2
......@@ -140,7 +140,7 @@ Callers of notify_change() need ->i_mutex now.
New super_block field "struct export_operations *s_export_op" for
explicit support for exporting, e.g. via NFS. The structure is fully
documented at its declaration in include/linux/fs.h, and in
Documentation/filesystems/Exporting.
Documentation/filesystems/nfs/Exporting.
Briefly it allows for the definition of decode_fh and encode_fh operations
to encode and decode filehandles, and allows the filesystem to use
......
Documentation/filesystems/proc.txt
浏览文件 @ 67cbf8a2
......@@ -38,6 +38,7 @@ Table of Contents
3.3 /proc/<pid>/io - Display the IO accounting fields
3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
3.5 /proc/<pid>/mountinfo - Information about mounts
3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
------------------------------------------------------------------------------
......@@ -1409,3 +1410,11 @@ For more information on mount propagation see:
Documentation/filesystems/sharedsubtree.txt
3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
--------------------------------------------------------
These files provide a method to access a tasks comm value. It also allows for
a task to set its own or one of its thread siblings comm value. The comm value
is limited in size compared to the cmdline value, so writing anything longer
then the kernel's TASK_COMM_LEN (currently 16 chars) will result in a truncated
comm value.
Documentation/filesystems/seq_file.txt
浏览文件 @ 67cbf8a2
......@@ -248,9 +248,7 @@ code, that is done in the initialization code in the usual way:
{
struct proc_dir_entry *entry;
entry = create_proc_entry("sequence", 0, NULL);
if (entry)
entry->proc_fops = &ct_file_ops;
proc_create("sequence", 0, NULL, &ct_file_ops);
return 0;
}
......
Documentation/filesystems/vfs.txt
浏览文件 @ 67cbf8a2
......@@ -472,7 +472,7 @@ __sync_single_inode) to check if ->writepages has been successful in
writing out the whole address_space.
The Writeback tag is used by filemap*wait* and sync_page* functions,
via wait_on_page_writeback_range, to wait for all writeback to
via filemap_fdatawait_range, to wait for all writeback to
complete. While waiting ->sync_page (if defined) will be called on
each page that is found to require writeback.
......
Documentation/gpio.txt
浏览文件 @ 67cbf8a2
......@@ -531,6 +531,13 @@ and have the following read/write attributes:
This file exists only if the pin can be configured as an
interrupt generating input pin.
"active_low" ... reads as either 0 (false) or 1 (true). Write
any nonzero value to invert the value attribute both
for reading and writing. Existing and subsequent
poll(2) support configuration via the edge attribute
for "rising" and "falling" edges will follow this
setting.
GPIO controllers have paths like /sys/class/gpio/gpiochip42/ (for the
controller implementing GPIOs starting at #42) and have the following
read-only attributes:
......@@ -566,6 +573,8 @@ requested using gpio_request():
int gpio_export_link(struct device *dev, const char *name,
unsigned gpio)
/* change the polarity of a GPIO node in sysfs */
int gpio_sysfs_set_active_low(unsigned gpio, int value);
After a kernel driver requests a GPIO, it may only be made available in
the sysfs interface by gpio_export(). The driver can control whether the
......@@ -580,3 +589,9 @@ After the GPIO has been exported, gpio_export_link() allows creating
symlinks from elsewhere in sysfs to the GPIO sysfs node. Drivers can
use this to provide the interface under their own device in sysfs with
a descriptive name.
Drivers can use gpio_sysfs_set_active_low() to hide GPIO line polarity
differences between boards from user space. This only affects the
sysfs interface. Polarity change can be done both before and after
gpio_export(), and previously enabled poll(2) support for either
rising or falling edge will be reconfigured to follow this setting.
Documentation/hwmon/lis3lv02d
浏览文件 @ 67cbf8a2
......@@ -3,7 +3,8 @@ Kernel driver lis3lv02d
Supported chips:
* STMicroelectronics LIS3LV02DL and LIS3LV02DQ
* STMicroelectronics LIS3LV02DL, LIS3LV02DQ (12 bits precision)
* STMicroelectronics LIS302DL, LIS3L02DQ, LIS331DL (8 bits)
Authors:
Yan Burman <burman.yan@gmail.com>
......@@ -13,32 +14,52 @@ Authors:
Description
-----------
This driver provides support for the accelerometer found in various HP
laptops sporting the feature officially called "HP Mobile Data
Protection System 3D" or "HP 3D DriveGuard". It detects automatically
laptops with this sensor. Known models (for now the HP 2133, nc6420,
nc2510, nc8510, nc84x0, nw9440 and nx9420) will have their axis
automatically oriented on standard way (eg: you can directly play
neverball). The accelerometer data is readable via
/sys/devices/platform/lis3lv02d.
This driver provides support for the accelerometer found in various HP laptops
sporting the feature officially called "HP Mobile Data Protection System 3D" or
"HP 3D DriveGuard". It detects automatically laptops with this sensor. Known
models (full list can be found in drivers/hwmon/hp_accel.c) will have their
axis automatically oriented on standard way (eg: you can directly play
neverball). The accelerometer data is readable via
/sys/devices/platform/lis3lv02d. Reported values are scaled
to mg values (1/1000th of earth gravity).
Sysfs attributes under /sys/devices/platform/lis3lv02d/:
position - 3D position that the accelerometer reports. Format: "(x,y,z)"
calibrate - read: values (x, y, z) that are used as the base for input
class device operation.
write: forces the base to be recalibrated with the current
position.
rate - reports the sampling rate of the accelerometer device in HZ
rate - read reports the sampling rate of the accelerometer device in HZ.
write changes sampling rate of the accelerometer device.
Only values which are supported by HW are accepted.
selftest - performs selftest for the chip as specified by chip manufacturer.
This driver also provides an absolute input class device, allowing
the laptop to act as a pinball machine-esque joystick.
the laptop to act as a pinball machine-esque joystick. Joystick device can be
calibrated. Joystick device can be in two different modes.
By default output values are scaled between -32768 .. 32767. In joystick raw
mode, joystick and sysfs position entry have the same scale. There can be
small difference due to input system fuzziness feature.
Events are also available as input event device.
Selftest is meant only for hardware diagnostic purposes. It is not meant to be
used during normal operations. Position data is not corrupted during selftest
but interrupt behaviour is not guaranteed to work reliably. In test mode, the
sensing element is internally moved little bit. Selftest measures difference
between normal mode and test mode. Chip specifications tell the acceptance
limit for each type of the chip. Limits are provided via platform data
to allow adjustment of the limits without a change to the actual driver.
Seltest returns either "OK x y z" or "FAIL x y z" where x, y and z are
measured difference between modes. Axes are not remapped in selftest mode.
Measurement values are provided to help HW diagnostic applications to make
final decision.
On HP laptops, if the led infrastructure is activated, support for a led
indicating disk protection will be provided as /sys/class/leds/hp::hddprotect.
Another feature of the driver is misc device called "freefall" that
acts similar to /dev/rtc and reacts on free-fall interrupts received
from the device. It supports blocking operations, poll/select and
fasync operation modes. You must read 1 bytes from the device. The
result is number of free-fall interrupts since the last successful
read (or 255 if number of interrupts would not fit).
read (or 255 if number of interrupts would not fit). See the hpfall.c
file for an example on using the device.
Axes orientation
......@@ -55,7 +76,7 @@ the accelerometer are converted into a "standard" organisation of the axes
* If the laptop is put upside-down, Z becomes negative
If your laptop model is not recognized (cf "dmesg"), you can send an
email to the authors to add it to the database. When reporting a new
email to the maintainer to add it to the database. When reporting a new
laptop, please include the output of "dmidecode" plus the value of
/sys/devices/platform/lis3lv02d/position in these four cases.
......
Documentation/hwmon/w83627ehf
浏览文件 @ 67cbf8a2
......@@ -81,8 +81,14 @@ pwm[1-4] - this file stores PWM duty cycle or DC value (fan speed) in range:
0 (stop) to 255 (full)
pwm[1-4]_enable - this file controls mode of fan/temperature control:
* 1 Manual Mode, write to pwm file any value 0-255 (full speed)
* 2 Thermal Cruise
* 1 Manual mode, write to pwm file any value 0-255 (full speed)
* 2 "Thermal Cruise" mode
* 3 "Fan Speed Cruise" mode
* 4 "Smart Fan III" mode
pwm[1-4]_mode - controls if output is PWM or DC level
* 0 DC output (0 - 12v)
* 1 PWM output
Thermal Cruise mode
-------------------
......
Documentation/i2c/writing-clients
浏览文件 @ 67cbf8a2
......@@ -44,7 +44,7 @@ static struct i2c_driver foo_driver = {
/* if device autodetection is needed: */
.class = I2C_CLASS_SOMETHING,
.detect = foo_detect,
.address_data = &addr_data,
.address_list = normal_i2c,
.shutdown = foo_shutdown, /* optional */
.suspend = foo_suspend, /* optional */
......
Documentation/infiniband/ipoib.txt
浏览文件 @ 67cbf8a2
......@@ -36,11 +36,11 @@ Datagram vs Connected modes
fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes.
In connected mode, the IB RC (Reliable Connected) transport is used.
Connected mode is to takes advantage of the connected nature of the
IB transport and allows an MTU up to the maximal IP packet size of
64K, which reduces the number of IP packets needed for handling
large UDP datagrams, TCP segments, etc and increases the performance
for large messages.
Connected mode takes advantage of the connected nature of the IB
transport and allows an MTU up to the maximal IP packet size of 64K,
which reduces the number of IP packets needed for handling large UDP
datagrams, TCP segments, etc and increases the performance for large
messages.
In connected mode, the interface's UD QP is still used for multicast
and communication with peers that don't support connected mode. In
......
Documentation/isdn/README.gigaset
浏览文件 @ 67cbf8a2
......@@ -68,22 +68,38 @@ GigaSet 307x Device Driver
for troubleshooting or to pass module parameters.
The module ser_gigaset provides a serial line discipline N_GIGASET_M101
which drives the device through the regular serial line driver. It must
be attached to the serial line to which the M101 is connected with the
ldattach(8) command (requires util-linux-ng release 2.14 or later), for
example:
ldattach GIGASET_M101 /dev/ttyS1
which uses the regular serial port driver to access the device, and must
therefore be attached to the serial device to which the M101 is connected.
The ldattach(8) command (included in util-linux-ng release 2.14 or later)
can be used for that purpose, for example:
ldattach GIGASET_M101 /dev/ttyS1
This will open the device file, attach the line discipline to it, and
then sleep in the background, keeping the device open so that the line
discipline remains active. To deactivate it, kill the daemon, for example
with
killall ldattach
killall ldattach
before disconnecting the device. To have this happen automatically at
system startup/shutdown on an LSB compatible system, create and activate
an appropriate LSB startup script /etc/init.d/gigaset. (The init name
'gigaset' is officially assigned to this project by LANANA.)
Alternatively, just add the 'ldattach' command line to /etc/rc.local.
The modules accept the following parameters:
Module Parameter Meaning
gigaset debug debug level (see section 3.2.)
startmode initial operation mode (see section 2.5.):
bas_gigaset ) 1=ISDN4linux/CAPI (default), 0=Unimodem
ser_gigaset )
usb_gigaset ) cidmode initial Call-ID mode setting (see section
2.5.): 1=on (default), 0=off
Depending on your distribution you may want to create a separate module
configuration file /etc/modprobe.d/gigaset for these, or add them to a
custom file like /etc/modprobe.conf.local.
2.2. Device nodes for user space programs
------------------------------------
The device can be accessed from user space (eg. by the user space tools
......@@ -93,11 +109,48 @@ GigaSet 307x Device Driver
- /dev/ttyGU0 for M105 (USB data boxes)
- /dev/ttyGB0 for the base driver (direct USB connection)
You can also select a "default device" which is used by the frontends when
If you connect more than one device of a type, they will get consecutive
device nodes, eg. /dev/ttyGU1 for a second M105.
You can also set a "default device" for the user space tools to use when
no device node is given as parameter, by creating a symlink /dev/ttyG to
one of them, eg.:
ln -s /dev/ttyGB0 /dev/ttyG
ln -s /dev/ttyGB0 /dev/ttyG
The devices accept the following device specific ioctl calls
(defined in gigaset_dev.h):
ioctl(int fd, GIGASET_REDIR, int *cmd);
If cmd==1, the device is set to be controlled exclusively through the
character device node; access from the ISDN subsystem is blocked.
If cmd==0, the device is set to be used from the ISDN subsystem and does
not communicate through the character device node.
ioctl(int fd, GIGASET_CONFIG, int *cmd);
(ser_gigaset and usb_gigaset only)
If cmd==1, the device is set to adapter configuration mode where commands
are interpreted by the M10x DECT adapter itself instead of being
forwarded to the base station. In this mode, the device accepts the
commands described in Siemens document "AT-Kommando Alignment M10x Data"
for setting the operation mode, associating with a base station and
querying parameters like field strengh and signal quality.
Note that there is no ioctl command for leaving adapter configuration
mode and returning to regular operation. In order to leave adapter
configuration mode, write the command ATO to the device.
ioctl(int fd, GIGASET_BRKCHARS, unsigned char brkchars[6]);
(usb_gigaset only)
Set the break characters on an M105's internal serial adapter to the six
bytes stored in brkchars[]. Unused bytes should be set to zero.
ioctl(int fd, GIGASET_VERSION, unsigned version[4]);
Retrieve version information from the driver. version[0] must be set to
one of:
- GIGVER_DRIVER: retrieve driver version
- GIGVER_COMPAT: retrieve interface compatibility version
- GIGVER_FWBASE: retrieve the firmware version of the base
Upon return, version[] is filled with the requested version information.
2.3. ISDN4linux
----------
......@@ -113,15 +166,24 @@ GigaSet 307x Device Driver
Connection State: 0, Response: -1
gigaset_process_response: resp_code -1 in ConState 0 !
Timeout occurred
you might need to use unimodem mode. (see section 2.5.)
you probably need to use unimodem mode. (see section 2.5.)
2.4. CAPI
----
If the driver is compiled with CAPI support (kernel configuration option
GIGASET_CAPI, experimental) it can also be used with CAPI 2.0 kernel and
user space applications. ISDN4Linux is supported in this configuration
user space applications. For user space access, the module capi.ko must
be loaded. The capiinit command (included in the capi4k-utils package)
does this for you.
The CAPI variant of the driver supports legacy ISDN4Linux applications
via the capidrv compatibility driver. The kernel module capidrv.ko must
be loaded explicitly ("modprobe capidrv") if needed.
be loaded explicitly with the command
modprobe capidrv
if needed, and cannot be unloaded again without unloading the driver
first. (These are limitations of capidrv.)
The note about unimodem mode in the preceding section applies here, too.
2.5. Unimodem mode
-------------
......@@ -134,9 +196,14 @@ GigaSet 307x Device Driver
You can switch back using
gigacontr --mode isdn
You can also load the driver using e.g.
modprobe usb_gigaset startmode=0
to prevent the driver from starting in "isdn4linux mode".
You can also put the driver directly into Unimodem mode when it's loaded,
by passing the module parameter startmode=0 to the hardware specific
module, e.g.
modprobe usb_gigaset startmode=0
or by adding a line like
options usb_gigaset startmode=0
to an appropriate module configuration file, like /etc/modprobe.d/gigaset
or /etc/modprobe.conf.local.
In this mode the device works like a modem connected to a serial port
(the /dev/ttyGU0, ... mentioned above) which understands the commands
......@@ -164,9 +231,8 @@ GigaSet 307x Device Driver
options ppp_async flag_time=0
to /etc/modprobe.conf. If your distribution has some local module
configuration file like /etc/modprobe.conf.local,
using that should be preferred.
to an appropriate module configuration file, like /etc/modprobe.d/gigaset
or /etc/modprobe.conf.local.
2.6. Call-ID (CID) mode
------------------
......@@ -189,12 +255,13 @@ GigaSet 307x Device Driver
settings (CID mode).
- If you have several DECT data devices (M10x) which you want to use
in turn, select Unimodem mode by passing the parameter "cidmode=0" to
the driver ("modprobe usb_gigaset cidmode=0" or modprobe.conf).
the appropriate driver module (ser_gigaset or usb_gigaset).
If you want both of these at once, you are out of luck.
You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
setting (ttyGxy is ttyGU0 or ttyGB0).
You can also use the tty class parameter "cidmode" of the device to
change its CID mode while the driver is loaded, eg.
echo 0 > /sys/class/tty/ttyGU0/cidmode
2.7. Unregistered Wireless Devices (M101/M105)
-----------------------------------------
......@@ -208,7 +275,7 @@ GigaSet 307x Device Driver
driver. In that situation, a restricted set of functions is available
which includes, in particular, those necessary for registering the device
to a base or for switching it between Fixed Part and Portable Part
modes.
modes. See the gigacontr(8) manpage for details.
3. Troubleshooting
---------------
......@@ -222,9 +289,7 @@ GigaSet 307x Device Driver
options isdn dialtimeout=15
to /etc/modprobe.conf. If your distribution has some local module
configuration file like /etc/modprobe.conf.local,
using that should be preferred.
to /etc/modprobe.d/gigaset, /etc/modprobe.conf.local or a similar file.
Problem:
Your isdn script aborts with a message about isdnlog.
......@@ -264,7 +329,8 @@ GigaSet 307x Device Driver
The initial value can be set using the debug parameter when loading the
module "gigaset", e.g. by adding a line
options gigaset debug=0
to /etc/modprobe.conf, ...
to your module configuration file, eg. /etc/modprobe.d/gigaset or
/etc/modprobe.conf.local.
Generated debugging information can be found
- as output of the command
......
Documentation/kernel-parameters.txt
浏览文件 @ 67cbf8a2
......@@ -1032,7 +1032,7 @@ and is between 256 and 4096 characters. It is defined in the file
No delay
ip= [IP_PNP]
See Documentation/filesystems/nfsroot.txt.
See Documentation/filesystems/nfs/nfsroot.txt.
ip2= [HW] Set IO/IRQ pairs for up to 4 IntelliPort boards
See comment before ip2_setup() in
......@@ -1553,10 +1553,10 @@ and is between 256 and 4096 characters. It is defined in the file
going to be removed in 2.6.29.
nfsaddrs= [NFS]
See Documentation/filesystems/nfsroot.txt.
See Documentation/filesystems/nfs/nfsroot.txt.
nfsroot= [NFS] nfs root filesystem for disk-less boxes.
See Documentation/filesystems/nfsroot.txt.
See Documentation/filesystems/nfs/nfsroot.txt.
nfs.callback_tcpport=
[NFS] set the TCP port on which the NFSv4 callback
......@@ -1787,6 +1787,11 @@ and is between 256 and 4096 characters. It is defined in the file
waiting for the ACK, so if this is set too high
interrupts *may* be lost!
omap_mux= [OMAP] Override bootloader pin multiplexing.
Format: <mux_mode0.mode_name=value>...
For example, to override I2C bus2:
omap_mux=i2c2_scl.i2c2_scl=0x100,i2c2_sda.i2c2_sda=0x100
opl3= [HW,OSS]
Format: <io>
......@@ -2663,6 +2668,8 @@ and is between 256 and 4096 characters. It is defined in the file
to a common usb-storage quirk flag as follows:
a = SANE_SENSE (collect more than 18 bytes
of sense data);
b = BAD_SENSE (don't collect more than 18
bytes of sense data);
c = FIX_CAPACITY (decrease the reported
device capacity by one sector);
h = CAPACITY_HEURISTICS (decrease the
......@@ -2722,6 +2729,11 @@ and is between 256 and 4096 characters. It is defined in the file
vmpoff= [KNL,S390] Perform z/VM CP command after power off.
Format: <command>
vt.cur_default= [VT] Default cursor shape.
Format: 0xCCBBAA, where AA, BB, and CC are the same as
the parameters of the <Esc>[?A;B;Cc escape sequence;
see VGA-softcursor.txt. Default: 2 = underline.
vt.default_blu= [VT]
Format: <blue0>,<blue1>,<blue2>,...,<blue15>
Change the default blue palette of the console.
......
Documentation/laptops/thinkpad-acpi.txt
浏览文件 @ 67cbf8a2
ThinkPad ACPI Extras Driver
Version 0.23
April 10th, 2009
Version 0.24
December 11th, 2009
Borislav Deianov <borislav@users.sf.net>
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
......@@ -460,6 +460,8 @@ event code Key Notes
For Lenovo ThinkPads with a new
BIOS, it has to be handled either
by the ACPI OSI, or by userspace.
The driver does the right thing,
never mess with this.
0x1011 0x10 FN+END Brightness down. See brightness
up for details.
......@@ -582,46 +584,15 @@ with hotkey_report_mode.
Brightness hotkey notes:
These are the current sane choices for brightness key mapping in
thinkpad-acpi:
Don't mess with the brightness hotkeys in a Thinkpad. If you want
notifications for OSD, use the sysfs backlight class event support.
For IBM and Lenovo models *without* ACPI backlight control (the ones on
which thinkpad-acpi will autoload its backlight interface by default,
and on which ACPI video does not export a backlight interface):
1. Don't enable or map the brightness hotkeys in thinkpad-acpi, as
these older firmware versions unfortunately won't respect the hotkey
mask for brightness keys anyway, and always reacts to them. This
usually work fine, unless X.org drivers are doing something to block
the BIOS. In that case, use (3) below. This is the default mode of
operation.
2. Enable the hotkeys, but map them to something else that is NOT
KEY_BRIGHTNESS_UP/DOWN or any other keycode that would cause
userspace to try to change the backlight level, and use that as an
on-screen-display hint.
3. IF AND ONLY IF X.org drivers find a way to block the firmware from
automatically changing the brightness, enable the hotkeys and map
them to KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN, and feed that to
something that calls xbacklight. thinkpad-acpi will not be able to
change brightness in that case either, so you should disable its
backlight interface.
For Lenovo models *with* ACPI backlight control:
1. Load up ACPI video and use that. ACPI video will report ACPI
events for brightness change keys. Do not mess with thinkpad-acpi
defaults in this case. thinkpad-acpi should not have anything to do
with backlight events in a scenario where ACPI video is loaded:
brightness hotkeys must be disabled, and the backlight interface is
to be kept disabled as well. This is the default mode of operation.
2. Do *NOT* load up ACPI video, enable the hotkeys in thinkpad-acpi,
and map them to KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN. Process
these keys on userspace somehow (e.g. by calling xbacklight).
The driver will do this automatically if it detects that ACPI video
has been disabled.
The driver will issue KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN events
automatically for the cases were userspace has to do something to
implement brightness changes. When you override these events, you will
either fail to handle properly the ThinkPads that require explicit
action to change backlight brightness, or the ThinkPads that require
that no action be taken to work properly.
Bluetooth
......@@ -1121,25 +1092,61 @@ WARNING:
its level up and down at every change.
Volume control -- /proc/acpi/ibm/volume
---------------------------------------
Volume control
--------------
procfs: /proc/acpi/ibm/volume
ALSA: "ThinkPad Console Audio Control", default ID: "ThinkPadEC"
NOTE: by default, the volume control interface operates in read-only
mode, as it is supposed to be used for on-screen-display purposes.
The read/write mode can be enabled through the use of the
"volume_control=1" module parameter.
This feature allows volume control on ThinkPad models which don't have
a hardware volume knob. The available commands are:
NOTE: distros are urged to not enable volume_control by default, this
should be done by the local admin only. The ThinkPad UI is for the
console audio control to be done through the volume keys only, and for
the desktop environment to just provide on-screen-display feedback.
Software volume control should be done only in the main AC97/HDA
mixer.
This feature allows volume control on ThinkPad models with a digital
volume knob (when available, not all models have it), as well as
mute/unmute control. The available commands are:
echo up >/proc/acpi/ibm/volume
echo down >/proc/acpi/ibm/volume
echo mute >/proc/acpi/ibm/volume
echo unmute >/proc/acpi/ibm/volume
echo 'level <level>' >/proc/acpi/ibm/volume
The <level> number range is 0 to 15 although not all of them may be
The <level> number range is 0 to 14 although not all of them may be
distinct. The unmute the volume after the mute command, use either the
up or down command (the level command will not unmute the volume).
up or down command (the level command will not unmute the volume), or
the unmute command.
The current volume level and mute state is shown in the file.
The ALSA mixer interface to this feature is still missing, but patches
to add it exist. That problem should be addressed in the not so
distant future.
You can use the volume_capabilities parameter to tell the driver
whether your thinkpad has volume control or mute-only control:
volume_capabilities=1 for mixers with mute and volume control,
volume_capabilities=2 for mixers with only mute control.
If the driver misdetects the capabilities for your ThinkPad model,
please report this to ibm-acpi-devel@lists.sourceforge.net, so that we
can update the driver.
There are two strategies for volume control. To select which one
should be used, use the volume_mode module parameter: volume_mode=1
selects EC mode, and volume_mode=3 selects EC mode with NVRAM backing
(so that volume/mute changes are remembered across shutdown/reboot).
The driver will operate in volume_mode=3 by default. If that does not
work well on your ThinkPad model, please report this to
ibm-acpi-devel@lists.sourceforge.net.
The driver supports the standard ALSA module parameters. If the ALSA
mixer is disabled, the driver will disable all volume functionality.
Fan control and monitoring: fan speed, fan enable/disable
......@@ -1405,6 +1412,7 @@ to enable more than one output class, just add their values.
0x0008 HKEY event interface, hotkeys
0x0010 Fan control
0x0020 Backlight brightness
0x0040 Audio mixer/volume control
There is also a kernel build option to enable more debugging
information, which may be necessary to debug driver problems.
......@@ -1465,3 +1473,9 @@ Sysfs interface changelog:
and it is always able to disable hot keys. Very old
thinkpads are properly supported. hotkey_bios_mask
is deprecated and marked for removal.
0x020600: Marker for backlight change event support.
0x020700: Support for mute-only mixers.
Volume control in read-only mode by default.
Marker for ALSA mixer support.
Documentation/lockstat.txt
浏览文件 @ 67cbf8a2
......@@ -62,8 +62,20 @@ applicable).
It also tracks 4 contention points per class. A contention point is a call site
that had to wait on lock acquisition.
- CONFIGURATION
Lock statistics are enabled via CONFIG_LOCK_STATS.
- USAGE
Enable collection of statistics:
# echo 1 >/proc/sys/kernel/lock_stat
Disable collection of statistics:
# echo 0 >/proc/sys/kernel/lock_stat
Look at the current lock statistics:
( line numbers not part of actual output, done for clarity in the explanation
......
Documentation/md.txt
浏览文件 @ 67cbf8a2
......@@ -233,9 +233,9 @@ All md devices contain:
resync_start
The point at which resync should start. If no resync is needed,
this will be a very large number. At array creation it will
default to 0, though starting the array as 'clean' will
set it much larger.
this will be a very large number (or 'none' since 2.6.30-rc1). At
array creation it will default to 0, though starting the array as
'clean' will set it much larger.
new_dev
This file can be written but not read. The value written should
......@@ -296,6 +296,51 @@ All md devices contain:
active-idle
like active, but no writes have been seen for a while (safe_mode_delay).
bitmap/location
This indicates where the write-intent bitmap for the array is
stored.
It can be one of "none", "file" or "[+-]N".
"file" may later be extended to "file:/file/name"
"[+-]N" means that many sectors from the start of the metadata.
This is replicated on all devices. For arrays with externally
managed metadata, the offset is from the beginning of the
device.
bitmap/chunksize
The size, in bytes, of the chunk which will be represented by a
single bit. For RAID456, it is a portion of an individual
device. For RAID10, it is a portion of the array. For RAID1, it
is both (they come to the same thing).
bitmap/time_base
The time, in seconds, between looking for bits in the bitmap to
be cleared. In the current implementation, a bit will be cleared
between 2 and 3 times "time_base" after all the covered blocks
are known to be in-sync.
bitmap/backlog
When write-mostly devices are active in a RAID1, write requests
to those devices proceed in the background - the filesystem (or
other user of the device) does not have to wait for them.
'backlog' sets a limit on the number of concurrent background
writes. If there are more than this, new writes will by
synchronous.
bitmap/metadata
This can be either 'internal' or 'external'.
'internal' is the default and means the metadata for the bitmap
is stored in the first 256 bytes of the allocated space and is
managed by the md module.
'external' means that bitmap metadata is managed externally to
the kernel (i.e. by some userspace program)
bitmap/can_clear
This is either 'true' or 'false'. If 'true', then bits in the
bitmap will be cleared when the corresponding blocks are thought
to be in-sync. If 'false', bits will never be cleared.
This is automatically set to 'false' if a write happens on a
degraded array, or if the array becomes degraded during a write.
When metadata is managed externally, it should be set to true
once the array becomes non-degraded, and this fact has been
recorded in the metadata.
As component devices are added to an md array, they appear in the 'md'
directory as new directories named
......@@ -334,8 +379,9 @@ Each directory contains:
Writing "writemostly" sets the writemostly flag.
Writing "-writemostly" clears the writemostly flag.
Writing "blocked" sets the "blocked" flag.
Writing "-blocked" clear the "blocked" flag and allows writes
Writing "-blocked" clears the "blocked" flag and allows writes
to complete.
Writing "in_sync" sets the in_sync flag.
This file responds to select/poll. Any change to 'faulty'
or 'blocked' causes an event.
......@@ -372,6 +418,24 @@ Each directory contains:
array. If a value less than the current component_size is
written, it will be rejected.
recovery_start
When the device is not 'in_sync', this records the number of
sectors from the start of the device which are known to be
correct. This is normally zero, but during a recovery
operation is will steadily increase, and if the recovery is
interrupted, restoring this value can cause recovery to
avoid repeating the earlier blocks. With v1.x metadata, this
value is saved and restored automatically.
This can be set whenever the device is not an active member of
the array, either before the array is activated, or before
the 'slot' is set.
Setting this to 'none' is equivalent to setting 'in_sync'.
Setting to any other value also clears the 'in_sync' flag.
An active md device will also contain and entry for each active device
in the array. These are named
......
Documentation/memory-hotplug.txt
浏览文件 @ 67cbf8a2
......@@ -160,12 +160,15 @@ Under each section, you can see 4 files.
NOTE:
These directories/files appear after physical memory hotplug phase.
If CONFIG_NUMA is enabled the
/sys/devices/system/memory/memoryXXX memory section
directories can also be accessed via symbolic links located in
the /sys/devices/system/node/node* directories. For example:
If CONFIG_NUMA is enabled the memoryXXX/ directories can also be accessed
via symbolic links located in the /sys/devices/system/node/node* directories.
For example:
/sys/devices/system/node/node0/memory9 -> ../../memory/memory9
A backlink will also be created:
/sys/devices/system/memory/memory9/node0 -> ../../node/node0
--------------------------------
4. Physical memory hot-add phase
--------------------------------
......
Documentation/misc-devices/ad525x_dpot.txt 0 → 100644
浏览文件 @ 67cbf8a2
---------------------------------
AD525x Digital Potentiometers
---------------------------------
The ad525x_dpot driver exports a simple sysfs interface. This allows you to
work with the immediate resistance settings as well as update the saved startup
settings. Access to the factory programmed tolerance is also provided, but
interpretation of this settings is required by the end application according to
the specific part in use.
---------
Files
---------
Each dpot device will have a set of eeprom, rdac, and tolerance files. How
many depends on the actual part you have, as will the range of allowed values.
The eeprom files are used to program the startup value of the device.
The rdac files are used to program the immediate value of the device.
The tolerance files are the read-only factory programmed tolerance settings
and may vary greatly on a part-by-part basis. For exact interpretation of
this field, please consult the datasheet for your part. This is presented
as a hex file for easier parsing.
-----------
Example
-----------
Locate the device in your sysfs tree. This is probably easiest by going into
the common i2c directory and locating the device by the i2c slave address.
# ls /sys/bus/i2c/devices/
0-0022 0-0027 0-002f
So assuming the device in question is on the first i2c bus and has the slave
address of 0x2f, we descend (unrelated sysfs entries have been trimmed).
# ls /sys/bus/i2c/devices/0-002f/
eeprom0 rdac0 tolerance0
You can use simple reads/writes to access these files:
# cd /sys/bus/i2c/devices/0-002f/
# cat eeprom0
0
# echo 10 > eeprom0
# cat eeprom0
10
# cat rdac0
5
# echo 3 > rdac0
# cat rdac0
3
Documentation/nommu-mmap.txt
浏览文件 @ 67cbf8a2
......@@ -119,6 +119,32 @@ FURTHER NOTES ON NO-MMU MMAP
granule but will only discard the excess if appropriately configured as
this has an effect on fragmentation.
(*) The memory allocated by a request for an anonymous mapping will normally
be cleared by the kernel before being returned in accordance with the
Linux man pages (ver 2.22 or later).
In the MMU case this can be achieved with reasonable performance as
regions are backed by virtual pages, with the contents only being mapped
to cleared physical pages when a write happens on that specific page
(prior to which, the pages are effectively mapped to the global zero page
from which reads can take place). This spreads out the time it takes to
initialize the contents of a page - depending on the write-usage of the
mapping.
In the no-MMU case, however, anonymous mappings are backed by physical
pages, and the entire map is cleared at allocation time. This can cause
significant delays during a userspace malloc() as the C library does an
anonymous mapping and the kernel then does a memset for the entire map.
However, for memory that isn't required to be precleared - such as that
returned by malloc() - mmap() can take a MAP_UNINITIALIZED flag to
indicate to the kernel that it shouldn't bother clearing the memory before
returning it. Note that CONFIG_MMAP_ALLOW_UNINITIALIZED must be enabled
to permit this, otherwise the flag will be ignored.
uClibc uses this to speed up malloc(), and the ELF-FDPIC binfmt uses this
to allocate the brk and stack region.
(*) A list of all the private copy and anonymous mappings on the system is
visible through /proc/maps in no-MMU mode.
......
Documentation/powerpc/dts-bindings/4xx/ppc440spe-adma.txt 0 → 100644
浏览文件 @ 67cbf8a2
PPC440SPe DMA/XOR (DMA Controller and XOR Accelerator)
Device nodes needed for operation of the ppc440spe-adma driver
are specified hereby. These are I2O/DMA, DMA and XOR nodes
for DMA engines and Memory Queue Module node. The latter is used
by ADMA driver for configuration of RAID-6 H/W capabilities of
the PPC440SPe. In addition to the nodes and properties described
below, the ranges property of PLB node must specify ranges for
DMA devices.
i) The I2O node
Required properties:
- compatible : "ibm,i2o-440spe";
- reg : <registers mapping>
- dcr-reg : <DCR registers range>
Example:
I2O: i2o@400100000 {
compatible = "ibm,i2o-440spe";
reg = <0x00000004 0x00100000 0x100>;
dcr-reg = <0x060 0x020>;
};
ii) The DMA node
Required properties:
- compatible : "ibm,dma-440spe";
- cell-index : 1 cell, hardware index of the DMA engine
(typically 0x0 and 0x1 for DMA0 and DMA1)
- reg : <registers mapping>
- dcr-reg : <DCR registers range>
- interrupts : <interrupt mapping for DMA0/1 interrupts sources:
2 sources: DMAx CS FIFO Needs Service IRQ (on UIC0)
and DMA Error IRQ (on UIC1). The latter is common
for both DMA engines>.
- interrupt-parent : needed for interrupt mapping
Example:
DMA0: dma0@400100100 {
compatible = "ibm,dma-440spe";
cell-index = <0>;
reg = <0x00000004 0x00100100 0x100>;
dcr-reg = <0x060 0x020>;
interrupt-parent = <&DMA0>;
interrupts = <0 1>;
#interrupt-cells = <1>;
#address-cells = <0>;
#size-cells = <0>;
interrupt-map = <
0 &UIC0 0x14 4
1 &UIC1 0x16 4>;
};
iii) XOR Accelerator node
Required properties:
- compatible : "amcc,xor-accelerator";
- reg : <registers mapping>
- interrupts : <interrupt mapping for XOR interrupt source>
- interrupt-parent : for interrupt mapping
Example:
xor-accel@400200000 {
compatible = "amcc,xor-accelerator";
reg = <0x00000004 0x00200000 0x400>;
interrupt-parent = <&UIC1>;
interrupts = <0x1f 4>;
};
iv) Memory Queue Module node
Required properties:
- compatible : "ibm,mq-440spe";
- dcr-reg : <DCR registers range>
Example:
MQ0: mq {
compatible = "ibm,mq-440spe";
dcr-reg = <0x040 0x020>;
};
Documentation/powerpc/dts-bindings/fsl/board.txt
浏览文件 @ 67cbf8a2
......@@ -20,12 +20,16 @@ Required properities:
- compatible : should be "fsl,fpga-pixis".
- reg : should contain the address and the length of the FPPGA register
set.
- interrupt-parent: should specify phandle for the interrupt controller.
- interrupts : should specify event (wakeup) IRQ.
Example (MPC8610HPCD):
board-control@e8000000 {
compatible = "fsl,fpga-pixis";
reg = <0xe8000000 32>;
interrupt-parent = <&mpic>;
interrupts = <8 8>;
};
* Freescale BCSR GPIO banks
......
Documentation/powerpc/dts-bindings/fsl/mpc5200.txt
浏览文件 @ 67cbf8a2
......@@ -103,7 +103,22 @@ fsl,mpc5200-gpt nodes
---------------------
On the mpc5200 and 5200b, GPT0 has a watchdog timer function. If the board
design supports the internal wdt, then the device node for GPT0 should
include the empty property 'fsl,has-wdt'.
include the empty property 'fsl,has-wdt'. Note that this does not activate
the watchdog. The timer will function as a GPT if the timer api is used, and
it will function as watchdog if the watchdog device is used. The watchdog
mode has priority over the gpt mode, i.e. if the watchdog is activated, any
gpt api call to this timer will fail with -EBUSY.
If you add the property
fsl,wdt-on-boot = <n>;
GPT0 will be marked as in-use watchdog, i.e. blocking every gpt access to it.
If n>0, the watchdog is started with a timeout of n seconds. If n=0, the
configuration of the watchdog is not touched. This is useful in two cases:
- just mark GPT0 as watchdog, blocking gpt accesses, and configure it later;
- do not touch a configuration assigned by the boot loader which supervises
the boot process itself.
The watchdog will respect the CONFIG_WATCHDOG_NOWAYOUT option.
An mpc5200-gpt can be used as a single line GPIO controller. To do so,
add the following properties to the gpt node:
......
Documentation/powerpc/dts-bindings/nintendo/gamecube.txt 0 → 100644
浏览文件 @ 67cbf8a2
Nintendo GameCube device tree
=============================
1) The "flipper" node
This node represents the multi-function "Flipper" chip, which packages
many of the devices found in the Nintendo GameCube.
Required properties:
- compatible : Should be "nintendo,flipper"
1.a) The Video Interface (VI) node
Represents the interface between the graphics processor and a external
video encoder.
Required properties:
- compatible : should be "nintendo,flipper-vi"
- reg : should contain the VI registers location and length
- interrupts : should contain the VI interrupt
1.b) The Processor Interface (PI) node
Represents the data and control interface between the main processor
and graphics and audio processor.
Required properties:
- compatible : should be "nintendo,flipper-pi"
- reg : should contain the PI registers location and length
1.b.i) The "Flipper" interrupt controller node
Represents the interrupt controller within the "Flipper" chip.
The node for the "Flipper" interrupt controller must be placed under
the PI node.
Required properties:
- compatible : should be "nintendo,flipper-pic"
1.c) The Digital Signal Procesor (DSP) node
Represents the digital signal processor interface, designed to offload
audio related tasks.
Required properties:
- compatible : should be "nintendo,flipper-dsp"
- reg : should contain the DSP registers location and length
- interrupts : should contain the DSP interrupt
1.c.i) The Auxiliary RAM (ARAM) node
Represents the non cpu-addressable ram designed mainly to store audio
related information.
The ARAM node must be placed under the DSP node.
Required properties:
- compatible : should be "nintendo,flipper-aram"
- reg : should contain the ARAM start (zero-based) and length
1.d) The Disk Interface (DI) node
Represents the interface used to communicate with mass storage devices.
Required properties:
- compatible : should be "nintendo,flipper-di"
- reg : should contain the DI registers location and length
- interrupts : should contain the DI interrupt
1.e) The Audio Interface (AI) node
Represents the interface to the external 16-bit stereo digital-to-analog
converter.
Required properties:
- compatible : should be "nintendo,flipper-ai"
- reg : should contain the AI registers location and length
- interrupts : should contain the AI interrupt
1.f) The Serial Interface (SI) node
Represents the interface to the four single bit serial interfaces.
The SI is a proprietary serial interface used normally to control gamepads.
It's NOT a RS232-type interface.
Required properties:
- compatible : should be "nintendo,flipper-si"
- reg : should contain the SI registers location and length
- interrupts : should contain the SI interrupt
1.g) The External Interface (EXI) node
Represents the multi-channel SPI-like interface.
Required properties:
- compatible : should be "nintendo,flipper-exi"
- reg : should contain the EXI registers location and length
- interrupts : should contain the EXI interrupt
Documentation/powerpc/dts-bindings/nintendo/wii.txt 0 → 100644
浏览文件 @ 67cbf8a2
Nintendo Wii device tree
========================
0) The root node
This node represents the Nintendo Wii video game console.
Required properties:
- model : Should be "nintendo,wii"
- compatible : Should be "nintendo,wii"
1) The "hollywood" node
This node represents the multi-function "Hollywood" chip, which packages
many of the devices found in the Nintendo Wii.
Required properties:
- compatible : Should be "nintendo,hollywood"
1.a) The Video Interface (VI) node
Represents the interface between the graphics processor and a external
video encoder.
Required properties:
- compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
- reg : should contain the VI registers location and length
- interrupts : should contain the VI interrupt
1.b) The Processor Interface (PI) node
Represents the data and control interface between the main processor
and graphics and audio processor.
Required properties:
- compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
- reg : should contain the PI registers location and length
1.b.i) The "Flipper" interrupt controller node
Represents the "Flipper" interrupt controller within the "Hollywood" chip.
The node for the "Flipper" interrupt controller must be placed under
the PI node.
Required properties:
- #interrupt-cells : <1>
- compatible : should be "nintendo,flipper-pic"
- interrupt-controller
1.c) The Digital Signal Procesor (DSP) node
Represents the digital signal processor interface, designed to offload
audio related tasks.
Required properties:
- compatible : should be "nintendo,hollywood-dsp","nintendo,flipper-dsp"
- reg : should contain the DSP registers location and length
- interrupts : should contain the DSP interrupt
1.d) The Serial Interface (SI) node
Represents the interface to the four single bit serial interfaces.
The SI is a proprietary serial interface used normally to control gamepads.
It's NOT a RS232-type interface.
Required properties:
- compatible : should be "nintendo,hollywood-si","nintendo,flipper-si"
- reg : should contain the SI registers location and length
- interrupts : should contain the SI interrupt
1.e) The Audio Interface (AI) node
Represents the interface to the external 16-bit stereo digital-to-analog
converter.
Required properties:
- compatible : should be "nintendo,hollywood-ai","nintendo,flipper-ai"
- reg : should contain the AI registers location and length
- interrupts : should contain the AI interrupt
1.f) The External Interface (EXI) node
Represents the multi-channel SPI-like interface.
Required properties:
- compatible : should be "nintendo,hollywood-exi","nintendo,flipper-exi"
- reg : should contain the EXI registers location and length
- interrupts : should contain the EXI interrupt
1.g) The Open Host Controller Interface (OHCI) nodes
Represent the USB 1.x Open Host Controller Interfaces.
Required properties:
- compatible : should be "nintendo,hollywood-usb-ohci","usb-ohci"
- reg : should contain the OHCI registers location and length
- interrupts : should contain the OHCI interrupt
1.h) The Enhanced Host Controller Interface (EHCI) node
Represents the USB 2.0 Enhanced Host Controller Interface.
Required properties:
- compatible : should be "nintendo,hollywood-usb-ehci","usb-ehci"
- reg : should contain the EHCI registers location and length
- interrupts : should contain the EHCI interrupt
1.i) The Secure Digital Host Controller Interface (SDHCI) nodes
Represent the Secure Digital Host Controller Interfaces.
Required properties:
- compatible : should be "nintendo,hollywood-sdhci","sdhci"
- reg : should contain the SDHCI registers location and length
- interrupts : should contain the SDHCI interrupt
1.j) The Inter-Processsor Communication (IPC) node
Represent the Inter-Processor Communication interface. This interface
enables communications between the Broadway and the Starlet processors.
- compatible : should be "nintendo,hollywood-ipc"
- reg : should contain the IPC registers location and length
- interrupts : should contain the IPC interrupt
1.k) The "Hollywood" interrupt controller node
Represents the "Hollywood" interrupt controller within the
"Hollywood" chip.
Required properties:
- #interrupt-cells : <1>
- compatible : should be "nintendo,hollywood-pic"
- reg : should contain the controller registers location and length
- interrupt-controller
- interrupts : should contain the cascade interrupt of the "flipper" pic
- interrupt-parent: should contain the phandle of the "flipper" pic
1.l) The General Purpose I/O (GPIO) controller node
Represents the dual access 32 GPIO controller interface.
Required properties:
- #gpio-cells : <2>
- compatible : should be "nintendo,hollywood-gpio"
- reg : should contain the IPC registers location and length
- gpio-controller
1.m) The control node
Represents the control interface used to setup several miscellaneous
settings of the "Hollywood" chip like boot memory mappings, resets,
disk interface mode, etc.
Required properties:
- compatible : should be "nintendo,hollywood-control"
- reg : should contain the control registers location and length
1.n) The Disk Interface (DI) node
Represents the interface used to communicate with mass storage devices.
Required properties:
- compatible : should be "nintendo,hollywood-di"
- reg : should contain the DI registers location and length
- interrupts : should contain the DI interrupt
Documentation/powerpc/dts-bindings/xilinx.txt
浏览文件 @ 67cbf8a2
......@@ -292,4 +292,15 @@
- reg-offset : A value of 3 is required
- reg-shift : A value of 2 is required
vii) Xilinx USB Host controller
The Xilinx USB host controller is EHCI compatible but with a different
base address for the EHCI registers, and it is always a big-endian
USB Host controller. The hardware can be configured as high speed only,
or high speed/full speed hybrid.
Required properties:
- xlnx,support-usb-fs: A value 0 means the core is built as high speed
only. A value 1 means the core also supports
full speed devices.
Documentation/serial/hayes-esp.txt 已删除 100644 → 0
浏览文件 @ 6c941c85
HAYES ESP DRIVER VERSION 2.1
A big thanks to the people at Hayes, especially Alan Adamson. Their support
has enabled me to provide enhancements to the driver.
Please report your experiences with this driver to me (arobinso@nyx.net). I
am looking for both positive and negative feedback.
*** IMPORTANT CHANGES FOR 2.1 ***
Support for PIO mode. Five situations will cause PIO mode to be used:
1) A multiport card is detected. PIO mode will always be used. (8 port cards
do not support DMA).
2) The DMA channel is set to an invalid value (anything other than 1 or 3).
3) The DMA buffer/channel could not be allocated. The port will revert to PIO
mode until it is reopened.
4) Less than a specified number of bytes need to be transferred to/from the
FIFOs. PIO mode will be used for that transfer only.
5) A port needs to do a DMA transfer and another port is already using the
DMA channel. PIO mode will be used for that transfer only.
Since the Hayes ESP seems to conflict with other cards (notably sound cards)
when using DMA, DMA is turned off by default. To use DMA, it must be turned
on explicitly, either with the "dma=" option described below or with
setserial. A multiport card can be forced into DMA mode by using setserial;
however, most multiport cards don't support DMA.
The latest version of setserial allows the enhanced configuration of the ESP
card to be viewed and modified.
***
This package contains the files needed to compile a module to support the Hayes
ESP card. The drivers are basically a modified version of the serial drivers.
Features:
- Uses the enhanced mode of the ESP card, allowing a wider range of
interrupts and features than compatibility mode
- Uses DMA and 16 bit PIO mode to transfer data to and from the ESP's FIFOs,
reducing CPU load
- Supports primary and secondary ports
If the driver is compiled as a module, the IRQs to use can be specified by
using the irq= option. The format is:
irq=[0x100],[0x140],[0x180],[0x200],[0x240],[0x280],[0x300],[0x380]
The address in brackets is the base address of the card. The IRQ of
nonexistent cards can be set to 0. If an IRQ of a card that does exist is set
to 0, the driver will attempt to guess at the correct IRQ. For example, to set
the IRQ of the card at address 0x300 to 12, the insmod command would be:
insmod esp irq=0,0,0,0,0,0,12,0
The custom divisor can be set by using the divisor= option. The format is the
same as for the irq= option. Each divisor value is a series of hex digits,
with each digit representing the divisor to use for a corresponding port. The
divisor value is constructed RIGHT TO LEFT. Specifying a nonzero divisor value
will automatically set the spd_cust flag. To calculate the divisor to use for
a certain baud rate, divide the port's base baud (generally 921600) by the
desired rate. For example, to set the divisor of the primary port at 0x300 to
4 and the divisor of the secondary port at 0x308 to 8, the insmod command would
be:
insmod esp divisor=0,0,0,0,0,0,0x84,0
The dma= option can be used to set the DMA channel. The channel can be either
1 or 3. Specifying any other value will force the driver to use PIO mode.
For example, to set the DMA channel to 3, the insmod command would be:
insmod esp dma=3
The rx_trigger= and tx_trigger= options can be used to set the FIFO trigger
levels. They specify when the ESP card should send an interrupt. Larger
values will decrease the number of interrupts; however, a value too high may
result in data loss. Valid values are 1 through 1023, with 768 being the
default. For example, to set the receive trigger level to 512 bytes and the
transmit trigger level to 700 bytes, the insmod command would be:
insmod esp rx_trigger=512 tx_trigger=700
The flow_off= and flow_on= options can be used to set the hardware flow off/
flow on levels. The flow on level must be lower than the flow off level, and
the flow off level should be higher than rx_trigger. Valid values are 1
through 1023, with 1016 being the default flow off level and 944 being the
default flow on level. For example, to set the flow off level to 1000 bytes
and the flow on level to 935 bytes, the insmod command would be:
insmod esp flow_off=1000 flow_on=935
The rx_timeout= option can be used to set the receive timeout value. This
value indicates how long after receiving the last character that the ESP card
should wait before signalling an interrupt. Valid values are 0 though 255,
with 128 being the default. A value too high will increase latency, and a
value too low will cause unnecessary interrupts. For example, to set the
receive timeout to 255, the insmod command would be:
insmod esp rx_timeout=255
The pio_threshold= option sets the threshold (in number of characters) for
using PIO mode instead of DMA mode. For example, if this value is 32,
transfers of 32 bytes or less will always use PIO mode.
insmod esp pio_threshold=32
Multiple options can be listed on the insmod command line by separating each
option with a space. For example:
insmod esp dma=3 trigger=512
The esp module can be automatically loaded when needed. To cause this to
happen, add the following lines to /etc/modprobe.conf (replacing the last line
with options for your configuration):
alias char-major-57 esp
alias char-major-58 esp
options esp irq=0,0,0,0,0,0,3,0 divisor=0,0,0,0,0,0,0x4,0
You may also need to run 'depmod -a'.
Devices must be created manually. To create the devices, note the output from
the module after it is inserted. The output will appear in the location where
kernel messages usually appear (usually /var/adm/messages). Create two devices
for each 'tty' mentioned, one with major of 57 and the other with major of 58.
The minor number should be the same as the tty number reported. The commands
would be (replace ? with the tty number):
mknod /dev/ttyP? c 57 ?
mknod /dev/cup? c 58 ?
For example, if the following line appears:
Oct 24 18:17:23 techno kernel: ttyP8 at 0x0140 (irq = 3) is an ESP primary port
...two devices should be created:
mknod /dev/ttyP8 c 57 8
mknod /dev/cup8 c 58 8
You may need to set the permissions on the devices:
chmod 666 /dev/ttyP*
chmod 666 /dev/cup*
The ESP module and the serial module should not conflict (they can be used at
the same time). After the ESP module has been loaded the ports on the ESP card
will no longer be accessible by the serial driver.
If I/O errors are experienced when accessing the port, check for IRQ and DMA
conflicts ('cat /proc/interrupts' and 'cat /proc/dma' for a list of IRQs and
DMAs currently in use).
Enjoy!
Andrew J. Robinson <arobinso@nyx.net>
Documentation/serial/tty.txt
浏览文件 @ 67cbf8a2
......@@ -42,7 +42,8 @@ TTY side interfaces:
open() - Called when the line discipline is attached to
the terminal. No other call into the line
discipline for this tty will occur until it
completes successfully. Can sleep.
completes successfully. Returning an error will
prevent the ldisc from being attached. Can sleep.
close() - This is called on a terminal when the line
discipline is being unplugged. At the point of
......@@ -52,7 +53,7 @@ close() - This is called on a terminal when the line
hangup() - Called when the tty line is hung up.
The line discipline should cease I/O to the tty.
No further calls into the ldisc code will occur.
Can sleep.
The return value is ignored. Can sleep.
write() - A process is writing data through the line
discipline. Multiple write calls are serialized
......@@ -83,6 +84,10 @@ ioctl() - Called when an ioctl is handed to the tty layer
that might be for the ldisc. Multiple ioctl calls
may occur in parallel. May sleep.
compat_ioctl() - Called when a 32 bit ioctl is handed to the tty layer
that might be for the ldisc. Multiple ioctl calls
may occur in parallel. May sleep.
Driver Side Interfaces:
receive_buf() - Hand buffers of bytes from the driver to the ldisc
......
Documentation/spinlocks.txt
浏览文件 @ 67cbf8a2
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 67cbf8a2
......@@ -19,6 +19,8 @@ Currently, these files might (depending on your configuration)
show up in /proc/sys/kernel:
- acpi_video_flags
- acct
- bootloader_type [ X86 only ]
- bootloader_version [ X86 only ]
- callhome [ S390 only ]
- auto_msgmni
- core_pattern
......@@ -93,6 +95,35 @@ valid for 30 seconds.
==============================================================
bootloader_type:
x86 bootloader identification
This gives the bootloader type number as indicated by the bootloader,
shifted left by 4, and OR'd with the low four bits of the bootloader
version. The reason for this encoding is that this used to match the
type_of_loader field in the kernel header; the encoding is kept for
backwards compatibility. That is, if the full bootloader type number
is 0x15 and the full version number is 0x234, this file will contain
the value 340 = 0x154.
See the type_of_loader and ext_loader_type fields in
Documentation/x86/boot.txt for additional information.
==============================================================
bootloader_version:
x86 bootloader version
The complete bootloader version number. In the example above, this
file will contain the value 564 = 0x234.
See the type_of_loader and ext_loader_ver fields in
Documentation/x86/boot.txt for additional information.
==============================================================
callhome:
Controls the kernel's callhome behavior in case of a kernel panic.
......
Documentation/thermal/sysfs-api.txt
浏览文件 @ 67cbf8a2
......@@ -206,6 +206,7 @@ passive
passive trip point for the zone. Activation is done by polling with
an interval of 1 second.
Unit: millidegrees Celsius
Valid values: 0 (disabled) or greater than 1000
RW, Optional
*****************************
......
Documentation/video4linux/gspca.txt
浏览文件 @ 67cbf8a2
......@@ -12,6 +12,7 @@ m5602 0402:5602 ALi Video Camera Controller
spca501 040a:0002 Kodak DVC-325
spca500 040a:0300 Kodak EZ200
zc3xx 041e:041e Creative WebCam Live!
ov519 041e:4003 Video Blaster WebCam Go Plus
spca500 041e:400a Creative PC-CAM 300
sunplus 041e:400b Creative PC-CAM 600
sunplus 041e:4012 PC-Cam350
......@@ -168,10 +169,14 @@ sunplus 055f:c650 Mustek MDC5500Z
zc3xx 055f:d003 Mustek WCam300A
zc3xx 055f:d004 Mustek WCam300 AN
conex 0572:0041 Creative Notebook cx11646
ov519 05a9:0511 Video Blaster WebCam 3/WebCam Plus, D-Link USB Digital Video Camera
ov519 05a9:0518 Creative WebCam
ov519 05a9:0519 OV519 Microphone
ov519 05a9:0530 OmniVision
ov519 05a9:2800 OmniVision SuperCAM
ov519 05a9:4519 Webcam Classic
ov519 05a9:8519 OmniVision
ov519 05a9:a511 D-Link USB Digital Video Camera
ov519 05a9:a518 D-Link DSB-C310 Webcam
sunplus 05da:1018 Digital Dream Enigma 1.3
stk014 05e1:0893 Syntek DV4000
......@@ -187,7 +192,7 @@ ov534 06f8:3002 Hercules Blog Webcam
ov534 06f8:3003 Hercules Dualpix HD Weblog
sonixj 06f8:3004 Hercules Classic Silver
sonixj 06f8:3008 Hercules Deluxe Optical Glass
pac7311 06f8:3009 Hercules Classic Link
pac7302 06f8:3009 Hercules Classic Link
spca508 0733:0110 ViewQuest VQ110
spca501 0733:0401 Intel Create and Share
spca501 0733:0402 ViewQuest M318B
......@@ -199,6 +204,7 @@ sunplus 0733:2221 Mercury Digital Pro 3.1p
sunplus 0733:3261 Concord 3045 spca536a
sunplus 0733:3281 Cyberpix S550V
spca506 0734:043b 3DeMon USB Capture aka
ov519 0813:0002 Dual Mode USB Camera Plus
spca500 084d:0003 D-Link DSC-350
spca500 08ca:0103 Aiptek PocketDV
sunplus 08ca:0104 Aiptek PocketDVII 1.3
......@@ -236,15 +242,15 @@ pac7311 093a:2603 Philips SPC 500 NC
pac7311 093a:2608 Trust WB-3300p
pac7311 093a:260e Gigaware VGA PC Camera, Trust WB-3350p, SIGMA cam 2350
pac7311 093a:260f SnakeCam
pac7311 093a:2620 Apollo AC-905
pac7311 093a:2621 PAC731x
pac7311 093a:2622 Genius Eye 312
pac7311 093a:2624 PAC7302
pac7311 093a:2626 Labtec 2200
pac7311 093a:2628 Genius iLook 300
pac7311 093a:2629 Genious iSlim 300
pac7311 093a:262a Webcam 300k
pac7311 093a:262c Philips SPC 230 NC
pac7302 093a:2620 Apollo AC-905
pac7302 093a:2621 PAC731x
pac7302 093a:2622 Genius Eye 312
pac7302 093a:2624 PAC7302
pac7302 093a:2626 Labtec 2200
pac7302 093a:2628 Genius iLook 300
pac7302 093a:2629 Genious iSlim 300
pac7302 093a:262a Webcam 300k
pac7302 093a:262c Philips SPC 230 NC
jeilinj 0979:0280 Sakar 57379
zc3xx 0ac8:0302 Z-star Vimicro zc0302
vc032x 0ac8:0321 Vimicro generic vc0321
......@@ -259,6 +265,7 @@ vc032x 0ac8:c002 Sony embedded vimicro
vc032x 0ac8:c301 Samsung Q1 Ultra Premium
spca508 0af9:0010 Hama USB Sightcam 100
spca508 0af9:0011 Hama USB Sightcam 100
ov519 0b62:0059 iBOT2 Webcam
sonixb 0c45:6001 Genius VideoCAM NB
sonixb 0c45:6005 Microdia Sweex Mini Webcam
sonixb 0c45:6007 Sonix sn9c101 + Tas5110D
......@@ -318,8 +325,10 @@ sn9c20x 0c45:62b3 PC Camera (SN9C202 + OV9655)
sn9c20x 0c45:62bb PC Camera (SN9C202 + OV7660)
sn9c20x 0c45:62bc PC Camera (SN9C202 + HV7131R)
sunplus 0d64:0303 Sunplus FashionCam DXG
ov519 0e96:c001 TRUST 380 USB2 SPACEC@M
etoms 102c:6151 Qcam Sangha CIF
etoms 102c:6251 Qcam xxxxxx VGA
ov519 1046:9967 W9967CF/W9968CF WebCam IC, Video Blaster WebCam Go
zc3xx 10fd:0128 Typhoon Webshot II USB 300k 0x0128
spca561 10fd:7e50 FlyCam Usb 100
zc3xx 10fd:8050 Typhoon Webshot II USB 300k
......@@ -332,7 +341,12 @@ spca501 1776:501c Arowana 300K CMOS Camera
t613 17a1:0128 TASCORP JPEG Webcam, NGS Cyclops
vc032x 17ef:4802 Lenovo Vc0323+MI1310_SOC
pac207 2001:f115 D-Link DSB-C120
sq905c 2770:9050 sq905c
sq905c 2770:905c DualCamera
sq905 2770:9120 Argus Digital Camera DC1512
sq905c 2770:913d sq905c
spca500 2899:012c Toptro Industrial
ov519 8020:ef04 ov519
spca508 8086:0110 Intel Easy PC Camera
spca500 8086:0630 Intel Pocket PC Camera
spca506 99fa:8988 Grandtec V.cap
......
Documentation/video4linux/sh_mobile_ceu_camera.txt 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
Documentation/video4linux/v4l2-framework.txt
浏览文件 @ 67cbf8a2
......@@ -561,6 +561,8 @@ video_device helper functions
There are a few useful helper functions:
- file/video_device private data
You can set/get driver private data in the video_device struct using:
void *video_get_drvdata(struct video_device *vdev);
......@@ -575,8 +577,7 @@ struct video_device *video_devdata(struct file *file);
returns the video_device belonging to the file struct.
The final helper function combines video_get_drvdata with
video_devdata:
The video_drvdata function combines video_get_drvdata with video_devdata:
void *video_drvdata(struct file *file);
......@@ -584,6 +585,17 @@ You can go from a video_device struct to the v4l2_device struct using:
struct v4l2_device *v4l2_dev = vdev->v4l2_dev;
- Device node name
The video_device node kernel name can be retrieved using
const char *video_device_node_name(struct video_device *vdev);
The name is used as a hint by userspace tools such as udev. The function
should be used where possible instead of accessing the video_device::num and
video_device::minor fields.
video buffer helper functions
-----------------------------
......
Documentation/vm/hugetlbpage.txt
浏览文件 @ 67cbf8a2
此差异已折叠。
Documentation/vm/hwpoison.txt
浏览文件 @ 67cbf8a2
此差异已折叠。
Documentation/vm/ksm.txt
浏览文件 @ 67cbf8a2
此差异已折叠。
Documentation/vm/page-types.c
浏览文件 @ 67cbf8a2
此差异已折叠。
MAINTAINERS
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/include/asm/core_t2.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/include/asm/elf.h
浏览文件 @ 67cbf8a2
......@@ -81,7 +81,6 @@ typedef elf_fpreg_t elf_fpregset_t[ELF_NFPREG];
#define ELF_DATA ELFDATA2LSB
#define ELF_ARCH EM_ALPHA
#define USE_ELF_CORE_DUMP
#define ELF_EXEC_PAGESIZE 8192
/* This is the location that an ET_DYN program is loaded if exec'ed. Typical
......
arch/alpha/include/asm/fcntl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/kernel/core_t2.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/alpha/kernel/srm_env.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/configs/omap3_touchbook_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/configs/zeus_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/include/asm/mach/irq.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/include/asm/mman.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/calls.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/early_printk.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/smp_twd.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/sys_arm.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-at91/include/mach/atmel-mci.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-bcmring/arch.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-bcmring/include/mach/reg_nand.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-bcmring/include/mach/reg_umi.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-footbridge/common.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/avila-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/avila-setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/common-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/coyote-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/coyote-setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/dsmg600-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/fsg-setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/goramo_mlr.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/gtwx5715-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/avila.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/coyote.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/dsmg600.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/fsg.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/gtwx5715.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/ixdp425.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/nas100d.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/nslu2.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/include/mach/prpmc1100.h 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/arm/mach-ixp4xx/ixdp425-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/ixp4xx_npe.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/nas100d-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ixp4xx/nslu2-setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-lh7a40x/clocks.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/board-dream.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/board-dream.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/include/mach/mmc.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-msm/io.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-ns9xxx/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/board-fsample.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/clock.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/clock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/clock_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/i2c.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/include/mach/lcd_dma.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/include/mach/lcdc.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/io.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/lcd_dma.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/mux.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/opp.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap1/opp_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-2430sdp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-3430sdp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-3630sdp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-cm-t35.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-ldp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-omap3touchbook.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-rx51.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-zoom2.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/board-zoom3.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock2xxx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock34xx.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock34xx.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock34xx_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock44xx.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock44xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock44xx_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clock_common_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/clockdomain.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/cm-regbits-44xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/cm.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/cm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/cm44xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/devices.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/dpll.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/gpmc-smc91x.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/i2c.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/id.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/io.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/mux.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/mux34xx.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/mux34xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/omap-headsmp.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/omap-smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/omap_hwmod.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/opp2420_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/opp2430_data.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/opp2xxx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/pm-debug.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/powerdomain.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/prcm-common.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/prm-regbits-44xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/prm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/prm44xx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/sdrc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/sdrc.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/serial.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/sram34xx.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-omap2/usb-ehci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/em-x270.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/include/mach/arcom-pcmcia.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/include/mach/zeus.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/viper.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-pxa/zeus.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-realview/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-s3c2442/mach-gta02.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-sa1100/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-sa1100/generic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-u300/include/mach/coh901318.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mach-w90x900/include/mach/nuc900_spi.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/mm/mmap.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-mxc/ehci.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-mxc/include/mach/mxc_ehci.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/debug-devices.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/debug-leds.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/devices.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/fb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/i2c.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/include/plat/clkdev_omap.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/include/plat/display.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/include/plat/i2c.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/include/plat/vram.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/include/plat/vrfb.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/mux.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/omap_device.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/plat-omap/usb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/arm/vfp/vfpmodule.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/boards/atngw100/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/boards/atngw100/mrmt.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/boards/atngw100/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/configs/atngw100mkii_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/configs/atngw100mkii_evklcd100_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/configs/atngw100mkii_evklcd101_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/include/asm/hardirq.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/include/asm/syscalls.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/kernel/sys_avr32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/kernel/syscall-stubs.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/mach-at32ap/at32ap700x.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/avr32/mach-at32ap/include/mach/atmel-mci.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/boot/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/configs/BF561-ACVILON_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/bfin-lq035q1.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/bug.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/clocks.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/dma.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/dpmc.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/fcntl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/gpio.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/io.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/ipipe.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/kgdb.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/module.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/pci.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/ptrace.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/trace.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/uaccess.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/include/asm/unistd.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/bfin_dma_5xx.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/bfin_gpio.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/dma-mapping.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/gptimers.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/ipipe.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/irqchip.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/kgdb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/kgdb_test.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/process.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/ptrace.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/signal.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/sys_bfin.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/time-ts.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/time.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/traps.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/lib/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/lib/checksum.c 已删除 100644 → 0
浏览文件 @ 6c941c85
此差异已折叠。
arch/blackfin/mach-bf518/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf527/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf538/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf538/ext-gpio.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf548/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf561/boards/acvilon.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf561/coreb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-bf561/smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-common/cpufreq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-common/entry.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/blackfin/mach-common/smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/cris/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/cris/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/cris/kernel/sys_cris.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/frv/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/frv/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/frv/kernel/sys_frv.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/include/asm/module.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/kernel/sys_h8300.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/kernel/syscalls.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/h8300/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/ia32/elfcore32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/bitops.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/dma-mapping.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/hw_irq.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/io.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/mca.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/meminit.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/numa.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/pgtable.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/processor.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/rwsem.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/head.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/iosapic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/mca.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/mca_asm.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/relocate_kernel.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/sys_ia64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/mm/contig.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/mm/discontig.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/mm/ioremap.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn2_smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/sn/pci/tioca_provider.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/xen/irq_xen.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/ia64/xen/time.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m32r/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m32r/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m32r/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m32r/kernel/sys_m32r.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m32r/kernel/syscall_table.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m68k/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m68k/include/asm/pgtable_mm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m68k/kernel/sys_m68k.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m68k/sun3/mmu_emu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/m68knommu/kernel/sys_m68k.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/Kconfig.debug
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/boot/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/cache.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/futex.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/page.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/pvr.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/include/asm/setup.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/cpu/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/cpu/cache.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/cpu/mb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/cpu/pvr.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/entry.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/ftrace.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/heartbeat.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/intc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/mcount.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/process.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/reset.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/signal.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/stacktrace.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/kernel/timer.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/lib/uaccess.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/mm/init.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/mm/pgtable.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/oprofile/Makefile 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/oprofile/microblaze_oprofile.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/microblaze/platform/platform.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/include/asm/fcntl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/kernel/kspd.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/kernel/syscall.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/loongson/common/mem.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/mm/cache.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mips/vr41xx/common/icu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/include/asm/mman.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/kernel/entry.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/kernel/kprobes.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/mn10300/kernel/sys_mn10300.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/hpux/sys_hpux.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/atomic.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/bug.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/fcntl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/ftrace.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/asm-offsets.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/signal.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/sys_parisc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/sys_parisc32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/kernel/unwind.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/parisc/lib/bitops.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/eiger.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/gamecube.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/gef_ppc9a.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/glacier.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/haleakala.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/katmai.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/kilauea.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/kmeter1.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/makalu.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/p1020rdb.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/p2020rdb_camp_core0.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/p2020rdb_camp_core1.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/p4080ds.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/redwood.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/wii.dts 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/dts/yosemite.dts
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/gamecube-head.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/gamecube.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/ugecon.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/ugecon.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/wii-head.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/wii.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/boot/wrapper
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/configs/gamecube_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/configs/wii_defconfig 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/async_tx.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/cpm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/cpm1.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/cpm2.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/dcr-regs.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/fixmap.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/hugetlb.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/hvcall.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/hw_irq.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/immap_qe.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/irq.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm_asm.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm_book3s.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm_book3s_64_asm.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm_host.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/kvm_ppc.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/lppaca.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/machdep.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/macio.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/mediabay.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/module.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/mpc52xx.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/nvram.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/paca.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/page.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/page_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/pgalloc.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/pgtable.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/pte-8xx.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/ptrace.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/qe.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/rtas.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/smp.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/systbl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/include/asm/udbg.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/crash.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/dma-swiotlb.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/head_8xx.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/io.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/iommu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/misc_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/nvram_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/setup-common.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/setup_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/syscalls.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/udbg.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/vector.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_32_mmu.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_emulate.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_interrupts.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_mmu.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_mmu_host.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_rmhandlers.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/book3s_64_slb.S 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/booke.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/emulate.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/powerpc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/timing.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/kvm/trace.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/lib/copy_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/lib/locks.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/40x_mmu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/44x_mmu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/fault.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/fsl_booke_mmu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/gup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/hash_utils_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/hugetlbpage-hash64.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/hugetlbpage.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/init_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/init_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/mmu_decl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/pgtable.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/pgtable_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/ppc_mmu_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/subpage-prot.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/mm/tlb_hash64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/52xx/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/85xx/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/85xx/corenet_ds.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/85xx/corenet_ds.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/85xx/p4080_ds.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/86xx/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/chrp/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/chrp/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/flipper-pic.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/flipper-pic.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/gamecube.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/hlwd-pic.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/hlwd-pic.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/usbgecko_udbg.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/usbgecko_udbg.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/embedded6xx/wii.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/ps3/mm.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/pseries/dlpar.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/platforms/pseries/offline_states.h 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/cpm1.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/cpm2_pic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/cpm_common.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/fsl_msi.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/fsl_pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/fsl_pmc.c 0 → 100644
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/i8259.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/ipic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/mpc8xx_pic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/mpic_u3msi.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/mv64x60_pic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe_ic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/tsi108_pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/uic.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/sysdev/xilinx_intc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/kernel/sys_s390.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/s390/lib/spinlock.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/score/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/score/kernel/sys_score.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/Kconfig.debug
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/boards/mach-kfr2r09/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/boards/mach-migor/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/boards/mach-se/7722/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/boards/mach-se/7724/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/configs/ecovec24_defconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/elf.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/io.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/pgtable_32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/spinlock.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/unistd_32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/include/asm/unistd_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/cpu/irq/ipr.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/cpu/sh2a/setup-mxg.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/cpu/sh5/fpu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/cpu/sh5/setup-sh5.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/early_printk.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/ftrace.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/irq.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/process_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/ptrace_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/setup.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/signal_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/sys_sh.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/syscalls_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/traps_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/kernel/traps_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/mm/cache-sh4.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/mm/ioremap_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/mm/ioremap_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/mm/mmap.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sh/mm/numa.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/Kconfig.debug
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/elf_32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/elf_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/fcntl.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/pci_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/string_32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/string_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/uaccess_32.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/uaccess_64.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/include/asm/unistd.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/entry.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/ftrace.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/iommu.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/irq_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/kprobes.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/ldc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/mdesc.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/nmi.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/of_device_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/pci.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/ptrace_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/sparc_ksyms_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/sys_sparc32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/sys_sparc_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/sys_sparc_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/syscalls.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/systbls.h
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/systbls_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/systbls_64.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/time_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/unaligned_32.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/unaligned_64.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/kernel/visemul.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/lib/Makefile
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/lib/bzero.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/lib/checksum_32.S
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/lib/ksyms.c
浏览文件 @ 67cbf8a2
此差异已折叠。
arch/sparc/lib/mcount.S
浏览文件 @ 67cbf8a2
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或