Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 169
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 593d0a3e 编写于 作者: K Konrad Rzeszutek Wilk
浏览文件
操作

Merge commit '4cb38750' into stable/for-linus-3.6 

* commit '4cb38750': (6849 commits)
  bcma: fix invalid PMU chip control masks
  [libata] pata_cmd64x: whitespace cleanup
  libata-acpi: fix up for acpi_pm_device_sleep_state API
  sata_dwc_460ex: device tree may specify dma_channel
  ahci, trivial: fixed coding style issues related to braces
  ahci_platform: add hibernation callbacks
  libata-eh.c: local functions should not be exposed globally
  libata-transport.c: local functions should not be exposed globally
  sata_dwc_460ex: support hardreset
  ata: use module_pci_driver
  drivers/ata/pata_pcmcia.c: adjust suspicious bit operation
  pata_imx: Convert to clk_prepare_enable/clk_disable_unprepare
  ahci: Enable SB600 64bit DMA on MSI K9AGM2 (MS-7327) v2
  [libata] Prevent interface errors with Seagate FreeAgent GoFlex
  drivers/acpi/glue: revert accidental license-related 6b66d958 bits
  libata-acpi: add missing inlines in libata.h
  i2c-omap: Add support for I2C_M_STOP message flag
  i2c: Fall back to emulated SMBus if the operation isn't supported natively
  i2c: Add SCCB support
  i2c-tiny-usb: Add support for the Robofuzz OSIF USB/I2C converter
  ...
上级 50e90041 4cb38750
展开全部 隐藏空白更改
内联 并排
Showing with 25529 addition and 11686 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.mailmap
浏览文件 @ 593d0a3e
......@@ -111,6 +111,7 @@ Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
Uwe Kleine-König <ukl@pengutronix.de>
Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Viresh Kumar <viresh.linux@gmail.com> <viresh.kumar@st.com>
Takashi YOSHII <takashi.yoshii.zj@renesas.com>
Yusuke Goda <goda.yusuke@renesas.com>
Gustavo Padovan <gustavo@las.ic.unicamp.br>
......
Documentation/ABI/stable/sysfs-driver-w1_ds28e04 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/bus/w1/devices/.../pio
Date: May 2012
Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
Description: read/write the contents of the two PIO's of the DS28E04-100
see Documentation/w1/slaves/w1_ds28e04 for detailed information
Users: any user space application which wants to communicate with DS28E04-100
What: /sys/bus/w1/devices/.../eeprom
Date: May 2012
Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
Description: read/write the contents of the EEPROM memory of the DS28E04-100
see Documentation/w1/slaves/w1_ds28e04 for detailed information
Users: any user space application which wants to communicate with DS28E04-100
Documentation/ABI/stable/vdso
浏览文件 @ 593d0a3e
......@@ -24,4 +24,4 @@ though.
(As of this writing, this ABI documentation as been confirmed for x86_64.
The maintainers of the other vDSO-using architectures should confirm
that it is correct for their architecture.)
\ No newline at end of file
that it is correct for their architecture.)
Documentation/ABI/testing/dev-kmsg
浏览文件 @ 593d0a3e
......@@ -58,16 +58,18 @@ Description: The /dev/kmsg character device node provides userspace access
The output format consists of a prefix carrying the syslog
prefix including priority and facility, the 64 bit message
sequence number and the monotonic timestamp in microseconds.
The values are separated by a ','. Future extensions might
add more comma separated values before the terminating ';'.
Unknown values should be gracefully ignored.
sequence number and the monotonic timestamp in microseconds,
and a flag field. All fields are separated by a ','.
Future extensions might add more comma separated values before
the terminating ';'. Unknown fields and values should be
gracefully ignored.
The human readable text string starts directly after the ';'
and is terminated by a '\n'. Untrusted values derived from
hardware or other facilities are printed, therefore
all non-printable characters in the log message are escaped
by "\x00" C-style hex encoding.
all non-printable characters and '\' itself in the log message
are escaped by "\x00" C-style hex encoding.
A line starting with ' ', is a continuation line, adding
key/value pairs to the log message, which provide the machine
......@@ -75,11 +77,11 @@ Description: The /dev/kmsg character device node provides userspace access
userspace.
Example:
7,160,424069;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
SUBSYSTEM=acpi
DEVICE=+acpi:PNP0A03:00
6,339,5140900;NET: Registered protocol family 10
30,340,5690716;udevd[80]: starting version 181
6,339,5140900,-;NET: Registered protocol family 10
30,340,5690716,-;udevd[80]: starting version 181
The DEVICE= key uniquely identifies devices the following way:
b12:8 - block dev_t
......@@ -87,4 +89,13 @@ Description: The /dev/kmsg character device node provides userspace access
n8 - netdev ifindex
+sound:card0 - subsystem:devname
The flags field carries '-' by default. A 'c' indicates a
fragment of a line. All following fragments are flagged with
'+'. Note, that these hints about continuation lines are not
neccessarily correct, and the stream could be interleaved with
unrelated messages, but merging the lines in the output
usually produces better human readable results. A similar
logic is used internally when messages are printed to the
console, /proc/kmsg or the syslog() syscall.
Users: dmesg(1), userspace kernel log consumers
Documentation/ABI/testing/sysfs-block-rssd
浏览文件 @ 593d0a3e
What: /sys/block/rssd*/registers
Date: March 2012
KernelVersion: 3.3
Contact: Asai Thambi S P <asamymuthupa@micron.com>
Description: This is a read-only file. Dumps below driver information and
hardware registers.
- S ACTive
- Command Issue
- Completed
- PORT IRQ STAT
- HOST IRQ STAT
- Allocated
- Commands in Q
What: /sys/block/rssd*/status
Date: April 2012
KernelVersion: 3.4
Contact: Asai Thambi S P <asamymuthupa@micron.com>
Description: This is a read-only file. Indicates the status of the device.
What: /sys/block/rssd*/flags
Date: May 2012
KernelVersion: 3.5
Contact: Asai Thambi S P <asamymuthupa@micron.com>
Description: This is a read-only file. Dumps the flags in port and driver
data structure
Documentation/ABI/testing/sysfs-block-zram
浏览文件 @ 593d0a3e
......@@ -96,4 +96,4 @@ Description:
overhead, allocated for this disk. So, allocator space
efficiency can be calculated using compr_data_size and this
statistic.
Unit: bytes
\ No newline at end of file
Unit: bytes
Documentation/ABI/testing/sysfs-bus-iio
浏览文件 @ 593d0a3e
......@@ -40,9 +40,9 @@ Contact: linux-iio@vger.kernel.org
Description:
Some devices have internal clocks. This parameter sets the
resulting sampling frequency. In many devices this
parameter has an effect on input filters etc rather than
parameter has an effect on input filters etc. rather than
simply controlling when the input is sampled. As this
effects datardy triggers, hardware buffers and the sysfs
effects data ready triggers, hardware buffers and the sysfs
direct access interfaces, it may be found in any of the
relevant directories. If it effects all of the above
then it is to be found in the base device directory.
......@@ -74,7 +74,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Raw (unscaled no bias removal etc) voltage measurement from
Raw (unscaled no bias removal etc.) voltage measurement from
channel Y. In special cases where the channel does not
correspond to externally available input one of the named
versions may be used. The number must always be specified and
......@@ -118,11 +118,11 @@ What: /sys/bus/iio/devices/iio:deviceX/in_temp_z_raw
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Raw (unscaled no bias removal etc) temperature measurement.
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
are milli degrees Celsuis.
are milli degrees Celsius.
What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
KernelVersion: 2.6.38
......@@ -148,10 +148,9 @@ KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Angular velocity about axis x, y or z (may be arbitrarily
assigned) Data converted by application of offset then scale to
radians per second. Has all the equivalent parameters as
per voltageY. Units after application of scale and offset are
radians per second.
assigned). Has all the equivalent parameters as per voltageY.
Units after application of scale and offset are radians per
second.
What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
......@@ -161,7 +160,7 @@ Contact: linux-iio@vger.kernel.org
Description:
Inclination raw reading about axis x, y or z (may be
arbitrarily assigned). Data converted by application of offset
and scale to Degrees.
and scale to degrees.
What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
......@@ -203,7 +202,7 @@ Contact: linux-iio@vger.kernel.org
Description:
If known for a device, offset to be added to <type>[Y]_raw prior
to scaling by <type>[Y]_scale in order to obtain value in the
<type> units as specified in <type>[y]_raw documentation.
<type> units as specified in <type>[Y]_raw documentation.
Not present if the offset is always 0 or unknown. If Y or
axis <x|y|z> is not present, then the offset applies to all
in channels of <type>.
......@@ -219,6 +218,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
......@@ -248,7 +248,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Hardware applied calibration offset. (assumed to fix production
Hardware applied calibration offset (assumed to fix production
inaccuracies).
What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
......@@ -265,7 +265,7 @@ what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
Hardware applied calibration scale factor. (assumed to fix
Hardware applied calibration scale factor (assumed to fix
production inaccuracies). If shared across all channels,
<type>_calibscale is used.
......@@ -273,11 +273,12 @@ What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
What: /sys/.../iio:deviceX/in_voltageX_scale_available
What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
What: /sys/.../iio:deviceX/out_voltageX_scale_available
What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
What: /sys/.../iio:deviceX/in_capacitance_scale_available
KernelVersion: 2.635
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
If a discrete set of scale values are available, they
If a discrete set of scale values is available, they
are listed in this attribute.
What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
......@@ -298,14 +299,19 @@ Description:
gives the 3dB frequency of the filter in Hz.
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Raw (unscaled, no bias etc.) output voltage for
channel Y. The number must always be specified and
unique if the output corresponds to a single channel.
While DAC like devices typically use out_voltage,
a continuous frequency generating device, such as
a DDS or PLL should use out_altvoltage.
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
......@@ -316,20 +322,26 @@ Description:
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode
KernelVersion: 2.6.38
Contact: linux-iio@vger.kernel.org
Description:
Specifies the output powerdown mode.
DAC output stage is disconnected from the amplifier and
1kohm_to_gnd: connected to ground via an 1kOhm resistor
100kohm_to_gnd: connected to ground via an 100kOhm resistor
three_state: left floating
1kohm_to_gnd: connected to ground via an 1kOhm resistor,
6kohm_to_gnd: connected to ground via a 6kOhm resistor,
20kohm_to_gnd: connected to ground via a 20kOhm resistor,
100kohm_to_gnd: connected to ground via an 100kOhm resistor,
three_state: left floating.
For a list of available output power down options read
outX_powerdown_mode_available. If Y is not present the
mode is shared across all outputs.
What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
What: /sys/.../iio:deviceX/out_altvotlageY_powerdown_mode_available
What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available
KernelVersion: 2.6.38
Contact: linux-iio@vger.kernel.org
Description:
......@@ -338,13 +350,34 @@ Description:
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown
KernelVersion: 2.6.38
Contact: linux-iio@vger.kernel.org
Description:
Writing 1 causes output Y to enter the power down mode specified
by the corresponding outY_powerdown_mode. Clearing returns to
normal operation. Y may be suppressed if all outputs are
controlled together.
by the corresponding outY_powerdown_mode. DAC output stage is
disconnected from the amplifier. Clearing returns to normal
operation. Y may be suppressed if all outputs are controlled
together.
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Output frequency for channel Y in Hz. The number must always be
specified and unique if the output corresponds to a single
channel.
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Phase in radians of one frequency/clock output Y
(out_altvoltageY) relative to another frequency/clock output
(out_altvoltageZ) of the device X. The number must always be
specified and unique if the output corresponds to a single
channel.
What: /sys/bus/iio/devices/iio:deviceX/events
KernelVersion: 2.6.35
......@@ -390,12 +423,12 @@ Description:
different values, but the device can only enable both thresholds
or neither.
Note the driver will assume the last p events requested are
to be enabled where p is however many it supports (which may
vary depending on the exact set requested. So if you want to be
to be enabled where p is how many it supports (which may vary
depending on the exact set requested. So if you want to be
sure you have set what you think you have, check the contents of
these attributes after everything is configured. Drivers may
have to buffer any parameters so that they are consistent when
a given event type is enabled a future point (and not those for
a given event type is enabled at a future point (and not those for
whatever event was previously enabled).
What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
......@@ -671,7 +704,7 @@ What: /sys/.../buffer/scan_elements/in_anglvel_type
What: /sys/.../buffer/scan_elements/in_magn_type
What: /sys/.../buffer/scan_elements/in_incli_type
What: /sys/.../buffer/scan_elements/in_voltageY_type
What: /sys/.../buffer/scan_elements/in_voltage-in_type
What: /sys/.../buffer/scan_elements/in_voltage_type
What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
What: /sys/.../buffer/scan_elements/in_timestamp_type
KernelVersion: 2.6.37
......@@ -692,7 +725,7 @@ Description:
the buffer output value appropriately. The storagebits value
also specifies the data alignment. So s48/64>>2 will be a
signed 48 bit integer stored in a 64 bit location aligned to
a a64 bit boundary. To obtain the clean value, shift right 2
a 64 bit boundary. To obtain the clean value, shift right 2
and apply a mask to zero the top 16 bits of the result.
For other storage combinations this attribute will be extended
appropriately.
......
Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present
What: /sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present
What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present
What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present
What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present
What: /sys/bus/iio/devices/iio:deviceX/vcxo_clk_present
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Reading returns either '1' or '0'.
'1' means that the clock in question is present.
'0' means that the clock is missing.
What: /sys/bus/iio/devices/iio:deviceX/pllY_locked
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Reading returns either '1' or '0'. '1' means that the
pllY is locked.
What: /sys/bus/iio/devices/iio:deviceX/store_eeprom
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Writing '1' stores the current device configuration into
on-chip EEPROM. After power-up or chip reset the device will
automatically load the saved configuration.
What: /sys/bus/iio/devices/iio:deviceX/sync_dividers
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Writing '1' triggers the clock distribution synchronization
functionality. All dividers are reset and the channels start
with their predefined phase offsets (out_altvoltageY_phase).
Writing this file has the effect as driving the external
/SYNC pin low.
Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Stores channel Y frequency resolution/channel spacing in Hz.
The value given directly influences the MODULUS used by
the fractional-N PLL. It is assumed that the algorithm
that is used to compute the various dividers, is able to
generate proper values for multiples of channel spacing.
What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency
KernelVersion: 3.4.0
Contact: linux-iio@vger.kernel.org
Description:
Sets channel Y REFin frequency in Hz. In some clock chained
applications, the reference frequency used by the PLL may
change during runtime. This attribute allows the user to
adjust the reference frequency accordingly.
The value written has no effect until out_altvoltageY_frequency
is updated. Consider to use out_altvoltageY_powerdown to power
down the PLL and it's RFOut buffers during REFin changes.
Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/.../events/in_illuminance0_thresh_either_en
Date: April 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Event generated when channel passes one of the four thresholds
in each direction (rising|falling) and a zone change occurs.
The corresponding light zone can be read from
in_illuminance0_zone.
What: /sys/.../events/in_illuminance0_threshY_hysteresis
Date: May 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Get the hysteresis for thresholds Y, that is,
threshY_hysteresis = threshY_raising - threshY_falling
What: /sys/.../events/illuminance_threshY_falling_value
What: /sys/.../events/illuminance_threshY_raising_value
Date: April 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Specifies the value of threshold that the device is comparing
against for the events enabled by
in_illuminance0_thresh_either_en (0..255), where Y in 0..3.
Note that threshY_falling must be less than or equal to
threshY_raising.
These thresholds correspond to the eight zone-boundary
registers (boundaryY_{low,high}) and define the five light
zones.
What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone
Date: April 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Get the current light zone (0..4) as defined by the
in_illuminance0_threshY_{falling,rising} thresholds.
What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw
Date: May 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Get output current for channel Y (0..255), that is,
out_currentY_currentZ_raw, where Z is the current zone.
What: /sys/bus/iio/devices/iio:deviceX/out_currentY_currentZ_raw
Date: May 2012
KernelVersion: 3.5
Contact: Johan Hovold <jhovold@gmail.com>
Description:
Set the output current for channel out_currentY when in zone
Z (0..255), where Y in 0..2 and Z in 0..4.
These values correspond to the ALS-mapper target registers for
ALS-mapper Y + 1.
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 593d0a3e
......@@ -208,3 +208,15 @@ Description:
such as ACPI. This file will read either "removable" or
"fixed" if the information is available, and "unknown"
otherwise.
What: /sys/bus/usb/devices/.../ltm_capable
Date: July 2012
Contact: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Description:
USB 3.0 devices may optionally support Latency Tolerance
Messaging (LTM). They indicate their support by setting a bit
in the bmAttributes field of their SuperSpeed BOS descriptors.
If that bit is set for the device, ltm_capable will read "yes".
If the device doesn't support LTM, the file will read "no".
The file will be present for all speeds of USB devices, and will
always read "no" for USB 1.1 and USB 2.0 devices.
Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
浏览文件 @ 593d0a3e
......@@ -40,4 +40,4 @@ Description: Controls the decimal places on the device.
the value of 10 ** n. Assume this field has
the value k and has 1 or more decimal places set,
to set the mth place (where m is not already set),
change this fields value to k + 10 ** m.
\ No newline at end of file
change this fields value to k + 10 ** m.
Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
浏览文件 @ 593d0a3e
......@@ -53,4 +53,4 @@ Description:
Documentation/ABI/stable/sysfs-class-backlight.
It can be enabled by writing the value stored in
/sys/class/backlight/<backlight>/max_brightness to
/sys/class/backlight/<backlight>/brightness.
\ No newline at end of file
/sys/class/backlight/<backlight>/brightness.
Documentation/ABI/testing/sysfs-class-mtd
浏览文件 @ 593d0a3e
......@@ -142,13 +142,14 @@ KernelVersion: 3.4
Contact: linux-mtd@lists.infradead.org
Description:
This allows the user to examine and adjust the criteria by which
mtd returns -EUCLEAN from mtd_read(). If the maximum number of
bit errors that were corrected on any single region comprising
an ecc step (as reported by the driver) equals or exceeds this
value, -EUCLEAN is returned. Otherwise, absent an error, 0 is
returned. Higher layers (e.g., UBI) use this return code as an
indication that an erase block may be degrading and should be
scrutinized as a candidate for being marked as bad.
mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the
maximum number of bit errors that were corrected on any single
region comprising an ecc step (as reported by the driver) equals
or exceeds this value, -EUCLEAN is returned. Otherwise, absent
an error, 0 is returned. Higher layers (e.g., UBI) use this
return code as an indication that an erase block may be
degrading and should be scrutinized as a candidate for being
marked as bad.
The initial value may be specified by the flash device driver.
If not, then the default value is ecc_strength.
......@@ -167,7 +168,7 @@ Description:
block degradation, but high enough to avoid the consequences of
a persistent return value of -EUCLEAN on devices where sticky
bitflips occur. Note that if bitflip_threshold exceeds
ecc_strength, -EUCLEAN is never returned by mtd_read().
ecc_strength, -EUCLEAN is never returned by the read operations.
Conversely, if bitflip_threshold is zero, -EUCLEAN is always
returned, absent a hard error.
......
Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_to_select
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be
is being controlled by press_speed.
Values are 0 or 1.
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.
Values are 0 or 1.
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: For details regarding this setting please refer to http://www.pc.ibm.com/ww/healthycomputing/trkpntb.html
Values are 0 or 1.
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/select_right
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate
a left or right mouse button click.
Values are 0 or 1.
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: This file contains the trackpoint sensitivity.
Values are decimal integers from 1 (lowest sensitivity) to 255 (highest sensitivity).
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_speed
Date: July 2011
Contact: linux-input@vger.kernel.org
Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.
Values are decimal integers from 1 (slowest) to 255 (fastest).
Documentation/ABI/testing/sysfs-driver-hid-roccat-savu 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: The mouse can store 5 profiles which can be switched by the
press of a button. A profile is split into general settings and
button settings. buttons holds informations about button layout.
When written, this file lets one write the respective profile
buttons to the mouse. The data has to be 47 bytes long.
The mouse will reject invalid data.
Which profile to write is determined by the profile number
contained in the data.
Before reading this file, control has to be written to select
which profile to read.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: When written, this file lets one select which data from which
profile will be read next. The data has to be 3 bytes long.
This file is writeonly.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/general
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: The mouse can store 5 profiles which can be switched by the
press of a button. A profile is split into general settings and
button settings. profile holds informations like resolution, sensitivity
and light effects.
When written, this file lets one write the respective profile
settings back to the mouse. The data has to be 43 bytes long.
The mouse will reject invalid data.
Which profile to write is determined by the profile number
contained in the data.
This file is writeonly.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: When read, this file returns general data like firmware version.
The data is 8 bytes long.
This file is readonly.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: When written, this file lets one store macros with max 500
keystrokes for a specific button for a specific profile.
Button and profile numbers are included in written data.
The data has to be 2083 bytes long.
Before reading this file, control has to be written to select
which profile and key to read.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
Date: Mai 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: The mouse can store 5 profiles which can be switched by the
press of a button. profile holds number of actual profile.
This value is persistent, so its value determines the profile
that's active when the mouse is powered on next time.
When written, the mouse activates the set profile immediately.
The data has to be 3 bytes long.
The mouse will reject invalid data.
Users: http://roccat.sourceforge.net
What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/sensor
Date: July 2012
Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
Description: The mouse has a Avago ADNS-3090 sensor.
This file allows reading and writing of the mouse sensors registers.
The data has to be 4 bytes long.
Users: http://roccat.sourceforge.net
Documentation/ABI/testing/sysfs-kernel-iommu_groups 0 → 100644
浏览文件 @ 593d0a3e
What: /sys/kernel/iommu_groups/
Date: May 2012
KernelVersion: v3.5
Contact: Alex Williamson <alex.williamson@redhat.com>
Description: /sys/kernel/iommu_groups/ contains a number of sub-
directories, each representing an IOMMU group. The
name of the sub-directory matches the iommu_group_id()
for the group, which is an integer value. Within each
subdirectory is another directory named "devices" with
links to the sysfs devices contained in this group.
The group directory also optionally contains a "name"
file if the IOMMU driver has chosen to register a more
common name for the group.
Users:
Documentation/ABI/testing/sysfs-power
浏览文件 @ 593d0a3e
......@@ -231,3 +231,16 @@ Description:
Reads from this file return a string consisting of the names of
wakeup sources created with the help of /sys/power/wake_lock
that are inactive at the moment, separated with spaces.
What: /sys/power/pm_print_times
Date: May 2012
Contact: Sameer Nanda <snanda@chromium.org>
Description:
The /sys/power/pm_print_times file allows user space to
control whether the time taken by devices to suspend and
resume is printed. These prints are useful for hunting down
devices that take too long to suspend or resume.
Writing a "1" enables this printing while writing a "0"
disables it. The default value is "0". Reading from this file
will display the current value.
Documentation/DocBook/80211.tmpl
浏览文件 @ 593d0a3e
......@@ -404,7 +404,6 @@
!Finclude/net/mac80211.h ieee80211_get_tkip_p1k
!Finclude/net/mac80211.h ieee80211_get_tkip_p1k_iv
!Finclude/net/mac80211.h ieee80211_get_tkip_p2k
!Finclude/net/mac80211.h ieee80211_key_removed
</chapter>
<chapter id="powersave">
......
Documentation/DocBook/media/v4l/controls.xml
浏览文件 @ 593d0a3e
......@@ -3988,7 +3988,7 @@ interface and may change in the future.</para>
from RGB to Y'CbCr color space.
</entry>
</row>
<row id = "v4l2-jpeg-chroma-subsampling">
<row>
<entrytbl spanname="descr" cols="2">
<tbody valign="top">
<row>
......
Documentation/DocBook/media/v4l/pixfmt.xml
浏览文件 @ 593d0a3e
......@@ -986,13 +986,13 @@ http://www.thedirks.org/winnov/</ulink></para></entry>
<row id="V4L2-PIX-FMT-Y4">
<entry><constant>V4L2_PIX_FMT_Y4</constant></entry>
<entry>'Y04 '</entry>
<entry>Old 4-bit greyscale format. Only the least significant 4 bits of each byte are used,
<entry>Old 4-bit greyscale format. Only the most significant 4 bits of each byte are used,
the other bits are set to 0.</entry>
</row>
<row id="V4L2-PIX-FMT-Y6">
<entry><constant>V4L2_PIX_FMT_Y6</constant></entry>
<entry>'Y06 '</entry>
<entry>Old 6-bit greyscale format. Only the least significant 6 bits of each byte are used,
<entry>Old 6-bit greyscale format. Only the most significant 6 bits of each byte are used,
the other bits are set to 0.</entry>
</row>
</tbody>
......
Documentation/DocBook/media/v4l/v4l2.xml
浏览文件 @ 593d0a3e
......@@ -560,6 +560,7 @@ and discussions on the V4L mailing list.</revremark>
&sub-g-tuner;
&sub-log-status;
&sub-overlay;
&sub-prepare-buf;
&sub-qbuf;
&sub-querybuf;
&sub-querycap;
......@@ -567,7 +568,6 @@ and discussions on the V4L mailing list.</revremark>
&sub-query-dv-preset;
&sub-query-dv-timings;
&sub-querystd;
&sub-prepare-buf;
&sub-reqbufs;
&sub-s-hw-freq-seek;
&sub-streamon;
......
Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
浏览文件 @ 593d0a3e
......@@ -108,10 +108,9 @@ information.</para>
/></entry>
</row>
<row>
<entry>__u32</entry>
<entry>struct&nbsp;v4l2_format</entry>
<entry><structfield>format</structfield></entry>
<entry>Filled in by the application, preserved by the driver.
See <xref linkend="v4l2-format" />.</entry>
<entry>Filled in by the application, preserved by the driver.</entry>
</row>
<row>
<entry>__u32</entry>
......
Documentation/DocBook/media/v4l/vidioc-dqevent.xml
浏览文件 @ 593d0a3e
......@@ -89,7 +89,7 @@
<row>
<entry></entry>
<entry>&v4l2-event-frame-sync;</entry>
<entry><structfield>frame</structfield></entry>
<entry><structfield>frame_sync</structfield></entry>
<entry>Event data for event V4L2_EVENT_FRAME_SYNC.</entry>
</row>
<row>
......
Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml
浏览文件 @ 593d0a3e
......@@ -284,13 +284,6 @@ These controls are described in <xref
processing controls. These controls are described in <xref
linkend="image-process-controls" />.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_CLASS_JPEG</constant></entry>
<entry>0x9d0000</entry>
<entry>The class containing JPEG compression controls.
These controls are described in <xref
linkend="jpeg-controls" />.</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/ManagementStyle
浏览文件 @ 593d0a3e
......@@ -178,7 +178,7 @@ sadly that you are one too, and that while we can all bask in the secure
knowledge that we're better than the average person (let's face it,
nobody ever believes that they're average or below-average), we should
also admit that we're not the sharpest knife around, and there will be
other people that are less of an idiot that you are.
other people that are less of an idiot than you are.
Some people react badly to smart people. Others take advantage of them.
......
Documentation/RCU/checklist.txt
浏览文件 @ 593d0a3e
......@@ -162,9 +162,9 @@ over a rather long period of time, but improvements are always welcome!
when publicizing a pointer to a structure that can
be traversed by an RCU read-side critical section.
5. If call_rcu(), or a related primitive such as call_rcu_bh() or
call_rcu_sched(), is used, the callback function must be
written to be called from softirq context. In particular,
5. If call_rcu(), or a related primitive such as call_rcu_bh(),
call_rcu_sched(), or call_srcu() is used, the callback function
must be written to be called from softirq context. In particular,
it cannot block.
6. Since synchronize_rcu() can block, it cannot be called from
......@@ -202,11 +202,12 @@ over a rather long period of time, but improvements are always welcome!
updater uses call_rcu_sched() or synchronize_sched(), then
the corresponding readers must disable preemption, possibly
by calling rcu_read_lock_sched() and rcu_read_unlock_sched().
If the updater uses synchronize_srcu(), the the corresponding
readers must use srcu_read_lock() and srcu_read_unlock(),
and with the same srcu_struct. The rules for the expedited
primitives are the same as for their non-expedited counterparts.
Mixing things up will result in confusion and broken kernels.
If the updater uses synchronize_srcu() or call_srcu(),
the the corresponding readers must use srcu_read_lock() and
srcu_read_unlock(), and with the same srcu_struct. The rules for
the expedited primitives are the same as for their non-expedited
counterparts. Mixing things up will result in confusion and
broken kernels.
One exception to this rule: rcu_read_lock() and rcu_read_unlock()
may be substituted for rcu_read_lock_bh() and rcu_read_unlock_bh()
......@@ -333,14 +334,14 @@ over a rather long period of time, but improvements are always welcome!
victim CPU from ever going offline.)
14. SRCU (srcu_read_lock(), srcu_read_unlock(), srcu_dereference(),
synchronize_srcu(), and synchronize_srcu_expedited()) may only
be invoked from process context. Unlike other forms of RCU, it
-is- permissible to block in an SRCU read-side critical section
(demarked by srcu_read_lock() and srcu_read_unlock()), hence the
"SRCU": "sleepable RCU". Please note that if you don't need
to sleep in read-side critical sections, you should be using
RCU rather than SRCU, because RCU is almost always faster and
easier to use than is SRCU.
synchronize_srcu(), synchronize_srcu_expedited(), and call_srcu())
may only be invoked from process context. Unlike other forms of
RCU, it -is- permissible to block in an SRCU read-side critical
section (demarked by srcu_read_lock() and srcu_read_unlock()),
hence the "SRCU": "sleepable RCU". Please note that if you
don't need to sleep in read-side critical sections, you should be
using RCU rather than SRCU, because RCU is almost always faster
and easier to use than is SRCU.
If you need to enter your read-side critical section in a
hardirq or exception handler, and then exit that same read-side
......@@ -353,8 +354,8 @@ over a rather long period of time, but improvements are always welcome!
cleanup_srcu_struct(). These are passed a "struct srcu_struct"
that defines the scope of a given SRCU domain. Once initialized,
the srcu_struct is passed to srcu_read_lock(), srcu_read_unlock()
synchronize_srcu(), and synchronize_srcu_expedited(). A given
synchronize_srcu() waits only for SRCU read-side critical
synchronize_srcu(), synchronize_srcu_expedited(), and call_srcu().
A given synchronize_srcu() waits only for SRCU read-side critical
sections governed by srcu_read_lock() and srcu_read_unlock()
calls that have been passed the same srcu_struct. This property
is what makes sleeping read-side critical sections tolerable --
......@@ -374,7 +375,7 @@ over a rather long period of time, but improvements are always welcome!
requiring SRCU's read-side deadlock immunity or low read-side
realtime latency.
Note that, rcu_assign_pointer() relates to SRCU just as they do
Note that, rcu_assign_pointer() relates to SRCU just as it does
to other forms of RCU.
15. The whole point of call_rcu(), synchronize_rcu(), and friends
......
Documentation/RCU/rcubarrier.txt
浏览文件 @ 593d0a3e
......@@ -79,8 +79,6 @@ complete. Pseudo-code using rcu_barrier() is as follows:
2. Execute rcu_barrier().
3. Allow the module to be unloaded.
Quick Quiz #1: Why is there no srcu_barrier()?
The rcutorture module makes use of rcu_barrier in its exit function
as follows:
......@@ -162,7 +160,7 @@ for any pre-existing callbacks to complete.
Then lines 55-62 print status and do operation-specific cleanup, and
then return, permitting the module-unload operation to be completed.
Quick Quiz #2: Is there any other situation where rcu_barrier() might
Quick Quiz #1: Is there any other situation where rcu_barrier() might
be required?
Your module might have additional complications. For example, if your
......@@ -242,7 +240,7 @@ reaches zero, as follows:
4 complete(&rcu_barrier_completion);
5 }
Quick Quiz #3: What happens if CPU 0's rcu_barrier_func() executes
Quick Quiz #2: What happens if CPU 0's rcu_barrier_func() executes
immediately (thus incrementing rcu_barrier_cpu_count to the
value one), but the other CPU's rcu_barrier_func() invocations
are delayed for a full grace period? Couldn't this result in
......@@ -259,12 +257,7 @@ so that your module may be safely unloaded.
Answers to Quick Quizzes
Quick Quiz #1: Why is there no srcu_barrier()?
Answer: Since there is no call_srcu(), there can be no outstanding SRCU
callbacks. Therefore, there is no need to wait for them.
Quick Quiz #2: Is there any other situation where rcu_barrier() might
Quick Quiz #1: Is there any other situation where rcu_barrier() might
be required?
Answer: Interestingly enough, rcu_barrier() was not originally
......@@ -278,7 +271,7 @@ Answer: Interestingly enough, rcu_barrier() was not originally
implementing rcutorture, and found that rcu_barrier() solves
this problem as well.
Quick Quiz #3: What happens if CPU 0's rcu_barrier_func() executes
Quick Quiz #2: What happens if CPU 0's rcu_barrier_func() executes
immediately (thus incrementing rcu_barrier_cpu_count to the
value one), but the other CPU's rcu_barrier_func() invocations
are delayed for a full grace period? Couldn't this result in
......
Documentation/RCU/torture.txt
浏览文件 @ 593d0a3e
......@@ -174,11 +174,20 @@ torture_type The type of RCU to test, with string values as follows:
and synchronize_rcu_bh_expedited().
"srcu": srcu_read_lock(), srcu_read_unlock() and
call_srcu().
"srcu_sync": srcu_read_lock(), srcu_read_unlock() and
synchronize_srcu().
"srcu_expedited": srcu_read_lock(), srcu_read_unlock() and
synchronize_srcu_expedited().
"srcu_raw": srcu_read_lock_raw(), srcu_read_unlock_raw(),
and call_srcu().
"srcu_raw_sync": srcu_read_lock_raw(), srcu_read_unlock_raw(),
and synchronize_srcu().
"sched": preempt_disable(), preempt_enable(), and
call_rcu_sched().
......
Documentation/RCU/whatisRCU.txt
浏览文件 @ 593d0a3e
......@@ -833,9 +833,9 @@ sched: Critical sections Grace period Barrier
SRCU: Critical sections Grace period Barrier
srcu_read_lock synchronize_srcu N/A
srcu_read_unlock synchronize_srcu_expedited
srcu_read_lock_raw
srcu_read_lock synchronize_srcu srcu_barrier
srcu_read_unlock call_srcu
srcu_read_lock_raw synchronize_srcu_expedited
srcu_read_unlock_raw
srcu_dereference
......
Documentation/arm/SPEAr/overview.txt
浏览文件 @ 593d0a3e
......@@ -60,4 +60,4 @@ Introduction
Document Author
---------------
Viresh Kumar <viresh.kumar@st.com>, (c) 2010-2012 ST Microelectronics
Viresh Kumar <viresh.linux@gmail.com>, (c) 2010-2012 ST Microelectronics
Documentation/arm/Samsung-S3C24XX/H1940.txt
浏览文件 @ 593d0a3e
......@@ -37,4 +37,4 @@ Maintainers
Thanks to the many others who have also provided support.
(c) 2005 Ben Dooks
\ No newline at end of file
(c) 2005 Ben Dooks
Documentation/arm/Samsung-S3C24XX/SMDK2440.txt
浏览文件 @ 593d0a3e
......@@ -53,4 +53,4 @@ Maintainers
and to Simtec Electronics for allowing me time to work on this.
(c) 2004 Ben Dooks
\ No newline at end of file
(c) 2004 Ben Dooks
Documentation/cgroups/cgroups.txt
浏览文件 @ 593d0a3e
......@@ -370,15 +370,12 @@ To mount a cgroup hierarchy with just the cpuset and memory
subsystems, type:
# mount -t cgroup -o cpuset,memory hier1 /sys/fs/cgroup/rg1
To change the set of subsystems bound to a mounted hierarchy, just
remount with different options:
# mount -o remount,cpuset,blkio hier1 /sys/fs/cgroup/rg1
Now memory is removed from the hierarchy and blkio is added.
Note this will add blkio to the hierarchy but won't remove memory or
cpuset, because the new options are appended to the old ones:
# mount -o remount,blkio /sys/fs/cgroup/rg1
While remounting cgroups is currently supported, it is not recommend
to use it. Remounting allows changing bound subsystems and
release_agent. Rebinding is hardly useful as it only works when the
hierarchy is empty and release_agent itself should be replaced with
conventional fsnotify. The support for remounting will be removed in
the future.
To Specify a hierarchy's release_agent:
# mount -t cgroup -o cpuset,release_agent="/sbin/cpuset_release_agent" \
......@@ -637,16 +634,6 @@ void exit(struct task_struct *task)
Called during task exit.
int populate(struct cgroup *cgrp)
(cgroup_mutex held by caller)
Called after creation of a cgroup to allow a subsystem to populate
the cgroup directory with file entries. The subsystem should make
calls to cgroup_add_file() with objects of type cftype (see
include/linux/cgroup.h for details). Note that although this
method can return an error code, the error code is currently not
always handled well.
void post_clone(struct cgroup *cgrp)
(cgroup_mutex held by caller)
......@@ -656,7 +643,7 @@ example in cpusets, no task may attach before 'cpus' and 'mems' are set
up.
void bind(struct cgroup *root)
(cgroup_mutex and ss->hierarchy_mutex held by caller)
(cgroup_mutex held by caller)
Called when a cgroup subsystem is rebound to a different hierarchy
and root cgroup. Currently this will only involve movement between
......
Documentation/connector/cn_test.c
浏览文件 @ 593d0a3e
......@@ -69,9 +69,13 @@ static int cn_test_want_notify(void)
return -ENOMEM;
}
nlh = NLMSG_PUT(skb, 0, 0x123, NLMSG_DONE, size - sizeof(*nlh));
nlh = nlmsg_put(skb, 0, 0x123, NLMSG_DONE, size - sizeof(*nlh), 0);
if (!nlh) {
kfree_skb(skb);
return -EMSGSIZE;
}
msg = (struct cn_msg *)NLMSG_DATA(nlh);
msg = nlmsg_data(nlh);
memset(msg, 0, size0);
......@@ -117,11 +121,6 @@ static int cn_test_want_notify(void)
pr_info("request was sent: group=0x%x\n", ctl->group);
return 0;
nlmsg_failure:
pr_err("failed to send %u.%u\n", msg->seq, msg->ack);
kfree_skb(skb);
return -EINVAL;
}
#endif
......
Documentation/device-mapper/verity.txt
浏览文件 @ 593d0a3e
......@@ -7,39 +7,39 @@ This target is read-only.
Construction Parameters
=======================
<version> <dev> <hash_dev> <hash_start>
<version> <dev> <hash_dev>
<data_block_size> <hash_block_size>
<num_data_blocks> <hash_start_block>
<algorithm> <digest> <salt>
<version>
This is the version number of the on-disk format.
This is the type of the on-disk hash format.
0 is the original format used in the Chromium OS.
The salt is appended when hashing, digests are stored continuously and
the rest of the block is padded with zeros.
The salt is appended when hashing, digests are stored continuously and
the rest of the block is padded with zeros.
1 is the current format that should be used for new devices.
The salt is prepended when hashing and each digest is
padded with zeros to the power of two.
The salt is prepended when hashing and each digest is
padded with zeros to the power of two.
<dev>
This is the device containing the data the integrity of which needs to be
This is the device containing data, the integrity of which needs to be
checked. It may be specified as a path, like /dev/sdaX, or a device number,
<major>:<minor>.
<hash_dev>
This is the device that that supplies the hash tree data. It may be
This is the device that supplies the hash tree data. It may be
specified similarly to the device path and may be the same device. If the
same device is used, the hash_start should be outside of the dm-verity
configured device size.
same device is used, the hash_start should be outside the configured
dm-verity device.
<data_block_size>
The block size on a data device. Each block corresponds to one digest on
the hash device.
The block size on a data device in bytes.
Each block corresponds to one digest on the hash device.
<hash_block_size>
The size of a hash block.
The size of a hash block in bytes.
<num_data_blocks>
The number of data blocks on the data device. Additional blocks are
......@@ -65,7 +65,7 @@ Construction Parameters
Theory of operation
===================
dm-verity is meant to be setup as part of a verified boot path. This
dm-verity is meant to be set up as part of a verified boot path. This
may be anything ranging from a boot using tboot or trustedgrub to just
booting from a known-good device (like a USB drive or CD).
......@@ -73,20 +73,20 @@ When a dm-verity device is configured, it is expected that the caller
has been authenticated in some way (cryptographic signatures, etc).
After instantiation, all hashes will be verified on-demand during
disk access. If they cannot be verified up to the root node of the
tree, the root hash, then the I/O will fail. This should identify
tree, the root hash, then the I/O will fail. This should detect
tampering with any data on the device and the hash data.
Cryptographic hashes are used to assert the integrity of the device on a
per-block basis. This allows for a lightweight hash computation on first read
into the page cache. Block hashes are stored linearly-aligned to the nearest
block the size of a page.
per-block basis. This allows for a lightweight hash computation on first read
into the page cache. Block hashes are stored linearly, aligned to the nearest
block size.
Hash Tree
---------
Each node in the tree is a cryptographic hash. If it is a leaf node, the hash
is of some block data on disk. If it is an intermediary node, then the hash is
of a number of child nodes.
of some data block on disk is calculated. If it is an intermediary node,
the hash of a number of child nodes is calculated.
Each entry in the tree is a collection of neighboring nodes that fit in one
block. The number is determined based on block_size and the size of the
......@@ -110,63 +110,23 @@ alg = sha256, num_blocks = 32768, block_size = 4096
On-disk format
==============
Below is the recommended on-disk format. The verity kernel code does not
read the on-disk header. It only reads the hash blocks which directly
follow the header. It is expected that a user-space tool will verify the
integrity of the verity_header and then call dmsetup with the correct
parameters. Alternatively, the header can be omitted and the dmsetup
parameters can be passed via the kernel command-line in a rooted chain
of trust where the command-line is verified.
The verity kernel code does not read the verity metadata on-disk header.
It only reads the hash blocks which directly follow the header.
It is expected that a user-space tool will verify the integrity of the
verity header.
The on-disk format is especially useful in cases where the hash blocks
are on a separate partition. The magic number allows easy identification
of the partition contents. Alternatively, the hash blocks can be stored
in the same partition as the data to be verified. In such a configuration
the filesystem on the partition would be sized a little smaller than
the full-partition, leaving room for the hash blocks.
struct superblock {
uint8_t signature[8]
"verity\0\0";
uint8_t version;
1 - current format
uint8_t data_block_bits;
log2(data block size)
uint8_t hash_block_bits;
log2(hash block size)
uint8_t pad1[1];
zero padding
uint16_t salt_size;
big-endian salt size
uint8_t pad2[2];
zero padding
uint32_t data_blocks_hi;
big-endian high 32 bits of the 64-bit number of data blocks
uint32_t data_blocks_lo;
big-endian low 32 bits of the 64-bit number of data blocks
uint8_t algorithm[16];
cryptographic algorithm
uint8_t salt[384];
salt (the salt size is specified above)
uint8_t pad3[88];
zero padding to 512-byte boundary
}
Alternatively, the header can be omitted and the dmsetup parameters can
be passed via the kernel command-line in a rooted chain of trust where
the command-line is verified.
Directly following the header (and with sector number padded to the next hash
block boundary) are the hash blocks which are stored a depth at a time
(starting from the root), sorted in order of increasing index.
The full specification of kernel parameters and on-disk metadata format
is available at the cryptsetup project's wiki page
http://code.google.com/p/cryptsetup/wiki/DMVerity
Status
======
V (for Valid) is returned if every check performed so far was valid.
......@@ -174,21 +134,22 @@ If any check failed, C (for Corruption) is returned.
Example
=======
Setup a device:
dmsetup create vroot --table \
"0 2097152 "\
"verity 1 /dev/sda1 /dev/sda2 4096 4096 2097152 1 "\
Set up a device:
# dmsetup create vroot --readonly --table \
"0 2097152 verity 1 /dev/sda1 /dev/sda2 4096 4096 262144 1 sha256 "\
"4392712ba01368efdf14b05c76f9e4df0d53664630b5d48632ed17a137f39076 "\
"1234000000000000000000000000000000000000000000000000000000000000"
A command line tool veritysetup is available to compute or verify
the hash tree or activate the kernel driver. This is available from
the LVM2 upstream repository and may be supplied as a package called
device-mapper-verity-tools:
git://sources.redhat.com/git/lvm2
http://sourceware.org/git/?p=lvm2.git
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/verity?cvsroot=lvm2
veritysetup -a vroot /dev/sda1 /dev/sda2 \
4392712ba01368efdf14b05c76f9e4df0d53664630b5d48632ed17a137f39076
the hash tree or activate the kernel device. This is available from
the cryptsetup upstream repository http://code.google.com/p/cryptsetup/
(as a libcryptsetup extension).
Create hash on the device:
# veritysetup format /dev/sda1 /dev/sda2
...
Root hash: 4392712ba01368efdf14b05c76f9e4df0d53664630b5d48632ed17a137f39076
Activate the device:
# veritysetup create vroot /dev/sda1 /dev/sda2 \
4392712ba01368efdf14b05c76f9e4df0d53664630b5d48632ed17a137f39076
Documentation/devices.txt
浏览文件 @ 593d0a3e
......@@ -2416,6 +2416,8 @@ Your cooperation is appreciated.
1 = /dev/raw/raw1 First raw I/O device
2 = /dev/raw/raw2 Second raw I/O device
...
max minor number of raw device is set by kernel config
MAX_RAW_DEVS or raw module parameter 'max_raw_devs'
163 char
......
Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt 0 → 100644
浏览文件 @ 593d0a3e
Marvell Armada 370 and Armada XP Interrupt Controller
-----------------------------------------------------
Required properties:
- compatible: Should be "marvell,mpic"
- interrupt-controller: Identifies the node as an interrupt controller.
- #interrupt-cells: The number of cells to define the interrupts. Should be 1.
The cell is the IRQ number
- reg: Should contain PMIC registers location and length. First pair
for the main interrupt registers, second pair for the per-CPU
interrupt registers
Example:
mpic: interrupt-controller@d0020000 {
compatible = "marvell,mpic";
#interrupt-cells = <1>;
#address-cells = <1>;
#size-cells = <1>;
interrupt-controller;
reg = <0xd0020000 0x1000>,
<0xd0021000 0x1000>;
};
Documentation/devicetree/bindings/arm/armada-370-xp-timer.txt 0 → 100644
浏览文件 @ 593d0a3e
Marvell Armada 370 and Armada XP Global Timers
----------------------------------------------
Required properties:
- compatible: Should be "marvell,armada-370-xp-timer"
- interrupts: Should contain the list of Global Timer interrupts
- reg: Should contain the base address of the Global Timer registers
Optional properties:
- marvell,timer-25Mhz: Tells whether the Global timer supports the 25
Mhz fixed mode (available on Armada XP and not on Armada 370)
Documentation/devicetree/bindings/arm/armada-370-xp.txt 0 → 100644
浏览文件 @ 593d0a3e
Marvell Armada 370 and Armada XP Platforms Device Tree Bindings
---------------------------------------------------------------
Boards with a SoC of the Marvell Armada 370 and Armada XP families
shall have the following property:
Required root node property:
compatible: must contain "marvell,armada-370-xp"
In addition, boards using the Marvell Armada 370 SoC shall have the
following property:
Required root node property:
compatible: must contain "marvell,armada370"
In addition, boards using the Marvell Armada XP SoC shall have the
following property:
Required root node property:
compatible: must contain "marvell,armadaxp"
Documentation/devicetree/bindings/arm/atmel-aic.txt
浏览文件 @ 593d0a3e
......@@ -4,7 +4,7 @@ Required properties:
- compatible: Should be "atmel,<chip>-aic"
- interrupt-controller: Identifies the node as an interrupt controller.
- interrupt-parent: For single AIC system, it is an empty property.
- #interrupt-cells: The number of cells to define the interrupts. It sould be 2.
- #interrupt-cells: The number of cells to define the interrupts. It sould be 3.
The first cell is the IRQ number (aka "Peripheral IDentifier" on datasheet).
The second cell is used to specify flags:
bits[3:0] trigger type and level flags:
......@@ -14,7 +14,10 @@ Required properties:
8 = active low level-sensitive.
Valid combinations are 1, 2, 3, 4, 8.
Default flag for internal sources should be set to 4 (active high).
The third cell is used to specify the irq priority from 0 (lowest) to 7
(highest).
- reg: Should contain AIC registers location and length
- atmel,external-irqs: u32 array of external irqs.
Examples:
/*
......@@ -24,7 +27,7 @@ Examples:
compatible = "atmel,at91rm9200-aic";
interrupt-controller;
interrupt-parent;
#interrupt-cells = <2>;
#interrupt-cells = <3>;
reg = <0xfffff000 0x200>;
};
......@@ -34,5 +37,5 @@ Examples:
dma: dma-controller@ffffec00 {
compatible = "atmel,at91sam9g45-dma";
reg = <0xffffec00 0x200>;
interrupts = <21 4>;
interrupts = <21 4 5>;
};
Documentation/devicetree/bindings/arm/davinci/cp-intc.txt 0 → 100644
浏览文件 @ 593d0a3e
* TI Common Platform Interrupt Controller
Common Platform Interrupt Controller (cp_intc) is used on
OMAP-L1x SoCs and can support several configurable number
of interrupts.
Main node required properties:
- compatible : should be:
"ti,cp-intc"
- interrupt-controller : Identifies the node as an interrupt controller
- #interrupt-cells : Specifies the number of cells needed to encode an
interrupt source. The type shall be a <u32> and the value shall be 1.
The cell contains the interrupt number in the range [0-128].
- ti,intc-size: Number of interrupts handled by the interrupt controller.
- reg: physical base address and size of the intc registers map.
Example:
intc: interrupt-controller@1 {
compatible = "ti,cp-intc";
interrupt-controller;
#interrupt-cells = <1>;
ti,intc-size = <101>;
reg = <0xfffee000 0x2000>;
};
Documentation/devicetree/bindings/arm/mvebu-system-controller.txt 0 → 100644
浏览文件 @ 593d0a3e
MVEBU System Controller
-----------------------
MVEBU (Marvell SOCs: Armada 370/XP, Dove, mv78xx0, Kirkwood, Orion5x)
Required properties:
- compatible: one of:
- "marvell,orion-system-controller"
- "marvell,armada-370-xp-system-controller"
- reg: Should contain system controller registers location and length.
Example:
system-controller@d0018200 {
compatible = "marvell,armada-370-xp-system-controller";
reg = <0xd0018200 0x500>;
};
Documentation/devicetree/bindings/arm/olimex.txt 0 → 100644
浏览文件 @ 593d0a3e
Olimex i.MX Platforms Device Tree Bindings
------------------------------------------
i.MX23 Olinuxino Low Cost Board
Required root node properties:
- compatible = "olimex,imx23-olinuxino", "fsl,imx23";
Documentation/devicetree/bindings/arm/omap/omap.txt
浏览文件 @ 593d0a3e
......@@ -47,3 +47,9 @@ Boards:
- AM335X EVM : Software Developement Board for AM335x
compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3"
- AM335X Bone : Low cost community board
compatible = "ti,am335x-bone", "ti,am33xx", "ti,omap3"
- OMAP5 EVM : Evaluation Module
compatible = "ti,omap5-evm", "ti,omap5"
Documentation/devicetree/bindings/arm/primecell.txt
浏览文件 @ 593d0a3e
......@@ -13,11 +13,17 @@ Required properties:
Optional properties:
- arm,primecell-periphid : Value to override the h/w value with
- clocks : From common clock binding. First clock is phandle to clock for apb
pclk. Additional clocks are optional and specific to those peripherals.
- clock-names : From common clock binding. Shall be "apb_pclk" for first clock.
Example:
serial@fff36000 {
compatible = "arm,pl011", "arm,primecell";
arm,primecell-periphid = <0x00341011>;
clocks = <&pclk>;
clock-names = "apb_pclk";
};
Documentation/devicetree/bindings/arm/tegra/emc.txt → Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-emc.txt
浏览文件 @ 593d0a3e
......@@ -15,7 +15,7 @@ Child device nodes describe the memory settings for different configurations and
Example:
emc@7000f400 {
memory-controller@7000f400 {
#address-cells = < 1 >;
#size-cells = < 0 >;
compatible = "nvidia,tegra20-emc";
......
Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-mc.txt
浏览文件 @ 593d0a3e
......@@ -8,7 +8,7 @@ Required properties:
- interrupts : Should contain MC General interrupt.
Example:
mc {
memory-controller@0x7000f000 {
compatible = "nvidia,tegra20-mc";
reg = <0x7000f000 0x024
0x7000f03c 0x3c4>;
......
Documentation/devicetree/bindings/arm/tegra/nvidia,tegra30-mc.txt
浏览文件 @ 593d0a3e
......@@ -8,7 +8,7 @@ Required properties:
- interrupts : Should contain MC General interrupt.
Example:
mc {
memory-controller {
compatible = "nvidia,tegra30-mc";
reg = <0x7000f000 0x010
0x7000f03c 0x1b4
......
Documentation/devicetree/bindings/clock/calxeda.txt 0 → 100644
浏览文件 @ 593d0a3e
Device Tree Clock bindings for Calxeda highbank platform
This binding uses the common clock binding[1].
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
Required properties:
- compatible : shall be one of the following:
"calxeda,hb-pll-clock" - for a PLL clock
"calxeda,hb-a9periph-clock" - The A9 peripheral clock divided from the
A9 clock.
"calxeda,hb-a9bus-clock" - The A9 bus clock divided from the A9 clock.
"calxeda,hb-emmc-clock" - Divided clock for MMC/SD controller.
- reg : shall be the control register offset from SYSREGs base for the clock.
- clocks : shall be the input parent clock phandle for the clock. This is
either an oscillator or a pll output.
- #clock-cells : from common clock binding; shall be set to 0.
Documentation/devicetree/bindings/clock/clock-bindings.txt 0 → 100644
浏览文件 @ 593d0a3e
This binding is a work-in-progress, and are based on some experimental
work by benh[1].
Sources of clock signal can be represented by any node in the device
tree. Those nodes are designated as clock providers. Clock consumer
nodes use a phandle and clock specifier pair to connect clock provider
outputs to clock inputs. Similar to the gpio specifiers, a clock
specifier is an array of one more more cells identifying the clock
output on a device. The length of a clock specifier is defined by the
value of a #clock-cells property in the clock provider node.
[1] http://patchwork.ozlabs.org/patch/31551/
==Clock providers==
Required properties:
#clock-cells: Number of cells in a clock specifier; Typically 0 for nodes
with a single clock output and 1 for nodes with multiple
clock outputs.
Optional properties:
clock-output-names: Recommended to be a list of strings of clock output signal
names indexed by the first cell in the clock specifier.
However, the meaning of clock-output-names is domain
specific to the clock provider, and is only provided to
encourage using the same meaning for the majority of clock
providers. This format may not work for clock providers
using a complex clock specifier format. In those cases it
is recommended to omit this property and create a binding
specific names property.
Clock consumer nodes must never directly reference
the provider's clock-output-names property.
For example:
oscillator {
#clock-cells = <1>;
clock-output-names = "ckil", "ckih";
};
- this node defines a device with two clock outputs, the first named
"ckil" and the second named "ckih". Consumer nodes always reference
clocks by index. The names should reflect the clock output signal
names for the device.
==Clock consumers==
Required properties:
clocks: List of phandle and clock specifier pairs, one pair
for each clock input to the device. Note: if the
clock provider specifies '0' for #clock-cells, then
only the phandle portion of the pair will appear.
Optional properties:
clock-names: List of clock input name strings sorted in the same
order as the clocks property. Consumers drivers
will use clock-names to match clock input names
with clocks specifiers.
clock-ranges: Empty property indicating that child nodes can inherit named
clocks from this node. Useful for bus nodes to provide a
clock to their children.
For example:
device {
clocks = <&osc 1>, <&ref 0>;
clock-names = "baud", "register";
};
This represents a device with two clock inputs, named "baud" and "register".
The baud clock is connected to output 1 of the &osc device, and the register
clock is connected to output 0 of the &ref.
==Example==
/* external oscillator */
osc: oscillator {
compatible = "fixed-clock";
#clock-cells = <1>;
clock-frequency = <32678>;
clock-output-names = "osc";
};
/* phase-locked-loop device, generates a higher frequency clock
* from the external oscillator reference */
pll: pll@4c000 {
compatible = "vendor,some-pll-interface"
#clock-cells = <1>;
clocks = <&osc 0>;
clock-names = "ref";
reg = <0x4c000 0x1000>;
clock-output-names = "pll", "pll-switched";
};
/* UART, using the low frequency oscillator for the baud clock,
* and the high frequency switched PLL output for register
* clocking */
uart@a000 {
compatible = "fsl,imx-uart";
reg = <0xa000 0x1000>;
interrupts = <33>;
clocks = <&osc 0>, <&pll 1>;
clock-names = "baud", "register";
};
This DT fragment defines three devices: an external oscillator to provide a
low-frequency reference clock, a PLL device to generate a higher frequency
clock signal, and a UART.
* The oscillator is fixed-frequency, and provides one clock output, named "osc".
* The PLL is both a clock provider and a clock consumer. It uses the clock
signal generated by the external oscillator, and provides two output signals
("pll" and "pll-switched").
* The UART has its baud clock connected the external oscillator and its
register clock connected to the PLL clock (the "pll-switched" signal)
Documentation/devicetree/bindings/clock/fixed-clock.txt 0 → 100644
浏览文件 @ 593d0a3e
Binding for simple fixed-rate clock sources.
This binding uses the common clock binding[1].
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
Required properties:
- compatible : shall be "fixed-clock".
- #clock-cells : from common clock binding; shall be set to 0.
- clock-frequency : frequency of clock in Hz. Should be a single cell.
Optional properties:
- gpios : From common gpio binding; gpio connection to clock enable pin.
- clock-output-names : From common clock binding.
Example:
clock {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <1000000000>;
};
Documentation/devicetree/bindings/fb/mxsfb.txt 0 → 100644
浏览文件 @ 593d0a3e
* Freescale MXS LCD Interface (LCDIF)
Required properties:
- compatible: Should be "fsl,<chip>-lcdif". Supported chips include
imx23 and imx28.
- reg: Address and length of the register set for lcdif
- interrupts: Should contain lcdif interrupts
Optional properties:
- panel-enable-gpios : Should specify the gpio for panel enable
Examples:
lcdif@80030000 {
compatible = "fsl,imx28-lcdif";
reg = <0x80030000 2000>;
interrupts = <38 86>;
panel-enable-gpios = <&gpio3 30 0>;
};
Documentation/devicetree/bindings/gpio/fsl-imx-gpio.txt
浏览文件 @ 593d0a3e
......@@ -8,8 +8,16 @@ Required properties:
by low 16 pins and the second one is for high 16 pins.
- gpio-controller : Marks the device node as a gpio controller.
- #gpio-cells : Should be two. The first cell is the pin number and
the second cell is used to specify optional parameters (currently
unused).
the second cell is used to specify the gpio polarity:
0 = active high
1 = active low
- interrupt-controller: Marks the device node as an interrupt controller.
- #interrupt-cells : Should be 2. The first cell is the GPIO number.
The second cell bits[3:0] is used to specify trigger type and level flags:
1 = low-to-high edge triggered.
2 = high-to-low edge triggered.
4 = active high level-sensitive.
8 = active low level-sensitive.
Example:
......@@ -19,4 +27,6 @@ gpio0: gpio@73f84000 {
interrupts = <50 51>;
gpio-controller;
#gpio-cells = <2>;
interrupt-controller;
#interrupt-cells = <2>;
};
Documentation/devicetree/bindings/gpio/gpio-mxs.txt
浏览文件 @ 593d0a3e
......@@ -13,8 +13,9 @@ Required properties for GPIO node:
- interrupts : Should be the port interrupt shared by all 32 pins.
- gpio-controller : Marks the device node as a gpio controller.
- #gpio-cells : Should be two. The first cell is the pin number and
the second cell is used to specify optional parameters (currently
unused).
the second cell is used to specify the gpio polarity:
0 = active high
1 = active low
- interrupt-controller: Marks the device node as an interrupt controller.
- #interrupt-cells : Should be 2. The first cell is the GPIO number.
The second cell bits[3:0] is used to specify trigger type and level flags:
......
Documentation/devicetree/bindings/gpio/gpio-nmk.txt
浏览文件 @ 593d0a3e
......@@ -26,6 +26,6 @@ Example:
#gpio-cells = <2>;
gpio-controller;
interrupt-controller;
supports-sleepmode;
st,supports-sleepmode;
gpio-bank = <1>;
};
Documentation/devicetree/bindings/gpio/led.txt
浏览文件 @ 593d0a3e
......@@ -55,4 +55,4 @@ run-control {
gpios = <&mpc8572 7 0>;
default-state = "on";
};
}
};
Documentation/devicetree/bindings/input/fsl-mma8450.txt
浏览文件 @ 593d0a3e
......@@ -2,6 +2,7 @@
Required properties:
- compatible : "fsl,mma8450".
- reg: the I2C address of MMA8450
Example:
......
Documentation/devicetree/bindings/input/lpc32xx-key.txt 0 → 100644
浏览文件 @ 593d0a3e
NXP LPC32xx Key Scan Interface
Required Properties:
- compatible: Should be "nxp,lpc3220-key"
- reg: Physical base address of the controller and length of memory mapped
region.
- interrupts: The interrupt number to the cpu.
- keypad,num-rows: Number of rows and columns, e.g. 1: 1x1, 6: 6x6
- keypad,num-columns: Must be equal to keypad,num-rows since LPC32xx only
supports square matrices
- nxp,debounce-delay-ms: Debounce delay in ms
- nxp,scan-delay-ms: Repeated scan period in ms
- linux,keymap: the key-code to be reported when the key is pressed
and released, see also
Documentation/devicetree/bindings/input/matrix-keymap.txt
Example:
key@40050000 {
compatible = "nxp,lpc3220-key";
reg = <0x40050000 0x1000>;
interrupts = <54 0>;
keypad,num-rows = <1>;
keypad,num-columns = <1>;
nxp,debounce-delay-ms = <3>;
nxp,scan-delay-ms = <34>;
linux,keymap = <0x00000002>;
};
Documentation/devicetree/bindings/input/omap-keypad.txt 0 → 100644
浏览文件 @ 593d0a3e
* TI's Keypad Controller device tree bindings
TI's Keypad controller is used to interface a SoC with a matrix-type
keypad device. The keypad controller supports multiple row and column lines.
A key can be placed at each intersection of a unique row and a unique column.
The keypad controller can sense a key-press and key-release and report the
event using a interrupt to the cpu.
Required SoC Specific Properties:
- compatible: should be one of the following
- "ti,omap4-keypad": For controllers compatible with omap4 keypad
controller.
Required Board Specific Properties, in addition to those specified by
the shared matrix-keyboard bindings:
- keypad,num-rows: Number of row lines connected to the keypad
controller.
- keypad,num-columns: Number of column lines connected to the
keypad controller.
Optional Properties specific to linux:
- linux,keypad-no-autorepeat: do no enable autorepeat feature.
Example:
keypad@4ae1c000{
compatible = "ti,omap4-keypad";
keypad,num-rows = <2>;
keypad,num-columns = <8>;
linux,keypad-no-autorepeat;
};
Documentation/devicetree/bindings/input/twl6040-vibra.txt 已删除 100644 → 0
浏览文件 @ 50e90041
Vibra driver for the twl6040 family
The vibra driver is a child of the twl6040 MFD dirver.
Documentation/devicetree/bindings/mfd/twl6040.txt
Required properties:
- compatible : Must be "ti,twl6040-vibra";
- interrupts: 4, Vibra overcurrent interrupt
- vddvibl-supply: Regulator supplying the left vibra motor
- vddvibr-supply: Regulator supplying the right vibra motor
- vibldrv_res: Board specific left driver resistance
- vibrdrv_res: Board specific right driver resistance
- viblmotor_res: Board specific left motor resistance
- vibrmotor_res: Board specific right motor resistance
Optional properties:
- vddvibl_uV: If the vddvibl default voltage need to be changed
- vddvibr_uV: If the vddvibr default voltage need to be changed
Example:
/*
* 8-channel high quality low-power audio codec
* http://www.ti.com/lit/ds/symlink/twl6040.pdf
*/
twl6040: twl6040@4b {
...
twl6040_vibra: twl6040@1 {
compatible = "ti,twl6040-vibra";
interrupts = <4>;
vddvibl-supply = <&vbat>;
vddvibr-supply = <&vbat>;
vibldrv_res = <8>;
vibrdrv_res = <3>;
viblmotor_res = <10>;
vibrmotor_res = <10>;
};
};
Documentation/devicetree/bindings/iommu/nvidia,tegra30-smmu.txt 0 → 100644
浏览文件 @ 593d0a3e
NVIDIA Tegra 30 IOMMU H/W, SMMU (System Memory Management Unit)
Required properties:
- compatible : "nvidia,tegra30-smmu"
- reg : Should contain 3 register banks(address and length) for each
of the SMMU register blocks.
- interrupts : Should contain MC General interrupt.
- nvidia,#asids : # of ASIDs
- dma-window : IOVA start address and length.
- nvidia,ahb : phandle to the ahb bus connected to SMMU.
Example:
smmu {
compatible = "nvidia,tegra30-smmu";
reg = <0x7000f010 0x02c
0x7000f1f0 0x010
0x7000f228 0x05c>;
nvidia,#asids = <4>; /* # of ASIDs */
dma-window = <0 0x40000000>; /* IOVA start & length */
nvidia,ahb = <&ahb>;
};
Documentation/devicetree/bindings/mfd/mc13xxx.txt
浏览文件 @ 593d0a3e
......@@ -46,8 +46,8 @@ Examples:
ecspi@70010000 { /* ECSPI1 */
fsl,spi-num-chipselects = <2>;
cs-gpios = <&gpio3 24 0>, /* GPIO4_24 */
<&gpio3 25 0>; /* GPIO4_25 */
cs-gpios = <&gpio4 24 0>, /* GPIO4_24 */
<&gpio4 25 0>; /* GPIO4_25 */
status = "okay";
pmic: mc13892@0 {
......
Documentation/devicetree/bindings/mfd/tps65910.txt
浏览文件 @ 593d0a3e
......@@ -17,18 +17,46 @@ Required properties:
device need to be present. The definition for each of these nodes is defined
using the standard binding for regulators found at
Documentation/devicetree/bindings/regulator/regulator.txt.
The regulator is matched with the regulator-compatible.
The valid names for regulators are:
The valid regulator-compatible values are:
tps65910: vrtc, vio, vdd1, vdd2, vdd3, vdig1, vdig2, vpll, vdac, vaux1,
vaux2, vaux33, vmmc
tps65911: vrtc, vio, vdd1, vdd3, vddctrl, ldo1, ldo2, ldo3, ldo4, ldo5,
ldo6, ldo7, ldo8
- xxx-supply: Input voltage supply regulator.
These entries are require if regulators are enabled for a device. Missing of these
properties can cause the regulator registration fails.
If some of input supply is powered through battery or always-on supply then
also it is require to have these parameters with proper node handle of always
on power supply.
tps65910:
vcc1-supply: VDD1 input.
vcc2-supply: VDD2 input.
vcc3-supply: VAUX33 and VMMC input.
vcc4-supply: VAUX1 and VAUX2 input.
vcc5-supply: VPLL and VDAC input.
vcc6-supply: VDIG1 and VDIG2 input.
vcc7-supply: VRTC input.
vccio-supply: VIO input.
tps65911:
vcc1-supply: VDD1 input.
vcc2-supply: VDD2 input.
vcc3-supply: LDO6, LDO7 and LDO8 input.
vcc4-supply: LDO5 input.
vcc5-supply: LDO3 and LDO4 input.
vcc6-supply: LDO1 and LDO2 input.
vcc7-supply: VRTC input.
vccio-supply: VIO input.
Optional properties:
- ti,vmbch-threshold: (tps65911) main battery charged threshold
comparator. (see VMBCH_VSEL in TPS65910 datasheet)
- ti,vmbch2-threshold: (tps65911) main battery discharged threshold
comparator. (see VMBCH_VSEL in TPS65910 datasheet)
- ti,en-ck32k-xtal: enable external 32-kHz crystal oscillator (see CK32K_CTRL
in TPS6591X datasheet)
- ti,en-gpio-sleep: enable sleep control for gpios
There should be 9 entries here, one for each gpio.
......@@ -56,74 +84,110 @@ Example:
ti,en-gpio-sleep = <0 0 1 0 0 0 0 0 0>;
vcc1-supply = <&reg_parent>;
vcc2-supply = <&some_reg>;
vcc3-supply = <...>;
vcc4-supply = <...>;
vcc5-supply = <...>;
vcc6-supply = <...>;
vcc7-supply = <...>;
vccio-supply = <...>;
regulators {
vdd1_reg: vdd1 {
#address-cells = <1>;
#size-cells = <0>;
vdd1_reg: regulator@0 {
regulator-compatible = "vdd1";
reg = <0>;
regulator-min-microvolt = < 600000>;
regulator-max-microvolt = <1500000>;
regulator-always-on;
regulator-boot-on;
ti,regulator-ext-sleep-control = <0>;
};
vdd2_reg: vdd2 {
vdd2_reg: regulator@1 {
regulator-compatible = "vdd2";
reg = <1>;
regulator-min-microvolt = < 600000>;
regulator-max-microvolt = <1500000>;
regulator-always-on;
regulator-boot-on;
ti,regulator-ext-sleep-control = <4>;
};
vddctrl_reg: vddctrl {
vddctrl_reg: regulator@2 {
regulator-compatible = "vddctrl";
reg = <2>;
regulator-min-microvolt = < 600000>;
regulator-max-microvolt = <1400000>;
regulator-always-on;
regulator-boot-on;
ti,regulator-ext-sleep-control = <0>;
};
vio_reg: vio {
vio_reg: regulator@3 {
regulator-compatible = "vio";
reg = <3>;
regulator-min-microvolt = <1500000>;
regulator-max-microvolt = <1800000>;
regulator-always-on;
regulator-boot-on;
ti,regulator-ext-sleep-control = <1>;
};
ldo1_reg: ldo1 {
ldo1_reg: regulator@4 {
regulator-compatible = "ldo1";
reg = <4>;
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
ti,regulator-ext-sleep-control = <0>;
};
ldo2_reg: ldo2 {
ldo2_reg: regulator@5 {
regulator-compatible = "ldo2";
reg = <5>;
regulator-min-microvolt = <1050000>;
regulator-max-microvolt = <1050000>;
ti,regulator-ext-sleep-control = <0>;
};
ldo3_reg: ldo3 {
ldo3_reg: regulator@6 {
regulator-compatible = "ldo3";
reg = <6>;
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
ti,regulator-ext-sleep-control = <0>;
};
ldo4_reg: ldo4 {
ldo4_reg: regulator@7 {
regulator-compatible = "ldo4";
reg = <7>;
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
regulator-always-on;
ti,regulator-ext-sleep-control = <0>;
};
ldo5_reg: ldo5 {
ldo5_reg: regulator@8 {
regulator-compatible = "ldo5";
reg = <8>;
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
ti,regulator-ext-sleep-control = <0>;
};
ldo6_reg: ldo6 {
ldo6_reg: regulator@9 {
regulator-compatible = "ldo6";
reg = <9>;
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
ti,regulator-ext-sleep-control = <0>;
};
ldo7_reg: ldo7 {
ldo7_reg: regulator@10 {
regulator-compatible = "ldo7";
reg = <10>;
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
regulator-always-on;
regulator-boot-on;
ti,regulator-ext-sleep-control = <1>;
};
ldo8_reg: ldo8 {
ldo8_reg: regulator@11 {
regulator-compatible = "ldo8";
reg = <11>;
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
regulator-always-on;
......
Documentation/devicetree/bindings/misc/at25.txt 0 → 100644
浏览文件 @ 593d0a3e
Atmel AT25 eeprom
Required properties:
- compatible : "atmel,at25".
- reg : chip select number
- spi-max-frequency : max spi frequency to use
- at25,byte-len : total eeprom size in bytes
- at25,addr-mode : addr-mode flags, as defined in include/linux/spi/eeprom.h
- at25,page-size : size of the eeprom page
Examples:
at25@0 {
compatible = "atmel,at25";
reg = <0>
spi-max-frequency = <5000000>;
at25,byte-len = <0x8000>;
at25,addr-mode = <2>;
at25,page-size = <64>;
};
Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
浏览文件 @ 593d0a3e
......@@ -3,21 +3,22 @@
The Enhanced Secure Digital Host Controller provides an interface
for MMC, SD, and SDIO types of memory cards.
This file documents differences between the core properties described
by mmc.txt and the properties used by the sdhci-esdhc driver.
Required properties:
- compatible : should be
"fsl,<chip>-esdhc", "fsl,esdhc"
- reg : should contain eSDHC registers location and length.
- interrupts : should contain eSDHC interrupt.
- interrupt-parent : interrupt source phandle.
- clock-frequency : specifies eSDHC base clock frequency.
- sdhci,wp-inverted : (optional) specifies that eSDHC controller
reports inverted write-protect state; New devices should use
the generic "wp-inverted" property.
- sdhci,1-bit-only : (optional) specifies that a controller can
only handle 1-bit data transfers. New devices should use the
generic "bus-width = <1>" property.
- sdhci,auto-cmd12: (optional) specifies that a controller can
only handle auto CMD12.
Optional properties:
- sdhci,wp-inverted : specifies that eSDHC controller reports
inverted write-protect state; New devices should use the generic
"wp-inverted" property.
- sdhci,1-bit-only : specifies that a controller can only handle
1-bit data transfers. New devices should use the generic
"bus-width = <1>" property.
- sdhci,auto-cmd12: specifies that a controller can only handle auto
CMD12.
Example:
......
Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.txt
浏览文件 @ 593d0a3e
......@@ -3,17 +3,15 @@
The Enhanced Secure Digital Host Controller on Freescale i.MX family
provides an interface for MMC, SD, and SDIO types of memory cards.
This file documents differences between the core properties described
by mmc.txt and the properties used by the sdhci-esdhc-imx driver.
Required properties:
- compatible : Should be "fsl,<chip>-esdhc"
- reg : Should contain eSDHC registers location and length
- interrupts : Should contain eSDHC interrupt
Optional properties:
- non-removable : Indicate the card is wired to host permanently
- fsl,cd-internal : Indicate to use controller internal card detection
- fsl,wp-internal : Indicate to use controller internal write protection
- cd-gpios : Specify GPIOs for card detection
- wp-gpios : Specify GPIOs for write protection
Examples:
......@@ -29,6 +27,6 @@ esdhc@70008000 {
compatible = "fsl,imx51-esdhc";
reg = <0x70008000 0x4000>;
interrupts = <2>;
cd-gpios = <&gpio0 6 0>; /* GPIO1_6 */
wp-gpios = <&gpio0 5 0>; /* GPIO1_5 */
cd-gpios = <&gpio1 6 0>; /* GPIO1_6 */
wp-gpios = <&gpio1 5 0>; /* GPIO1_5 */
};
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt
浏览文件 @ 593d0a3e
MMC/SD/SDIO slot directly connected to a SPI bus
This file documents differences between the core properties described
by mmc.txt and the properties used by the mmc_spi driver.
Required properties:
- compatible : should be "mmc-spi-slot".
- reg : should specify SPI address (chip-select number).
- spi-max-frequency : maximum frequency for this device (Hz).
- voltage-ranges : two cells are required, first cell specifies minimum
slot voltage (mV), second cell specifies maximum slot voltage (mV).
......@@ -11,8 +12,7 @@ Required properties:
Optional properties:
- gpios : may specify GPIOs in this order: Card-Detect GPIO,
Write-Protect GPIO. Note that this does not follow the
binding from mmc.txt, for historic reasons.
- interrupts : the interrupt of a card detect interrupt.
binding from mmc.txt, for historical reasons.
- interrupt-parent : the phandle for the interrupt controller that
services interrupts for this device.
......
Documentation/devicetree/bindings/mmc/mmc.txt
浏览文件 @ 593d0a3e
......@@ -2,13 +2,17 @@ These properties are common to multiple MMC host controllers. Any host
that requires the respective functionality should implement them using
these definitions.
Interpreted by the OF core:
- reg: Registers location and length.
- interrupts: Interrupts used by the MMC controller.
Required properties:
- bus-width: Number of data lines, can be <1>, <4>, or <8>
Optional properties:
- cd-gpios : Specify GPIOs for card detection, see gpio binding
- wp-gpios : Specify GPIOs for write protection, see gpio binding
- cd-inverted: when present, polarity on the wp gpio line is inverted
- cd-gpios: Specify GPIOs for card detection, see gpio binding
- wp-gpios: Specify GPIOs for write protection, see gpio binding
- cd-inverted: when present, polarity on the cd gpio line is inverted
- wp-inverted: when present, polarity on the wp gpio line is inverted
- non-removable: non-removable slot (like eMMC)
- max-frequency: maximum operating clock frequency
......
Documentation/devicetree/bindings/mmc/mmci.txt
浏览文件 @ 593d0a3e
* ARM PrimeCell MultiMedia Card Interface (MMCI) PL180/1
The ARM PrimeCell MMCI PL180 and PL181 provides and interface for
The ARM PrimeCell MMCI PL180 and PL181 provides an interface for
reading and writing to MultiMedia and SD cards alike.
This file documents differences between the core properties described
by mmc.txt and the properties used by the mmci driver.
Required properties:
- compatible : contains "arm,pl18x", "arm,primecell".
- reg : contains pl18x registers and length.
- interrupts : contains the device IRQ(s).
- arm,primecell-periphid : contains the PrimeCell Peripheral ID.
Optional properties:
- wp-gpios : contains any write protect (ro) gpios
- cd-gpios : contains any card detection gpios
- cd-inverted : indicates whether the cd gpio is inverted
- max-frequency : contains the maximum operating frequency
- bus-width : number of data lines, can be <1>, <4>, or <8>
- mmc-cap-mmc-highspeed : indicates whether MMC is high speed capable
- mmc-cap-sd-highspeed : indicates whether SD is high speed capable
Documentation/devicetree/bindings/mmc/mxs-mmc.txt
浏览文件 @ 593d0a3e
......@@ -3,16 +3,14 @@
The Freescale MXS Synchronous Serial Ports (SSP) can act as a MMC controller
to support MMC, SD, and SDIO types of memory cards.
This file documents differences between the core properties in mmc.txt
and the properties used by the mxsmmc driver.
Required properties:
- compatible: Should be "fsl,<chip>-mmc". The supported chips include
imx23 and imx28.
- reg: Should contain registers location and length
- interrupts: Should contain ERROR and DMA interrupts
- fsl,ssp-dma-channel: APBH DMA channel for the SSP
- bus-width: Number of data lines, can be <1>, <4>, or <8>
Optional properties:
- wp-gpios: Specify GPIOs for write protection
Examples:
......
Documentation/devicetree/bindings/mmc/nvidia-sdhci.txt → Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt
浏览文件 @ 593d0a3e
......@@ -3,15 +3,13 @@
This controller on Tegra family SoCs provides an interface for MMC, SD,
and SDIO types of memory cards.
This file documents differences between the core properties described
by mmc.txt and the properties used by the sdhci-tegra driver.
Required properties:
- compatible : Should be "nvidia,<chip>-sdhci"
- reg : Should contain SD/MMC registers location and length
- interrupts : Should contain SD/MMC interrupt
- bus-width : Number of data lines, can be <1>, <4>, or <8>
Optional properties:
- cd-gpios : Specify GPIOs for card detection
- wp-gpios : Specify GPIOs for write protection
- power-gpios : Specify GPIOs for power control
Example:
......
Documentation/devicetree/bindings/mmc/sdhci-pxa.txt 0 → 100644
浏览文件 @ 593d0a3e
* Marvell sdhci-pxa v2/v3 controller
This file documents differences between the core properties in mmc.txt
and the properties used by the sdhci-pxav2 and sdhci-pxav3 drivers.
Required properties:
- compatible: Should be "mrvl,pxav2-mmc" or "mrvl,pxav3-mmc".
Optional properties:
- mrvl,clk-delay-cycles: Specify a number of cycles to delay for tuning.
Example:
sdhci@d4280800 {
compatible = "mrvl,pxav3-mmc";
reg = <0xd4280800 0x800>;
bus-width = <8>;
interrupts = <27>;
non-removable;
mrvl,clk-delay-cycles = <31>;
};
Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
浏览文件 @ 593d0a3e
......@@ -3,21 +3,20 @@
The Highspeed MMC Host Controller on TI OMAP family
provides an interface for MMC, SD, and SDIO types of memory cards.
This file documents differences between the core properties described
by mmc.txt and the properties used by the omap_hsmmc driver.
Required properties:
- compatible:
Should be "ti,omap2-hsmmc", for OMAP2 controllers
Should be "ti,omap3-hsmmc", for OMAP3 controllers
Should be "ti,omap4-hsmmc", for OMAP4 controllers
- ti,hwmods: Must be "mmc<n>", n is controller instance starting 1
- reg : should contain hsmmc registers location and length
Optional properties:
ti,dual-volt: boolean, supports dual voltage cards
<supply-name>-supply: phandle to the regulator device tree node
"supply-name" examples are "vmmc", "vmmc_aux" etc
bus-width: Number of data lines, default assumed is 1 if the property is missing.
cd-gpios: GPIOs for card detection
wp-gpios: GPIOs for write protection
ti,non-removable: non-removable slot (like eMMC)
ti,needs-special-reset: Requires a special softreset sequence
......
Documentation/devicetree/bindings/mtd/partition.txt
浏览文件 @ 593d0a3e
......@@ -35,4 +35,4 @@ flash@0 {
uimage@100000 {
reg = <0x0100000 0x200000>;
};
];
};
Documentation/devicetree/bindings/net/broadcom-bcm87xx.txt 0 → 100644
浏览文件 @ 593d0a3e
The Broadcom BCM87XX devices are a family of 10G Ethernet PHYs. They
have these bindings in addition to the standard PHY bindings.
Compatible: Should contain "broadcom,bcm8706" or "broadcom,bcm8727" and
"ethernet-phy-ieee802.3-c45"
Optional Properties:
- broadcom,c45-reg-init : one of more sets of 4 cells. The first cell
is the MDIO Manageable Device (MMD) address, the second a register
address within the MMD, the third cell contains a mask to be ANDed
with the existing register value, and the fourth cell is ORed with
he result to yield the new register value. If the third cell has a
value of zero, no read of the existing value is performed.
Example:
ethernet-phy@5 {
reg = <5>;
compatible = "broadcom,bcm8706", "ethernet-phy-ieee802.3-c45";
interrupt-parent = <&gpio>;
interrupts = <12 8>; /* Pin 12, active low */
/*
* Set PMD Digital Control Register for
* GPIO[1] Tx/Rx
* GPIO[0] R64 Sync Acquired
*/
broadcom,c45-reg-init = <1 0xc808 0xff8f 0x70>;
};
Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
浏览文件 @ 593d0a3e
......@@ -11,6 +11,9 @@ Required properties:
- reg : Offset and length of the register set for this device
- interrupts : Interrupt tuple for this device
Optional properties:
- clock-frequency : The oscillator frequency driving the flexcan device
Example:
......
Documentation/devicetree/bindings/net/davinci_emac.txt 0 → 100644
浏览文件 @ 593d0a3e
* Texas Instruments Davinci EMAC
This file provides information, what the device node
for the davinci_emac interface contains.
Required properties:
- compatible: "ti,davinci-dm6467-emac";
- reg: Offset and length of the register set for the device
- ti,davinci-ctrl-reg-offset: offset to control register
- ti,davinci-ctrl-mod-reg-offset: offset to control module register
- ti,davinci-ctrl-ram-offset: offset to control module ram
- ti,davinci-ctrl-ram-size: size of control module ram
- ti,davinci-rmii-en: use RMII
- ti,davinci-no-bd-ram: has the emac controller BD RAM
- phy-handle: Contains a phandle to an Ethernet PHY.
if not, davinci_emac driver defaults to 100/FULL
- interrupts: interrupt mapping for the davinci emac interrupts sources:
4 sources: <Receive Threshold Interrupt
Receive Interrupt
Transmit Interrupt
Miscellaneous Interrupt>
Optional properties:
- local-mac-address : 6 bytes, mac address
Example (enbw_cmc board):
eth0: emac@1e20000 {
compatible = "ti,davinci-dm6467-emac";
reg = <0x220000 0x4000>;
ti,davinci-ctrl-reg-offset = <0x3000>;
ti,davinci-ctrl-mod-reg-offset = <0x2000>;
ti,davinci-ctrl-ram-offset = <0>;
ti,davinci-ctrl-ram-size = <0x2000>;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = <33
34
35
36
>;
interrupt-parent = <&intc>;
};
Documentation/devicetree/bindings/net/fsl-fec.txt
浏览文件 @ 593d0a3e
......@@ -7,10 +7,14 @@ Required properties:
- phy-mode : String, operation mode of the PHY interface.
Supported values are: "mii", "gmii", "sgmii", "tbi", "rmii",
"rgmii", "rgmii-id", "rgmii-rxid", "rgmii-txid", "rtbi", "smii".
- phy-reset-gpios : Should specify the gpio for phy reset
Optional properties:
- local-mac-address : 6 bytes, mac address
- phy-reset-gpios : Should specify the gpio for phy reset
- phy-reset-duration : Reset duration in milliseconds. Should present
only if property "phy-reset-gpios" is available. Missing the property
will have the duration be 1 millisecond. Numbers greater than 1000 are
invalid and 1 millisecond will be used instead.
Example:
......@@ -19,6 +23,6 @@ ethernet@83fec000 {
reg = <0x83fec000 0x4000>;
interrupts = <87>;
phy-mode = "mii";
phy-reset-gpios = <&gpio1 14 0>; /* GPIO2_14 */
phy-reset-gpios = <&gpio2 14 0>; /* GPIO2_14 */
local-mac-address = [00 04 9F 01 1B B9];
};
Documentation/devicetree/bindings/net/phy.txt
浏览文件 @ 593d0a3e
......@@ -14,10 +14,20 @@ Required properties:
- linux,phandle : phandle for this node; likely referenced by an
ethernet controller node.
Optional Properties:
- compatible: Compatible list, may contain
"ethernet-phy-ieee802.3-c22" or "ethernet-phy-ieee802.3-c45" for
PHYs that implement IEEE802.3 clause 22 or IEEE802.3 clause 45
specifications. If neither of these are specified, the default is to
assume clause 22. The compatible list may also contain other
elements.
Example:
ethernet-phy@0 {
linux,phandle = <2452000>
compatible = "ethernet-phy-ieee802.3-c22";
linux,phandle = <2452000>;
interrupt-parent = <40000>;
interrupts = <35 1>;
reg = <0>;
......
Documentation/devicetree/bindings/net/stmmac.txt
浏览文件 @ 593d0a3e
* STMicroelectronics 10/100/1000 Ethernet driver (GMAC)
Required properties:
- compatible: Should be "st,spear600-gmac"
- compatible: Should be "snps,dwmac-<ip_version>" "snps,dwmac"
For backwards compatibility: "st,spear600-gmac" is also supported.
- reg: Address and length of the register set for the device
- interrupt-parent: Should be the phandle for the interrupt controller
that services interrupts for this device
......
Documentation/devicetree/bindings/pinctrl/fsl,imx6q-pinctrl.txt
浏览文件 @ 593d0a3e
......@@ -1626,3 +1626,5 @@ MX6Q_PAD_SD2_DAT3__PCIE_CTRL_MUX_11 1587
MX6Q_PAD_SD2_DAT3__GPIO_1_12 1588
MX6Q_PAD_SD2_DAT3__SJC_DONE 1589
MX6Q_PAD_SD2_DAT3__ANATOP_TESTO_3 1590
MX6Q_PAD_ENET_RX_ER__ANATOP_USBOTG_ID 1591
MX6Q_PAD_GPIO_1__ANATOP_USBOTG_ID 1592
Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt 0 → 100644
浏览文件 @ 593d0a3e
One-register-per-pin type device tree based pinctrl driver
Required properties:
- compatible : "pinctrl-single"
- reg : offset and length of the register set for the mux registers
- pinctrl-single,register-width : pinmux register access width in bits
- pinctrl-single,function-mask : mask of allowed pinmux function bits
in the pinmux register
Optional properties:
- pinctrl-single,function-off : function off mode for disabled state if
available and same for all registers; if not specified, disabling of
pin functions is ignored
This driver assumes that there is only one register for each pin,
and uses the common pinctrl bindings as specified in the pinctrl-bindings.txt
document in this directory.
The pin configuration nodes for pinctrl-single are specified as pinctrl
register offset and value pairs using pinctrl-single,pins. Only the bits
specified in pinctrl-single,function-mask are updated. For example, setting
a pin for a device could be done with:
pinctrl-single,pins = <0xdc 0x118>;
Where 0xdc is the offset from the pinctrl register base address for the
device pinctrl register, and 0x118 contains the desired value of the
pinctrl register. See the device example and static board pins example
below for more information.
Example:
/* SoC common file */
/* first controller instance for pins in core domain */
pmx_core: pinmux@4a100040 {
compatible = "pinctrl-single";
reg = <0x4a100040 0x0196>;
#address-cells = <1>;
#size-cells = <0>;
pinctrl-single,register-width = <16>;
pinctrl-single,function-mask = <0xffff>;
};
/* second controller instance for pins in wkup domain */
pmx_wkup: pinmux@4a31e040 {
compatible = "pinctrl-single;
reg = <0x4a31e040 0x0038>;
#address-cells = <1>;
#size-cells = <0>;
pinctrl-single,register-width = <16>;
pinctrl-single,function-mask = <0xffff>;
};
/* board specific .dts file */
&pmx_core {
/*
* map all board specific static pins enabled by the pinctrl driver
* itself during the boot (or just set them up in the bootloader)
*/
pinctrl-names = "default";
pinctrl-0 = <&board_pins>;
board_pins: pinmux_board_pins {
pinctrl-single,pins = <
0x6c 0xf
0x6e 0xf
0x70 0xf
0x72 0xf
>;
};
/* map uart2 pins */
uart2_pins: pinmux_uart2_pins {
pinctrl-single,pins = <
0xd8 0x118
0xda 0
0xdc 0x118
0xde 0
>;
};
};
&uart2 {
pinctrl-names = "default";
pinctrl-0 = <&uart2_pins>;
};
Documentation/devicetree/bindings/regulator/fixed-regulator.txt
浏览文件 @ 593d0a3e
......@@ -10,6 +10,7 @@ Optional properties:
If this property is missing, the default assumed is Active low.
- gpio-open-drain: GPIO is open drain type.
If this property is missing then default assumption is false.
-vin-supply: Input supply name.
Any property defined as part of the core regulator
binding, defined in regulator.txt, can also be used.
......@@ -29,4 +30,5 @@ Example:
enable-active-high;
regulator-boot-on;
gpio-open-drain;
vin-supply = <&parent_reg>;
};
Documentation/devicetree/bindings/regulator/regulator.txt
浏览文件 @ 593d0a3e
......@@ -10,6 +10,11 @@ Optional properties:
- regulator-always-on: boolean, regulator should never be disabled
- regulator-boot-on: bootloader/firmware enabled regulator
- <name>-supply: phandle to the parent supply/regulator node
- regulator-ramp-delay: ramp delay for regulator(in uV/uS)
- regulator-compatible: If a regulator chip contains multiple
regulators, and if the chip's binding contains a child node that
describes each regulator, then this property indicates which regulator
this child node is intended to configure.
Example:
......
Documentation/devicetree/bindings/regulator/tps65217.txt 0 → 100644
浏览文件 @ 593d0a3e
TPS65217 family of regulators
Required properties:
- compatible: "ti,tps65217"
- reg: I2C slave address
- regulators: list of regulators provided by this controller, must be named
after their hardware counterparts: dcdc[1-3] and ldo[1-4]
- regulators: This is the list of child nodes that specify the regulator
initialization data for defined regulators. Not all regulators for the given
device need to be present. The definition for each of these nodes is defined
using the standard binding for regulators found at
Documentation/devicetree/bindings/regulator/regulator.txt.
The valid names for regulators are:
tps65217: dcdc1, dcdc2, dcdc3, ldo1, ldo2, ldo3 and ldo4
Each regulator is defined using the standard binding for regulators.
Example:
tps: tps@24 {
compatible = "ti,tps65217";
regulators {
#address-cells = <1>;
#size-cells = <0>;
dcdc1_reg: regulator@0 {
reg = <0>;
regulator-compatible = "dcdc1";
regulator-min-microvolt = <900000>;
regulator-max-microvolt = <1800000>;
regulator-boot-on;
regulator-always-on;
};
dcdc2_reg: regulator@1 {
reg = <1>;
regulator-compatible = "dcdc2";
regulator-min-microvolt = <900000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
dcdc3_reg: regulator@2 {
reg = <2>;
regulator-compatible = "dcdc3";
regulator-min-microvolt = <900000>;
regulator-max-microvolt = <1500000>;
regulator-boot-on;
regulator-always-on;
};
ldo1_reg: regulator@3 {
reg = <3>;
regulator-compatible = "ldo1";
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
ldo2_reg: regulator@4 {
reg = <4>;
regulator-compatible = "ldo2";
regulator-min-microvolt = <900000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
ldo3_reg: regulator@5 {
reg = <5>;
regulator-compatible = "ldo3";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
ldo4_reg: regulator@6 {
reg = <6>;
regulator-compatible = "ldo4";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
};
};
Documentation/devicetree/bindings/regulator/tps6586x.txt
浏览文件 @ 593d0a3e
......@@ -6,8 +6,17 @@ Required properties:
- interrupts: the interrupt outputs of the controller
- #gpio-cells: number of cells to describe a GPIO
- gpio-controller: mark the device as a GPIO controller
- regulators: list of regulators provided by this controller, must be named
after their hardware counterparts: sm[0-2], ldo[0-9] and ldo_rtc
- regulators: list of regulators provided by this controller, must have
property "regulator-compatible" to match their hardware counterparts:
sm[0-2], ldo[0-9] and ldo_rtc
- sm0-supply: The input supply for the SM0.
- sm1-supply: The input supply for the SM1.
- sm2-supply: The input supply for the SM2.
- vinldo01-supply: The input supply for the LDO1 and LDO2
- vinldo23-supply: The input supply for the LDO2 and LDO3
- vinldo4-supply: The input supply for the LDO4
- vinldo678-supply: The input supply for the LDO6, LDO7 and LDO8
- vinldo9-supply: The input supply for the LDO9
Each regulator is defined using the standard binding for regulators.
......@@ -21,75 +30,113 @@ Example:
#gpio-cells = <2>;
gpio-controller;
sm0-supply = <&some_reg>;
sm1-supply = <&some_reg>;
sm2-supply = <&some_reg>;
vinldo01-supply = <...>;
vinldo23-supply = <...>;
vinldo4-supply = <...>;
vinldo678-supply = <...>;
vinldo9-supply = <...>;
regulators {
sm0_reg: sm0 {
#address-cells = <1>;
#size-cells = <0>;
sm0_reg: regulator@0 {
reg = <0>;
regulator-compatible = "sm0";
regulator-min-microvolt = < 725000>;
regulator-max-microvolt = <1500000>;
regulator-boot-on;
regulator-always-on;
};
sm1_reg: sm1 {
sm1_reg: regulator@1 {
reg = <1>;
regulator-compatible = "sm1";
regulator-min-microvolt = < 725000>;
regulator-max-microvolt = <1500000>;
regulator-boot-on;
regulator-always-on;
};
sm2_reg: sm2 {
sm2_reg: regulator@2 {
reg = <2>;
regulator-compatible = "sm2";
regulator-min-microvolt = <3000000>;
regulator-max-microvolt = <4550000>;
regulator-boot-on;
regulator-always-on;
};
ldo0_reg: ldo0 {
ldo0_reg: regulator@3 {
reg = <3>;
regulator-compatible = "ldo0";
regulator-name = "PCIE CLK";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
};
ldo1_reg: ldo1 {
ldo1_reg: regulator@4 {
reg = <4>;
regulator-compatible = "ldo1";
regulator-min-microvolt = < 725000>;
regulator-max-microvolt = <1500000>;
};
ldo2_reg: ldo2 {
ldo2_reg: regulator@5 {
reg = <5>;
regulator-compatible = "ldo2";
regulator-min-microvolt = < 725000>;
regulator-max-microvolt = <1500000>;
};
ldo3_reg: ldo3 {
ldo3_reg: regulator@6 {
reg = <6>;
regulator-compatible = "ldo3";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
ldo4_reg: ldo4 {
ldo4_reg: regulator@7 {
reg = <7>;
regulator-compatible = "ldo4";
regulator-min-microvolt = <1700000>;
regulator-max-microvolt = <2475000>;
};
ldo5_reg: ldo5 {
ldo5_reg: regulator@8 {
reg = <8>;
regulator-compatible = "ldo5";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
ldo6_reg: ldo6 {
ldo6_reg: regulator@9 {
reg = <9>;
regulator-compatible = "ldo6";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
ldo7_reg: ldo7 {
ldo7_reg: regulator@10 {
reg = <10>;
regulator-compatible = "ldo7";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
ldo8_reg: ldo8 {
ldo8_reg: regulator@11 {
reg = <11>;
regulator-compatible = "ldo8";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
ldo9_reg: ldo9 {
ldo9_reg: regulator@12 {
reg = <12>;
regulator-compatible = "ldo9";
regulator-min-microvolt = <1250000>;
regulator-max-microvolt = <3300000>;
};
......
Documentation/devicetree/bindings/regulator/twl-regulator.txt
浏览文件 @ 593d0a3e
......@@ -15,7 +15,6 @@ For twl6030 regulators/LDOs
- "ti,twl6030-vusb" for VUSB LDO
- "ti,twl6030-v1v8" for V1V8 LDO
- "ti,twl6030-v2v1" for V2V1 LDO
- "ti,twl6030-clk32kg" for CLK32KG RESOURCE
- "ti,twl6030-vdd1" for VDD1 SMPS
- "ti,twl6030-vdd2" for VDD2 SMPS
- "ti,twl6030-vdd3" for VDD3 SMPS
......
Documentation/devicetree/bindings/rtc/dw-apb.txt 0 → 100644
浏览文件 @ 593d0a3e
* Designware APB timer
Required properties:
- compatible: "snps,dw-apb-timer-sp" or "snps,dw-apb-timer-osc"
- reg: physical base address of the controller and length of memory mapped
region.
- interrupts: IRQ line for the timer.
- clock-frequency: The frequency in HZ of the timer.
- clock-freq: For backwards compatibility with picoxcell
Example:
timer1: timer@ffc09000 {
compatible = "snps,dw-apb-timer-sp";
interrupts = <0 168 4>;
clock-frequency = <200000000>;
reg = <0xffc09000 0x1000>;
};
timer2: timer@ffd00000 {
compatible = "snps,dw-apb-timer-osc";
interrupts = <0 169 4>;
clock-frequency = <200000000>;
reg = <0xffd00000 0x1000>;
};
Documentation/devicetree/bindings/rtc/stmp3xxx-rtc.txt 0 → 100644
浏览文件 @ 593d0a3e
* STMP3xxx/i.MX28 Time Clock controller
Required properties:
- compatible: should be one of the following.
* "fsl,stmp3xxx-rtc"
- reg: physical base address of the controller and length of memory mapped
region.
- interrupts: rtc alarm interrupt
Example:
rtc@80056000 {
compatible = "fsl,imx28-rtc", "fsl,stmp3xxx-rtc";
reg = <0x80056000 2000>;
interrupts = <29>;
};
Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt
浏览文件 @ 593d0a3e
......@@ -17,6 +17,6 @@ ecspi@70010000 {
reg = <0x70010000 0x4000>;
interrupts = <36>;
fsl,spi-num-chipselects = <2>;
cs-gpios = <&gpio3 24 0>, /* GPIO4_24 */
<&gpio3 25 0>; /* GPIO4_25 */
cs-gpios = <&gpio3 24 0>, /* GPIO3_24 */
<&gpio3 25 0>; /* GPIO3_25 */
};
Documentation/devicetree/bindings/spi/spi-orion.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/devicetree/bindings/spi/spi-samsung.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/devicetree/bindings/usb/ci13xxx-imx.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/devicetree/bindings/usb/mxs-phy.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/devicetree/bindings/watchdog/omap-wdt.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/hid/uhid.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/hwmon/coretemp
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/hwmon/da9052 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/hwmon/hih6130 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/i2c/busses/i2c-i801
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/i2c/busses/i2c-piix4
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/i2c/writing-clients
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/kdump/kdump.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/networking/bridge.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/networking/can.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/networking/s2io.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/networking/stmmac.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/networking/vxge.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/nfc/nfc-hci.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/power/devices.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/power/swsusp.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/prctl/no_new_privs.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/ramoops.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/sound/alsa/hdspm.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/usb/mass-storage.txt 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/virtual/kvm/msr.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/vm/frontswap.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/w1/slaves/w1_ds28e04 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/workqueue.txt
浏览文件 @ 593d0a3e
此差异已折叠。
Documentation/x86/boot.txt
浏览文件 @ 593d0a3e
此差异已折叠。
MAINTAINERS
浏览文件 @ 593d0a3e
此差异已折叠。
Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/alpha/kernel/pci.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/aks-cdu.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/armada-370-xp.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/db8500.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/ea3250.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/evk-pro3.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/ge863-pro3.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/highbank.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx23-evk.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx23-olinuxino.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx23-stmp378x_devb.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx23.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx27-3ds.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28-apx4devkit.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28-cfa10036.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28-evk.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28-m28evk.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28-tx28.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx31-bug.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx31.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx6q-arm2.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/imx6q.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/lpc32xx.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap2.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap2420-h4.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap3-beagle.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap3-evm.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap4-panda.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap4-sdp.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap4-var_som.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap5-evm.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/phy3250.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/snowball.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/socfpga_cyclone5.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear1310-evb.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear1310.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear1340-evb.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear1340.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear13xx.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear300-evb.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear300.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear310-evb.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear310.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear320-evb.dts
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear320.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear3xx.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/spear600.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/tegra20-whistler.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/tegra20.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/tegra30.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/vexpress-v2m.dtsi
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/exynos_defconfig 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/lpc32xx_defconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/mvebu_defconfig 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/mxs_defconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/socfpga_defconfig 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/configs/tegra_defconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/include/asm/atomic.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/include/asm/domain.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/include/asm/futex.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/include/asm/mach/irq.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/include/asm/thread_info.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/bios32.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/fiq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/kprobes-test-arm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/kprobes-thumb.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/perf_event.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/ptrace.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/signal.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/signal.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/Makefile.boot
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91rm9200.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9260.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9261.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9263.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9g45.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9rl.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91sam9x5.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/at91x40.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-1arm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-carmeva.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-cpu9krea.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-cpuat91.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-csb337.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-csb637.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-dt.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-eb01.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-eb9200.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-ecbat91.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-eco920.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-foxg20.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-gsia18s.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-kafa.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-kb9202.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-rm9200dk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-rm9200ek.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-rsi-ews.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/board-yl-9200.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/generic.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/gpio.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_spi.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-at91/include/mach/at91_ssc.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-at91/include/mach/entry-macro.S 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-at91/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-clps711x/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-clps711x/p720t.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-davinci/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-davinci/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-davinci/cp_intc.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-davinci/include/mach/dm365.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-davinci/include/mach/dm646x.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-davinci/pm_domain.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ep93xx/edb93xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ep93xx/soc.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/mach-nuri.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/mach-origen.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/pm_domains.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/pmu.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-exynos/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-highbank/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-highbank/clock.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-highbank/core.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-highbank/highbank.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-highbank/smc.S 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx1.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx21.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx25.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx27.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx31.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx35.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx51-imx53.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-imx6q.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/clk-pllv2.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/crm-regs-imx5.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx21.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx25.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx27.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx31.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx35.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx51.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/devices-imx53.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/ehci-imx25.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/ehci-imx35.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/ehci-imx5.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/hotplug.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/imx27-dt.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/imx31-dt.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/imx51-dt.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/imx53-dt.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-apf9328.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-cpuimx27.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-cpuimx35.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-cpuimx51sd.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-imx27ipcam.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-imx6q.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx1ads.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx21ads.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx25_3ds.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx27_3ds.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx27ads.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx31_3ds.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx31ads.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx31lilly.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx31lite.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx35_3ds.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx51_3ds.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx53_ard.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx53_evk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx53_loco.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mx53_smd.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-mxt_td60.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-pca100.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-pcm037.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-pcm038.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-pcm043.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-qong.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-scb9328.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mach-vpr200.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx1.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx21.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx25.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx27.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx3.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mm-imx5.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mx31lilly-db.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mx31lite-db.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/mx51_efika.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-imx/pm-imx5.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-integrator/core.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-kirkwood/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-lpc32xx/Kconfig 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-lpc32xx/Makefile.boot
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-lpc32xx/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-lpc32xx/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-lpc32xx/phy3250.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-lpc32xx/serial.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mmp/include/mach/gpio-pxa.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-mmp/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/Kconfig 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/Makefile 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/Makefile.boot 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/armada-370-xp.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/common.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/include/mach/armada-370-xp.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/include/mach/timex.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/include/mach/uncompress.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/irq-armada-370-xp.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mvebu/system-controller.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/Makefile.boot
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/devices-mx23.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/devices-mx28.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/mach-apx4devkit.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/mach-mxs.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-mxs/module-tx28.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-nomadik/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-nomadik/clock.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-nomadik/cpu-8815.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-nomadik/i2c-8815nhk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-generic.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-palmte.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-palmtt.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-palmz71.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/board-sx1.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/clock_data.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/include/mach/usb.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/timer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap1/usb.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/am35xx-emac.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-2430sdp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-4430sdp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-cm-t35.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-flash.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-generic.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-n8x0.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clock.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clock33xx_data.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clockdomain.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clockdomain33xx.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/clockdomains33xx_data.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cm-regbits-33xx.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cm.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cm33xx.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cm33xx.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cminst44xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cminst44xx.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/common.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/control.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/control.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cpuidle34xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/cpuidle44xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/devices.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/dpll3xxx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/drm.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/dsp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/hdq1w.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/id.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/io.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/iomap.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/mailbox.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/msdi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/mux.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap-headsmp.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap-hotplug.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap-iommu.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap-smp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap4-common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap_hwmod.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap_l3_noc.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/omap_l3_smx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/opp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/pm.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/pm34xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/powerdomain.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/powerdomain.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/powerdomain33xx.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/powerdomains33xx_data.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prcm-common.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prcm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm-regbits-33xx.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm2xxx_3xxx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm2xxx_3xxx.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm33xx.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm33xx.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm44xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm44xx.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/prm_common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/serial.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/sr_device.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/timer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/twl-common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/usb-fs.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-omap2/usb-musb.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/usb-tusb6010.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/voltage.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-omap2/voltagedomains33xx_data.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-orion5x/include/mach/io.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-picoxcell/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-picoxcell/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-picoxcell/common.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-prima2/include/mach/gpio.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-pxa/hx4700.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-rpc/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/common-smdk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/include/mach/bast-pmu.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-s3c24xx/mach-gta02.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/mach-qt2410.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/mach-rx1950.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/pm-s3c2410.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/pm-s3c2412.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/s3c2412.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/s3c244x.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c24xx/setup-ts.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c64xx/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s3c64xx/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5p64x0/dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5p64x0/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pc100/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pc100/dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pc100/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pv210/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pv210/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pv210/mach-aquila.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pv210/mach-goni.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-s5pv210/setup-spi.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-shmobile/platsmp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-socfpga/Makefile 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-socfpga/Makefile.boot 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-socfpga/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-socfpga/include/mach/uncompress.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-socfpga/socfpga.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear13xx/spear1310.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear13xx/spear1340.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear13xx/spear13xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear3xx/spear300.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear3xx/spear310.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear3xx/spear320.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear3xx/spear3xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-spear6xx/spear6xx.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/Makefile.boot
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/apbio.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/apbio.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/board-paz00.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/board-seaboard-pinmux.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-tegra/board-seaboard.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-tegra/board-seaboard.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-tegra/board.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/cpu-tegra.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/cpuidle.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/pcie.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/powergate.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/reset.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/sleep.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/tegra2_clocks.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/timer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-tegra/usb_phy.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-u300/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-u300/clock.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-u300/clock.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-u300/core.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-u300/timer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ux500/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ux500/board-mop500.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ux500/board-mop500.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ux500/cpu-db8500.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-ux500/timer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-versatile/core.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-versatile/pci.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vexpress/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vexpress/ct-ca9x4.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vexpress/include/mach/clkdev.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-vexpress/v2m.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vt8500/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vt8500/bv07.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vt8500/include/mach/restart.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vt8500/include/mach/system.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/mach-vt8500/restart.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mach-vt8500/wm8505_7in.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mm/dma-mapping.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mm/mm.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/net/bpf_jit_32.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/net/bpf_jit_32.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/3ds_debugboard.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/avic.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/cpuidle.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/epit.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/include/mach/cpuidle.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/time.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-mxc/tzic.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/counter_32k.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/include/plat/omap54xx.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/include/plat/omap730.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/plat-omap/include/plat/omap850.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/plat-omap/mailbox.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-omap/usb.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/plat-orion/common.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-pxa/ssp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-s3c24xx/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/adc.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/devs.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/dma-ops.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/include/plat/pd.h 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/plat-samsung/pd.c 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/arm/plat-samsung/pwm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/s3c-dma-ops.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-samsung/s5p-clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-spear/pl080.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-spear/restart.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-spear/shirq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-versatile/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/arm/plat-versatile/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/include/asm/context.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/include/asm/dpmc.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/include/asm/gpio.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/include/asm/irq.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/include/asm/traps.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/kernel/bfin_dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/kernel/dma-mapping.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-bf609/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-bf609/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-bf609/clock.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-bf609/ints-priority.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-bf609/pm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-common/cpufreq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-common/entry.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/blackfin/mach-common/pm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/boot/dts/evmc6678.dts 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/boot/dts/tms320c6678.dtsi 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/configs/evmc6678_defconfig 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/include/asm/irq.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/kernel/irq.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/kernel/setup.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/kernel/signal.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/kernel/soc.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/platforms/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/platforms/megamod-pic.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/c6x/platforms/plldata.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/frv/mb93090-mb00/pci-vdk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/include/asm/pgtable.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/include/asm/uaccess.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/kernel/setup.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/kernel/signal.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/kernel/time.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/h8300/mm/init.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/hexagon/kernel/smp.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/include/asm/iommu.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/include/asm/kvm.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/kernel/ia64_ksyms.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/kernel/pci-dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/kvm/Kconfig
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/kvm/vmm.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/mm/fault.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/ia64/pci/pci.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/boot/compressed/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/boot/compressed/misc.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/include/asm/ptrace.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/include/asm/smp.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/kernel/ptrace.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m32r/kernel/signal.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/Kconfig.bus
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/Kconfig.cpu
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/dma.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/gpio.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/io_mm.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m520xsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m523xsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m525xsim.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m527xsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m528xsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m532xsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m5441xsim.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m54xxacr.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m54xxpci.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/m54xxsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/mcfclk.h 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/mcfgpio.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/mcfsim.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/mcftimer.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/mcfuart.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/include/asm/pci.h
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/kernel/Makefile
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/kernel/dma.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/kernel/entry.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/kernel/entry_mm.S 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/m68k/kernel/entry_no.S 已删除 100644 → 0
浏览文件 @ 50e90041
此差异已折叠。
arch/m68k/kernel/module.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/kernel/pcibios.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/mm/memory.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/clk.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/gpio.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/head.S
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/intc-525x.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m5206.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m520x.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m523x.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m5249.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m525x.c 0 → 100644
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m5272.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m527x.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m528x.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m5307.c
浏览文件 @ 593d0a3e
此差异已折叠。
arch/m68k/platform/coldfire/m532x.c
浏览文件 @ 593d0a3e
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或