Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
提交 50e59058 编写于 作者: M Mauro Carvalho Chehab
浏览文件
操作

Merge tag 'v3.16-rc1' into patchwork 

Linux 3.16-rc1

* tag 'v3.16-rc1': (11443 commits)
  Linux 3.16-rc1
  net: sctp: fix permissions for rto_alpha and rto_beta knobs
  vxlan: Checksum fixes
  net: add skb_pop_rcv_encapsulation
  udp: call __skb_checksum_complete when doing full checksum
  net: Fix save software checksum complete
  net: Fix GSO constants to match NETIF flags
  fix __swap_writepage() compile failure on old gcc versions
  udp: ipv4: do not waste time in __udp4_lib_mcast_demux_lookup
  vxlan: use dev->needed_headroom instead of dev->hard_header_len
  MAINTAINERS: update cxgb4 maintainer
  x86/vdso: Fix vdso_install
  NVMe: Fix START_STOP_UNIT Scsi->NVMe translation.
  btrfs: fix error handling in create_pending_snapshot
  btrfs: fix use of uninit "ret" in end_extent_writepage()
  btrfs: free ulist in qgroup_shared_accounting() error path
  Btrfs: fix qgroups sanity test crash or hang
  btrfs: prevent RCU warning when dereferencing radix tree slot
  Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting
  btrfs: new ioctl TREE_SEARCH_V2
  ...
上级 f7a27ff1 7171511e
展开全部 隐藏空白更改
内联 并排
Showing with 43562 addition and 6329 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.gitignore
浏览文件 @ 50e59058
......@@ -22,7 +22,6 @@
*.lst
*.symtypes
*.order
modules.builtin
*.elf
*.bin
*.gz
......@@ -33,6 +32,8 @@ modules.builtin
*.lzo
*.patch
*.gcno
modules.builtin
Module.symvers
#
# Top-level generic files
......@@ -44,7 +45,6 @@ modules.builtin
/vmlinuz
/System.map
/Module.markers
/Module.symvers
#
# Debian directory (make deb-pkg)
......
Documentation/ABI/stable/sysfs-devices-system-cpu 0 → 100644
浏览文件 @ 50e59058
What: /sys/devices/system/cpu/dscr_default
Date: 13-May-2014
KernelVersion: v3.15.0
Contact:
Description: Writes are equivalent to writing to
/sys/devices/system/cpu/cpuN/dscr on all CPUs.
Reads return the last written value or 0.
This value is not a global default: it is a way to set
all per-CPU defaults at the same time.
Values: 64 bit unsigned integer (bit field)
What: /sys/devices/system/cpu/cpu[0-9]+/dscr
Date: 13-May-2014
KernelVersion: v3.15.0
Contact:
Description: Default value for the Data Stream Control Register (DSCR) on
a CPU.
This default value is used when the kernel is executing and
for any process that has not set the DSCR itself.
If a process ever sets the DSCR (via direct access to the
SPR) that value will be persisted for that process and used
on any CPU where it executes (overriding the value described
here).
If set by a process it will be inherited by child processes.
Values: 64 bit unsigned integer (bit field)
Documentation/ABI/testing/configfs-usb-gadget
浏览文件 @ 50e59058
......@@ -62,6 +62,40 @@ KernelVersion: 3.11
Description:
This group contains functions available to this USB gadget.
What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>
Date: May 2014
KernelVersion: 3.16
Description:
This group contains "Feature Descriptors" specific for one
gadget's USB interface or one interface group described
by an IAD.
The attributes:
compatible_id - 8-byte string for "Compatible ID"
sub_compatible_id - 8-byte string for "Sub Compatible ID"
What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>
Date: May 2014
KernelVersion: 3.16
Description:
This group contains "Extended Property Descriptors" specific for one
gadget's USB interface or one interface group described
by an IAD.
The attributes:
type - value 1..7 for interpreting the data
1: unicode string
2: unicode string with environment variable
3: binary
4: little-endian 32-bit
5: big-endian 32-bit
6: unicode string with a symbolic link
7: multiple unicode strings
data - blob of data to be interpreted depending on
type
What: /config/usb-gadget/gadget/strings
Date: Jun 2013
KernelVersion: 3.11
......@@ -79,3 +113,14 @@ Description:
product - gadget's product description
manufacturer - gadget's manufacturer description
What: /config/usb-gadget/gadget/os_desc
Date: May 2014
KernelVersion: 3.16
Description:
This group contains "OS String" extension handling attributes.
use - flag turning "OS Desctiptors" support on/off
b_vendor_code - one-byte value used for custom per-device and
per-interface requests
qw_sign - an identifier to be reported as "OS String"
proper
Documentation/ABI/testing/ima_policy
浏览文件 @ 50e59058
......@@ -23,7 +23,7 @@ Description:
[fowner]]
lsm: [[subj_user=] [subj_role=] [subj_type=]
[obj_user=] [obj_role=] [obj_type=]]
option: [[appraise_type=]]
option: [[appraise_type=]] [permit_directio]
base: func:= [BPRM_CHECK][MMAP_CHECK][FILE_CHECK][MODULE_CHECK]
mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC]
......
Documentation/ABI/testing/sysfs-bus-iio
浏览文件 @ 50e59058
......@@ -114,14 +114,17 @@ What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw
What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw
What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw
What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw
What: /sys/bus/iio/devices/iio:deviceX/in_temp_z_raw
What: /sys/bus/iio/devices/iio:deviceX/in_temp_ambient_raw
What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_raw
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Raw (unscaled no bias removal etc.) temperature measurement.
If an axis is specified it generally means that the temperature
sensor is associated with one part of a compound device (e.g.
a gyroscope axis). Units after application of scale and offset
a gyroscope axis). The ambient and object modifiers distinguish
between ambient (reference) and distant temperature for contact-
less measurements. Units after application of scale and offset
are milli degrees Celsius.
What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
......@@ -210,6 +213,14 @@ Contact: linux-iio@vger.kernel.org
Description:
Scaled humidity measurement in milli percent.
What: /sys/bus/iio/devices/iio:deviceX/in_X_mean_raw
KernelVersion: 3.5
Contact: linux-iio@vger.kernel.org
Description:
Averaged raw measurement from channel X. The number of values
used for averaging is device specific. The converting rules for
normal raw values also applies to the averaged raw values.
What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
......@@ -784,6 +795,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_incli_x_en
What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en
What: /sys/.../iio:deviceX/scan_elements/in_pressure_en
What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -799,6 +811,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_type
What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type
What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type
What: /sys/.../iio:deviceX/scan_elements/in_pressure_type
What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -845,6 +858,7 @@ What: /sys/.../iio:deviceX/scan_elements/in_incli_y_index
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
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -881,6 +895,25 @@ Description:
on-chip EEPROM. After power-up or chip reset the device will
automatically load the saved configuration.
What: /sys/.../iio:deviceX/in_illuminanceY_input
What: /sys/.../iio:deviceX/in_illuminanceY_raw
What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw
KernelVersion: 3.4
Contact: linux-iio@vger.kernel.org
Description:
Illuminance measurement, units after application of scale
and offset are lux.
What: /sys/.../iio:deviceX/in_intensityY_raw
What: /sys/.../iio:deviceX/in_intensityY_ir_raw
What: /sys/.../iio:deviceX/in_intensityY_both_raw
KernelVersion: 3.4
Contact: linux-iio@vger.kernel.org
Description:
Unit-less light intensity. Modifiers both and ir indicate
that measurements contains visible and infrared light
components or just infrared light, respectively.
What: /sys/.../iio:deviceX/in_intensity_red_integration_time
What: /sys/.../iio:deviceX/in_intensity_green_integration_time
What: /sys/.../iio:deviceX/in_intensity_blue_integration_time
......@@ -891,3 +924,12 @@ Contact: linux-iio@vger.kernel.org
Description:
This attribute is used to get/set the integration time in
seconds.
What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw
KernelVersion: 3.15
Contact: linux-iio@vger.kernel.org
Description:
Raw value of quaternion components using a format
x y z w. Here x, y, and z component represents the axis about
which a rotation will occur and w component represents the
amount of rotation.
Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 0 → 100644
浏览文件 @ 50e59058
What /sys/bus/iio/devices/iio:deviceX/in_proximity_raw
Date: March 2014
KernelVersion: 3.15
Contact: Matt Ranostay <mranostay@gmail.com>
Description:
Get the current distance in meters of storm (1km steps)
1000-40000 = distance in meters
What /sys/bus/iio/devices/iio:deviceX/sensor_sensitivity
Date: March 2014
KernelVersion: 3.15
Contact: Matt Ranostay <mranostay@gmail.com>
Description:
Show or set the gain boost of the amp, from 0-31 range.
18 = indoors (default)
14 = outdoors
Documentation/ABI/testing/sysfs-bus-pci
浏览文件 @ 50e59058
......@@ -250,3 +250,24 @@ Description:
valid. For example, writing a 2 to this file when sriov_numvfs
is not 0 and not 2 already will return an error. Writing a 10
when the value of sriov_totalvfs is 8 will return an error.
What: /sys/bus/pci/devices/.../driver_override
Date: April 2014
Contact: Alex Williamson <alex.williamson@redhat.com>
Description:
This file allows the driver for a device to be specified which
will override standard static and dynamic ID matching. When
specified, only a driver with a name matching the value written
to driver_override will have an opportunity to bind to the
device. The override is specified by writing a string to the
driver_override file (echo pci-stub > driver_override) and
may be cleared with an empty string (echo > driver_override).
This returns the device to standard matching rules binding.
Writing to driver_override does not automatically unbind the
device from its current driver or make any attempt to
automatically load the specified driver. If no driver with a
matching name is currently loaded in the kernel, the device
will not bind to any driver. This also allows devices to
opt-out of driver binding using a driver_override name such as
"none". Only a single driver may be specified in the override,
there is no support for parsing delimiters.
Documentation/ABI/testing/sysfs-class-net
浏览文件 @ 50e59058
......@@ -169,6 +169,14 @@ Description:
"unknown", "notpresent", "down", "lowerlayerdown", "testing",
"dormant", "up".
What: /sys/class/net/<iface>/phys_port_id
Date: July 2013
KernelVersion: 3.12
Contact: netdev@vger.kernel.org
Description:
Indicates the interface unique physical port identifier 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-cdc_ncm 0 → 100644
浏览文件 @ 50e59058
What: /sys/class/net/<iface>/cdc_ncm/min_tx_pkt
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
The driver will pad NCM Transfer Blocks (NTBs) longer
than this to tx_max, allowing the device to receive
tx_max sized frames with no terminating short
packet. NTBs shorter than this limit are transmitted
as-is, without any padding, and are terminated with a
short USB packet.
Padding to tx_max allows the driver to transmit NTBs
back-to-back without any interleaving short USB
packets. This reduces the number of short packet
interrupts in the device, and represents a tradeoff
between USB bus bandwidth and device DMA optimization.
Set to 0 to pad all frames. Set greater than tx_max to
disable all padding.
What: /sys/class/net/<iface>/cdc_ncm/rx_max
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
The maximum NTB size for RX. Cannot exceed the
maximum value supported by the device. Must allow at
least one max sized datagram plus headers.
The actual limits are device dependent. See
dwNtbInMaxSize.
Note: Some devices will silently ignore changes to
this value, resulting in oversized NTBs and
corresponding framing errors.
What: /sys/class/net/<iface>/cdc_ncm/tx_max
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
The maximum NTB size for TX. Cannot exceed the
maximum value supported by the device. Must allow at
least one max sized datagram plus headers.
The actual limits are device dependent. See
dwNtbOutMaxSize.
What: /sys/class/net/<iface>/cdc_ncm/tx_timer_usecs
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Datagram aggregation timeout in µs. The driver will
wait up to 3 times this timeout for more datagrams to
aggregate before transmitting an NTB frame.
Valid range: 5 to 4000000
Set to 0 to disable aggregation.
The following read-only attributes all represent fields of the
structure defined in section 6.2.1 "GetNtbParameters" of "Universal
Serial Bus Communications Class Subclass Specifications for Network
Control Model Devices" (CDC NCM), Revision 1.0 (Errata 1), November
24, 2010 from USB Implementers Forum, Inc. The descriptions are
quoted from table 6-3 of CDC NCM: "NTB Parameter Structure".
What: /sys/class/net/<iface>/cdc_ncm/bmNtbFormatsSupported
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Bit 0: 16-bit NTB supported (set to 1)
Bit 1: 32-bit NTB supported
Bits 2 – 15: reserved (reset to zero; must be ignored by host)
What: /sys/class/net/<iface>/cdc_ncm/dwNtbInMaxSize
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
IN NTB Maximum Size in bytes
What: /sys/class/net/<iface>/cdc_ncm/wNdpInDivisor
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Divisor used for IN NTB Datagram payload alignment
What: /sys/class/net/<iface>/cdc_ncm/wNdpInPayloadRemainder
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Remainder used to align input datagram payload within
the NTB: (Payload Offset) mod (wNdpInDivisor) =
wNdpInPayloadRemainder
What: /sys/class/net/<iface>/cdc_ncm/wNdpInAlignment
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
NDP alignment modulus for NTBs on the IN pipe. Shall
be a power of 2, and shall be at least 4.
What: /sys/class/net/<iface>/cdc_ncm/dwNtbOutMaxSize
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
OUT NTB Maximum Size
What: /sys/class/net/<iface>/cdc_ncm/wNdpOutDivisor
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
OUT NTB Datagram alignment modulus
What: /sys/class/net/<iface>/cdc_ncm/wNdpOutPayloadRemainder
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Remainder used to align output datagram payload
offsets within the NTB: Padding, shall be transmitted
as zero by function, and ignored by host. (Payload
Offset) mod (wNdpOutDivisor) = wNdpOutPayloadRemainder
What: /sys/class/net/<iface>/cdc_ncm/wNdpOutAlignment
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
NDP alignment modulus for use in NTBs on the OUT
pipe. Shall be a power of 2, and shall be at least 4.
What: /sys/class/net/<iface>/cdc_ncm/wNtbOutMaxDatagrams
Date: May 2014
KernelVersion: 3.16
Contact: Bjørn Mork <bjorn@mork.no>
Description:
Maximum number of datagrams that the host may pack
into a single OUT NTB. Zero means that the device
imposes no limit.
Documentation/ABI/testing/sysfs-class-net-queues 0 → 100644
浏览文件 @ 50e59058
What: /sys/class/<iface>/queues/rx-<queue>/rps_cpus
Date: March 2010
KernelVersion: 2.6.35
Contact: netdev@vger.kernel.org
Description:
Mask of the CPU(s) currently enabled to participate into the
Receive Packet Steering packet processing flow for this
network device queue. Possible values depend on the number
of available CPU(s) in the system.
What: /sys/class/<iface>/queues/rx-<queue>/rps_flow_cnt
Date: April 2010
KernelVersion: 2.6.35
Contact: netdev@vger.kernel.org
Description:
Number of Receive Packet Steering flows being currently
processed by this particular network device receive queue.
What: /sys/class/<iface>/queues/tx-<queue>/tx_timeout
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the number of transmit timeout events seen by this
network interface transmit queue.
What: /sys/class/<iface>/queues/tx-<queue>/xps_cpus
Date: November 2010
KernelVersion: 2.6.38
Contact: netdev@vger.kernel.org
Description:
Mask of the CPU(s) currently enabled to participate into the
Transmit Packet Steering packet processing flow for this
network device transmit queue. Possible vaules depend on the
number of available CPU(s) in the system.
What: /sys/class/<iface>/queues/tx-<queue>/byte_queue_limits/hold_time
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the hold time in milliseconds to measure the slack
of this particular network device transmit queue.
Default value is 1000.
What: /sys/class/<iface>/queues/tx-<queue>/byte_queue_limits/inflight
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the number of bytes (objects) in flight on this
network device transmit queue.
What: /sys/class/<iface>/queues/tx-<queue>/byte_queue_limits/limit
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the current limit of bytes allowed to be queued
on this network device transmit queue. This value is clamped
to be within the bounds defined by limit_max and limit_min.
What: /sys/class/<iface>/queues/tx-<queue>/byte_queue_limits/limit_max
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the absolute maximum limit of bytes allowed to be
queued on this network device transmit queue. See
include/linux/dynamic_queue_limits.h for the default value.
What: /sys/class/<iface>/queues/tx-<queue>/byte_queue_limits/limit_min
Date: November 2011
KernelVersion: 3.3
Contact: netdev@vger.kernel.org
Description:
Indicates the absolute minimum limit of bytes allowed to be
queued on this network device transmit queue. Default value is
0.
Documentation/ABI/testing/sysfs-class-net-statistics 0 → 100644
浏览文件 @ 50e59058
What: /sys/class/<iface>/statistics/collisions
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of collisions seen by this network device.
This value might not be relevant with all MAC layers.
What: /sys/class/<iface>/statistics/multicast
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of multicast packets received by this
network device.
What: /sys/class/<iface>/statistics/rx_bytes
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of bytes received by this network device.
See the network driver for the exact meaning of when this
value is incremented.
What: /sys/class/<iface>/statistics/rx_compressed
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of compressed packets received by this
network device. This value might only be relevant for interfaces
that support packet compression (e.g: PPP).
What: /sys/class/<iface>/statistics/rx_crc_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets received with a CRC (FCS) error
by this network device. Note that the specific meaning might
depend on the MAC layer used by the interface.
What: /sys/class/<iface>/statistics/rx_dropped
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets received by the network device
but dropped, that are not forwarded to the upper layers for
packet processing. See the network driver for the exact
meaning of this value.
What: /sys/class/<iface>/statistics/rx_fifo_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of receive FIFO errors seen by this
network device. See the network driver for the exact
meaning of this value.
What: /sys/class/<iface>/statistics/rx_frame_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of received frames with error, such as
alignment errors. Note that the specific meaning depends on
on the MAC layer protocol used. See the network driver for
the exact meaning of this value.
What: /sys/class/<iface>/statistics/rx_length_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of received error packet with a length
error, oversized or undersized. See the network driver for the
exact meaning of this value.
What: /sys/class/<iface>/statistics/rx_missed_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of received packets that have been missed
due to lack of capacity in the receive side. See the network
driver for the exact meaning of this value.
What: /sys/class/<iface>/statistics/rx_over_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of received packets that are oversized
compared to what the network device is configured to accept
(e.g: larger than MTU). See the network driver for the exact
meaning of this value.
What: /sys/class/<iface>/statistics/rx_packets
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the total number of good packets received by this
network device.
What: /sys/class/<iface>/statistics/tx_aborted_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets that have been aborted
during transmission by a network device (e.g: because of
a medium collision). See the network driver for the exact
meaning of this value.
What: /sys/class/<iface>/statistics/tx_bytes
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of bytes transmitted by a network
device. See the network driver for the exact meaning of this
value, in particular whether this accounts for all successfully
transmitted packets or all packets that have been queued for
transmission.
What: /sys/class/<iface>/statistics/tx_carrier_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets that could not be transmitted
because of carrier errors (e.g: physical link down). See the
network driver for the exact meaning of this value.
What: /sys/class/<iface>/statistics/tx_compressed
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of transmitted compressed packets. Note
this might only be relevant for devices that support
compression (e.g: PPP).
What: /sys/class/<iface>/statistics/tx_dropped
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets dropped during transmission.
See the driver for the exact reasons as to why the packets were
dropped.
What: /sys/class/<iface>/statistics/tx_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets in error during transmission by
a network device. See the driver for the exact reasons as to
why the packets were dropped.
What: /sys/class/<iface>/statistics/tx_fifo_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets having caused a transmit
FIFO error. See the driver for the exact reasons as to why the
packets were dropped.
What: /sys/class/<iface>/statistics/tx_heartbeat_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets transmitted that have been
reported as heartbeat errors. See the driver for the exact
reasons as to why the packets were dropped.
What: /sys/class/<iface>/statistics/tx_packets
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets transmitted by a network
device. See the driver for whether this reports the number of all
attempted or successful transmissions.
What: /sys/class/<iface>/statistics/tx_window_errors
Date: April 2005
KernelVersion: 2.6.12
Contact: netdev@vger.kernel.org
Description:
Indicates the number of packets not successfully transmitted
due to a window collision. The specific meaning depends on the
MAC layer used. On Ethernet this is usually used to report
late collisions errors.
Documentation/ABI/testing/sysfs-devices-system-cpu
浏览文件 @ 50e59058
......@@ -128,7 +128,7 @@ Description: Discover cpuidle policy and mechanism
What: /sys/devices/system/cpu/cpu#/cpufreq/*
Date: pre-git history
Contact: cpufreq@vger.kernel.org
Contact: linux-pm@vger.kernel.org
Description: Discover and change clock speed of CPUs
Clock scaling allows you to change the clock speed of the
......@@ -146,7 +146,7 @@ Description: Discover and change clock speed of CPUs
What: /sys/devices/system/cpu/cpu#/cpufreq/freqdomain_cpus
Date: June 2013
Contact: cpufreq@vger.kernel.org
Contact: linux-pm@vger.kernel.org
Description: Discover CPUs in the same CPU frequency coordination domain
freqdomain_cpus is the list of CPUs (online+offline) that share
......
Documentation/ABI/testing/sysfs-driver-hid-thingm 已删除 100644 → 0
浏览文件 @ f7a27ff1
What: /sys/class/leds/blink1::<serial>/rgb
Date: January 2013
Contact: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Description: The ThingM blink1 is an USB RGB LED. The color notation is
3-byte hexadecimal. Read this attribute to get the last set
color. Write the 24-bit hexadecimal color to change the current
LED color. The default color is full white (0xFFFFFF).
For instance, set the color to green with: echo 00FF00 > rgb
What: /sys/class/leds/blink1::<serial>/fade
Date: January 2013
Contact: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Description: This attribute allows to set a fade time in milliseconds for
the next color change. Read the attribute to know the current
fade time. The default value is set to 0 (no fade time). For
instance, set a fade time of 2 seconds with: echo 2000 > fade
What: /sys/class/leds/blink1::<serial>/play
Date: January 2013
Contact: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Description: This attribute is used to play/pause the light patterns. Write 1
to start playing, 0 to stop. Reading this attribute returns the
current playing status.
Documentation/ABI/testing/sysfs-platform-brcmstb-gisb-arb 0 → 100644
浏览文件 @ 50e59058
What: /sys/devices/../../gisb_arb_timeout
Date: May 2014
KernelVersion: 3.17
Contact: Florian Fainelli <f.fainelli@gmail.com>
Description:
Returns the currently configured raw timeout value of the
Broadcom Set Top Box internal GISB bus arbiter. Minimum value
is 1, and maximum value is 0xffffffff.
Documentation/ABI/testing/sysfs-platform-chipidea-usb-otg 0 → 100644
浏览文件 @ 50e59058
What: /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req
Date: Feb 2014
Contact: Li Jun <b47624@freescale.com>
Description:
Can be set and read.
Set a_bus_req(A-device bus request) input to be 1 if
the application running on the A-device wants to use the bus,
and to be 0 when the application no longer wants to use
the bus(or wants to work as peripheral). a_bus_req can also
be set to 1 by kernel in response to remote wakeup signaling
from the B-device, the A-device should decide to resume the bus.
Valid values are "1" and "0".
Reading: returns 1 if the application running on the A-device
is using the bus as host role, otherwise 0.
What: /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_drop
Date: Feb 2014
Contact: Li Jun <b47624@freescale.com>
Description:
Can be set and read
The a_bus_drop(A-device bus drop) input is 1 when the
application running on the A-device wants to power down
the bus, and is 0 otherwise, When a_bus_drop is 1, then
the a_bus_req shall be 0.
Valid values are "1" and "0".
Reading: returns 1 if the bus is off(vbus is turned off) by
A-device, otherwise 0.
What: /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req
Date: Feb 2014
Contact: Li Jun <b47624@freescale.com>
Description:
Can be set and read.
The b_bus_req(B-device bus request) input is 1 during the time
that the application running on the B-device wants to use the
bus as host, and is 0 when the application no longer wants to
work as host and decides to switch back to be peripheral.
Valid values are "1" and "0".
Reading: returns if the application running on the B device
is using the bus as host role, otherwise 0.
What: /sys/bus/platform/devices/ci_hdrc.0/inputs/a_clr_err
Date: Feb 2014
Contact: Li Jun <b47624@freescale.com>
Description:
Only can be set.
The a_clr_err(A-device Vbus error clear) input is used to clear
vbus error, then A-device will power down the bus.
Valid value is "1"
Documentation/ABI/testing/sysfs-power
浏览文件 @ 50e59058
......@@ -7,19 +7,30 @@ Description:
subsystem.
What: /sys/power/state
Date: August 2006
Date: May 2014
Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
The /sys/power/state file controls the system power state.
Reading from this file returns what states are supported,
which is hard-coded to 'freeze' (Low-Power Idle), 'standby'
(Power-On Suspend), 'mem' (Suspend-to-RAM), and 'disk'
(Suspend-to-Disk).
The /sys/power/state file controls system sleep states.
Reading from this file returns the available sleep state
labels, which may be "mem", "standby", "freeze" and "disk"
(hibernation). The meanings of the first three labels depend on
the relative_sleep_states command line argument as follows:
1) relative_sleep_states = 1
"mem", "standby", "freeze" represent non-hibernation sleep
states from the deepest ("mem", always present) to the
shallowest ("freeze"). "standby" and "freeze" may or may
not be present depending on the capabilities of the
platform. "freeze" can only be present if "standby" is
present.
2) relative_sleep_states = 0 (default)
"mem" - "suspend-to-RAM", present if supported.
"standby" - "power-on suspend", present if supported.
"freeze" - "suspend-to-idle", always present.
Writing to this file one of these strings causes the system to
transition into that state. Please see the file
Documentation/power/states.txt for a description of each of
these states.
transition into the corresponding state, if available. See
Documentation/power/states.txt for a description of what
"suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean.
What: /sys/power/disk
Date: September 2006
......
Documentation/Changes
浏览文件 @ 50e59058
......@@ -73,6 +73,11 @@ Perl
You will need perl 5 and the following modules: Getopt::Long, Getopt::Std,
File::Basename, and File::Find to build the kernel.
BC
--
You will need bc to build kernels 3.10 and higher
System utilities
================
......
Documentation/CodingStyle
浏览文件 @ 50e59058
......@@ -660,15 +660,23 @@ There are a number of driver model diagnostic macros in <linux/device.h>
which you should use to make sure messages are matched to the right device
and driver, and are tagged with the right level: dev_err(), dev_warn(),
dev_info(), and so forth. For messages that aren't associated with a
particular device, <linux/printk.h> defines pr_debug() and pr_info().
particular device, <linux/printk.h> defines pr_notice(), pr_info(),
pr_warn(), pr_err(), etc.
Coming up with good debugging messages can be quite a challenge; and once
you have them, they can be a huge help for remote troubleshooting. Such
messages should be compiled out when the DEBUG symbol is not defined (that
is, by default they are not included). When you use dev_dbg() or pr_debug(),
that's automatic. Many subsystems have Kconfig options to turn on -DDEBUG.
A related convention uses VERBOSE_DEBUG to add dev_vdbg() messages to the
ones already enabled by DEBUG.
you have them, they can be a huge help for remote troubleshooting. However
debug message printing is handled differently than printing other non-debug
messages. While the other pr_XXX() functions print unconditionally,
pr_debug() does not; it is compiled out by default, unless either DEBUG is
defined or CONFIG_DYNAMIC_DEBUG is set. That is true for dev_dbg() also,
and a related convention uses VERBOSE_DEBUG to add dev_vdbg() messages to
the ones already enabled by DEBUG.
Many subsystems have Kconfig debug options to turn on -DDEBUG in the
corresponding Makefile; in other cases specific files #define DEBUG. And
when a debug message should be unconditionally printed, such as if it is
already inside a debug-related #ifdef secton, printk(KERN_DEBUG ...) can be
used.
Chapter 14: Allocating memory
......
Documentation/DMA-API-HOWTO.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/DMA-API.txt
浏览文件 @ 50e59058
......@@ -4,22 +4,26 @@
James E.J. Bottomley <James.Bottomley@HansenPartnership.com>
This document describes the DMA API. For a more gentle introduction
of the API (and actual examples) see
Documentation/DMA-API-HOWTO.txt.
of the API (and actual examples), see Documentation/DMA-API-HOWTO.txt.
This API is split into two pieces. Part I describes the API. Part II
describes the extensions to the API for supporting non-consistent
memory machines. Unless you know that your driver absolutely has to
support non-consistent platforms (this is usually only legacy
platforms) you should only use the API described in part I.
This API is split into two pieces. Part I describes the basic API.
Part II describes extensions for supporting non-consistent memory
machines. Unless you know that your driver absolutely has to support
non-consistent platforms (this is usually only legacy platforms) you
should only use the API described in part I.
Part I - dma_ API
-------------------------------------
To get the dma_ API, you must #include <linux/dma-mapping.h>
To get the dma_ API, you must #include <linux/dma-mapping.h>. This
provides dma_addr_t and the interfaces described below.
A dma_addr_t can hold any valid DMA or bus address for the platform. It
can be given to a device to use as a DMA source or target. A CPU cannot
reference a dma_addr_t directly because there may be translation between
its physical address space and the bus address space.
Part Ia - Using large dma-coherent buffers
Part Ia - Using large DMA-coherent buffers
------------------------------------------
void *
......@@ -33,20 +37,21 @@ to make sure to flush the processor's write buffers before telling
devices to read that memory.)
This routine allocates a region of <size> bytes of consistent memory.
It also returns a <dma_handle> which may be cast to an unsigned
integer the same width as the bus and used as the physical address
base of the region.
Returns: a pointer to the allocated region (in the processor's virtual
It returns a pointer to the allocated region (in the processor's virtual
address space) or NULL if the allocation failed.
It also returns a <dma_handle> which may be cast to an unsigned integer the
same width as the bus and given to the device as the bus address base of
the region.
Note: consistent memory can be expensive on some platforms, and the
minimum allocation length may be as big as a page, so you should
consolidate your requests for consistent memory as much as possible.
The simplest way to do that is to use the dma_pool calls (see below).
The flag parameter (dma_alloc_coherent only) allows the caller to
specify the GFP_ flags (see kmalloc) for the allocation (the
The flag parameter (dma_alloc_coherent() only) allows the caller to
specify the GFP_ flags (see kmalloc()) for the allocation (the
implementation may choose to ignore flags that affect the location of
the returned memory, like GFP_DMA).
......@@ -61,24 +66,24 @@ void
dma_free_coherent(struct device *dev, size_t size, void *cpu_addr,
dma_addr_t dma_handle)
Free the region of consistent memory you previously allocated. dev,
size and dma_handle must all be the same as those passed into the
consistent allocate. cpu_addr must be the virtual address returned by
the consistent allocate.
Free a region of consistent memory you previously allocated. dev,
size and dma_handle must all be the same as those passed into
dma_alloc_coherent(). cpu_addr must be the virtual address returned by
the dma_alloc_coherent().
Note that unlike their sibling allocation calls, these routines
may only be called with IRQs enabled.
Part Ib - Using small dma-coherent buffers
Part Ib - Using small DMA-coherent buffers
------------------------------------------
To get this part of the dma_ API, you must #include <linux/dmapool.h>
Many drivers need lots of small dma-coherent memory regions for DMA
Many drivers need lots of small DMA-coherent memory regions for DMA
descriptors or I/O buffers. Rather than allocating in units of a page
or more using dma_alloc_coherent(), you can use DMA pools. These work
much like a struct kmem_cache, except that they use the dma-coherent allocator,
much like a struct kmem_cache, except that they use the DMA-coherent allocator,
not __get_free_pages(). Also, they understand common hardware constraints
for alignment, like queue heads needing to be aligned on N-byte boundaries.
......@@ -87,7 +92,7 @@ for alignment, like queue heads needing to be aligned on N-byte boundaries.
dma_pool_create(const char *name, struct device *dev,
size_t size, size_t align, size_t alloc);
The pool create() routines initialize a pool of dma-coherent buffers
dma_pool_create() initializes a pool of DMA-coherent buffers
for use with a given device. It must be called in a context which
can sleep.
......@@ -102,25 +107,26 @@ from this pool must not cross 4KByte boundaries.
void *dma_pool_alloc(struct dma_pool *pool, gfp_t gfp_flags,
dma_addr_t *dma_handle);
This allocates memory from the pool; the returned memory will meet the size
and alignment requirements specified at creation time. Pass GFP_ATOMIC to
prevent blocking, or if it's permitted (not in_interrupt, not holding SMP locks),
pass GFP_KERNEL to allow blocking. Like dma_alloc_coherent(), this returns
two values: an address usable by the cpu, and the dma address usable by the
pool's device.
This allocates memory from the pool; the returned memory will meet the
size and alignment requirements specified at creation time. Pass
GFP_ATOMIC to prevent blocking, or if it's permitted (not
in_interrupt, not holding SMP locks), pass GFP_KERNEL to allow
blocking. Like dma_alloc_coherent(), this returns two values: an
address usable by the CPU, and the DMA address usable by the pool's
device.
void dma_pool_free(struct dma_pool *pool, void *vaddr,
dma_addr_t addr);
This puts memory back into the pool. The pool is what was passed to
the pool allocation routine; the cpu (vaddr) and dma addresses are what
dma_pool_alloc(); the CPU (vaddr) and DMA addresses are what
were returned when that routine allocated the memory being freed.
void dma_pool_destroy(struct dma_pool *pool);
The pool destroy() routines free the resources of the pool. They must be
dma_pool_destroy() frees the resources of the pool. It must be
called in a context which can sleep. Make sure you've freed all allocated
memory back to the pool before you destroy it.
......@@ -187,9 +193,9 @@ dma_map_single(struct device *dev, void *cpu_addr, size_t size,
enum dma_data_direction direction)
Maps a piece of processor virtual memory so it can be accessed by the
device and returns the physical handle of the memory.
device and returns the bus address of the memory.
The direction for both api's may be converted freely by casting.
The direction for both APIs may be converted freely by casting.
However the dma_ API uses a strongly typed enumerator for its
direction:
......@@ -198,31 +204,30 @@ DMA_TO_DEVICE data is going from the memory to the device
DMA_FROM_DEVICE data is coming from the device to the memory
DMA_BIDIRECTIONAL direction isn't known
Notes: Not all memory regions in a machine can be mapped by this
API. Further, regions that appear to be physically contiguous in
kernel virtual space may not be contiguous as physical memory. Since
this API does not provide any scatter/gather capability, it will fail
if the user tries to map a non-physically contiguous piece of memory.
For this reason, it is recommended that memory mapped by this API be
obtained only from sources which guarantee it to be physically contiguous
(like kmalloc).
Further, the physical address of the memory must be within the
dma_mask of the device (the dma_mask represents a bit mask of the
addressable region for the device. I.e., if the physical address of
the memory anded with the dma_mask is still equal to the physical
address, then the device can perform DMA to the memory). In order to
Notes: Not all memory regions in a machine can be mapped by this API.
Further, contiguous kernel virtual space may not be contiguous as
physical memory. Since this API does not provide any scatter/gather
capability, it will fail if the user tries to map a non-physically
contiguous piece of memory. For this reason, memory to be mapped by
this API should be obtained from sources which guarantee it to be
physically contiguous (like kmalloc).
Further, the bus address of the memory must be within the
dma_mask of the device (the dma_mask is a bit mask of the
addressable region for the device, i.e., if the bus address of
the memory ANDed with the dma_mask is still equal to the bus
address, then the device can perform DMA to the memory). To
ensure that the memory allocated by kmalloc is within the dma_mask,
the driver may specify various platform-dependent flags to restrict
the physical memory range of the allocation (e.g. on x86, GFP_DMA
guarantees to be within the first 16Mb of available physical memory,
the bus address range of the allocation (e.g., on x86, GFP_DMA
guarantees to be within the first 16MB of available bus addresses,
as required by ISA devices).
Note also that the above constraints on physical contiguity and
dma_mask may not apply if the platform has an IOMMU (a device which
supplies a physical to virtual mapping between the I/O memory bus and
the device). However, to be portable, device driver writers may *not*
assume that such an IOMMU exists.
maps an I/O bus address to a physical memory address). However, to be
portable, device driver writers may *not* assume that such an IOMMU
exists.
Warnings: Memory coherency operates at a granularity called the cache
line width. In order for memory mapped by this API to operate
......@@ -281,9 +286,9 @@ cache width is.
int
dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
In some circumstances dma_map_single and dma_map_page will fail to create
In some circumstances dma_map_single() and dma_map_page() will fail to create
a mapping. A driver can check for these errors by testing the returned
dma address with dma_mapping_error(). A non-zero return value means the mapping
DMA address with dma_mapping_error(). A non-zero return value means the mapping
could not be created and the driver should take appropriate action (e.g.
reduce current DMA mapping usage or delay and try again later).
......@@ -291,7 +296,7 @@ reduce current DMA mapping usage or delay and try again later).
dma_map_sg(struct device *dev, struct scatterlist *sg,
int nents, enum dma_data_direction direction)
Returns: the number of physical segments mapped (this may be shorter
Returns: the number of bus address segments mapped (this may be shorter
than <nents> passed in if some elements of the scatter/gather list are
physically or virtually adjacent and an IOMMU maps them with a single
entry).
......@@ -299,7 +304,7 @@ entry).
Please note that the sg cannot be mapped again if it has been mapped once.
The mapping process is allowed to destroy information in the sg.
As with the other mapping interfaces, dma_map_sg can fail. When it
As with the other mapping interfaces, dma_map_sg() can fail. When it
does, 0 is returned and a driver must take appropriate action. It is
critical that the driver do something, in the case of a block driver
aborting the request or even oopsing is better than doing nothing and
......@@ -335,7 +340,7 @@ must be the same as those and passed in to the scatter/gather mapping
API.
Note: <nents> must be the number you passed in, *not* the number of
physical entries returned.
bus address entries returned.
void
dma_sync_single_for_cpu(struct device *dev, dma_addr_t dma_handle, size_t size,
......@@ -350,7 +355,7 @@ void
dma_sync_sg_for_device(struct device *dev, struct scatterlist *sg, int nelems,
enum dma_data_direction direction)
Synchronise a single contiguous or scatter/gather mapping for the cpu
Synchronise a single contiguous or scatter/gather mapping for the CPU
and device. With the sync_sg API, all the parameters must be the same
as those passed into the single mapping API. With the sync_single API,
you can use dma_handle and size parameters that aren't identical to
......@@ -391,10 +396,10 @@ The four functions above are just like the counterpart functions
without the _attrs suffixes, except that they pass an optional
struct dma_attrs*.
struct dma_attrs encapsulates a set of "dma attributes". For the
struct dma_attrs encapsulates a set of "DMA attributes". For the
definition of struct dma_attrs see linux/dma-attrs.h.
The interpretation of dma attributes is architecture-specific, and
The interpretation of DMA attributes is architecture-specific, and
each attribute should be documented in Documentation/DMA-attributes.txt.
If struct dma_attrs* is NULL, the semantics of each of these
......@@ -458,7 +463,7 @@ Note: where the platform can return consistent memory, it will
guarantee that the sync points become nops.
Warning: Handling non-consistent memory is a real pain. You should
only ever use this API if you positively know your driver will be
only use this API if you positively know your driver will be
required to work on one of the rare (usually non-PCI) architectures
that simply cannot make consistent memory.
......@@ -492,30 +497,29 @@ continuing on for size. Again, you *must* observe the cache line
boundaries when doing this.
int
dma_declare_coherent_memory(struct device *dev, dma_addr_t bus_addr,
dma_declare_coherent_memory(struct device *dev, phys_addr_t phys_addr,
dma_addr_t device_addr, size_t size, int
flags)
Declare region of memory to be handed out by dma_alloc_coherent when
Declare region of memory to be handed out by dma_alloc_coherent() when
it's asked for coherent memory for this device.
bus_addr is the physical address to which the memory is currently
assigned in the bus responding region (this will be used by the
platform to perform the mapping).
phys_addr is the CPU physical address to which the memory is currently
assigned (this will be ioremapped so the CPU can access the region).
device_addr is the physical address the device needs to be programmed
with actually to address this memory (this will be handed out as the
device_addr is the bus address the device needs to be programmed
with to actually address this memory (this will be handed out as the
dma_addr_t in dma_alloc_coherent()).
size is the size of the area (must be multiples of PAGE_SIZE).
flags can be or'd together and are:
flags can be ORed together and are:
DMA_MEMORY_MAP - request that the memory returned from
dma_alloc_coherent() be directly writable.
DMA_MEMORY_IO - request that the memory returned from
dma_alloc_coherent() be addressable using read/write/memcpy_toio etc.
dma_alloc_coherent() be addressable using read()/write()/memcpy_toio() etc.
One or both of these flags must be present.
......@@ -572,7 +576,7 @@ region is occupied.
Part III - Debug drivers use of the DMA-API
-------------------------------------------
The DMA-API as described above as some constraints. DMA addresses must be
The DMA-API as described above has some constraints. DMA addresses must be
released with the corresponding function with the same size for example. With
the advent of hardware IOMMUs it becomes more and more important that drivers
do not violate those constraints. In the worst case such a violation can
......@@ -690,11 +694,11 @@ architectural default.
void debug_dmap_mapping_error(struct device *dev, dma_addr_t dma_addr);
dma-debug interface debug_dma_mapping_error() to debug drivers that fail
to check dma mapping errors on addresses returned by dma_map_single() and
to check DMA mapping errors on addresses returned by dma_map_single() and
dma_map_page() interfaces. This interface clears a flag set by
debug_dma_map_page() to indicate that dma_mapping_error() has been called by
the driver. When driver does unmap, debug_dma_unmap() checks the flag and if
this flag is still set, prints warning message that includes call trace that
leads up to the unmap. This interface can be called from dma_mapping_error()
routines to enable dma mapping error check debugging.
routines to enable DMA mapping error check debugging.
Documentation/DMA-ISA-LPC.txt
浏览文件 @ 50e59058
......@@ -16,7 +16,7 @@ To do ISA style DMA you need to include two headers:
#include <asm/dma.h>
The first is the generic DMA API used to convert virtual addresses to
physical addresses (see Documentation/DMA-API.txt for details).
bus addresses (see Documentation/DMA-API.txt for details).
The second contains the routines specific to ISA DMA transfers. Since
this is not present on all platforms make sure you construct your
......@@ -50,7 +50,7 @@ early as possible and not release it until the driver is unloaded.)
Part III - Address translation
------------------------------
To translate the virtual address to a physical use the normal DMA
To translate the virtual address to a bus address, use the normal DMA
API. Do _not_ use isa_virt_to_phys() even though it does the same
thing. The reason for this is that the function isa_virt_to_phys()
will require a Kconfig dependency to ISA, not just ISA_DMA_API which
......
Documentation/DMA-attributes.txt
浏览文件 @ 50e59058
......@@ -98,5 +98,5 @@ DMA_ATTR_FORCE_CONTIGUOUS
By default DMA-mapping subsystem is allowed to assemble the buffer
allocated by dma_alloc_attrs() function from individual pages if it can
be mapped as contiguous chunk into device dma address space. By
specifing this attribute the allocated buffer is forced to be contiguous
specifying this attribute the allocated buffer is forced to be contiguous
also in physical memory.
Documentation/DocBook/80211.tmpl
浏览文件 @ 50e59058
......@@ -100,6 +100,7 @@
!Finclude/net/cfg80211.h wdev_priv
!Finclude/net/cfg80211.h ieee80211_iface_limit
!Finclude/net/cfg80211.h ieee80211_iface_combination
!Finclude/net/cfg80211.h cfg80211_check_combinations
</chapter>
<chapter>
<title>Actions and configuration</title>
......
Documentation/DocBook/Makefile
浏览文件 @ 50e59058
......@@ -14,7 +14,8 @@ DOCBOOKS := z8530book.xml device-drivers.xml \
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
80211.xml debugobjects.xml sh.xml regulator.xml \
alsa-driver-api.xml writing-an-alsa-driver.xml \
tracepoint.xml drm.xml media_api.xml w1.xml
tracepoint.xml drm.xml media_api.xml w1.xml \
writing_musb_glue_layer.xml
include Documentation/DocBook/media/Makefile
......
Documentation/DocBook/drm.tmpl
浏览文件 @ 50e59058
此差异已折叠。
Documentation/DocBook/filesystems.tmpl
浏览文件 @ 50e59058
......@@ -62,7 +62,7 @@
!Efs/mpage.c
!Efs/namei.c
!Efs/buffer.c
!Efs/bio.c
!Eblock/bio.c
!Efs/seq_file.c
!Efs/filesystems.c
!Efs/fs-writeback.c
......
Documentation/DocBook/media/Makefile
浏览文件 @ 50e59058
......@@ -195,7 +195,7 @@ DVB_DOCUMENTED = \
#
install_media_images = \
$(Q)cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
$(Q)-cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
$(MEDIA_OBJ_DIR)/%: $(MEDIA_SRC_DIR)/%.b64
$(Q)base64 -d $< >$@
......
Documentation/DocBook/writing_musb_glue_layer.tmpl 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/EDID/1024x768.S
浏览文件 @ 50e59058
......@@ -36,7 +36,7 @@
#define DPI 72
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux XGA"
#define ESTABLISHED_TIMINGS_BITS 0x08 /* Bit 3 -> 1024x768 @60 Hz */
#define ESTABLISHED_TIMING2_BITS 0x08 /* Bit 3 -> 1024x768 @60 Hz */
#define HSYNC_POL 0
#define VSYNC_POL 0
#define CRC 0x55
......
Documentation/EDID/1280x1024.S
浏览文件 @ 50e59058
......@@ -36,7 +36,7 @@
#define DPI 72
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux SXGA"
#define ESTABLISHED_TIMINGS_BITS 0x00 /* none */
/* No ESTABLISHED_TIMINGx_BITS */
#define HSYNC_POL 1
#define VSYNC_POL 1
#define CRC 0xa0
......
Documentation/EDID/1600x1200.S
浏览文件 @ 50e59058
......@@ -36,7 +36,7 @@
#define DPI 72
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux UXGA"
#define ESTABLISHED_TIMINGS_BITS 0x00 /* none */
/* No ESTABLISHED_TIMINGx_BITS */
#define HSYNC_POL 1
#define VSYNC_POL 1
#define CRC 0x9d
......
Documentation/EDID/1680x1050.S
浏览文件 @ 50e59058
......@@ -36,7 +36,7 @@
#define DPI 96
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux WSXGA"
#define ESTABLISHED_TIMINGS_BITS 0x00 /* none */
/* No ESTABLISHED_TIMINGx_BITS */
#define HSYNC_POL 1
#define VSYNC_POL 1
#define CRC 0x26
......
Documentation/EDID/1920x1080.S
浏览文件 @ 50e59058
......@@ -36,7 +36,7 @@
#define DPI 96
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux FHD"
#define ESTABLISHED_TIMINGS_BITS 0x00 /* none */
/* No ESTABLISHED_TIMINGx_BITS */
#define HSYNC_POL 1
#define VSYNC_POL 1
#define CRC 0x05
......
Documentation/EDID/800x600.S 0 → 100644
浏览文件 @ 50e59058
/*
800x600.S: EDID data set for standard 800x600 60 Hz monitor
Copyright (C) 2011 Carsten Emde <C.Emde@osadl.org>
Copyright (C) 2014 Linaro Limited
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
*/
/* EDID */
#define VERSION 1
#define REVISION 3
/* Display */
#define CLOCK 40000 /* kHz */
#define XPIX 800
#define YPIX 600
#define XY_RATIO XY_RATIO_4_3
#define XBLANK 256
#define YBLANK 28
#define XOFFSET 40
#define XPULSE 128
#define YOFFSET (63+1)
#define YPULSE (63+4)
#define DPI 72
#define VFREQ 60 /* Hz */
#define TIMING_NAME "Linux SVGA"
#define ESTABLISHED_TIMING1_BITS 0x01 /* Bit 0: 800x600 @ 60Hz */
#define HSYNC_POL 1
#define VSYNC_POL 1
#define CRC 0xc2
#include "edid.S"
Documentation/EDID/HOWTO.txt
浏览文件 @ 50e59058
......@@ -18,7 +18,7 @@ CONFIG_DRM_LOAD_EDID_FIRMWARE was introduced. It allows to provide an
individually prepared or corrected EDID data set in the /lib/firmware
directory from where it is loaded via the firmware interface. The code
(see drivers/gpu/drm/drm_edid_load.c) contains built-in data sets for
commonly used screen resolutions (1024x768, 1280x1024, 1600x1200,
commonly used screen resolutions (800x600, 1024x768, 1280x1024, 1600x1200,
1680x1050, 1920x1080) as binary blobs, but the kernel source tree does
not contain code to create these data. In order to elucidate the origin
of the built-in binary EDID blobs and to facilitate the creation of
......
Documentation/EDID/edid.S
浏览文件 @ 50e59058
......@@ -33,6 +33,17 @@
#define XY_RATIO_5_4 0b10
#define XY_RATIO_16_9 0b11
/* Provide defaults for the timing bits */
#ifndef ESTABLISHED_TIMING1_BITS
#define ESTABLISHED_TIMING1_BITS 0x00
#endif
#ifndef ESTABLISHED_TIMING2_BITS
#define ESTABLISHED_TIMING2_BITS 0x00
#endif
#ifndef ESTABLISHED_TIMING3_BITS
#define ESTABLISHED_TIMING3_BITS 0x00
#endif
#define mfgname2id(v1,v2,v3) \
((((v1-'@')&0x1f)<<10)+(((v2-'@')&0x1f)<<5)+((v3-'@')&0x1f))
#define swap16(v1) ((v1>>8)+((v1&0xff)<<8))
......@@ -139,7 +150,7 @@ white_x_y_msb: .byte 0x50,0x54
Bit 2 640x480 @ 75 Hz
Bit 1 800x600 @ 56 Hz
Bit 0 800x600 @ 60 Hz */
estbl_timing1: .byte 0x00
estbl_timing1: .byte ESTABLISHED_TIMING1_BITS
/* Bit 7 800x600 @ 72 Hz
Bit 6 800x600 @ 75 Hz
......@@ -149,11 +160,11 @@ estbl_timing1: .byte 0x00
Bit 2 1024x768 @ 72 Hz
Bit 1 1024x768 @ 75 Hz
Bit 0 1280x1024 @ 75 Hz */
estbl_timing2: .byte ESTABLISHED_TIMINGS_BITS
estbl_timing2: .byte ESTABLISHED_TIMING2_BITS
/* Bit 7 1152x870 @ 75 Hz (Apple Macintosh II)
Bits 6-0 Other manufacturer-specific display mod */
estbl_timing3: .byte 0x00
estbl_timing3: .byte ESTABLISHED_TIMING3_BITS
/* Standard timing */
/* X resolution, less 31, divided by 8 (256-2288 pixels) */
......
Documentation/IRQ-domain.txt
浏览文件 @ 50e59058
......@@ -41,8 +41,7 @@ An interrupt controller driver creates and registers an irq_domain by
calling one of the irq_domain_add_*() functions (each mapping method
has a different allocator function, more on that later). The function
will return a pointer to the irq_domain on success. The caller must
provide the allocator function with an irq_domain_ops structure with
the .map callback populated as a minimum.
provide the allocator function with an irq_domain_ops structure.
In most cases, the irq_domain will begin empty without any mappings
between hwirq and IRQ numbers. Mappings are added to the irq_domain
......
Documentation/RCU/00-INDEX
浏览文件 @ 50e59058
......@@ -12,6 +12,8 @@ lockdep-splat.txt
- RCU Lockdep splats explained.
NMI-RCU.txt
- Using RCU to Protect Dynamic NMI Handlers
rcu_dereference.txt
- Proper care and feeding of return values from rcu_dereference()
rcubarrier.txt
- RCU and Unloadable Modules
rculist_nulls.txt
......
Documentation/RCU/checklist.txt
浏览文件 @ 50e59058
......@@ -114,12 +114,16 @@ over a rather long period of time, but improvements are always welcome!
http://www.openvms.compaq.com/wizard/wiz_2637.html
The rcu_dereference() primitive is also an excellent
documentation aid, letting the person reading the code
know exactly which pointers are protected by RCU.
documentation aid, letting the person reading the
code know exactly which pointers are protected by RCU.
Please note that compilers can also reorder code, and
they are becoming increasingly aggressive about doing
just that. The rcu_dereference() primitive therefore
also prevents destructive compiler optimizations.
just that. The rcu_dereference() primitive therefore also
prevents destructive compiler optimizations. However,
with a bit of devious creativity, it is possible to
mishandle the return value from rcu_dereference().
Please see rcu_dereference.txt in this directory for
more information.
The rcu_dereference() primitive is used by the
various "_rcu()" list-traversal primitives, such
......
Documentation/RCU/rcu_dereference.txt 0 → 100644
浏览文件 @ 50e59058
PROPER CARE AND FEEDING OF RETURN VALUES FROM rcu_dereference()
Most of the time, you can use values from rcu_dereference() or one of
the similar primitives without worries. Dereferencing (prefix "*"),
field selection ("->"), assignment ("="), address-of ("&"), addition and
subtraction of constants, and casts all work quite naturally and safely.
It is nevertheless possible to get into trouble with other operations.
Follow these rules to keep your RCU code working properly:
o You must use one of the rcu_dereference() family of primitives
to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
will complain. Worse yet, your code can see random memory-corruption
bugs due to games that compilers and DEC Alpha can play.
Without one of the rcu_dereference() primitives, compilers
can reload the value, and won't your code have fun with two
different values for a single pointer! Without rcu_dereference(),
DEC Alpha can load a pointer, dereference that pointer, and
return data preceding initialization that preceded the store of
the pointer.
In addition, the volatile cast in rcu_dereference() prevents the
compiler from deducing the resulting pointer value. Please see
the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH"
for an example where the compiler can in fact deduce the exact
value of the pointer, and thus cause misordering.
o Do not use single-element RCU-protected arrays. The compiler
is within its right to assume that the value of an index into
such an array must necessarily evaluate to zero. The compiler
could then substitute the constant zero for the computation, so
that the array index no longer depended on the value returned
by rcu_dereference(). If the array index no longer depends
on rcu_dereference(), then both the compiler and the CPU
are within their rights to order the array access before the
rcu_dereference(), which can cause the array access to return
garbage.
o Avoid cancellation when using the "+" and "-" infix arithmetic
operators. For example, for a given variable "x", avoid
"(x-x)". There are similar arithmetic pitfalls from other
arithmetic operatiors, such as "(x*0)", "(x/(x+1))" or "(x%1)".
The compiler is within its rights to substitute zero for all of
these expressions, so that subsequent accesses no longer depend
on the rcu_dereference(), again possibly resulting in bugs due
to misordering.
Of course, if "p" is a pointer from rcu_dereference(), and "a"
and "b" are integers that happen to be equal, the expression
"p+a-b" is safe because its value still necessarily depends on
the rcu_dereference(), thus maintaining proper ordering.
o Avoid all-zero operands to the bitwise "&" operator, and
similarly avoid all-ones operands to the bitwise "|" operator.
If the compiler is able to deduce the value of such operands,
it is within its rights to substitute the corresponding constant
for the bitwise operation. Once again, this causes subsequent
accesses to no longer depend on the rcu_dereference(), causing
bugs due to misordering.
Please note that single-bit operands to bitwise "&" can also
be dangerous. At this point, the compiler knows that the
resulting value can only take on one of two possible values.
Therefore, a very small amount of additional information will
allow the compiler to deduce the exact value, which again can
result in misordering.
o If you are using RCU to protect JITed functions, so that the
"()" function-invocation operator is applied to a value obtained
(directly or indirectly) from rcu_dereference(), you may need to
interact directly with the hardware to flush instruction caches.
This issue arises on some systems when a newly JITed function is
using the same memory that was used by an earlier JITed function.
o Do not use the results from the boolean "&&" and "||" when
dereferencing. For example, the following (rather improbable)
code is buggy:
int a[2];
int index;
int force_zero_index = 1;
...
r1 = rcu_dereference(i1)
r2 = a[r1 && force_zero_index]; /* BUGGY!!! */
The reason this is buggy is that "&&" and "||" are often compiled
using branches. While weak-memory machines such as ARM or PowerPC
do order stores after such branches, they can speculate loads,
which can result in misordering bugs.
o Do not use the results from relational operators ("==", "!=",
">", ">=", "<", or "<=") when dereferencing. For example,
the following (quite strange) code is buggy:
int a[2];
int index;
int flip_index = 0;
...
r1 = rcu_dereference(i1)
r2 = a[r1 != flip_index]; /* BUGGY!!! */
As before, the reason this is buggy is that relational operators
are often compiled using branches. And as before, although
weak-memory machines such as ARM or PowerPC do order stores
after such branches, but can speculate loads, which can again
result in misordering bugs.
o Be very careful about comparing pointers obtained from
rcu_dereference() against non-NULL values. As Linus Torvalds
explained, if the two pointers are equal, the compiler could
substitute the pointer you are comparing against for the pointer
obtained from rcu_dereference(). For example:
p = rcu_dereference(gp);
if (p == &default_struct)
do_default(p->a);
Because the compiler now knows that the value of "p" is exactly
the address of the variable "default_struct", it is free to
transform this code into the following:
p = rcu_dereference(gp);
if (p == &default_struct)
do_default(default_struct.a);
On ARM and Power hardware, the load from "default_struct.a"
can now be speculated, such that it might happen before the
rcu_dereference(). This could result in bugs due to misordering.
However, comparisons are OK in the following cases:
o The comparison was against the NULL pointer. If the
compiler knows that the pointer is NULL, you had better
not be dereferencing it anyway. If the comparison is
non-equal, the compiler is none the wiser. Therefore,
it is safe to compare pointers from rcu_dereference()
against NULL pointers.
o The pointer is never dereferenced after being compared.
Since there are no subsequent dereferences, the compiler
cannot use anything it learned from the comparison
to reorder the non-existent subsequent dereferences.
This sort of comparison occurs frequently when scanning
RCU-protected circular linked lists.
o The comparison is against a pointer that references memory
that was initialized "a long time ago." The reason
this is safe is that even if misordering occurs, the
misordering will not affect the accesses that follow
the comparison. So exactly how long ago is "a long
time ago"? Here are some possibilities:
o Compile time.
o Boot time.
o Module-init time for module code.
o Prior to kthread creation for kthread code.
o During some prior acquisition of the lock that
we now hold.
o Before mod_timer() time for a timer handler.
There are many other possibilities involving the Linux
kernel's wide array of primitives that cause code to
be invoked at a later time.
o The pointer being compared against also came from
rcu_dereference(). In this case, both pointers depend
on one rcu_dereference() or another, so you get proper
ordering either way.
That said, this situation can make certain RCU usage
bugs more likely to happen. Which can be a good thing,
at least if they happen during testing. An example
of such an RCU usage bug is shown in the section titled
"EXAMPLE OF AMPLIFIED RCU-USAGE BUG".
o All of the accesses following the comparison are stores,
so that a control dependency preserves the needed ordering.
That said, it is easy to get control dependencies wrong.
Please see the "CONTROL DEPENDENCIES" section of
Documentation/memory-barriers.txt for more details.
o The pointers are not equal -and- the compiler does
not have enough information to deduce the value of the
pointer. Note that the volatile cast in rcu_dereference()
will normally prevent the compiler from knowing too much.
o Disable any value-speculation optimizations that your compiler
might provide, especially if you are making use of feedback-based
optimizations that take data collected from prior runs. Such
value-speculation optimizations reorder operations by design.
There is one exception to this rule: Value-speculation
optimizations that leverage the branch-prediction hardware are
safe on strongly ordered systems (such as x86), but not on weakly
ordered systems (such as ARM or Power). Choose your compiler
command-line options wisely!
EXAMPLE OF AMPLIFIED RCU-USAGE BUG
Because updaters can run concurrently with RCU readers, RCU readers can
see stale and/or inconsistent values. If RCU readers need fresh or
consistent values, which they sometimes do, they need to take proper
precautions. To see this, consider the following code fragment:
struct foo {
int a;
int b;
int c;
};
struct foo *gp1;
struct foo *gp2;
void updater(void)
{
struct foo *p;
p = kmalloc(...);
if (p == NULL)
deal_with_it();
p->a = 42; /* Each field in its own cache line. */
p->b = 43;
p->c = 44;
rcu_assign_pointer(gp1, p);
p->b = 143;
p->c = 144;
rcu_assign_pointer(gp2, p);
}
void reader(void)
{
struct foo *p;
struct foo *q;
int r1, r2;
p = rcu_dereference(gp2);
if (p == NULL)
return;
r1 = p->b; /* Guaranteed to get 143. */
q = rcu_dereference(gp1); /* Guaranteed non-NULL. */
if (p == q) {
/* The compiler decides that q->c is same as p->c. */
r2 = p->c; /* Could get 44 on weakly order system. */
}
do_something_with(r1, r2);
}
You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
but you should not be. After all, the updater might have been invoked
a second time between the time reader() loaded into "r1" and the time
that it loaded into "r2". The fact that this same result can occur due
to some reordering from the compiler and CPUs is beside the point.
But suppose that the reader needs a consistent view?
Then one approach is to use locking, for example, as follows:
struct foo {
int a;
int b;
int c;
spinlock_t lock;
};
struct foo *gp1;
struct foo *gp2;
void updater(void)
{
struct foo *p;
p = kmalloc(...);
if (p == NULL)
deal_with_it();
spin_lock(&p->lock);
p->a = 42; /* Each field in its own cache line. */
p->b = 43;
p->c = 44;
spin_unlock(&p->lock);
rcu_assign_pointer(gp1, p);
spin_lock(&p->lock);
p->b = 143;
p->c = 144;
spin_unlock(&p->lock);
rcu_assign_pointer(gp2, p);
}
void reader(void)
{
struct foo *p;
struct foo *q;
int r1, r2;
p = rcu_dereference(gp2);
if (p == NULL)
return;
spin_lock(&p->lock);
r1 = p->b; /* Guaranteed to get 143. */
q = rcu_dereference(gp1); /* Guaranteed non-NULL. */
if (p == q) {
/* The compiler decides that q->c is same as p->c. */
r2 = p->c; /* Locking guarantees r2 == 144. */
}
spin_unlock(&p->lock);
do_something_with(r1, r2);
}
As always, use the right tool for the job!
EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH
If a pointer obtained from rcu_dereference() compares not-equal to some
other pointer, the compiler normally has no clue what the value of the
first pointer might be. This lack of knowledge prevents the compiler
from carrying out optimizations that otherwise might destroy the ordering
guarantees that RCU depends on. And the volatile cast in rcu_dereference()
should prevent the compiler from guessing the value.
But without rcu_dereference(), the compiler knows more than you might
expect. Consider the following code fragment:
struct foo {
int a;
int b;
};
static struct foo variable1;
static struct foo variable2;
static struct foo *gp = &variable1;
void updater(void)
{
initialize_foo(&variable2);
rcu_assign_pointer(gp, &variable2);
/*
* The above is the only store to gp in this translation unit,
* and the address of gp is not exported in any way.
*/
}
int reader(void)
{
struct foo *p;
p = gp;
barrier();
if (p == &variable1)
return p->a; /* Must be variable1.a. */
else
return p->b; /* Must be variable2.b. */
}
Because the compiler can see all stores to "gp", it knows that the only
possible values of "gp" are "variable1" on the one hand and "variable2"
on the other. The comparison in reader() therefore tells the compiler
the exact value of "p" even in the not-equals case. This allows the
compiler to make the return values independent of the load from "gp",
in turn destroying the ordering between this load and the loads of the
return values. This can result in "p->b" returning pre-initialization
garbage values.
In short, rcu_dereference() is -not- optional when you are going to
dereference the resulting pointer.
Documentation/RCU/stallwarn.txt
浏览文件 @ 50e59058
......@@ -24,7 +24,7 @@ CONFIG_RCU_CPU_STALL_TIMEOUT
timing of the next warning for the current stall.
Stall-warning messages may be enabled and disabled completely via
/sys/module/rcutree/parameters/rcu_cpu_stall_suppress.
/sys/module/rcupdate/parameters/rcu_cpu_stall_suppress.
CONFIG_RCU_CPU_STALL_VERBOSE
......
Documentation/RCU/whatisRCU.txt
浏览文件 @ 50e59058
......@@ -326,11 +326,11 @@ used as follows:
a. synchronize_rcu() rcu_read_lock() / rcu_read_unlock()
call_rcu() rcu_dereference()
b. call_rcu_bh() rcu_read_lock_bh() / rcu_read_unlock_bh()
rcu_dereference_bh()
b. synchronize_rcu_bh() rcu_read_lock_bh() / rcu_read_unlock_bh()
call_rcu_bh() rcu_dereference_bh()
c. synchronize_sched() rcu_read_lock_sched() / rcu_read_unlock_sched()
preempt_disable() / preempt_enable()
call_rcu_sched() preempt_disable() / preempt_enable()
local_irq_save() / local_irq_restore()
hardirq enter / hardirq exit
NMI enter / NMI exit
......@@ -794,10 +794,22 @@ in docbook. Here is the list, by category.
RCU list traversal:
list_entry_rcu
list_first_entry_rcu
list_next_rcu
list_for_each_entry_rcu
list_for_each_entry_continue_rcu
hlist_first_rcu
hlist_next_rcu
hlist_pprev_rcu
hlist_for_each_entry_rcu
hlist_for_each_entry_rcu_bh
hlist_for_each_entry_continue_rcu
hlist_for_each_entry_continue_rcu_bh
hlist_nulls_first_rcu
hlist_nulls_for_each_entry_rcu
list_for_each_entry_continue_rcu
hlist_bl_first_rcu
hlist_bl_for_each_entry_rcu
RCU pointer/list update:
......@@ -806,28 +818,38 @@ RCU pointer/list update:
list_add_tail_rcu
list_del_rcu
list_replace_rcu
hlist_del_rcu
hlist_add_after_rcu
hlist_add_before_rcu
hlist_add_head_rcu
hlist_del_rcu
hlist_del_init_rcu
hlist_replace_rcu
list_splice_init_rcu()
hlist_nulls_del_init_rcu
hlist_nulls_del_rcu
hlist_nulls_add_head_rcu
hlist_bl_add_head_rcu
hlist_bl_del_init_rcu
hlist_bl_del_rcu
hlist_bl_set_first_rcu
RCU: Critical sections Grace period Barrier
rcu_read_lock synchronize_net rcu_barrier
rcu_read_unlock synchronize_rcu
rcu_dereference synchronize_rcu_expedited
call_rcu
kfree_rcu
rcu_read_lock_held call_rcu
rcu_dereference_check kfree_rcu
rcu_dereference_protected
bh: Critical sections Grace period Barrier
rcu_read_lock_bh call_rcu_bh rcu_barrier_bh
rcu_read_unlock_bh synchronize_rcu_bh
rcu_dereference_bh synchronize_rcu_bh_expedited
rcu_dereference_bh_check
rcu_dereference_bh_protected
rcu_read_lock_bh_held
sched: Critical sections Grace period Barrier
......@@ -835,7 +857,12 @@ sched: Critical sections Grace period Barrier
rcu_read_unlock_sched call_rcu_sched
[preempt_disable] synchronize_sched_expedited
[and friends]
rcu_read_lock_sched_notrace
rcu_read_unlock_sched_notrace
rcu_dereference_sched
rcu_dereference_sched_check
rcu_dereference_sched_protected
rcu_read_lock_sched_held
SRCU: Critical sections Grace period Barrier
......@@ -843,6 +870,8 @@ SRCU: Critical sections Grace period Barrier
srcu_read_lock synchronize_srcu srcu_barrier
srcu_read_unlock call_srcu
srcu_dereference synchronize_srcu_expedited
srcu_dereference_check
srcu_read_lock_held
SRCU: Initialization/cleanup
init_srcu_struct
......@@ -850,9 +879,13 @@ SRCU: Initialization/cleanup
All: lockdep-checked RCU-protected pointer access
rcu_dereference_check
rcu_dereference_protected
rcu_access_index
rcu_access_pointer
rcu_dereference_index_check
rcu_dereference_raw
rcu_lockdep_assert
rcu_sleep_check
RCU_NONIDLE
See the comment headers in the source code (or the docbook generated
from them) for more information.
......
Documentation/SubmittingPatches
浏览文件 @ 50e59058
......@@ -132,6 +132,20 @@ Example:
platform_set_drvdata(), but left the variable "dev" unused,
delete it.
If your patch fixes a bug in a specific commit, e.g. you found an issue using
git-bisect, please use the 'Fixes:' tag with the first 12 characters of the
SHA-1 ID, and the one line summary.
Example:
Fixes: e21d2170f366 ("video: remove unnecessary platform_set_drvdata()")
The following git-config settings can be used to add a pretty format for
outputting the above style in the git log or git show commands
[core]
abbrev = 12
[pretty]
fixes = Fixes: %h (\"%s\")
3) Separate your changes.
......@@ -443,7 +457,7 @@ person it names. This tag documents that potentially interested parties
have been included in the discussion
14) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by:
14) Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
If this patch fixes a problem reported by somebody else, consider adding a
Reported-by: tag to credit the reporter for their contribution. Please
......@@ -498,6 +512,12 @@ idea was not posted in a public forum. That said, if we diligently credit our
idea reporters, they will, hopefully, be inspired to help us again in the
future.
A Fixes: tag indicates that the patch fixes an issue in a previous commit. It
is used to make it easy to determine where a bug originated, which can help
review a bug fix. This tag also assists the stable kernel team in determining
which stable kernel versions should receive your fix. This is the preferred
method for indicating a bug fixed by the patch. See #2 above for more details.
15) The canonical patch format
......
Documentation/acpi/enumeration.txt
浏览文件 @ 50e59058
......@@ -296,7 +296,7 @@ specifies the path to the controller. In order to use these GPIOs in Linux
we need to translate them to the corresponding Linux GPIO descriptors.
There is a standard GPIO API for that and is documented in
Documentation/gpio.txt.
Documentation/gpio/.
In the above example we can get the corresponding two GPIO descriptors with
a code like this:
......
Documentation/arm/00-INDEX
浏览文件 @ 50e59058
......@@ -46,5 +46,7 @@ swp_emulation
- SWP/SWPB emulation handler/logging description
tcm.txt
- ARM Tightly Coupled Memory
uefi.txt
- [U]EFI configuration and runtime services documentation
vlocks.txt
- Voting locks, low-level mechanism relying on memory system atomic writes.
Documentation/arm/Marvell/README
浏览文件 @ 50e59058
......@@ -234,6 +234,11 @@ Berlin family (Digital Entertainment)
Core: Marvell PJ4B (ARMv7), Tauros3 L2CC
Homepage: http://www.marvell.com/digital-entertainment/armada-1500/
Product Brief: http://www.marvell.com/digital-entertainment/armada-1500/assets/Marvell-ARMADA-1500-Product-Brief.pdf
88DE3114, Armada 1500 Pro
Design name: BG2-Q
Core: Quad Core ARM Cortex-A9, PL310 L2CC
Homepage: http://www.marvell.com/digital-entertainment/armada-1500-pro/
Product Brief: http://www.marvell.com/digital-entertainment/armada-1500-pro/assets/Marvell_ARMADA_1500_PRO-01_product_brief.pdf
88DE????
Design name: BG3
Core: ARM Cortex-A15, CA15 integrated L2CC
......
Documentation/arm/memory.txt
浏览文件 @ 50e59058
......@@ -41,16 +41,9 @@ fffe8000 fffeffff DTCM mapping area for platforms with
fffe0000 fffe7fff ITCM mapping area for platforms with
ITCM mounted inside the CPU.
fff00000 fffdffff Fixmap mapping region. Addresses provided
ffc00000 ffdfffff Fixmap mapping region. Addresses provided
by fix_to_virt() will be located here.
ffc00000 ffefffff DMA memory mapping region. Memory returned
by the dma_alloc_xxx functions will be
dynamically mapped here.
ff000000 ffbfffff Reserved for future expansion of DMA
mapping region.
fee00000 feffffff Mapping of PCI I/O space. This is a static
mapping within the vmalloc space.
......
Documentation/arm/sti/stih407-overview.txt 0 → 100644
浏览文件 @ 50e59058
STiH407 Overview
================
Introduction
------------
The STiH407 is the new generation of SoC for Multi-HD, AVC set-top boxes
and server/connected client application for satellite, cable, terrestrial
and IP-STB markets.
Features
- ARM Cortex-A9 1.5 GHz dual core CPU (28nm)
- SATA2, USB 3.0, PCIe, Gbit Ethernet
Document Author
---------------
Maxime Coquelin <maxime.coquelin@st.com>, (c) 2014 ST Microelectronics
Documentation/arm/uefi.txt 0 → 100644
浏览文件 @ 50e59058
UEFI, the Unified Extensible Firmware Interface, is a specification
governing the behaviours of compatible firmware interfaces. It is
maintained by the UEFI Forum - http://www.uefi.org/.
UEFI is an evolution of its predecessor 'EFI', so the terms EFI and
UEFI are used somewhat interchangeably in this document and associated
source code. As a rule, anything new uses 'UEFI', whereas 'EFI' refers
to legacy code or specifications.
UEFI support in Linux
=====================
Booting on a platform with firmware compliant with the UEFI specification
makes it possible for the kernel to support additional features:
- UEFI Runtime Services
- Retrieving various configuration information through the standardised
interface of UEFI configuration tables. (ACPI, SMBIOS, ...)
For actually enabling [U]EFI support, enable:
- CONFIG_EFI=y
- CONFIG_EFI_VARS=y or m
The implementation depends on receiving information about the UEFI environment
in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
UEFI stub
=========
The "stub" is a feature that extends the Image/zImage into a valid UEFI
PE/COFF executable, including a loader application that makes it possible to
load the kernel directly from the UEFI shell, boot menu, or one of the
lightweight bootloaders like Gummiboot or rEFInd.
The kernel image built with stub support remains a valid kernel image for
booting in non-UEFI environments.
UEFI kernel support on ARM
==========================
UEFI kernel support on the ARM architectures (arm and arm64) is only available
when boot is performed through the stub.
When booting in UEFI mode, the stub deletes any memory nodes from a provided DT.
Instead, the kernel reads the UEFI memory map.
The stub populates the FDT /chosen node with (and the kernel scans for) the
following parameters:
________________________________________________________________________________
Name | Size | Description
================================================================================
linux,uefi-system-table | 64-bit | Physical address of the UEFI System Table.
--------------------------------------------------------------------------------
linux,uefi-mmap-start | 64-bit | Physical address of the UEFI memory map,
| | populated by the UEFI GetMemoryMap() call.
--------------------------------------------------------------------------------
linux,uefi-mmap-size | 32-bit | Size in bytes of the UEFI memory map
| | pointed to in previous entry.
--------------------------------------------------------------------------------
linux,uefi-mmap-desc-size | 32-bit | Size in bytes of each entry in the UEFI
| | memory map.
--------------------------------------------------------------------------------
linux,uefi-mmap-desc-ver | 32-bit | Version of the mmap descriptor format.
--------------------------------------------------------------------------------
linux,uefi-stub-kern-ver | string | Copy of linux_banner from build.
--------------------------------------------------------------------------------
For verbose debug messages, specify 'uefi_debug' on the kernel command line.
Documentation/arm64/booting.txt
浏览文件 @ 50e59058
......@@ -85,6 +85,10 @@ The decompressed kernel image contains a 64-byte header as follows:
Header notes:
- code0/code1 are responsible for branching to stext.
- when booting through EFI, code0/code1 are initially skipped.
res5 is an offset to the PE header and the PE header has the EFI
entry point (efi_stub_entry). When the stub has done its work, it
jumps to code0 to resume the normal boot process.
The image must be placed at the specified offset (currently 0x80000)
from the start of the system RAM and called there. The start of the
......
Documentation/atomic_ops.txt
浏览文件 @ 50e59058
......@@ -285,15 +285,13 @@ If a caller requires memory barrier semantics around an atomic_t
operation which does not return a value, a set of interfaces are
defined which accomplish this:
void smp_mb__before_atomic_dec(void);
void smp_mb__after_atomic_dec(void);
void smp_mb__before_atomic_inc(void);
void smp_mb__after_atomic_inc(void);
void smp_mb__before_atomic(void);
void smp_mb__after_atomic(void);
For example, smp_mb__before_atomic_dec() can be used like so:
For example, smp_mb__before_atomic() can be used like so:
obj->dead = 1;
smp_mb__before_atomic_dec();
smp_mb__before_atomic();
atomic_dec(&obj->ref_count);
It makes sure that all memory operations preceding the atomic_dec()
......@@ -302,15 +300,10 @@ operation. In the above example, it guarantees that the assignment of
"1" to obj->dead will be globally visible to other cpus before the
atomic counter decrement.
Without the explicit smp_mb__before_atomic_dec() call, the
Without the explicit smp_mb__before_atomic() call, the
implementation could legally allow the atomic counter update visible
to other cpus before the "obj->dead = 1;" assignment.
The other three interfaces listed are used to provide explicit
ordering with respect to memory operations after an atomic_dec() call
(smp_mb__after_atomic_dec()) and around atomic_inc() calls
(smp_mb__{before,after}_atomic_inc()).
A missing memory barrier in the cases where they are required by the
atomic_t implementation above can have disastrous results. Here is
an example, which follows a pattern occurring frequently in the Linux
......@@ -487,12 +480,12 @@ Finally there is the basic operation:
Which returns a boolean indicating if bit "nr" is set in the bitmask
pointed to by "addr".
If explicit memory barriers are required around clear_bit() (which
does not return a value, and thus does not need to provide memory
barrier semantics), two interfaces are provided:
If explicit memory barriers are required around {set,clear}_bit() (which do
not return a value, and thus does not need to provide memory barrier
semantics), two interfaces are provided:
void smp_mb__before_clear_bit(void);
void smp_mb__after_clear_bit(void);
void smp_mb__before_atomic(void);
void smp_mb__after_atomic(void);
They are used as follows, and are akin to their atomic_t operation
brothers:
......@@ -500,13 +493,13 @@ brothers:
/* All memory operations before this call will
* be globally visible before the clear_bit().
*/
smp_mb__before_clear_bit();
smp_mb__before_atomic();
clear_bit( ... );
/* The clear_bit() will be visible before all
* subsequent memory operations.
*/
smp_mb__after_clear_bit();
smp_mb__after_atomic();
There are two special bitops with lock barrier semantics (acquire/release,
same as spinlocks). These operate in the same way as their non-_lock/unlock
......
Documentation/cgroups/memory.txt
浏览文件 @ 50e59058
......@@ -270,6 +270,11 @@ When oom event notifier is registered, event will be delivered.
2.7 Kernel Memory Extension (CONFIG_MEMCG_KMEM)
WARNING: Current implementation lacks reclaim support. That means allocation
attempts will fail when close to the limit even if there are plenty of
kmem available for reclaim. That makes this option unusable in real
life so DO NOT SELECT IT unless for development purposes.
With the Kernel memory extension, the Memory Controller is able to limit
the amount of kernel memory used by the system. Kernel memory is fundamentally
different than user memory, since it can't be swapped out, which makes it
......@@ -453,15 +458,11 @@ About use_hierarchy, see Section 6.
5.1 force_empty
memory.force_empty interface is provided to make cgroup's memory usage empty.
You can use this interface only when the cgroup has no tasks.
When writing anything to this
# echo 0 > memory.force_empty
Almost all pages tracked by this memory cgroup will be unmapped and freed.
Some pages cannot be freed because they are locked or in-use. Such pages are
moved to parent (if use_hierarchy==1) or root (if use_hierarchy==0) and this
cgroup will be empty.
the cgroup will be reclaimed and as many pages reclaimed as possible.
The typical use case for this interface is before calling rmdir().
Because rmdir() moves all pages to parent, some out-of-use page caches can be
......@@ -535,16 +536,13 @@ Note:
5.3 swappiness
Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.
Please note that unlike the global swappiness, memcg knob set to 0
really prevents from any swapping even if there is a swap storage
available. This might lead to memcg OOM killer if there are no file
pages to reclaim.
Overrides /proc/sys/vm/swappiness for the particular group. The tunable
in the root cgroup corresponds to the global swappiness setting.
Following cgroups' swappiness can't be changed.
- root cgroup (uses /proc/sys/vm/swappiness).
- a cgroup which uses hierarchy and it has other cgroup(s) below it.
- a cgroup which uses hierarchy and not the root of hierarchy.
Please note that unlike during the global reclaim, limit reclaim
enforces that 0 swappiness really prevents from any swapping even if
there is a swap storage available. This might lead to memcg OOM killer
if there are no file pages to reclaim.
5.4 failcnt
......@@ -754,7 +752,6 @@ You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
#echo 1 > memory.oom_control
This operation is only allowed to the top cgroup of a sub-hierarchy.
If OOM-killer is disabled, tasks under cgroup will hang/sleep
in memory cgroup's OOM-waitqueue when they request accountable memory.
......
Documentation/cgroups/unified-hierarchy.txt 0 → 100644
浏览文件 @ 50e59058
Cgroup unified hierarchy
April, 2014 Tejun Heo <tj@kernel.org>
This document describes the changes made by unified hierarchy and
their rationales. It will eventually be merged into the main cgroup
documentation.
CONTENTS
1. Background
2. Basic Operation
2-1. Mounting
2-2. cgroup.subtree_control
2-3. cgroup.controllers
3. Structural Constraints
3-1. Top-down
3-2. No internal tasks
4. Other Changes
4-1. [Un]populated Notification
4-2. Other Core Changes
4-3. Per-Controller Changes
4-3-1. blkio
4-3-2. cpuset
4-3-3. memory
5. Planned Changes
5-1. CAP for resource control
1. Background
cgroup allows an arbitrary number of hierarchies and each hierarchy
can host any number of controllers. While this seems to provide a
high level of flexibility, it isn't quite useful in practice.
For example, as there is only one instance of each controller, utility
type controllers such as freezer which can be useful in all
hierarchies can only be used in one. The issue is exacerbated by the
fact that controllers can't be moved around once hierarchies are
populated. Another issue is that all controllers bound to a hierarchy
are forced to have exactly the same view of the hierarchy. It isn't
possible to vary the granularity depending on the specific controller.
In practice, these issues heavily limit which controllers can be put
on the same hierarchy and most configurations resort to putting each
controller on its own hierarchy. Only closely related ones, such as
the cpu and cpuacct controllers, make sense to put on the same
hierarchy. This often means that userland ends up managing multiple
similar hierarchies repeating the same steps on each hierarchy
whenever a hierarchy management operation is necessary.
Unfortunately, support for multiple hierarchies comes at a steep cost.
Internal implementation in cgroup core proper is dazzlingly
complicated but more importantly the support for multiple hierarchies
restricts how cgroup is used in general and what controllers can do.
There's no limit on how many hierarchies there may be, which means
that a task's cgroup membership can't be described in finite length.
The key may contain any varying number of entries and is unlimited in
length, which makes it highly awkward to handle and leads to addition
of controllers which exist only to identify membership, which in turn
exacerbates the original problem.
Also, as a controller can't have any expectation regarding what shape
of hierarchies other controllers would be on, each controller has to
assume that all other controllers are operating on completely
orthogonal hierarchies. This makes it impossible, or at least very
cumbersome, for controllers to cooperate with each other.
In most use cases, putting controllers on hierarchies which are
completely orthogonal to each other isn't necessary. What usually is
called for is the ability to have differing levels of granularity
depending on the specific controller. In other words, hierarchy may
be collapsed from leaf towards root when viewed from specific
controllers. For example, a given configuration might not care about
how memory is distributed beyond a certain level while still wanting
to control how CPU cycles are distributed.
Unified hierarchy is the next version of cgroup interface. It aims to
address the aforementioned issues by having more structure while
retaining enough flexibility for most use cases. Various other
general and controller-specific interface issues are also addressed in
the process.
2. Basic Operation
2-1. Mounting
Currently, unified hierarchy can be mounted with the following mount
command. Note that this is still under development and scheduled to
change soon.
mount -t cgroup -o __DEVEL__sane_behavior cgroup $MOUNT_POINT
All controllers which are not bound to other hierarchies are
automatically bound to unified hierarchy and show up at the root of
it. Controllers which are enabled only in the root of unified
hierarchy can be bound to other hierarchies at any time. This allows
mixing unified hierarchy with the traditional multiple hierarchies in
a fully backward compatible way.
2-2. cgroup.subtree_control
All cgroups on unified hierarchy have a "cgroup.subtree_control" file
which governs which controllers are enabled on the children of the
cgroup. Let's assume a hierarchy like the following.
root - A - B - C
\ D
root's "cgroup.subtree_control" file determines which controllers are
enabled on A. A's on B. B's on C and D. This coincides with the
fact that controllers on the immediate sub-level are used to
distribute the resources of the parent. In fact, it's natural to
assume that resource control knobs of a child belong to its parent.
Enabling a controller in a "cgroup.subtree_control" file declares that
distribution of the respective resources of the cgroup will be
controlled. Note that this means that controller enable states are
shared among siblings.
When read, the file contains a space-separated list of currently
enabled controllers. A write to the file should contain a
space-separated list of controllers with '+' or '-' prefixed (without
the quotes). Controllers prefixed with '+' are enabled and '-'
disabled. If a controller is listed multiple times, the last entry
wins. The specific operations are executed atomically - either all
succeed or fail.
2-3. cgroup.controllers
Read-only "cgroup.controllers" file contains a space-separated list of
controllers which can be enabled in the cgroup's
"cgroup.subtree_control" file.
In the root cgroup, this lists controllers which are not bound to
other hierarchies and the content changes as controllers are bound to
and unbound from other hierarchies.
In non-root cgroups, the content of this file equals that of the
parent's "cgroup.subtree_control" file as only controllers enabled
from the parent can be used in its children.
3. Structural Constraints
3-1. Top-down
As it doesn't make sense to nest control of an uncontrolled resource,
all non-root "cgroup.subtree_control" files can only contain
controllers which are enabled in the parent's "cgroup.subtree_control"
file. A controller can be enabled only if the parent has the
controller enabled and a controller can't be disabled if one or more
children have it enabled.
3-2. No internal tasks
One long-standing issue that cgroup faces is the competition between
tasks belonging to the parent cgroup and its children cgroups. This
is inherently nasty as two different types of entities compete and
there is no agreed-upon obvious way to handle it. Different
controllers are doing different things.
The cpu controller considers tasks and cgroups as equivalents and maps
nice levels to cgroup weights. This works for some cases but falls
flat when children should be allocated specific ratios of CPU cycles
and the number of internal tasks fluctuates - the ratios constantly
change as the number of competing entities fluctuates. There also are
other issues. The mapping from nice level to weight isn't obvious or
universal, and there are various other knobs which simply aren't
available for tasks.
The blkio controller implicitly creates a hidden leaf node for each
cgroup to host the tasks. The hidden leaf has its own copies of all
the knobs with "leaf_" prefixed. While this allows equivalent control
over internal tasks, it's with serious drawbacks. It always adds an
extra layer of nesting which may not be necessary, makes the interface
messy and significantly complicates the implementation.
The memory controller currently doesn't have a way to control what
happens between internal tasks and child cgroups and the behavior is
not clearly defined. There have been attempts to add ad-hoc behaviors
and knobs to tailor the behavior to specific workloads. Continuing
this direction will lead to problems which will be extremely difficult
to resolve in the long term.
Multiple controllers struggle with internal tasks and came up with
different ways to deal with it; unfortunately, all the approaches in
use now are severely flawed and, furthermore, the widely different
behaviors make cgroup as whole highly inconsistent.
It is clear that this is something which needs to be addressed from
cgroup core proper in a uniform way so that controllers don't need to
worry about it and cgroup as a whole shows a consistent and logical
behavior. To achieve that, unified hierarchy enforces the following
structural constraint:
Except for the root, only cgroups which don't contain any task may
have controllers enabled in their "cgroup.subtree_control" files.
Combined with other properties, this guarantees that, when a
controller is looking at the part of the hierarchy which has it
enabled, tasks are always only on the leaves. This rules out
situations where child cgroups compete against internal tasks of the
parent.
There are two things to note. Firstly, the root cgroup is exempt from
the restriction. Root contains tasks and anonymous resource
consumption which can't be associated with any other cgroup and
requires special treatment from most controllers. How resource
consumption in the root cgroup is governed is up to each controller.
Secondly, the restriction doesn't take effect if there is no enabled
controller in the cgroup's "cgroup.subtree_control" file. This is
important as otherwise it wouldn't be possible to create children of a
populated cgroup. To control resource distribution of a cgroup, the
cgroup must create children and transfer all its tasks to the children
before enabling controllers in its "cgroup.subtree_control" file.
4. Other Changes
4-1. [Un]populated Notification
cgroup users often need a way to determine when a cgroup's
subhierarchy becomes empty so that it can be cleaned up. cgroup
currently provides release_agent for it; unfortunately, this mechanism
is riddled with issues.
- It delivers events by forking and execing a userland binary
specified as the release_agent. This is a long deprecated method of
notification delivery. It's extremely heavy, slow and cumbersome to
integrate with larger infrastructure.
- There is single monitoring point at the root. There's no way to
delegate management of a subtree.
- The event isn't recursive. It triggers when a cgroup doesn't have
any tasks or child cgroups. Events for internal nodes trigger only
after all children are removed. This again makes it impossible to
delegate management of a subtree.
- Events are filtered from the kernel side. A "notify_on_release"
file is used to subscribe to or suppress release events. This is
unnecessarily complicated and probably done this way because event
delivery itself was expensive.
Unified hierarchy implements an interface file "cgroup.populated"
which can be used to monitor whether the cgroup's subhierarchy has
tasks in it or not. Its value is 0 if there is no task in the cgroup
and its descendants; otherwise, 1. poll and [id]notify events are
triggered when the value changes.
This is significantly lighter and simpler and trivially allows
delegating management of subhierarchy - subhierarchy monitoring can
block further propagation simply by putting itself or another process
in the subhierarchy and monitor events that it's interested in from
there without interfering with monitoring higher in the tree.
In unified hierarchy, the release_agent mechanism is no longer
supported and the interface files "release_agent" and
"notify_on_release" do not exist.
4-2. Other Core Changes
- None of the mount options is allowed.
- remount is disallowed.
- rename(2) is disallowed.
- The "tasks" file is removed. Everything should at process
granularity. Use the "cgroup.procs" file instead.
- The "cgroup.procs" file is not sorted. pids will be unique unless
they got recycled in-between reads.
- The "cgroup.clone_children" file is removed.
4-3. Per-Controller Changes
4-3-1. blkio
- blk-throttle becomes properly hierarchical.
4-3-2. cpuset
- Tasks are kept in empty cpusets after hotplug and take on the masks
of the nearest non-empty ancestor, instead of being moved to it.
- A task can be moved into an empty cpuset, and again it takes on the
masks of the nearest non-empty ancestor.
4-3-3. memory
- use_hierarchy is on by default and the cgroup file for the flag is
not created.
5. Planned Changes
5-1. CAP for resource control
Unified hierarchy will require one of the capabilities(7), which is
yet to be decided, for all resource control related knobs. Process
organization operations - creation of sub-cgroups and migration of
processes in sub-hierarchies may be delegated by changing the
ownership and/or permissions on the cgroup directory and
"cgroup.procs" interface file; however, all operations which affect
resource control - writes to a "cgroup.subtree_control" file or any
controller-specific knobs - will require an explicit CAP privilege.
This, in part, is to prevent the cgroup interface from being
inadvertently promoted to programmable API used by non-privileged
binaries. cgroup exposes various aspects of the system in ways which
aren't properly abstracted for direct consumption by regular programs.
This is an administration interface much closer to sysctl knobs than
system calls. Even the basic access model, being filesystem path
based, isn't suitable for direct consumption. There's no way to
access "my cgroup" in a race-free way or make multiple operations
atomic against migration to another cgroup.
Another aspect is that, for better or for worse, the cgroup interface
goes through far less scrutiny than regular interfaces for
unprivileged userland. The upside is that cgroup is able to expose
useful features which may not be suitable for general consumption in a
reasonable time frame. It provides a relatively short path between
internal details and userland-visible interface. Of course, this
shortcut comes with high risk. We go through what we go through for
general kernel APIs for good reasons. It may end up leaking internal
details in a way which can exert significant pain by locking the
kernel into a contract that can't be maintained in a reasonable
manner.
Also, due to the specific nature, cgroup and its controllers don't
tend to attract attention from a wide scope of developers. cgroup's
short history is already fraught with severely mis-designed
interfaces, unnecessary commitments to and exposing of internal
details, broken and dangerous implementations of various features.
Keeping cgroup as an administration interface is both advantageous for
its role and imperative given its nature. Some of the cgroup features
may make sense for unprivileged access. If deemed justified, those
must be further abstracted and implemented as a different interface,
be it a system call or process-private filesystem, and survive through
the scrutiny that any interface for general consumption is required to
go through.
Requiring CAP is not a complete solution but should serve as a
significant deterrent against spraying cgroup usages in non-privileged
programs.
Documentation/clk.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/cpu-freq/core.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/cpu-freq/index.txt
浏览文件 @ 50e59058
......@@ -35,8 +35,8 @@ Mailing List
------------
There is a CPU frequency changing CVS commit and general list where
you can report bugs, problems or submit patches. To post a message,
send an email to cpufreq@vger.kernel.org, to subscribe go to
http://vger.kernel.org/vger-lists.html#cpufreq and follow the
send an email to linux-pm@vger.kernel.org, to subscribe go to
http://vger.kernel.org/vger-lists.html#linux-pm and follow the
instructions there.
Links
......
Documentation/devicetree/bindings/arm/axxia.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/arm/pmu.txt
浏览文件 @ 50e59058
......@@ -8,6 +8,7 @@ Required properties:
- compatible : should be one of
"arm,armv8-pmuv3"
"arm,cortex-a17-pmu"
"arm,cortex-a15-pmu"
"arm,cortex-a12-pmu"
"arm,cortex-a9-pmu"
......
Documentation/devicetree/bindings/arm/rockchip.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/arm/sti.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/bus/brcm,gisb-arb.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/clock/qoriq-clock.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/clock/ti/dra7-atl.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/hsi/nokia-modem.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/hsi/omap-ssi.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/input/st-keyscan.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/adv7604.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mfd/bfticu.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mfd/qriox.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mfd/sun6i-prcm.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/misc/arm-charlcd.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mmc/sunxi-mmc.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mmc/usdhi6rol0.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/mtd/fsl-quadspi.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/amd-xgbe-phy.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/amd-xgbe.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/fixed-link.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/nfc/pn544.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/nfc/st21nfca.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/net/via-rhine.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/pci/rcar-pci.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/powerpc/4xx/hsta.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/powerpc/fsl/ccf.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/pwm/bcm-kona-pwm.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/regulator/ltc3589.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/rtc/xgene-rtc.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/alc5623.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/cs42l56.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/max98095.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/nokia,rx51.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/snow.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/sound/st,sta350.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/spi/spi-cadence.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/spi/spi-dw.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/usb/ci-hdrc-qcom.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/devicetree/bindings/video/panel-dpi.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/dma-buf-sharing.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/edac.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/efi-stub.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/email-clients.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/fb/sm501.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/fb/sstfb.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ 50e59058
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/filesystems/vfat.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/gpio/consumer.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/gpio/driver.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hid/uhid.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hsi.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/emc1403 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/hwmon-kernel-api.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/jc42
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/lm77
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/nct6683 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/shtc1 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/hwmon/sysfs-interface
浏览文件 @ 50e59058
此差异已折叠。
Documentation/input/alps.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/input/input.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/java.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/kbuild/modules.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/kmemleak.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/kprobes.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/memory-barriers.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/memory-hotplug.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/mtd/spi-nor.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/mutex-design.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/networking/can.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/networking/cdc_mbim.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/networking/dccp.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/networking/filter.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/platform/x86-laptop-drivers.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/power/devices.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/power/opp.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/power/runtime_pm.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/power/states.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/power/swsusp.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/powerpc/cpu_families.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/printk-formats.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/pwm.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/rbtree.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/rfkill.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/robust-futexes.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/s390/monreader.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/s390/zfcpdump.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/scsi/LICENSE.qla2xxx
浏览文件 @ 50e59058
此差异已折叠。
Documentation/security/Smack.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/security/Yama.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/serial/driver
浏览文件 @ 50e59058
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/trace/events.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/trace/ftrace.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/trace/tracepoints.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/usb/chipidea.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/usb/mass-storage.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vDSO/parse_vdso.c
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vDSO/vdso_standalone_test_x86.c 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vDSO/vdso_test.c
浏览文件 @ 50e59058
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/virtual/kvm/devices/vm.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vm/hwpoison.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vm/remap_file_pages.txt 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
Documentation/vm/transhuge.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/w1/w1.generic
浏览文件 @ 50e59058
此差异已折叠。
Documentation/w1/w1.netlink
浏览文件 @ 50e59058
此差异已折叠。
Documentation/x86/earlyprintk.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/x86/i386/IO-APIC.txt
浏览文件 @ 50e59058
此差异已折叠。
Documentation/x86/x86_64/mm.txt
浏览文件 @ 50e59058
此差异已折叠。
MAINTAINERS
浏览文件 @ 50e59058
此差异已折叠。
Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/alpha/include/asm/atomic.h
浏览文件 @ 50e59058
此差异已折叠。
arch/alpha/include/asm/bitops.h
浏览文件 @ 50e59058
此差异已折叠。
arch/alpha/include/asm/pci.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/boot/dts/angel4.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/atomic.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/bitops.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/cache.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/irq.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/processor.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/asm/sections.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/include/uapi/asm/Kbuild
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/devtree.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/entry.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/head.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/irq.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/process.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/smp.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/time.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/kernel/troubleshoot.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/mm/cache_arc700.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/plat-arcfpga/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/plat-arcfpga/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/plat-arcfpga/platform.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arc/plat-arcfpga/smp.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/compressed/head.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am335x-evmsk.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am335x-nano.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-380.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-385-db.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-385-rd.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-385.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9261ek.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9n12ek.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9rlek.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9x5_can.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9x5_isi.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9x5_lcd.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/at91sam9x5cm.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/atlas6.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/axm5516-amarillo.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/axm5516-cpus.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/axm55xx.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/bcm11351.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/bcm21664.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/bcm28155-ap.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/bcm59056.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/berlin2.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/berlin2cd.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/berlin2q-marvell-dmp.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/berlin2q.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/dra72x.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/dra74x.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos3250-pinctrl.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5260-pinctrl.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5260-xyref5260.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5260.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5410-smdk5410.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5410.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5420-peach-pit.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5800-peach-pi.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/exynos5800.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx25-pdk.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx27-pdk.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx35-pdk.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx50.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx51-babbage.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx51-digi-connectcore-jsk.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx51-digi-connectcore-som.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx53-mba53.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6dl-phytec-pbab01.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6dl-phytec-pfla02.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6dl-riotboard.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6dl.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6q-gk802.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6q-udoo.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6qdl-phytec-pbab01.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/k2e-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/k2hk-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/k2l-evm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/keystone.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-b3.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-db.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-km_common.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-km_fixedeth.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-nsa310-common.dtsi 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/boot/dts/kirkwood-nsa320.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-nsa3x0-common.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-openrd-base.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-openrd-client.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-openrd-ultimate.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood-openrd.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/kirkwood.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/marco.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap2420-clocks.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap2420.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap2430-clocks.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap2430.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap24xx-clocks.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-ldp.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-n900.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-overo-common-dvi.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap34xx.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap36xx.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-sdp.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-var-dvk-om44.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-var-om44customboard.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-var-som-om44-wlan.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-var-som-om44.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4-var-som.dts 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/boot/dts/omap4-var-stk-om44.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap5-cm-t54.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap5-sbc-t54.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap5-uevm.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/orion5x-lacie-d2-network.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/orion5x-maxtor-shared-storage-2.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/orion5x-mv88f5182.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/orion5x-rd88f5182-nas.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/orion5x.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/prima2.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064-ifc6410.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064-v2.0.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084-mtp.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-msm8660.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-msm8960.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r7s72100.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a73a4.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7740.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7779.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7791-henninger.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/rk3066a.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/rk3188.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/rk3xxx.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/s3c2416.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sama5d3.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sama5d3xcm.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sama5d3xmb.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/socfpga_cyclone5_socrates.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/socfpga_vt.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/ste-ccu9540.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/ste-href.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/ste-snowball.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/ste-u300.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih407-b2120.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih407-clock.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih407-pinctrl.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih407.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih415-b2000.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih415-b2020.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih415.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih416-b2000.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih416-b2020-revE.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih416-b2020.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih416.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/stih41x.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s-r7-tv-dongle.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun5i-a13.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun6i-a31-app4-evb1.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun6i-a31-m9.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun6i-a31.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-i12-tvbox.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra114-roth.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra114-tn7.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra124-jetson-tk1.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra124.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra30-colibri-eval-v3.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/tegra30-colibri.dtsi 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/twl4030.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/vexpress-v2m.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/vf610-colibri.dts 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/vf610-twr.dts
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/vf610.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/vt8500.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/wm8650.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/wm8850.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/boot/dts/zynq-7000.dtsi
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/common/bL_switcher.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/common/edma.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/common/mcpm_entry.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/common/mcpm_platsmp.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/axm55xx_defconfig 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/badge4_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/bcm_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/cm_x2xx_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/cm_x300_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/corgi_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/dove_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/em_x270_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/ep93xx_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/ixp4xx_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/keystone_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/kirkwood_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/kzm9g_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/mini2440_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/msm_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/multi_v5_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/mv78xx0_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/mvebu_v5_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/mvebu_v7_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/mxs_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/neponset_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/omap1_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/pcm027_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/qcom_defconfig 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/raumfeld_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/realview_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/s3c2410_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/s3c6400_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/sama5_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/shmobile_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/spitz_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/tegra_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/trizeps4_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/viper_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/configs/zeus_defconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/Kbuild
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/assembler.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/atomic.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/barrier.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/bitops.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/cacheflush.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/cp15.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/cputype.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/dcc.h 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/dma-iommu.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/dma-mapping.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/fixmap.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/ftrace.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/glue-cache.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/glue-df.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/highmem.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/io.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/kvm_host.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/kvm_psci.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/mach/arch.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/mcpm.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/memblock.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/memory.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/outercache.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/pci.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/prom.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/psci.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/setup.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/asm/uaccess.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/debug/imx-uart.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/debug/msm.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/debug/s3c24xx.S 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/debug/vf.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/debug/zynq.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/include/uapi/asm/kvm.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/atags_parse.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/bios32.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/devtree.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/entry-header.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/ftrace.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/head-common.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/head.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/hibernate.c 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/isa.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/iwmmxt.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/perf_event_cpu.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/perf_event_v7.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/psci.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/psci_smp.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/sleep.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/stacktrace.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/topology.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/unwind.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kernel/uprobes.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kvm/arm.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kvm/handle_exit.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/kvm/psci.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/at91sam9g45.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/at91sam9n12.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/at91sam9rl.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/at91sam9x5.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-1arm.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-carmeva.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-cpu9krea.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-cpuat91.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-csb337.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-csb637.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-eb9200.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-ecbat91.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-eco920.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-foxg20.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-gsia18s.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-kafa.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-kb9202.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-rm9200ek.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-rsi-ews.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board-yl-9200.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/board.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/gpio.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/gpio.h 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_adc.h 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/mach-at91/include/mach/gpio.h 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/mach-at91/leds.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-at91/sysirq_mask.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-axxia/Kconfig 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-axxia/Makefile 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-axxia/axxia.c 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-axxia/platsmp.c 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/bcm_5301x.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/bcm_kona_smc.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/bcm_kona_smc.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/bcm_kona_smc_asm.S 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/mach-bcm/board_bcm21664.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/board_bcm281xx.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/kona.c 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/mach-bcm/kona.h 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
arch/arm/mach-bcm/kona_l2_cache.c 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-bcm/kona_l2_cache.h 0 → 100644
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-berlin/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-berlin/berlin.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-cns3xxx/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-cns3xxx/core.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-davinci/da850.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-davinci/dm355.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-davinci/dm365.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-davinci/dm644x.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-davinci/dm646x.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-dove/irq.c
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-ep93xx/crunch-bits.S
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-exynos/Kconfig
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-exynos/Makefile
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-exynos/common.h
浏览文件 @ 50e59058
此差异已折叠。
arch/arm/mach-exynos/cpuidle.c 已删除 100644 → 0
浏览文件 @ f7a27ff1
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或