Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 14
Star 1
Fork 0
R
raspberrypi-kernel
提交 6724af48 编写于 作者: M Mark Brown
浏览文件
操作

Merge branch 'fix/fsl-dspi' of... 

Merge branch 'fix/fsl-dspi' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi into spi-fsl-dspi
上级 d2233325 9deef024
展开全部 隐藏空白更改
内联 并排
Showing with 47737 addition and 20672 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ 6724af48
......@@ -24,6 +24,7 @@
*.order
*.elf
*.bin
*.tar
*.gz
*.bz2
*.lzma
......
.mailmap
浏览文件 @ 6724af48
......@@ -100,6 +100,7 @@ Rajesh Shah <rajesh.shah@intel.com>
Ralf Baechle <ralf@linux-mips.org>
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Rémi Denis-Courmont <rdenis@simphalempin.com>
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Rudolf Marek <R.Marek@sh.cvut.cz>
Rui Saraiva <rmps@joel.ist.utl.pt>
Sachin P Sant <ssant@in.ibm.com>
......
CREDITS
浏览文件 @ 6724af48
......@@ -187,6 +187,10 @@ N: Krishna Balasubramanian
E: balasub@cis.ohio-state.edu
D: Wrote SYS V IPC (part of standard kernel since 0.99.10)
N: Chris Ball
E: chris@printf.net
D: Former maintainer of the MMC/SD/SDIO subsystem.
N: Dario Ballabio
E: ballabio_dario@emc.com
E: dario.ballabio@tiscalinet.it
......@@ -504,6 +508,10 @@ E: paul@paulbristow.net
W: http://paulbristow.net/linux/idefloppy.html
D: Maintainer of IDE/ATAPI floppy driver
N: Stefano Brivio
E: stefano.brivio@polimi.it
D: Broadcom B43 driver
N: Dominik Brodowski
E: linux@brodo.de
W: http://www.brodo.de/
......@@ -2041,6 +2049,10 @@ D: pirq addr, CS5535 alsa audio driver
S: Gurgaon, India
S: Kuala Lumpur, Malaysia
N: Mohit Kumar
D: ST Microelectronics SPEAr13xx PCI host bridge driver
D: Synopsys Designware PCI host bridge driver
N: Gabor Kuti
M: seasons@falcon.sch.bme.hu
M: seasons@makosteszta.sote.hu
......@@ -3004,6 +3016,19 @@ W: http://www.qsl.net/dl1bke/
D: Generic Z8530 driver, AX.25 DAMA slave implementation
D: Several AX.25 hacks
N: Ricardo Ribalda Delgado
E: ricardo.ribalda@gmail.com
W: http://ribalda.com
D: PLX USB338x driver
D: PCA9634 driver
D: Option GTM671WFS
D: Fintek F81216A
D: Various kernel hacks
S: Qtechnology A/S
S: Valby Langgade 142
S: 2500 Valby
S: Denmark
N: Francois-Rene Rideau
E: fare@tunes.org
W: http://www.tunes.org/~fare
......
Documentation/ABI/obsolete/sysfs-block-zram 0 → 100644
浏览文件 @ 6724af48
What: /sys/block/zram<id>/num_reads
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The num_reads file is read-only and specifies the number of
reads (failed or successful) done on this device.
Now accessible via zram<id>/stat node.
What: /sys/block/zram<id>/num_writes
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The num_writes file is read-only and specifies the number of
writes (failed or successful) done on this device.
Now accessible via zram<id>/stat node.
What: /sys/block/zram<id>/invalid_io
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The invalid_io file is read-only and specifies the number of
non-page-size-aligned I/O requests issued to this device.
Now accessible via zram<id>/io_stat node.
What: /sys/block/zram<id>/failed_reads
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The failed_reads file is read-only and specifies the number of
failed reads happened on this device.
Now accessible via zram<id>/io_stat node.
What: /sys/block/zram<id>/failed_writes
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The failed_writes file is read-only and specifies the number of
failed writes happened on this device.
Now accessible via zram<id>/io_stat node.
What: /sys/block/zram<id>/notify_free
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The notify_free file is read-only. Depending on device usage
scenario it may account a) the number of pages freed because
of swap slot free notifications or b) the number of pages freed
because of REQ_DISCARD requests sent by bio. The former ones
are sent to a swap block device when a swap slot is freed, which
implies that this disk is being used as a swap disk. The latter
ones are sent by filesystem mounted with discard option,
whenever some data blocks are getting discarded.
Now accessible via zram<id>/io_stat node.
What: /sys/block/zram<id>/zero_pages
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The zero_pages file is read-only and specifies number of zero
filled pages written to this disk. No memory is allocated for
such pages.
Now accessible via zram<id>/mm_stat node.
What: /sys/block/zram<id>/orig_data_size
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The orig_data_size file is read-only and specifies uncompressed
size of data stored in this disk. This excludes zero-filled
pages (zero_pages) since no memory is allocated for them.
Unit: bytes
Now accessible via zram<id>/mm_stat node.
What: /sys/block/zram<id>/compr_data_size
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The compr_data_size file is read-only and specifies compressed
size of data stored in this disk. So, compression ratio can be
calculated using orig_data_size and this statistic.
Unit: bytes
Now accessible via zram<id>/mm_stat node.
What: /sys/block/zram<id>/mem_used_total
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The mem_used_total file is read-only and specifies the amount
of memory, including allocator fragmentation and metadata
overhead, allocated for this disk. So, allocator space
efficiency can be calculated using compr_data_size and this
statistic.
Unit: bytes
Now accessible via zram<id>/mm_stat node.
What: /sys/block/zram<id>/mem_used_max
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The mem_used_max file is read/write and specifies the amount
of maximum memory zram have consumed to store compressed data.
For resetting the value, you should write "0". Otherwise,
you could see -EINVAL.
Unit: bytes
Downgraded to write-only node: so it's possible to set new
value only; its current value is stored in zram<id>/mm_stat
node.
What: /sys/block/zram<id>/mem_limit
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The mem_limit file is read/write and specifies the maximum
amount of memory ZRAM can use to store the compressed data.
The limit could be changed in run time and "0" means disable
the limit. No limit is the initial state. Unit: bytes
Downgraded to write-only node: so it's possible to set new
value only; its current value is stored in zram<id>/mm_stat
node.
Documentation/ABI/stable/sysfs-devices 0 → 100644
浏览文件 @ 6724af48
# Note: This documents additional properties of any device beyond what
# is documented in Documentation/sysfs-rules.txt
What: /sys/devices/*/of_path
Date: February 2015
Contact: Device Tree mailing list <devicetree@vger.kernel.org>
Description:
Any device associated with a device-tree node will have
an of_path symlink pointing to the corresponding device
node in /sys/firmware/devicetree/
Documentation/ABI/testing/configfs-usb-gadget-printer 0 → 100644
浏览文件 @ 6724af48
What: /config/usb-gadget/gadget/functions/printer.name
Date: Apr 2015
KernelVersion: 4.1
Description:
The attributes:
pnp_string - Data to be passed to the host in pnp string
q_len - Number of requests per endpoint
Documentation/ABI/testing/sysfs-block-dm
浏览文件 @ 6724af48
......@@ -23,3 +23,25 @@ Description: Device-mapper device suspend state.
Contains the value 1 while the device is suspended.
Otherwise it contains 0. Read-only attribute.
Users: util-linux, device-mapper udev rules
What: /sys/block/dm-<num>/dm/rq_based_seq_io_merge_deadline
Date: March 2015
KernelVersion: 4.1
Contact: dm-devel@redhat.com
Description: Allow control over how long a request that is a
reasonable merge candidate can be queued on the request
queue. The resolution of this deadline is in
microseconds (ranging from 1 to 100000 usecs).
Setting this attribute to 0 (the default) will disable
request-based DM's merge heuristic and associated extra
accounting. This attribute is not applicable to
bio-based DM devices so it will only ever report 0 for
them.
What: /sys/block/dm-<num>/dm/use_blk_mq
Date: March 2015
KernelVersion: 4.1
Contact: dm-devel@redhat.com
Description: Request-based Device-mapper blk-mq I/O path mode.
Contains the value 1 if the device is using blk-mq.
Otherwise it contains 0. Read-only attribute.
Documentation/ABI/testing/sysfs-block-zram
浏览文件 @ 6724af48
......@@ -141,3 +141,28 @@ Description:
amount of memory ZRAM can use to store the compressed data. The
limit could be changed in run time and "0" means disable the
limit. No limit is the initial state. Unit: bytes
What: /sys/block/zram<id>/compact
Date: August 2015
Contact: Minchan Kim <minchan@kernel.org>
Description:
The compact file is write-only and trigger compaction for
allocator zrm uses. The allocator moves some objects so that
it could free fragment space.
What: /sys/block/zram<id>/io_stat
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The io_stat file is read-only and accumulates device's I/O
statistics not accounted by block layer. For example,
failed_reads, failed_writes, etc. File format is similar to
block layer statistics file format.
What: /sys/block/zram<id>/mm_stat
Date: August 2015
Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Description:
The mm_stat file is read-only and represents device's mm
statistics (orig_data_size, compr_data_size, etc.) in a format
similar to block layer statistics file format.
Documentation/ABI/testing/sysfs-bus-iio
浏览文件 @ 6724af48
......@@ -253,6 +253,8 @@ What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset
What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset
What: /sys/bus/iio/devices/iio:deviceX/in_magn_offset
What: /sys/bus/iio/devices/iio:deviceX/in_rot_offset
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
......@@ -296,6 +298,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale
What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale
What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
......@@ -336,6 +339,7 @@ what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale
What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale
What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
......@@ -347,7 +351,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender
What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender
What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender
What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Gender of the user (e.g.: male, female) used by some pedometers
......@@ -358,7 +362,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available
What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available
What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available
What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Lists all available gender values (e.g.: male, female).
......@@ -375,7 +379,7 @@ Description:
type.
What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Weight of the user (in kg). It is needed by some pedometers
......@@ -612,6 +616,8 @@ Description:
a given event type is enabled a future point (and not those for
whatever event was previously enabled).
What: /sys/.../events/in_accel_thresh_rising_value
What: /sys/.../events/in_accel_thresh_falling_value
What: /sys/.../events/in_accel_x_raw_thresh_rising_value
What: /sys/.../events/in_accel_x_raw_thresh_falling_value
What: /sys/.../events/in_accel_y_raw_thresh_rising_value
......@@ -661,6 +667,24 @@ Description:
value is in raw device units or in processed units (as _raw
and _input do on sysfs direct channel read attributes).
What: /sys/.../events/in_accel_scale
What: /sys/.../events/in_accel_peak_scale
What: /sys/.../events/in_anglvel_scale
What: /sys/.../events/in_magn_scale
What: /sys/.../events/in_rot_from_north_magnetic_scale
What: /sys/.../events/in_rot_from_north_true_scale
What: /sys/.../events/in_voltage_scale
What: /sys/.../events/in_voltage_supply_scale
What: /sys/.../events/in_temp_scale
What: /sys/.../events/in_illuminance_scale
What: /sys/.../events/in_proximity_scale
KernelVersion: 3.21
Contact: linux-iio@vger.kernel.org
Description:
Specifies the conversion factor from the standard units
to device specific units used to set the event trigger
threshold.
What: /sys/.../events/in_accel_x_thresh_rising_hysteresis
What: /sys/.../events/in_accel_x_thresh_falling_hysteresis
What: /sys/.../events/in_accel_x_thresh_either_hysteresis
......@@ -776,7 +800,7 @@ Description:
What: /sys/.../events/in_accel_x_thresh_rising_period
What: /sys/.../events/in_accel_x_thresh_falling_period
hat: /sys/.../events/in_accel_x_roc_rising_period
What: /sys/.../events/in_accel_x_roc_rising_period
What: /sys/.../events/in_accel_x_roc_falling_period
What: /sys/.../events/in_accel_y_thresh_rising_period
What: /sys/.../events/in_accel_y_thresh_falling_period
......@@ -923,7 +947,7 @@ Description:
this type.
What: /sys/.../events/in_steps_change_en
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Event generated when channel passes a threshold on the absolute
......@@ -932,7 +956,7 @@ Description:
in_steps_change_value.
What: /sys/.../events/in_steps_change_value
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Specifies the value of change threshold that the
......@@ -997,6 +1021,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en
What: /sys/.../iio:deviceX/scan_elements/in_pressure_en
What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en
What: /sys/.../iio:deviceX/scan_elements/in_proximity_en
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1013,6 +1038,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type
What: /sys/.../iio:deviceX/scan_elements/in_pressure_type
What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type
What: /sys/.../iio:deviceX/scan_elements/in_proximity_type
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1064,6 +1090,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_timestamp_index
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_index
What: /sys/.../iio:deviceX/scan_elements/in_pressure_index
What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_index
What: /sys/.../iio:deviceX/scan_elements/in_proximity_index
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1104,7 +1131,7 @@ Description:
What: /sys/.../iio:deviceX/in_energy_input
What: /sys/.../iio:deviceX/in_energy_raw
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
This attribute is used to read the energy value reported by the
......@@ -1113,7 +1140,7 @@ Description:
What: /sys/.../iio:deviceX/in_distance_input
What: /sys/.../iio:deviceX/in_distance_raw
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
This attribute is used to read the distance covered by the user
......@@ -1143,9 +1170,13 @@ Description:
values should behave in the same way as a distance, i.e. lower
values indicate something is closer to the sensor.
What: /sys/.../iio:deviceX/in_illuminance_input
What: /sys/.../iio:deviceX/in_illuminance_raw
What: /sys/.../iio:deviceX/in_illuminanceY_input
What: /sys/.../iio:deviceX/in_illuminanceY_raw
What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw
What: /sys/.../iio:deviceX/in_illuminance_ir_raw
What: /sys/.../iio:deviceX/in_illuminance_clear_raw
KernelVersion: 3.4
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1174,7 +1205,7 @@ Description:
seconds.
What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Number of seconds in which to compute speed.
......@@ -1236,7 +1267,7 @@ Description:
Units after application of scale are m/s.
What: /sys/.../iio:deviceX/in_steps_debounce_count
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Specifies the number of steps that must occur within
......@@ -1244,8 +1275,92 @@ Description:
consumer is making steps.
What: /sys/.../iio:deviceX/in_steps_debounce_time
KernelVersion: 3.20
KernelVersion: 4.0
Contact: linux-iio@vger.kernel.org
Description:
Specifies number of seconds in which we compute the steps
that occur in order to decide if the consumer is making steps.
What: /sys/bus/iio/devices/iio:deviceX/buffer/watermark
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
A single positive integer specifying the maximum number of scan
elements to wait for.
Poll will block until the watermark is reached.
Blocking read will wait until the minimum between the requested
read amount or the low water mark is available.
Non-blocking read will retrieve the available samples from the
buffer even if there are less samples then watermark level. This
allows the application to block on poll with a timeout and read
the available samples after the timeout expires and thus have a
maximum delay guarantee.
What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
A read-only boolean value that indicates if the hardware fifo is
currently enabled or disabled. If the device does not have a
hardware fifo this entry is not present.
The hardware fifo is enabled when the buffer is enabled if the
current hardware fifo watermark level is set and other current
device settings allows it (e.g. if a trigger is set that samples
data differently that the hardware fifo does then hardware fifo
will not enabled).
If the hardware fifo is enabled and the level of the hardware
fifo reaches the hardware fifo watermark level the device will
flush its hardware fifo to the device buffer. Doing a non
blocking read on the device when no samples are present in the
device buffer will also force a flush.
When the hardware fifo is enabled there is no need to use a
trigger to use buffer mode since the watermark settings
guarantees that the hardware fifo is flushed to the device
buffer.
What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
Read-only entry that contains a single integer specifying the
current watermark level for the hardware fifo. If the device
does not have a hardware fifo this entry is not present.
The watermark level for the hardware fifo is set by the driver
based on the value set by the user in buffer/watermark but
taking into account hardware limitations (e.g. most hardware
buffers are limited to 32-64 samples, some hardware buffers
watermarks are fixed or have minimum levels). A value of 0
means that the hardware watermark is unset.
What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_min
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
A single positive integer specifying the minimum watermark level
for the hardware fifo of this device. If the device does not
have a hardware fifo this entry is not present.
If the user sets buffer/watermark to a value less than this one,
then the hardware watermark will remain unset.
What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_max
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
A single positive integer specifying the maximum watermark level
for the hardware fifo of this device. If the device does not
have a hardware fifo this entry is not present.
If the user sets buffer/watermark to a value greater than this
one, then the hardware watermark will be capped at this value.
What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_available
KernelVersion: 4.2
Contact: linux-iio@vger.kernel.org
Description:
A list of positive integers specifying the available watermark
levels for the hardware fifo. This entry is optional and if it
is not present it means that all the values between
hwfifo_watermark_min and hwfifo_watermark_max are supported.
If the user sets buffer/watermark to a value greater than
hwfifo_watermak_min but not equal to any of the values in this
list, the driver will chose an appropriate value for the
hardware fifo watermark level.
Documentation/ABI/testing/sysfs-class-cxl
浏览文件 @ 6724af48
......@@ -100,7 +100,7 @@ Description: read only
Hexadecimal value of the device ID found in this AFU
configuration record.
What: /sys/class/cxl/<afu>/cr<config num>/vendor
What: /sys/class/cxl/<afu>/cr<config num>/class
Date: February 2015
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
......
Documentation/ABI/testing/sysfs-class-led-flash 0 → 100644
浏览文件 @ 6724af48
What: /sys/class/leds/<led>/flash_brightness
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read/write
Set the brightness of this LED in the flash strobe mode, in
microamperes. The file is created only for the flash LED devices
that support setting flash brightness.
The value is between 0 and
/sys/class/leds/<led>/max_flash_brightness.
What: /sys/class/leds/<led>/max_flash_brightness
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read only
Maximum brightness level for this LED in the flash strobe mode,
in microamperes.
What: /sys/class/leds/<led>/flash_timeout
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read/write
Hardware timeout for flash, in microseconds. The flash strobe
is stopped after this period of time has passed from the start
of the strobe. The file is created only for the flash LED
devices that support setting flash timeout.
What: /sys/class/leds/<led>/max_flash_timeout
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read only
Maximum flash timeout for this LED, in microseconds.
What: /sys/class/leds/<led>/flash_strobe
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read/write
Flash strobe state. When written with 1 it triggers flash strobe
and when written with 0 it turns the flash off.
On read 1 means that flash is currently strobing and 0 means
that flash is off.
What: /sys/class/leds/<led>/flash_fault
Date: March 2015
KernelVersion: 4.0
Contact: Jacek Anaszewski <j.anaszewski@samsung.com>
Description: read only
Space separated list of flash faults that may have occurred.
Flash faults are re-read after strobing the flash. Possible
flash faults:
* led-over-voltage - flash controller voltage to the flash LED
has exceeded the limit specific to the flash controller
* flash-timeout-exceeded - the flash strobe was still on when
the timeout set by the user has expired; not all flash
controllers may set this in all such conditions
* controller-over-temperature - the flash controller has
overheated
* controller-short-circuit - the short circuit protection
of the flash controller has been triggered
* led-power-supply-over-current - current in the LED power
supply has exceeded the limit specific to the flash
controller
* indicator-led-fault - the flash controller has detected
a short or open circuit condition on the indicator LED
* led-under-voltage - flash controller voltage to the flash
LED has been below the minimum limit specific to
the flash
* controller-under-voltage - the input voltage of the flash
controller is below the limit under which strobing the
flash at full current will not be possible;
the condition persists until this flag is no longer set
* led-over-temperature - the temperature of the LED has exceeded
its allowed upper limit
Documentation/ABI/testing/sysfs-class-mtd
浏览文件 @ 6724af48
......@@ -222,3 +222,13 @@ Description:
The number of blocks that are marked as reserved, if any, in
this partition. These are typically used to store the in-flash
bad block table (BBT).
What: /sys/class/mtd/mtdX/offset
Date: March 2015
KernelVersion: 4.1
Contact: linux-mtd@lists.infradead.org
Description:
For a partition, the offset of that partition from the start
of the master device in bytes. This attribute is absent on
main devices, so it can be used to distinguish between
partitions and devices that aren't partitions.
Documentation/ABI/testing/sysfs-class-net
浏览文件 @ 6724af48
......@@ -188,6 +188,14 @@ Description:
Indicates the interface unique physical port identifier within
the NIC, as a string.
What: /sys/class/net/<iface>/phys_port_name
Date: March 2015
KernelVersion: 4.0
Contact: netdev@vger.kernel.org
Description:
Indicates the interface physical port name within the NIC,
as a string.
What: /sys/class/net/<iface>/speed
Date: October 2009
KernelVersion: 2.6.33
......
Documentation/ABI/testing/sysfs-class-net-queues
浏览文件 @ 6724af48
......@@ -24,6 +24,14 @@ Description:
Indicates the number of transmit timeout events seen by this
network interface transmit queue.
What: /sys/class/<iface>/queues/tx-<queue>/tx_maxrate
Date: March 2015
KernelVersion: 4.1
Contact: netdev@vger.kernel.org
Description:
A Mbps max-rate set for the queue, a value of zero means disabled,
default is disabled.
What: /sys/class/<iface>/queues/tx-<queue>/xps_cpus
Date: November 2010
KernelVersion: 2.6.38
......
Documentation/ABI/testing/sysfs-driver-hid
浏览文件 @ 6724af48
......@@ -8,3 +8,13 @@ Description: When read, this file returns the device's raw binary HID
report descriptor.
This file cannot be written.
Users: HIDAPI library (http://www.signal11.us/oss/hidapi)
What: For USB devices : /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
For BT devices : /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
Symlink : /sys/class/hidraw/hidraw<num>/device/country
Date: February 2015
KernelVersion: 3.19
Contact: Olivier Gay <ogay@logitech.com>
Description: When read, this file returns the hex integer value in ASCII
of the device's HID country code (e.g. 21 for US).
This file cannot be written.
Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff
浏览文件 @ 6724af48
......@@ -5,3 +5,48 @@ Contact: Michal Malý <madcatxster@gmail.com>
Description: Display minimum, maximum and current range of the steering
wheel. Writing a value within min and max boundaries sets the
range of the wheel.
What: /sys/bus/hid/drivers/logitech/<dev>/alternate_modes
Date: Feb 2015
KernelVersion: 4.1
Contact: Michal Malý <madcatxster@gmail.com>
Description: Displays a set of alternate modes supported by a wheel. Each
mode is listed as follows:
Tag: Mode Name
Currently active mode is marked with an asterisk. List also
contains an abstract item "native" which always denotes the
native mode of the wheel. Echoing the mode tag switches the
wheel into the corresponding mode. Depending on the exact model
of the wheel not all listed modes might always be selectable.
If a wheel cannot be switched into the desired mode, -EINVAL
is returned accompanied with an explanatory message in the
kernel log.
This entry is not created for devices that have only one mode.
Currently supported mode switches:
Driving Force Pro:
DF-EX --> DFP
G25:
DF-EX --> DFP --> G25
G27:
DF-EX <*> DFP <-> G25 <-> G27
DF-EX <*--------> G25 <-> G27
DF-EX <*----------------> G27
DFGT:
DF-EX <*> DFP <-> DFGT
DF-EX <*--------> DFGT
* hid_logitech module must be loaded with lg4ff_no_autoswitch=1
parameter set in order for the switch to DF-EX mode to work.
What: /sys/bus/hid/drivers/logitech/<dev>/real_id
Date: Feb 2015
KernelVersion: 4.1
Contact: Michal Malý <madcatxster@gmail.com>
Description: Displays the real model of the wheel regardless of any
alternate mode the wheel might be switched to.
It is a read-only value.
This entry is not created for devices that have only one mode.
Documentation/ABI/testing/sysfs-driver-toshiba_acpi
浏览文件 @ 6724af48
......@@ -8,9 +8,11 @@ Description: This file controls the keyboard backlight operation mode, valid
* 0x2 -> AUTO (also called TIMER)
* 0x8 -> ON
* 0x10 -> OFF
Note that the kernel 3.16 onwards this file accepts all listed
Note that from kernel 3.16 onwards this file accepts all listed
parameters, kernel 3.15 only accepts the first two (FN-Z and
AUTO).
Also note that toggling this value on type 1 devices, requires
a reboot for changes to take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
......@@ -67,15 +69,72 @@ Description: This file shows the current keyboard backlight type,
* 2 -> Type 2, supporting modes TIMER, ON and OFF
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Sleep & Charge charging mode, which
can be:
* 0 -> Disabled (0x00)
* 1 -> Alternate (0x09)
* 2 -> Auto (0x21)
* 3 -> Typical (0x11)
Note that from kernel 4.1 onwards this file accepts all listed
values, kernel 4.0 only supports the first three.
Note that this feature only works when connected to power, if
you want to use it under battery, see the entry named
"sleep_functions_on_battery"
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Sleep Functions under battery, and
set the level at which point they will be disabled, accepted
values can be:
* 0 -> Disabled
* 1-100 -> Battery level to disable sleep functions
Currently it prints two values, the first one indicates if the
feature is enabled or disabled, while the second one shows the
current battery level set.
Note that when the value is set to disabled, the sleep function
will only work when connected to power.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Rapid Charge state, which can be:
* 0 -> Disabled
* 1 -> Enabled
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_music
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the Sleep & Music state, which values can be:
* 0 -> Disabled
* 1 -> Enabled
Note that this feature only works when connected to power, if
you want to use it under battery, see the entry named
"sleep_functions_on_battery"
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file shows the current version of the driver
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the state of the internal fan, valid
values are:
......@@ -83,8 +142,8 @@ Description: This file controls the state of the internal fan, valid
* 1 -> ON
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_function_keys
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the Special Functions (hotkeys) operation
mode, valid values are:
......@@ -94,21 +153,29 @@ Description: This file controls the Special Functions (hotkeys) operation
and the hotkeys are accessed via FN-F{1-12}.
In the "Special Functions" mode, the F{1-12} keys trigger the
hotkey and the F{1-12} keys are accessed via FN-F{1-12}.
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls whether the laptop should turn ON whenever
the LID is opened, valid values are:
* 0 -> Disabled
* 1 -> Enabled
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_three
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls whether the USB 3 functionality, valid
values are:
Description: This file controls the USB 3 functionality, valid values are:
* 0 -> Disabled (Acts as a regular USB 2)
* 1 -> Enabled (Full USB 3 functionality)
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
Documentation/ABI/testing/sysfs-platform-dell-laptop 0 → 100644
浏览文件 @ 6724af48
What: /sys/class/leds/dell::kbd_backlight/als_enabled
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to control the automatic keyboard
illumination mode on some systems that have an ambient
light sensor. Write 1 to this file to enable the auto
mode, 0 to disable it.
What: /sys/class/leds/dell::kbd_backlight/als_setting
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to specifiy the on/off threshold value,
as reported by the ambient light sensor.
What: /sys/class/leds/dell::kbd_backlight/start_triggers
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to control the input triggers that
turn on the keyboard backlight illumination that is
disabled because of inactivity.
Read the file to see the triggers available. The ones
enabled are preceded by '+', those disabled by '-'.
To enable a trigger, write its name preceded by '+' to
this file. To disable a trigger, write its name preceded
by '-' instead.
For example, to enable the keyboard as trigger run:
echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
To disable it:
echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
Note that not all the available triggers can be configured.
What: /sys/class/leds/dell::kbd_backlight/stop_timeout
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to specify the interval after which the
keyboard illumination is disabled because of inactivity.
The timeouts are expressed in seconds, minutes, hours and
days, for which the symbols are 's', 'm', 'h' and 'd'
respectively.
To configure the timeout, write to this file a value along
with any the above units. If no unit is specified, the value
is assumed to be expressed in seconds.
For example, to set the timeout to 10 minutes run:
echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout
Note that when this file is read, the returned value might be
expressed in a different unit than the one used when the timeout
was set.
Also note that only some timeouts are supported and that
some systems might fall back to a specific timeout in case
an invalid timeout is written to this file.
Documentation/CodeOfConflict 0 → 100644
浏览文件 @ 6724af48
Code of Conflict
----------------
The Linux kernel development effort is a very personal process compared
to "traditional" ways of developing software. Your code and ideas
behind it will be carefully reviewed, often resulting in critique and
criticism. The review will almost always require improvements to the
code before it can be included in the kernel. Know that this happens
because everyone involved wants to see the best possible solution for
the overall success of Linux. This development process has been proven
to create the most robust operating system kernel ever, and we do not
want to do anything to cause the quality of submission and eventual
result to ever decrease.
If however, anyone feels personally abused, threatened, or otherwise
uncomfortable due to this process, that is not acceptable. If so,
please contact the Linux Foundation's Technical Advisory Board at
<tab@lists.linux-foundation.org>, or the individual members, and they
will work to resolve the issue to the best of their ability. For more
information on who is on the Technical Advisory Board and what their
role is, please see:
http://www.linuxfoundation.org/programs/advisory-councils/tab
As a reviewer of code, please strive to keep things civil and focused on
the technical issues involved. We are all humans, and frustrations can
be high on both sides of the process. Try to keep in mind the immortal
words of Bill and Ted, "Be excellent to each other."
Documentation/CodingStyle
浏览文件 @ 6724af48
......@@ -13,7 +13,7 @@ and NOT read it. Burn them, it's a great symbolic gesture.
Anyway, here goes:
Chapter 1: Indentation
Chapter 1: Indentation
Tabs are 8 characters, and thus indentations are also 8 characters.
There are heretic movements that try to make indentations 4 (or even 2!)
......@@ -56,7 +56,6 @@ instead of "double-indenting" the "case" labels. E.g.:
break;
}
Don't put multiple statements on a single line unless you have
something to hide:
......@@ -156,25 +155,25 @@ comments on.
Do not unnecessarily use braces where a single statement will do.
if (condition)
action();
if (condition)
action();
and
if (condition)
do_this();
else
do_that();
if (condition)
do_this();
else
do_that();
This does not apply if only one branch of a conditional statement is a single
statement; in the latter case use braces in both branches:
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
3.1: Spaces
......@@ -186,8 +185,11 @@ although they are not required in the language, as in: "sizeof info" after
"struct fileinfo info;" is declared).
So use a space after these keywords:
if, switch, case, for, do, while
but not with sizeof, typeof, alignof, or __attribute__. E.g.,
s = sizeof(struct file);
Do not add spaces around (inside) parenthesized expressions. This example is
......@@ -209,12 +211,15 @@ such as any of these:
= + - < > * / % | & ^ <= >= == != ? :
but no space after unary operators:
& * + - ~ ! sizeof typeof alignof __attribute__ defined
no space before the postfix increment & decrement unary operators:
++ --
no space after the prefix increment & decrement unary operators:
++ --
and no space around the '.' and "->" structure member operators.
......@@ -268,13 +273,11 @@ See chapter 6 (Functions).
Chapter 5: Typedefs
Please don't use things like "vps_t".
It's a _mistake_ to use typedef for structures and pointers. When you see a
vps_t a;
in the source, what does it mean?
In contrast, if it says
struct virtual_container *a;
......@@ -372,11 +375,11 @@ In source files, separate functions with one blank line. If the function is
exported, the EXPORT* macro for it should follow immediately after the closing
function brace line. E.g.:
int system_is_up(void)
{
return system_state == SYSTEM_RUNNING;
}
EXPORT_SYMBOL(system_is_up);
int system_is_up(void)
{
return system_state == SYSTEM_RUNNING;
}
EXPORT_SYMBOL(system_is_up);
In function prototypes, include parameter names with their data types.
Although this is not required by the C language, it is preferred in Linux
......@@ -405,34 +408,34 @@ The rationale for using gotos is:
modifications are prevented
- saves the compiler work to optimize redundant code away ;)
int fun(int a)
{
int result = 0;
char *buffer;
buffer = kmalloc(SIZE, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
if (condition1) {
while (loop1) {
...
int fun(int a)
{
int result = 0;
char *buffer;
buffer = kmalloc(SIZE, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
if (condition1) {
while (loop1) {
...
}
result = 1;
goto out_buffer;
}
result = 1;
goto out_buffer;
...
out_buffer:
kfree(buffer);
return result;
}
...
out_buffer:
kfree(buffer);
return result;
}
A common type of bug to be aware of it "one err bugs" which look like this:
err:
kfree(foo->bar);
kfree(foo);
return ret;
err:
kfree(foo->bar);
kfree(foo);
return ret;
The bug in this code is that on some exit paths "foo" is NULL. Normally the
fix for this is to split it up into two error labels "err_bar:" and "err_foo:".
......@@ -503,9 +506,9 @@ values. To do the latter, you can stick the following in your .emacs file:
(defun c-lineup-arglist-tabs-only (ignored)
"Line up argument lists by tabs, not spaces"
(let* ((anchor (c-langelem-pos c-syntactic-element))
(column (c-langelem-2nd-pos c-syntactic-element))
(offset (- (1+ column) anchor))
(steps (floor offset c-basic-offset)))
(column (c-langelem-2nd-pos c-syntactic-element))
(offset (- (1+ column) anchor))
(steps (floor offset c-basic-offset)))
(* (max steps 1)
c-basic-offset)))
......@@ -612,7 +615,7 @@ have a reference count on it, you almost certainly have a bug.
Names of macros defining constants and labels in enums are capitalized.
#define CONSTANT 0x12345
#define CONSTANT 0x12345
Enums are preferred when defining several related constants.
......@@ -623,28 +626,28 @@ Generally, inline functions are preferable to macros resembling functions.
Macros with multiple statements should be enclosed in a do - while block:
#define macrofun(a, b, c) \
do { \
if (a == 5) \
do_this(b, c); \
} while (0)
#define macrofun(a, b, c) \
do { \
if (a == 5) \
do_this(b, c); \
} while (0)
Things to avoid when using macros:
1) macros that affect control flow:
#define FOO(x) \
do { \
if (blah(x) < 0) \
return -EBUGGERED; \
} while(0)
#define FOO(x) \
do { \
if (blah(x) < 0) \
return -EBUGGERED; \
} while(0)
is a _very_ bad idea. It looks like a function call but exits the "calling"
function; don't break the internal parsers of those who will read the code.
2) macros that depend on having a local variable with a magic name:
#define FOO(val) bar(index, val)
#define FOO(val) bar(index, val)
might look like a good thing, but it's confusing as hell when one reads the
code and it's prone to breakage from seemingly innocent changes.
......@@ -656,8 +659,21 @@ bite you if somebody e.g. turns FOO into an inline function.
must enclose the expression in parentheses. Beware of similar issues with
macros using parameters.
#define CONSTANT 0x4000
#define CONSTEXP (CONSTANT | 3)
#define CONSTANT 0x4000
#define CONSTEXP (CONSTANT | 3)
5) namespace collisions when defining local variables in macros resembling
functions:
#define FOO(x) \
({ \
typeof(x) ret; \
ret = calc_ret(x); \
(ret); \
)}
ret is a common name for a local variable - __foo_ret is less likely
to collide with an existing variable.
The cpp manual deals with macros exhaustively. The gcc internals manual also
covers RTL which is used frequently with assembly language in the kernel.
......@@ -796,11 +812,11 @@ you should use, rather than explicitly coding some variant of them yourself.
For example, if you need to calculate the length of an array, take advantage
of the macro
#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
Similarly, if you need to calculate the size of some structure member, use
#define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
#define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
There are also min() and max() macros that do strict type checking if you
need them. Feel free to peruse that header file to see what else is already
......@@ -813,19 +829,19 @@ Some editors can interpret configuration information embedded in source files,
indicated with special markers. For example, emacs interprets lines marked
like this:
-*- mode: c -*-
-*- mode: c -*-
Or like this:
/*
Local Variables:
compile-command: "gcc -DMAGIC_DEBUG_FLAG foo.c"
End:
*/
/*
Local Variables:
compile-command: "gcc -DMAGIC_DEBUG_FLAG foo.c"
End:
*/
Vim interprets markers that look like this:
/* vim:set sw=8 noet */
/* vim:set sw=8 noet */
Do not include any of these in source files. People have their own personal
editor configurations, and your source files should not override them. This
......@@ -902,9 +918,9 @@ At the end of any non-trivial #if or #ifdef block (more than a few lines),
place a comment after the #endif on the same line, noting the conditional
expression used. For instance:
#ifdef CONFIG_SOMETHING
...
#endif /* CONFIG_SOMETHING */
#ifdef CONFIG_SOMETHING
...
#endif /* CONFIG_SOMETHING */
Appendix I: References
......
Documentation/DocBook/drm.tmpl
浏览文件 @ 6724af48
......@@ -1293,7 +1293,7 @@ int max_width, max_height;</synopsis>
</para>
<para>
If a page flip can be successfully scheduled the driver must set the
<code>drm_crtc-&lt;fb</code> field to the new framebuffer pointed to
<code>drm_crtc-&gt;fb</code> field to the new framebuffer pointed to
by <code>fb</code>. This is important so that the reference counting
on framebuffers stays balanced.
</para>
......@@ -3979,6 +3979,11 @@ int num_ioctls;</synopsis>
!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_disable_interrupts
!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_enable_interrupts
</sect2>
<sect2>
<title>Intel GVT-g Guest Support(vGPU)</title>
!Pdrivers/gpu/drm/i915/i915_vgpu.c Intel GVT-g guest support
!Idrivers/gpu/drm/i915/i915_vgpu.c
</sect2>
</sect1>
<sect1>
<title>Display Hardware Handling</title>
......@@ -4046,6 +4051,17 @@ int num_ioctls;</synopsis>
<title>Frame Buffer Compression (FBC)</title>
!Pdrivers/gpu/drm/i915/intel_fbc.c Frame Buffer Compression (FBC)
!Idrivers/gpu/drm/i915/intel_fbc.c
</sect2>
<sect2>
<title>Display Refresh Rate Switching (DRRS)</title>
!Pdrivers/gpu/drm/i915/intel_dp.c Display Refresh Rate Switching (DRRS)
!Fdrivers/gpu/drm/i915/intel_dp.c intel_dp_set_drrs_state
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_enable
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_disable
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_invalidate
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_flush
!Fdrivers/gpu/drm/i915/intel_dp.c intel_dp_drrs_init
</sect2>
<sect2>
<title>DPIO</title>
......@@ -4168,7 +4184,7 @@ int num_ioctls;</synopsis>
<sect2>
<title>Buffer Object Eviction</title>
<para>
This section documents the interface function for evicting buffer
This section documents the interface functions for evicting buffer
objects to make space available in the virtual gpu address spaces.
Note that this is mostly orthogonal to shrinking buffer objects
caches, which has the goal to make main memory (shared with the gpu
......@@ -4176,6 +4192,17 @@ int num_ioctls;</synopsis>
</para>
!Idrivers/gpu/drm/i915/i915_gem_evict.c
</sect2>
<sect2>
<title>Buffer Object Memory Shrinking</title>
<para>
This section documents the interface function for shrinking memory
usage of buffer object caches. Shrinking is used to make main memory
available. Note that this is mostly orthogonal to evicting buffer
objects, which has the goal to make space in gpu virtual address
spaces.
</para>
!Idrivers/gpu/drm/i915/i915_gem_shrinker.c
</sect2>
</sect1>
<sect1>
......
Documentation/DocBook/media/v4l/biblio.xml
浏览文件 @ 6724af48
<bibliography>
<title>References</title>
<biblioentry id="eia608">
<abbrev>EIA&nbsp;608-B</abbrev>
<biblioentry id="cea608">
<abbrev>CEA&nbsp;608-E</abbrev>
<authorgroup>
<corpauthor>Electronic Industries Alliance (<ulink
url="http://www.eia.org">http://www.eia.org</ulink>)</corpauthor>
<corpauthor>Consumer Electronics Association (<ulink
url="http://www.ce.org">http://www.ce.org</ulink>)</corpauthor>
</authorgroup>
<title>EIA 608-B "Recommended Practice for Line 21 Data
Service"</title>
<title>CEA-608-E R-2014 "Line 21 Data Services"</title>
</biblioentry>
<biblioentry id="en300294">
......
Documentation/DocBook/media/v4l/compat.xml
浏览文件 @ 6724af48
......@@ -2491,7 +2491,7 @@ that used it. It was originally scheduled for removal in 2.6.35.
</listitem>
<listitem>
<para>Added <constant>V4L2_EVENT_CTRL_CH_RANGE</constant> control event
changes flag. See <xref linkend="changes-flags"/>.</para>
changes flag. See <xref linkend="ctrl-changes-flags"/>.</para>
</listitem>
</orderedlist>
</section>
......
Documentation/DocBook/media/v4l/dev-sliced-vbi.xml
浏览文件 @ 6724af48
......@@ -254,7 +254,7 @@ ETS&nbsp;300&nbsp;231, lsb first transmitted.</entry>
<row>
<entry><constant>V4L2_SLICED_CAPTION_525</constant></entry>
<entry>0x1000</entry>
<entry><xref linkend="eia608" /></entry>
<entry><xref linkend="cea608" /></entry>
<entry>NTSC line 21, 284 (second field 21)</entry>
<entry>Two bytes in transmission order, including parity
bit, lsb first transmitted.</entry>
......
Documentation/DocBook/media/v4l/media-ioc-enum-entities.xml
浏览文件 @ 6724af48
......@@ -143,86 +143,28 @@
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>v4l</structfield></entry>
<entry><structfield>dev</structfield></entry>
<entry></entry>
<entry>Valid for V4L sub-devices and nodes only.</entry>
<entry>Valid for (sub-)devices that create a single device node.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>major</structfield></entry>
<entry>V4L device node major number. For V4L sub-devices with no
device node, set by the driver to 0.</entry>
<entry>Device node major number.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>minor</structfield></entry>
<entry>V4L device node minor number. For V4L sub-devices with no
device node, set by the driver to 0.</entry>
</row>
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>fb</structfield></entry>
<entry></entry>
<entry>Valid for frame buffer nodes only.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>major</structfield></entry>
<entry>Frame buffer device node major number.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>minor</structfield></entry>
<entry>Frame buffer device node minor number.</entry>
</row>
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>alsa</structfield></entry>
<entry></entry>
<entry>Valid for ALSA devices only.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>card</structfield></entry>
<entry>ALSA card number</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>device</structfield></entry>
<entry>ALSA device number</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>subdevice</structfield></entry>
<entry>ALSA sub-device number</entry>
</row>
<row>
<entry></entry>
<entry>int</entry>
<entry><structfield>dvb</structfield></entry>
<entry></entry>
<entry>DVB card number</entry>
<entry>Device node minor number.</entry>
</row>
<row>
<entry></entry>
<entry>__u8</entry>
<entry><structfield>raw</structfield>[180]</entry>
<entry><structfield>raw</structfield>[184]</entry>
<entry></entry>
<entry></entry>
</row>
......@@ -253,8 +195,24 @@
<entry>ALSA card</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB</constant></entry>
<entry>DVB card</entry>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_FE</constant></entry>
<entry>DVB frontend devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DEMUX</constant></entry>
<entry>DVB demux devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DVR</constant></entry>
<entry>DVB DVR devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_CA</constant></entry>
<entry>DVB CAM devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_NET</constant></entry>
<entry>DVB network devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV</constant></entry>
......@@ -282,6 +240,10 @@
it in some digital video standard, with appropriate embedded timing
signals.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_TUNER</constant></entry>
<entry>TV and/or radio tuner</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/pixfmt-packed-rgb.xml
浏览文件 @ 6724af48
......@@ -303,45 +303,6 @@ for a pixel lie next to each other in memory.</para>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
</row>
<row id="V4L2-PIX-FMT-BGR666">
<entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
<entry>'BGRH'</entry>
<entry></entry>
<entry>b<subscript>5</subscript></entry>
<entry>b<subscript>4</subscript></entry>
<entry>b<subscript>3</subscript></entry>
<entry>b<subscript>2</subscript></entry>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
<entry>g<subscript>5</subscript></entry>
<entry>g<subscript>4</subscript></entry>
<entry></entry>
<entry>g<subscript>3</subscript></entry>
<entry>g<subscript>2</subscript></entry>
<entry>g<subscript>1</subscript></entry>
<entry>g<subscript>0</subscript></entry>
<entry>r<subscript>5</subscript></entry>
<entry>r<subscript>4</subscript></entry>
<entry>r<subscript>3</subscript></entry>
<entry>r<subscript>2</subscript></entry>
<entry></entry>
<entry>r<subscript>1</subscript></entry>
<entry>r<subscript>0</subscript></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
</row>
<row id="V4L2-PIX-FMT-BGR24">
<entry><constant>V4L2_PIX_FMT_BGR24</constant></entry>
<entry>'BGR3'</entry>
......@@ -404,6 +365,46 @@ for a pixel lie next to each other in memory.</para>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
</row>
<row id="V4L2-PIX-FMT-BGR666">
<entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
<entry>'BGRH'</entry>
<entry></entry>
<entry>b<subscript>5</subscript></entry>
<entry>b<subscript>4</subscript></entry>
<entry>b<subscript>3</subscript></entry>
<entry>b<subscript>2</subscript></entry>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
<entry>g<subscript>5</subscript></entry>
<entry>g<subscript>4</subscript></entry>
<entry></entry>
<entry>g<subscript>3</subscript></entry>
<entry>g<subscript>2</subscript></entry>
<entry>g<subscript>1</subscript></entry>
<entry>g<subscript>0</subscript></entry>
<entry>r<subscript>5</subscript></entry>
<entry>r<subscript>4</subscript></entry>
<entry>r<subscript>3</subscript></entry>
<entry>r<subscript>2</subscript></entry>
<entry></entry>
<entry>r<subscript>1</subscript></entry>
<entry>r<subscript>0</subscript></entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry></entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
</row>
<row id="V4L2-PIX-FMT-ABGR32">
<entry><constant>V4L2_PIX_FMT_ABGR32</constant></entry>
<entry>'AR24'</entry>
......
Documentation/DocBook/media/v4l/pixfmt-sgrbg8.xml
浏览文件 @ 6724af48
......@@ -38,10 +38,10 @@ columns and rows.</para>
</row>
<row>
<entry>start&nbsp;+&nbsp;4:</entry>
<entry>R<subscript>10</subscript></entry>
<entry>B<subscript>11</subscript></entry>
<entry>R<subscript>12</subscript></entry>
<entry>B<subscript>13</subscript></entry>
<entry>B<subscript>10</subscript></entry>
<entry>G<subscript>11</subscript></entry>
<entry>B<subscript>12</subscript></entry>
<entry>G<subscript>13</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;8:</entry>
......@@ -52,10 +52,10 @@ columns and rows.</para>
</row>
<row>
<entry>start&nbsp;+&nbsp;12:</entry>
<entry>R<subscript>30</subscript></entry>
<entry>B<subscript>31</subscript></entry>
<entry>R<subscript>32</subscript></entry>
<entry>B<subscript>33</subscript></entry>
<entry>B<subscript>30</subscript></entry>
<entry>G<subscript>31</subscript></entry>
<entry>B<subscript>32</subscript></entry>
<entry>G<subscript>33</subscript></entry>
</row>
</tbody>
</tgroup>
......
Documentation/DocBook/media/v4l/pixfmt-srggb10p.xml
浏览文件 @ 6724af48
......@@ -38,7 +38,7 @@
<title>Byte Order.</title>
<para>Each cell is one byte.
<informaltable frame="topbot" colsep="1" rowsep="1">
<tgroup cols="5" align="center" border="1">
<tgroup cols="5" align="center">
<colspec align="left" colwidth="2*" />
<tbody valign="top">
<row>
......
Documentation/DocBook/media/v4l/pixfmt-yuv420m.xml
浏览文件 @ 6724af48
......@@ -29,12 +29,12 @@ and Cr planes have half as many pad bytes after their rows. In other
words, two Cx rows (including padding) is exactly as long as one Y row
(including padding).</para>
<para><constant>V4L2_PIX_FMT_NV12M</constant> is intended to be
<para><constant>V4L2_PIX_FMT_YUV420M</constant> is intended to be
used only in drivers and applications that support the multi-planar API,
described in <xref linkend="planar-apis"/>. </para>
<example>
<title><constant>V4L2_PIX_FMT_YVU420M</constant> 4 &times; 4
<title><constant>V4L2_PIX_FMT_YUV420M</constant> 4 &times; 4
pixel image</title>
<formalpara>
......
Documentation/DocBook/media/v4l/pixfmt.xml
浏览文件 @ 6724af48
......@@ -80,9 +80,9 @@ padding bytes after the last line of an image cross a system page
boundary. Input devices may write padding bytes, the value is
undefined. Output devices ignore the contents of padding
bytes.</para><para>When the image format is planar the
<structfield>bytesperline</structfield> value applies to the largest
<structfield>bytesperline</structfield> value applies to the first
plane and is divided by the same factor as the
<structfield>width</structfield> field for any smaller planes. For
<structfield>width</structfield> field for the other planes. For
example the Cb and Cr planes of a YUV 4:2:0 image have half as many
padding bytes following each line as the Y plane. To avoid ambiguities
drivers must return a <structfield>bytesperline</structfield> value
......@@ -182,14 +182,14 @@ see <xref linkend="colorspaces" />.</entry>
</entry>
</row>
<row>
<entry>__u16</entry>
<entry>__u32</entry>
<entry><structfield>bytesperline</structfield></entry>
<entry>Distance in bytes between the leftmost pixels in two adjacent
lines. See &v4l2-pix-format;.</entry>
</row>
<row>
<entry>__u16</entry>
<entry><structfield>reserved[7]</structfield></entry>
<entry><structfield>reserved[6]</structfield></entry>
<entry>Reserved for future extensions. Should be zeroed by the
application.</entry>
</row>
......@@ -483,8 +483,8 @@ is the Y'CbCr encoding identifier (&v4l2-ycbcr-encoding;) to specify non-standar
Y'CbCr encodings and the third is the quantization identifier (&v4l2-quantization;)
to specify non-standard quantization methods. Most of the time only the colorspace
field of &v4l2-pix-format; or &v4l2-pix-format-mplane; needs to be filled in. Note
that the default R'G'B' quantization is always full range for all colorspaces,
so this won't be mentioned explicitly for each colorspace description.</para>
that the default R'G'B' quantization is full range for all colorspaces except for
BT.2020 which uses limited range R'G'B' quantization.</para>
<table pgwide="1" frame="none" id="v4l2-colorspace">
<title>V4L2 Colorspaces</title>
......@@ -598,7 +598,8 @@ so this won't be mentioned explicitly for each colorspace description.</para>
<row>
<entry><constant>V4L2_QUANTIZATION_DEFAULT</constant></entry>
<entry>Use the default quantization encoding as defined by the colorspace.
This is always full range for R'G'B' and usually limited range for Y'CbCr.</entry>
This is always full range for R'G'B' (except for the BT.2020 colorspace) and usually
limited range for Y'CbCr.</entry>
</row>
<row>
<entry><constant>V4L2_QUANTIZATION_FULL_RANGE</constant></entry>
......@@ -620,8 +621,8 @@ is mapped to [16&hellip;235]. Cb and Cr are mapped from [-0.5&hellip;0.5] to [16
<section>
<title>Detailed Colorspace Descriptions</title>
<section>
<title id="col-smpte-170m">Colorspace SMPTE 170M (<constant>V4L2_COLORSPACE_SMPTE170M</constant>)</title>
<section id="col-smpte-170m">
<title>Colorspace SMPTE 170M (<constant>V4L2_COLORSPACE_SMPTE170M</constant>)</title>
<para>The <xref linkend="smpte170m" /> standard defines the colorspace used by NTSC and PAL and by SDTV
in general. The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_601</constant>.
The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and
......@@ -666,8 +667,7 @@ as the SMPTE C set, so this colorspace is sometimes called SMPTE C as well.</par
<variablelist>
<varlistentry>
<term>The transfer function defined for SMPTE 170M is the same as the
one defined in Rec. 709. Normally L is in the range [0&hellip;1], but for the extended
gamut xvYCC encoding values outside that range are allowed.</term>
one defined in Rec. 709.</term>
<listitem>
<para>L' = -1.099(-L)<superscript>0.45</superscript>&nbsp;+&nbsp;0.099&nbsp;for&nbsp;L&nbsp;&le;&nbsp;-0.018</para>
<para>L' = 4.5L&nbsp;for&nbsp;-0.018&nbsp;&lt;&nbsp;L&nbsp;&lt;&nbsp;0.018</para>
......@@ -702,29 +702,10 @@ defined in the <xref linkend="itu601" /> standard and this colorspace is sometim
though BT.601 does not mention any color primaries.</para>
<para>The default quantization is limited range, but full range is possible although
rarely seen.</para>
<para>The <constant>V4L2_YCBCR_ENC_601</constant> encoding as described above is the
default for this colorspace, but it can be overridden with <constant>V4L2_YCBCR_ENC_709</constant>,
in which case the Rec. 709 Y'CbCr encoding is used.</para>
<variablelist>
<varlistentry>
<term>The xvYCC 601 encoding (<constant>V4L2_YCBCR_ENC_XV601</constant>, <xref linkend="xvycc" />) is similar
to the BT.601 encoding, but it allows for R', G' and B' values that are outside the range
[0&hellip;1]. The resulting Y', Cb and Cr values are scaled and offset:</term>
<listitem>
<para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;255)</para>
<para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B')</para>
<para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B')</para>
</listitem>
</varlistentry>
</variablelist>
<para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are clamped
to the range [-0.5&hellip;0.5]. The non-standard xvYCC 709 encoding can also be used by selecting
<constant>V4L2_YCBCR_ENC_XV709</constant>. The xvYCC encodings always use full range
quantization.</para>
</section>
<section>
<title id="col-rec709">Colorspace Rec. 709 (<constant>V4L2_COLORSPACE_REC709</constant>)</title>
<section id="col-rec709">
<title>Colorspace Rec. 709 (<constant>V4L2_COLORSPACE_REC709</constant>)</title>
<para>The <xref linkend="itu709" /> standard defines the colorspace used by HDTV in general. The default
Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_709</constant>. The default Y'CbCr quantization is
limited range. The chromaticities of the primary colors and the white reference are:</para>
......@@ -803,26 +784,39 @@ rarely seen.</para>
<para>The <constant>V4L2_YCBCR_ENC_709</constant> encoding described above is the default
for this colorspace, but it can be overridden with <constant>V4L2_YCBCR_ENC_601</constant>, in which
case the BT.601 Y'CbCr encoding is used.</para>
<para>Two additional extended gamut Y'CbCr encodings are also possible with this colorspace:</para>
<variablelist>
<varlistentry>
<term>The xvYCC 709 encoding (<constant>V4L2_YCBCR_ENC_XV709</constant>, <xref linkend="xvycc" />)
is similar to the Rec. 709 encoding, but it allows for R', G' and B' values that are outside the range
[0&hellip;1]. The resulting Y', Cb and Cr values are scaled and offset:</term>
<listitem>
<para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.2126R'&nbsp;+&nbsp;0.7152G'&nbsp;+&nbsp;0.0722B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;255)</para>
<para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(-0.1146R'&nbsp;-&nbsp;0.3854G'&nbsp;+&nbsp;0.5B')</para>
<para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;255)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.4542G'&nbsp;-&nbsp;0.0458B')</para>
<para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;256)&nbsp;*&nbsp;(0.2126R'&nbsp;+&nbsp;0.7152G'&nbsp;+&nbsp;0.0722B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;256)</para>
<para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;256)&nbsp;*&nbsp;(-0.1146R'&nbsp;-&nbsp;0.3854G'&nbsp;+&nbsp;0.5B')</para>
<para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;256)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.4542G'&nbsp;-&nbsp;0.0458B')</para>
</listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry>
<term>The xvYCC 601 encoding (<constant>V4L2_YCBCR_ENC_XV601</constant>, <xref linkend="xvycc" />) is similar
to the BT.601 encoding, but it allows for R', G' and B' values that are outside the range
[0&hellip;1]. The resulting Y', Cb and Cr values are scaled and offset:</term>
<listitem>
<para>Y'&nbsp;=&nbsp;(219&nbsp;/&nbsp;256)&nbsp;*&nbsp;(0.299R'&nbsp;+&nbsp;0.587G'&nbsp;+&nbsp;0.114B')&nbsp;+&nbsp;(16&nbsp;/&nbsp;256)</para>
<para>Cb&nbsp;=&nbsp;(224&nbsp;/&nbsp;256)&nbsp;*&nbsp;(-0.169R'&nbsp;-&nbsp;0.331G'&nbsp;+&nbsp;0.5B')</para>
<para>Cr&nbsp;=&nbsp;(224&nbsp;/&nbsp;256)&nbsp;*&nbsp;(0.5R'&nbsp;-&nbsp;0.419G'&nbsp;-&nbsp;0.081B')</para>
</listitem>
</varlistentry>
</variablelist>
<para>Y' is clamped to the range [0&hellip;1] and Cb and Cr are clamped
to the range [-0.5&hellip;0.5]. The non-standard xvYCC 601 encoding can also be used by
selecting <constant>V4L2_YCBCR_ENC_XV601</constant>. The xvYCC encodings always use full
range quantization.</para>
to the range [-0.5&hellip;0.5]. The non-standard xvYCC 709 or xvYCC 601 encodings can be used by
selecting <constant>V4L2_YCBCR_ENC_XV709</constant> or <constant>V4L2_YCBCR_ENC_XV601</constant>.
The xvYCC encodings always use full range quantization.</para>
</section>
<section>
<title id="col-srgb">Colorspace sRGB (<constant>V4L2_COLORSPACE_SRGB</constant>)</title>
<section id="col-srgb">
<title>Colorspace sRGB (<constant>V4L2_COLORSPACE_SRGB</constant>)</title>
<para>The <xref linkend="srgb" /> standard defines the colorspace used by most webcams and computer graphics. The
default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_SYCC</constant>. The default Y'CbCr quantization
is full range. The chromaticities of the primary colors and the white reference are:</para>
......@@ -898,8 +892,8 @@ encoding, it is not. The <constant>V4L2_YCBCR_ENC_XV601</constant> scales and of
values before quantization, but this encoding does not do that.</para>
</section>
<section>
<title id="col-adobergb">Colorspace Adobe RGB (<constant>V4L2_COLORSPACE_ADOBERGB</constant>)</title>
<section id="col-adobergb">
<title>Colorspace Adobe RGB (<constant>V4L2_COLORSPACE_ADOBERGB</constant>)</title>
<para>The <xref linkend="adobergb" /> standard defines the colorspace used by computer graphics
that use the AdobeRGB colorspace. This is also known as the <xref linkend="oprgb" /> standard.
The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr
......@@ -970,12 +964,12 @@ clamped to the range [-0.5&hellip;0.5]. This transform is identical to one defin
SMPTE 170M/BT.601. The Y'CbCr quantization is limited range.</para>
</section>
<section>
<title id="col-bt2020">Colorspace BT.2020 (<constant>V4L2_COLORSPACE_BT2020</constant>)</title>
<section id="col-bt2020">
<title>Colorspace BT.2020 (<constant>V4L2_COLORSPACE_BT2020</constant>)</title>
<para>The <xref linkend="itu2020" /> standard defines the colorspace used by Ultra-high definition
television (UHDTV). The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_BT2020</constant>.
The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and
the white reference are:</para>
The default R'G'B' quantization is limited range (!), and so is the default Y'CbCr quantization.
The chromaticities of the primary colors and the white reference are:</para>
<table frame="none">
<title>BT.2020 Chromaticities</title>
<tgroup cols="3" align="left">
......@@ -1032,7 +1026,7 @@ the white reference are:</para>
<term>The luminance (Y') and color difference (Cb and Cr) are obtained with the
following <constant>V4L2_YCBCR_ENC_BT2020</constant> encoding:</term>
<listitem>
<para>Y'&nbsp;=&nbsp;0.2627R'&nbsp;+&nbsp;0.6789G'&nbsp;+&nbsp;0.0593B'</para>
<para>Y'&nbsp;=&nbsp;0.2627R'&nbsp;+&nbsp;0.6780G'&nbsp;+&nbsp;0.0593B'</para>
<para>Cb&nbsp;=&nbsp;-0.1396R'&nbsp;-&nbsp;0.3604G'&nbsp;+&nbsp;0.5B'</para>
<para>Cr&nbsp;=&nbsp;0.5R'&nbsp;-&nbsp;0.4598G'&nbsp;-&nbsp;0.0402B'</para>
</listitem>
......@@ -1046,7 +1040,7 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
<varlistentry>
<term>Luma:</term>
<listitem>
<para>Yc'&nbsp;=&nbsp;(0.2627R&nbsp;+&nbsp;0.6789G&nbsp;+&nbsp;0.0593B)'</para>
<para>Yc'&nbsp;=&nbsp;(0.2627R&nbsp;+&nbsp;0.6780G&nbsp;+&nbsp;0.0593B)'</para>
</listitem>
</varlistentry>
</variablelist>
......@@ -1054,7 +1048,7 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
<varlistentry>
<term>B'&nbsp;-&nbsp;Yc'&nbsp;&le;&nbsp;0:</term>
<listitem>
<para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;1.9404</para>
<para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Yc')&nbsp;/&nbsp;1.9404</para>
</listitem>
</varlistentry>
</variablelist>
......@@ -1062,7 +1056,7 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
<varlistentry>
<term>B'&nbsp;-&nbsp;Yc'&nbsp;&gt;&nbsp;0:</term>
<listitem>
<para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Y')&nbsp;/&nbsp;1.5816</para>
<para>Cbc&nbsp;=&nbsp;(B'&nbsp;-&nbsp;Yc')&nbsp;/&nbsp;1.5816</para>
</listitem>
</varlistentry>
</variablelist>
......@@ -1086,8 +1080,8 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
clamped to the range [-0.5&hellip;0.5]. The Yc'CbcCrc quantization is limited range.</para>
</section>
<section>
<title id="col-smpte-240m">Colorspace SMPTE 240M (<constant>V4L2_COLORSPACE_SMPTE240M</constant>)</title>
<section id="col-smpte-240m">
<title>Colorspace SMPTE 240M (<constant>V4L2_COLORSPACE_SMPTE240M</constant>)</title>
<para>The <xref linkend="smpte240m" /> standard was an interim standard used during the early days of HDTV (1988-1998).
It has been superseded by Rec. 709. The default Y'CbCr encoding is <constant>V4L2_YCBCR_ENC_SMPTE240M</constant>.
The default Y'CbCr quantization is limited range. The chromaticities of the primary colors and the
......@@ -1159,8 +1153,8 @@ following <constant>V4L2_YCBCR_ENC_SMPTE240M</constant> encoding:</term>
clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range.</para>
</section>
<section>
<title id="col-sysm">Colorspace NTSC 1953 (<constant>V4L2_COLORSPACE_470_SYSTEM_M</constant>)</title>
<section id="col-sysm">
<title>Colorspace NTSC 1953 (<constant>V4L2_COLORSPACE_470_SYSTEM_M</constant>)</title>
<para>This standard defines the colorspace used by NTSC in 1953. In practice this
colorspace is obsolete and SMPTE 170M should be used instead. The default Y'CbCr encoding
is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr quantization is limited range.
......@@ -1237,8 +1231,8 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
This transform is identical to one defined in SMPTE 170M/BT.601.</para>
</section>
<section>
<title id="col-sysbg">Colorspace EBU Tech. 3213 (<constant>V4L2_COLORSPACE_470_SYSTEM_BG</constant>)</title>
<section id="col-sysbg">
<title>Colorspace EBU Tech. 3213 (<constant>V4L2_COLORSPACE_470_SYSTEM_BG</constant>)</title>
<para>The <xref linkend="tech3213" /> standard defines the colorspace used by PAL/SECAM in 1975. In practice this
colorspace is obsolete and SMPTE 170M should be used instead. The default Y'CbCr encoding
is <constant>V4L2_YCBCR_ENC_601</constant>. The default Y'CbCr quantization is limited range.
......@@ -1311,8 +1305,8 @@ clamped to the range [-0.5&hellip;0.5]. The Y'CbCr quantization is limited range
This transform is identical to one defined in SMPTE 170M/BT.601.</para>
</section>
<section>
<title id="col-jpeg">Colorspace JPEG (<constant>V4L2_COLORSPACE_JPEG</constant>)</title>
<section id="col-jpeg">
<title>Colorspace JPEG (<constant>V4L2_COLORSPACE_JPEG</constant>)</title>
<para>This colorspace defines the colorspace used by most (Motion-)JPEG formats. The chromaticities
of the primary colors and the white reference are identical to sRGB. The Y'CbCr encoding is
<constant>V4L2_YCBCR_ENC_601</constant> with full range quantization where
......
Documentation/DocBook/media/v4l/v4l2.xml
浏览文件 @ 6724af48
......@@ -136,6 +136,7 @@ Remote Controller chapter.</contrib>
<year>2012</year>
<year>2013</year>
<year>2014</year>
<year>2015</year>
<holder>Bill Dirks, Michael H. Schimek, Hans Verkuil, Martin
Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab,
Pawel Osciak</holder>
......@@ -151,6 +152,14 @@ structs, ioctls) must be noted in more detail in the history chapter
(compat.xml), along with the possible impact on existing drivers and
applications. -->
<revision>
<revnumber>3.21</revnumber>
<date>2015-02-13</date>
<authorinitials>mcc</authorinitials>
<revremark>Fix documentation for media controller device nodes and add support for DVB device nodes.
Add support for Tuner sub-device.
</revremark>
</revision>
<revision>
<revnumber>3.19</revnumber>
<date>2014-12-05</date>
......
Documentation/DocBook/media/v4l/vidioc-cropcap.xml
浏览文件 @ 6724af48
......@@ -59,6 +59,11 @@ constant except when switching the video standard. Remember this
switch can occur implicit when switching the video input or
output.</para>
<para>Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>
and use <constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>.</para>
<para>This ioctl must be implemented for video capture or output devices that
support cropping and/or scaling and/or have non-square pixels, and for overlay devices.</para>
......@@ -73,9 +78,7 @@ support cropping and/or scaling and/or have non-square pixels, and for overlay d
<entry>Type of the data stream, set by the application.
Only these types are valid here:
<constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant> and
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> and
<constant>V4L2_BUF_TYPE_VIDEO_OVERLAY</constant>. See <xref linkend="v4l2-buf-type" />.</entry>
</row>
<row>
......
Documentation/DocBook/media/v4l/vidioc-dqevent.xml
浏览文件 @ 6724af48
......@@ -64,7 +64,7 @@
<entry>__u32</entry>
<entry><structfield>type</structfield></entry>
<entry></entry>
<entry>Type of the event.</entry>
<entry>Type of the event, see <xref linkend="event-type" />.</entry>
</row>
<row>
<entry>union</entry>
......@@ -154,6 +154,113 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="event-type">
<title>Event Types</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_EVENT_ALL</constant></entry>
<entry>0</entry>
<entry>All events. V4L2_EVENT_ALL is valid only for
VIDIOC_UNSUBSCRIBE_EVENT for unsubscribing all events at once.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_VSYNC</constant></entry>
<entry>1</entry>
<entry>This event is triggered on the vertical sync.
This event has a &v4l2-event-vsync; associated with it.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_EOS</constant></entry>
<entry>2</entry>
<entry>This event is triggered when the end of a stream is reached.
This is typically used with MPEG decoders to report to the application
when the last of the MPEG stream has been decoded.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL</constant></entry>
<entry>3</entry>
<entry><para>This event requires that the <structfield>id</structfield>
matches the control ID from which you want to receive events.
This event is triggered if the control's value changes, if a
button control is pressed or if the control's flags change.
This event has a &v4l2-event-ctrl; associated with it. This struct
contains much of the same information as &v4l2-queryctrl; and
&v4l2-control;.</para>
<para>If the event is generated due to a call to &VIDIOC-S-CTRL; or
&VIDIOC-S-EXT-CTRLS;, then the event will <emphasis>not</emphasis> be sent to
the file handle that called the ioctl function. This prevents
nasty feedback loops. If you <emphasis>do</emphasis> want to get the
event, then set the <constant>V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK</constant>
flag.
</para>
<para>This event type will ensure that no information is lost when
more events are raised than there is room internally. In that
case the &v4l2-event-ctrl; of the second-oldest event is kept,
but the <structfield>changes</structfield> field of the
second-oldest event is ORed with the <structfield>changes</structfield>
field of the oldest event.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_FRAME_SYNC</constant></entry>
<entry>4</entry>
<entry>
<para>Triggered immediately when the reception of a
frame has begun. This event has a
&v4l2-event-frame-sync; associated with it.</para>
<para>If the hardware needs to be stopped in the case of a
buffer underrun it might not be able to generate this event.
In such cases the <structfield>frame_sequence</structfield>
field in &v4l2-event-frame-sync; will not be incremented. This
causes two consecutive frame sequence numbers to have n times
frame interval in between them.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_SOURCE_CHANGE</constant></entry>
<entry>5</entry>
<entry>
<para>This event is triggered when a source parameter change is
detected during runtime by the video device. It can be a
runtime resolution change triggered by a video decoder or the
format change happening on an input connector.
This event requires that the <structfield>id</structfield>
matches the input index (when used with a video device node)
or the pad index (when used with a subdevice node) from which
you want to receive events.</para>
<para>This event has a &v4l2-event-src-change; associated
with it. The <structfield>changes</structfield> bitfield denotes
what has changed for the subscribed pad. If multiple events
occurred before application could dequeue them, then the changes
will have the ORed value of all the events generated.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
<entry>6</entry>
<entry>
<para>Triggered whenever the motion detection state for one or more of the regions
changes. This event has a &v4l2-event-motion-det; associated with it.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_PRIVATE_START</constant></entry>
<entry>0x08000000</entry>
<entry>Base event number for driver-private events.</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="v4l2-event-vsync">
<title>struct <structname>v4l2_event_vsync</structname></title>
<tgroup cols="3">
......@@ -177,7 +284,7 @@
<entry>__u32</entry>
<entry><structfield>changes</structfield></entry>
<entry></entry>
<entry>A bitmask that tells what has changed. See <xref linkend="changes-flags" />.</entry>
<entry>A bitmask that tells what has changed. See <xref linkend="ctrl-changes-flags" />.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -309,8 +416,8 @@
</tgroup>
</table>
<table pgwide="1" frame="none" id="changes-flags">
<title>Changes</title>
<table pgwide="1" frame="none" id="ctrl-changes-flags">
<title>Control Changes</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
......@@ -318,9 +425,9 @@
<entry><constant>V4L2_EVENT_CTRL_CH_VALUE</constant></entry>
<entry>0x0001</entry>
<entry>This control event was triggered because the value of the control
changed. Special case: if a button control is pressed, then this
event is sent as well, even though there is not explicit value
associated with a button control.</entry>
changed. Special cases: Volatile controls do no generate this event;
If a control has the <constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant>
flag set, then this event is sent as well, regardless its value.</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL_CH_FLAGS</constant></entry>
......
Documentation/DocBook/media/v4l/vidioc-g-crop.xml
浏览文件 @ 6724af48
......@@ -70,6 +70,11 @@ structure or returns the &EINVAL; if cropping is not supported.</para>
<constant>VIDIOC_S_CROP</constant> ioctl with a pointer to this
structure.</para>
<para>Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>
and use <constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>.</para>
<para>The driver first adjusts the requested dimensions against
hardware limits, &ie; the bounds given by the capture/output window,
and it rounds to the closest possible values of horizontal and
......
Documentation/DocBook/media/v4l/vidioc-g-dv-timings.xml
浏览文件 @ 6724af48
......@@ -318,10 +318,20 @@ can't generate such frequencies, then the flag will also be cleared.
</row>
<row>
<entry>V4L2_DV_FL_HALF_LINE</entry>
<entry>Specific to interlaced formats: if set, then field 1 (aka the odd field)
is really one half-line longer and field 2 (aka the even field) is really one half-line
shorter, so each field has exactly the same number of half-lines. Whether half-lines can be
detected or used depends on the hardware.
<entry>Specific to interlaced formats: if set, then the vertical frontporch
of field 1 (aka the odd field) is really one half-line longer and the vertical backporch
of field 2 (aka the even field) is really one half-line shorter, so each field has exactly
the same number of half-lines. Whether half-lines can be detected or used depends on
the hardware.
</entry>
</row>
<row>
<entry>V4L2_DV_FL_IS_CE_VIDEO</entry>
<entry>If set, then this is a Consumer Electronics (CE) video format.
Such formats differ from other formats (commonly called IT formats) in that if
R'G'B' encoding is used then by default the R'G'B' values use limited range
(i.e. 16-235) as opposed to full range (i.e. 0-255). All formats defined in CEA-861
except for the 640x480p59.94 format are CE formats.
</entry>
</row>
</tbody>
......
Documentation/DocBook/media/v4l/vidioc-g-fbuf.xml
浏览文件 @ 6724af48
......@@ -240,9 +240,9 @@ where padding bytes after the last line of an image cross a system
page boundary. Capture devices may write padding bytes, the value is
undefined. Output devices ignore the contents of padding
bytes.</para><para>When the image format is planar the
<structfield>bytesperline</structfield> value applies to the largest
<structfield>bytesperline</structfield> value applies to the first
plane and is divided by the same factor as the
<structfield>width</structfield> field for any smaller planes. For
<structfield>width</structfield> field for the other planes. For
example the Cb and Cr planes of a YUV 4:2:0 image have half as many
padding bytes following each line as the Y plane. To avoid ambiguities
drivers must return a <structfield>bytesperline</structfield> value
......
Documentation/DocBook/media/v4l/vidioc-g-selection.xml
浏览文件 @ 6724af48
......@@ -60,8 +60,8 @@
<para>To query the cropping (composing) rectangle set &v4l2-selection;
<structfield> type </structfield> field to the respective buffer type.
Do not use multiplanar buffers. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>. Use
Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant> and use
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>. The next step is
setting the value of &v4l2-selection; <structfield>target</structfield> field
......
Documentation/DocBook/media/v4l/vidioc-g-sliced-vbi-cap.xml
浏览文件 @ 6724af48
......@@ -205,7 +205,7 @@ ETS&nbsp;300&nbsp;231, lsb first transmitted.</entry>
<row>
<entry><constant>V4L2_SLICED_CAPTION_525</constant></entry>
<entry>0x1000</entry>
<entry><xref linkend="eia608" /></entry>
<entry><xref linkend="cea608" /></entry>
<entry>NTSC line 21, 284 (second field 21)</entry>
<entry>Two bytes in transmission order, including parity
bit, lsb first transmitted.</entry>
......
Documentation/DocBook/media/v4l/vidioc-querycap.xml
浏览文件 @ 6724af48
......@@ -102,10 +102,10 @@ The bus_info must start with "PCI:" for PCI boards, "PCIe:" for PCI Express boar
<entry>__u32</entry>
<entry><structfield>version</structfield></entry>
<entry><para>Version number of the driver.</para>
<para>Starting on kernel 3.1, the version reported is provided per
V4L2 subsystem, following the same Kernel numberation scheme. However, it
should not always return the same version as the kernel, if, for example,
an stable or distribution-modified kernel uses the V4L2 stack from a
<para>Starting with kernel 3.1, the version reported is provided by the
V4L2 subsystem following the kernel numbering scheme. However, it
may not always return the same version as the kernel if, for example,
a stable or distribution-modified kernel uses the V4L2 stack from a
newer kernel.</para>
<para>The version number is formatted using the
<constant>KERNEL_VERSION()</constant> macro:</para></entry>
......
Documentation/DocBook/media/v4l/vidioc-queryctrl.xml
浏览文件 @ 6724af48
......@@ -600,7 +600,9 @@ writing a value will cause the device to carry out a given action
changes continuously. A typical example would be the current gain value if the device
is in auto-gain mode. In such a case the hardware calculates the gain value based on
the lighting conditions which can change over time. Note that setting a new value for
a volatile control will have no effect. The new value will just be ignored.</entry>
a volatile control will have no effect and no <constant>V4L2_EVENT_CTRL_CH_VALUE</constant>
will be sent, unless the <constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant> flag
(see below) is also set. Otherwise the new value will just be ignored.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_FLAG_HAS_PAYLOAD</constant></entry>
......@@ -610,6 +612,14 @@ using one of the pointer fields of &v4l2-ext-control;. This flag is set for cont
that are an array, string, or have a compound type. In all cases you have to set a
pointer to memory containing the payload of the control.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant></entry>
<entry>0x0200</entry>
<entry>The value provided to the control will be propagated to the driver
even if remains constant. This is required when the control represents an action
on the hardware. For example: clearing an error flag or triggering the flash. All the
controls of the type <constant>V4L2_CTRL_TYPE_BUTTON</constant> have this flag set.</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-frame-interval.xml
浏览文件 @ 6724af48
......@@ -67,9 +67,9 @@
<para>To enumerate frame intervals applications initialize the
<structfield>index</structfield>, <structfield>pad</structfield>,
<structfield>code</structfield>, <structfield>width</structfield> and
<structfield>height</structfield> fields of
&v4l2-subdev-frame-interval-enum; and call the
<structfield>which</structfield>, <structfield>code</structfield>,
<structfield>width</structfield> and <structfield>height</structfield>
fields of &v4l2-subdev-frame-interval-enum; and call the
<constant>VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL</constant> ioctl with a pointer
to this structure. Drivers fill the rest of the structure or return
an &EINVAL; if one of the input fields is invalid. All frame intervals are
......@@ -123,7 +123,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Frame intervals to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-frame-size.xml
浏览文件 @ 6724af48
......@@ -61,9 +61,9 @@
ioctl.</para>
<para>To enumerate frame sizes applications initialize the
<structfield>pad</structfield>, <structfield>code</structfield> and
<structfield>index</structfield> fields of the
&v4l2-subdev-mbus-code-enum; and call the
<structfield>pad</structfield>, <structfield>which</structfield> ,
<structfield>code</structfield> and <structfield>index</structfield>
fields of the &v4l2-subdev-mbus-code-enum; and call the
<constant>VIDIOC_SUBDEV_ENUM_FRAME_SIZE</constant> ioctl with a pointer to
the structure. Drivers fill the minimum and maximum frame sizes or return
an &EINVAL; if one of the input parameters is invalid.</para>
......@@ -127,7 +127,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Frame sizes to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-mbus-code.xml
浏览文件 @ 6724af48
......@@ -56,8 +56,8 @@
</note>
<para>To enumerate media bus formats available at a given sub-device pad
applications initialize the <structfield>pad</structfield> and
<structfield>index</structfield> fields of &v4l2-subdev-mbus-code-enum; and
applications initialize the <structfield>pad</structfield>, <structfield>which</structfield>
and <structfield>index</structfield> fields of &v4l2-subdev-mbus-code-enum; and
call the <constant>VIDIOC_SUBDEV_ENUM_MBUS_CODE</constant> ioctl with a
pointer to this structure. Drivers fill the rest of the structure or return
an &EINVAL; if either the <structfield>pad</structfield> or
......@@ -93,7 +93,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Media bus format codes to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subscribe-event.xml
浏览文件 @ 6724af48
......@@ -60,7 +60,9 @@
<row>
<entry>__u32</entry>
<entry><structfield>type</structfield></entry>
<entry>Type of the event.</entry>
<entry>Type of the event, see <xref linkend="event-type" />. Note that
<constant>V4L2_EVENT_ALL</constant> can be used with VIDIOC_UNSUBSCRIBE_EVENT
for unsubscribing all events at once.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -84,113 +86,6 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="event-type">
<title>Event Types</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_EVENT_ALL</constant></entry>
<entry>0</entry>
<entry>All events. V4L2_EVENT_ALL is valid only for
VIDIOC_UNSUBSCRIBE_EVENT for unsubscribing all events at once.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_VSYNC</constant></entry>
<entry>1</entry>
<entry>This event is triggered on the vertical sync.
This event has a &v4l2-event-vsync; associated with it.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_EOS</constant></entry>
<entry>2</entry>
<entry>This event is triggered when the end of a stream is reached.
This is typically used with MPEG decoders to report to the application
when the last of the MPEG stream has been decoded.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL</constant></entry>
<entry>3</entry>
<entry><para>This event requires that the <structfield>id</structfield>
matches the control ID from which you want to receive events.
This event is triggered if the control's value changes, if a
button control is pressed or if the control's flags change.
This event has a &v4l2-event-ctrl; associated with it. This struct
contains much of the same information as &v4l2-queryctrl; and
&v4l2-control;.</para>
<para>If the event is generated due to a call to &VIDIOC-S-CTRL; or
&VIDIOC-S-EXT-CTRLS;, then the event will <emphasis>not</emphasis> be sent to
the file handle that called the ioctl function. This prevents
nasty feedback loops. If you <emphasis>do</emphasis> want to get the
event, then set the <constant>V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK</constant>
flag.
</para>
<para>This event type will ensure that no information is lost when
more events are raised than there is room internally. In that
case the &v4l2-event-ctrl; of the second-oldest event is kept,
but the <structfield>changes</structfield> field of the
second-oldest event is ORed with the <structfield>changes</structfield>
field of the oldest event.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_FRAME_SYNC</constant></entry>
<entry>4</entry>
<entry>
<para>Triggered immediately when the reception of a
frame has begun. This event has a
&v4l2-event-frame-sync; associated with it.</para>
<para>If the hardware needs to be stopped in the case of a
buffer underrun it might not be able to generate this event.
In such cases the <structfield>frame_sequence</structfield>
field in &v4l2-event-frame-sync; will not be incremented. This
causes two consecutive frame sequence numbers to have n times
frame interval in between them.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_SOURCE_CHANGE</constant></entry>
<entry>5</entry>
<entry>
<para>This event is triggered when a source parameter change is
detected during runtime by the video device. It can be a
runtime resolution change triggered by a video decoder or the
format change happening on an input connector.
This event requires that the <structfield>id</structfield>
matches the input index (when used with a video device node)
or the pad index (when used with a subdevice node) from which
you want to receive events.</para>
<para>This event has a &v4l2-event-src-change; associated
with it. The <structfield>changes</structfield> bitfield denotes
what has changed for the subscribed pad. If multiple events
occurred before application could dequeue them, then the changes
will have the ORed value of all the events generated.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
<entry>6</entry>
<entry>
<para>Triggered whenever the motion detection state for one or more of the regions
changes. This event has a &v4l2-event-motion-det; associated with it.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_PRIVATE_START</constant></entry>
<entry>0x08000000</entry>
<entry>Base event number for driver-private events.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="event-flags">
<title>Event Flags</title>
<tgroup cols="3">
......
Documentation/IRQ-domain.txt
浏览文件 @ 6724af48
......@@ -95,8 +95,7 @@ since it doesn't need to allocate a table as large as the largest
hwirq number. The disadvantage is that hwirq to IRQ number lookup is
dependent on how many entries are in the table.
Very few drivers should need this mapping. At the moment, powerpc
iseries is the only user.
Very few drivers should need this mapping.
==== No Map ===-
irq_domain_add_nomap()
......
Documentation/Makefile
浏览文件 @ 6724af48
subdir-y := accounting arm auxdisplay blackfin connector \
subdir-y := accounting auxdisplay blackfin connector \
filesystems filesystems ia64 laptops mic misc-devices \
networking pcmcia prctl ptp spi timers vDSO video4linux \
watchdog
Documentation/PCI/MSI-HOWTO.txt
浏览文件 @ 6724af48
......@@ -353,7 +353,7 @@ retry:
rc = pci_enable_msix_range(adapter->pdev, adapter->msix_entries,
maxvec, maxvec);
/*
* -ENOSPC is the only error code allowed to be analized
* -ENOSPC is the only error code allowed to be analyzed
*/
if (rc == -ENOSPC) {
if (maxvec == 1)
......@@ -370,7 +370,7 @@ retry:
return rc;
}
Note how pci_enable_msix_range() return value is analized for a fallback -
Note how pci_enable_msix_range() return value is analyzed for a fallback -
any error code other than -ENOSPC indicates a fatal error and should not
be retried.
......@@ -486,7 +486,7 @@ during development.
If your device supports both MSI-X and MSI capabilities, you should use
the MSI-X facilities in preference to the MSI facilities. As mentioned
above, MSI-X supports any number of interrupts between 1 and 2048.
In constrast, MSI is restricted to a maximum of 32 interrupts (and
In contrast, MSI is restricted to a maximum of 32 interrupts (and
must be a power of two). In addition, the MSI interrupt vectors must
be allocated consecutively, so the system might not be able to allocate
as many vectors for MSI as it could for MSI-X. On some platforms, MSI
......@@ -501,18 +501,9 @@ necessary to disable interrupts (Linux guarantees the same interrupt will
not be re-entered). If a device uses multiple interrupts, the driver
must disable interrupts while the lock is held. If the device sends
a different interrupt, the driver will deadlock trying to recursively
acquire the spinlock.
There are two solutions. The first is to take the lock with
spin_lock_irqsave() or spin_lock_irq() (see
Documentation/DocBook/kernel-locking). The second is to specify
IRQF_DISABLED to request_irq() so that the kernel runs the entire
interrupt routine with interrupts disabled.
If your MSI interrupt routine does not hold the lock for the whole time
it is running, the first solution may be best. The second solution is
normally preferred as it avoids making two transitions from interrupt
disabled to enabled and back again.
acquire the spinlock. Such deadlocks can be avoided by using
spin_lock_irqsave() or spin_lock_irq() which disable local interrupts
and acquire the lock (see Documentation/DocBook/kernel-locking).
4.6 How to tell whether MSI/MSI-X is enabled on a device
......
Documentation/PCI/pci-error-recovery.txt
浏览文件 @ 6724af48
......@@ -256,7 +256,7 @@ STEP 4: Slot Reset
------------------
In response to a return value of PCI_ERS_RESULT_NEED_RESET, the
the platform will peform a slot reset on the requesting PCI device(s).
the platform will perform a slot reset on the requesting PCI device(s).
The actual steps taken by a platform to perform a slot reset
will be platform-dependent. Upon completion of slot reset, the
platform will call the device slot_reset() callback.
......
Documentation/PCI/pci.txt
浏览文件 @ 6724af48
......@@ -564,14 +564,14 @@ to be handled by platform and generic code, not individual drivers.
8. Vendor and device identifications
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
One is not required to add new device ids to include/linux/pci_ids.h.
Please add PCI_VENDOR_ID_xxx for vendors and a hex constant for device ids.
Do not add new device or vendor IDs to include/linux/pci_ids.h unless they
are shared across multiple drivers. You can add private definitions in
your driver if they're helpful, or just use plain hex constants.
PCI_VENDOR_ID_xxx constants are re-used. The device ids are arbitrary
hex numbers (vendor controlled) and normally used only in a single
location, the pci_device_id table.
The device IDs are arbitrary hex numbers (vendor controlled) and normally used
only in a single location, the pci_device_id table.
Please DO submit new vendor/device ids to pciids.sourceforge.net project.
Please DO submit new vendor/device IDs to http://pciids.sourceforge.net/.
......
Documentation/PCI/pcieaer-howto.txt
浏览文件 @ 6724af48
......@@ -66,8 +66,8 @@ hardware (mostly chipsets) has root ports that cannot obtain the reporting
source ID. nosourceid=n by default.
2.3 AER error output
When a PCI-E AER error is captured, an error message will be outputed to
console. If it's a correctable error, it is outputed as a warning.
When a PCI-E AER error is captured, an error message will be outputted to
console. If it's a correctable error, it is outputted as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
......
Documentation/SubmittingPatches
浏览文件 @ 6724af48
......@@ -614,8 +614,8 @@ The canonical patch message body contains the following:
- An empty line.
- The body of the explanation, which will be copied to the
permanent changelog to describe this patch.
- The body of the explanation, line wrapped at 75 columns, which will
be copied to the permanent changelog to describe this patch.
- The "Signed-off-by:" lines, described above, which will
also go in the changelog.
......
Documentation/acpi/apei/einj.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/acpi/enumeration.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm/00-INDEX
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm/Booting
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm/Marvell/README
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm/README
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm/SH-Mobile/Makefile 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/arm/SH-Mobile/vrl4.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/arm/msm/gpiomux.txt 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/arm64/acpi_object_usage.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/arm64/arm-acpi.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/atomic_ops.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/blackfin/Makefile
浏览文件 @ 6724af48
此差异已折叠。
Documentation/block/biodoc.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/blockdev/nbd.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/blockdev/zram.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/cgroups/cpusets.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/cgroups/memory.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/cma/debugfs.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/cpu-hotplug.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/crypto/crypto-API-userspace.txt 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/device-mapper/log-writes.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arc/pct.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arc/pmu.txt 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/devicetree/bindings/arm/al,alpine.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arm/altera.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arm/armada-39x.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arm/omap/ctrl.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/arm/omap/l4.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/bus/renesas,bsc.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/bus/simple-pm-bus.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/clock/pwm-clock.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/common-properties.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/cris/axis.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/cris/boards.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/cris/interrupts.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/crypto/img-hash.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/dma/apm-xgene-dma.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/dma/jz4780-dma.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/gpio/gpio-altera.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-digicolor.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-jz4780.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-xlp9xx.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/iio/adc/mcp320x.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/iio/adc/mcp3422.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mailbox/arm-mhu.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/mt9v032.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/ov2640.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/ov2659.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/media/ti,omap3isp.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mfd/axp20x.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mfd/da9150.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mfd/mt6397.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mfd/qcom,tcsr.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mfd/sky81452.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mips/brcm/soc.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/mmc/mmc-card.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/net/nfc/nxp-nci.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/phy/dm816x-phy.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/phy/sun9i-usb-phy.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/power/fsl,imx-gpc.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/rtc/digicolor-rtc.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/sound/max98925.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/bindings/sound/storm.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/devicetree/of_selftest.txt 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/devicetree/of_unittest.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/dma-buf-sharing.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/email-clients.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/dlmfs.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/ocfs2.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/filesystems/xfs.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/gpio/board.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/gpio/consumer.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/hid/hid-sensor.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/hwmon/it87
浏览文件 @ 6724af48
此差异已折叠。
Documentation/hwmon/jc42
浏览文件 @ 6724af48
此差异已折叠。
Documentation/hwmon/nct7904 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/i2c/slave-eeprom-backend 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/i2c/slave-interface 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/i2c/summary
浏览文件 @ 6724af48
此差异已折叠。
Documentation/i2o/README 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/i2o/ioctl 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Documentation/input/alps.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/input/event-codes.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/input/gpio-tilt.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/input/walkera0701.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/input/yealink.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/kmemcheck.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/kprobes.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/leds/leds-class-flash.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/md-cluster.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/memory-barriers.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/memory-hotplug.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/can.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/filter.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/igb.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/ixgb.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/ixgbe.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/mpls-sysctl.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/pktgen.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/rds.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/s2io.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/networking/vxge.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/pinctrl.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/powerpc/pci_iov_resource_on_powernv.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/printk-formats.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/rtc.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/scsi/ncr53c8xx.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/scsi/tmscsim.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/security/Smack.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/sound/alsa/timestamping.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/spi/spi-summary
浏览文件 @ 6724af48
此差异已折叠。
Documentation/spi/spidev_test.c
浏览文件 @ 6724af48
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/timers/NO_HZ.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/trace/coresight.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/usb/chipidea.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/video4linux/vivid.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/vm/cleancache.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/vm/hugetlbpage.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/vm/pagemap.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/vm/transhuge.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/vm/zsmalloc.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Documentation/x86/boot.txt
浏览文件 @ 6724af48
此差异已折叠。
Documentation/zh_CN/arm64/legacy_instructions.txt 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
Kbuild
浏览文件 @ 6724af48
此差异已折叠。
MAINTAINERS
浏览文件 @ 6724af48
此差异已折叠。
Makefile
浏览文件 @ 6724af48
此差异已折叠。
README
浏览文件 @ 6724af48
此差异已折叠。
arch/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/alpha/include/asm/processor.h
浏览文件 @ 6724af48
此差异已折叠。
arch/alpha/kernel/pci.c
浏览文件 @ 6724af48
此差异已折叠。
arch/alpha/kernel/rtc.c
浏览文件 @ 6724af48
此差异已折叠。
arch/alpha/kernel/sys_nautilus.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/boot/dts/angel4.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/configs/nsimosci_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/arcregs.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/bitops.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/perf_event.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/processor.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/stacktrace.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/include/asm/thread_info.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/perf_event.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/process.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/setup.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/signal.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/stacktrace.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/traps.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/troubleshoot.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/unaligned.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/kernel/unwind.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/mm/fault.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arc/mm/init.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/compressed/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/compressed/head.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/compressed/mmcif-sh7372.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/compressed/sdhi-sh7372.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/compressed/sdhi-shmobile.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/compressed/sdhi-shmobile.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/alpine-db.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/alpine.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-bone.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-chiliboard.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-chilisom.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-evmsk.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-lxm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am335x-nano.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am3517.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/am437x-sk-evm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-388-db.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-388-gp.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-388-rd.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-390.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-398-db.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-398.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-39x.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-xp-linksys-mamba.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91-sama5d4_xplained.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91rm9200.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9g25.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9g25ek.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9n12ek.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9x5cm.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/at91sam9x5ek.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/bcm-cygnus.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/bcm4709-netgear-r8000.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/bcm7445.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/bcm958300k.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/bcm958305k.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dm8168-evm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dm816x.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dove.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dra72x.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/dra74x.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/emev2-kzm9d.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/emev2.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4-cpu-thermal.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4212.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4412-tmu-sensor-conf.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5420-trip-points.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5440-tmu-sensor-conf.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5440-trip-points.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/hip04.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx25-pdk.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx25-pinfunc.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx28-apf28.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx50.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6q-cubox-i.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6q.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sl-evk.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sl-warp.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sx-sdb-reva.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sx-sdb.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sx-sdb.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/imx6sx.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/kirkwood-nas2big.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/meson.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/meson8-minix-neo-x8.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/meson8.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/mt6589.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/nspire-cx.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/nspire.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap2.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap2420.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap2430.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-beagle.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-igep.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-n9.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-n900.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-n950.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-pandora-1ghz.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-pandora-600mhz.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-pandora-common.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3-zoom3.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap34xx-hs.dtsi 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/omap34xx.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap36xx-hs.dtsi 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/omap36xx.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap4-sdp.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap5-cm-t54.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap5-uevm.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-ipq8064.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-msm8660.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-msm8960.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-pm8841.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-pm8941.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/qcom-pma8084.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a73a4.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7740.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7778-bockw.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7794-alt.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/r8a7794.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/rk3288-evb.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/rk3288-popmetal.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/rk3288.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d35ek.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_can.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_emac.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_gmac.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_lcd.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_mci2.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_tcb1.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d3_uart.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sama5d4.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sh7372-mackerel.dts 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/sh7372.dtsi 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/sh73a0-kzm9g-reference.dts 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/boot/dts/sh73a0-kzm9g.dts
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sh73a0.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/stih416.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sun5i-a13.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra114.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124-jetson-tk1-emc.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124-nyan-big-emc.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124-nyan-blaze-emc.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124-nyan-blaze.dts 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124-nyan.dtsi 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra124.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra20.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/tegra30.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/vf-colibri.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/vf500.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/boot/dts/vfxxx.dtsi
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/common/bL_switcher.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/common/mcpm_entry.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/ape6evm_defconfig 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/configs/at91_dt_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/badge4_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/mackerel_defconfig 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/configs/msm_defconfig 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/configs/multi_v5_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/mvebu_v7_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/mxs_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/omap1_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/qcom_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/sama5_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/shmobile_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/configs/vexpress_defconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/Kconfig 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/aes-ce-core.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/aes-ce-glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/aesbs-glue.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/bsaes-armv7.pl
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/ghash-ce-core.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/ghash-ce-glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha1-ce-core.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha1-ce-glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha1.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha1_glue.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha1_neon_glue.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha2-ce-core.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha2-ce-glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha256-armv4.pl 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha256-core.S_shipped 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha256_glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha256_glue.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/crypto/sha256_neon_glue.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/Kbuild
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/arm-cci.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/assembler.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/auxvec.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/cpuidle.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/cputype.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/crypto/sha1.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/include/asm/elf.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/futex.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/jump_label.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/kvm_arm.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/kvm_host.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/kvm_mmio.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/kvm_mmu.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/mach/time.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/mcpm.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/mmu.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/pmu.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/seccomp.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/include/asm/smp_plat.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/thread_info.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/uaccess.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/unified.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/vdso.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/asm/vdso_datapage.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/debug/at91.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/debug/msm.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/uapi/asm/Kbuild
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/uapi/asm/auxvec.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/include/uapi/asm/kvm.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/arthur.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/kernel/asm-offsets.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/bios32.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/cpuidle.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/head-nommu.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/hibernate.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/hw_breakpoint.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/machine_kexec.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/module.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/perf_event_cpu.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/perf_event_v7.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/psci-call.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/psci.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/reboot.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/reboot.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/return_address.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/sleep.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/swp_emulate.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/vdso.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/arm.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/guest.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/interrupts_head.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/mmio.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/mmu.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/kvm/trace.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/lib/clear_user.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/lib/copy_to_user.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/lib/csumpartialcopyuser.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/lib/delay.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/Kconfig 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/Makefile 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/alpine_cpu_pm.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/alpine_cpu_pm.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/alpine_cpu_resume.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/alpine_machine.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-alpine/platsmp.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-asm9260/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/at91rm9200.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/at91rm9200_time.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/at91sam9.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/generic.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_dbgu.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_matrix.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_st.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91rm9200.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9260.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9261.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9263.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9g45.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9n12.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9rl.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/at91sam9x5.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/cpu.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/hardware.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/io.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/sama5d3.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/sama5d4.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/include/mach/uncompress.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/pm.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/pm_slowclock.S 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/pm_suspend.S 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/sama5.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/setup.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-at91/soc.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-at91/soc.h 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-bcm/bcm_cygnus.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-cns3xxx/pm.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-davinci/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-davinci/asp.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-davinci/cpuidle.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-davinci/dm646x.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-dove/pcie.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/common.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/exynos.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/firmware.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/mcpm-exynos.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/platsmp.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/pm.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/pm_domains.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/regs-pmu.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/sleep.S
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/smc.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-exynos/suspend.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/clk-imx25.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/clk-imx6q.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/common.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/cpu-imx25.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6q.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6sl.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6sx.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/devices-imx25.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/devices/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/devices/Makefile
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/ehci-imx25.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/gpc.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/hardware.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/imx25-dt.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/iomux-mx25.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/iomux-mx3.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/iomux-v3.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/iomux-v3.h
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-cpuimx35.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-eukrea_cpuimx25.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/mach-imx25.c 0 → 100644
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-imx6q.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-imx6sl.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-imx6sx.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-mx25_3ds.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/mach-mx35_3ds.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-pcm043.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mach-vpr200.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-imx/mm-imx25.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/mx25.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-imx/pm-imx6.c
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-mediatek/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-meson/Kconfig
浏览文件 @ 6724af48
此差异已折叠。
arch/arm/mach-msm/Kconfig 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/Makefile 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/Makefile.boot 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-halibut.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-msm7x30.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-qsd8x50.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-sapphire.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-trout-gpio.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-trout-mmc.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-trout-panel.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-trout.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/board-trout.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/clock-pcom.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/clock-pcom.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/clock.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/clock.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/common.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/devices-msm7x00.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/devices-msm7x30.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/devices-qsd8x50.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/devices.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/dma.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/gpiomux-8x50.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/gpiomux-v1.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/gpiomux.c 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/gpiomux.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/clk.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/entry-macro.S 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/hardware.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/irqs-7x00.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/irqs-7x30.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/irqs-8x50.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/irqs.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
arch/arm/mach-msm/include/mach/msm_gpiomux.h 已删除 100644 → 0
浏览文件 @ d2233325
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或