Skip to content

L
linux
Commit 206c59d1 authored by Johannes Berg's avatar Johannes Berg
Browse files
Options

Merge remote-tracking branch 'net-next/master' into mac80211-next 

Merge back net-next to get wireless driver changes (from Kalle)
to be able to create the API change across all trees properly.
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
parents 5ec596c4 c3eee1fb
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 37177 additions and 31121 deletions

Too many changes to show.
Plain diff Email patch

To preserve performance only 1000 of 1000+ files are displayed.

CREDITS
View file @ 206c59d1
......@@ -2049,6 +2049,10 @@ D: pirq addr, CS5535 alsa audio driver
S: Gurgaon, India
S: Kuala Lumpur, Malaysia
N: Mohit Kumar
D: ST Microelectronics SPEAr13xx PCI host bridge driver
D: Synopsys Designware PCI host bridge driver
N: Gabor Kuti
M: seasons@falcon.sch.bme.hu
M: seasons@makosteszta.sote.hu
......@@ -3705,6 +3709,13 @@ N: Dirk Verworner
D: Co-author of German book ``Linux-Kernel-Programmierung''
D: Co-founder of Berlin Linux User Group
N: Andrew Victor
E: linux@maxim.org.za
W: http://maxim.org.za/at91_26.html
D: First maintainer of Atmel ARM-based SoC, aka AT91
D: Introduced support for at91rm9200, the first chip of AT91 family
S: South Africa
N: Riku Voipio
E: riku.voipio@iki.fi
D: Author of PCA9532 LED and Fintek f75375s hwmon driver
......
Documentation/ABI/testing/sysfs-block-dm
View file @ 206c59d1
......@@ -23,3 +23,25 @@ Description: Device-mapper device suspend state.
Contains the value 1 while the device is suspended.
Otherwise it contains 0. Read-only attribute.
Users: util-linux, device-mapper udev rules
What: /sys/block/dm-<num>/dm/rq_based_seq_io_merge_deadline
Date: March 2015
KernelVersion: 4.1
Contact: dm-devel@redhat.com
Description: Allow control over how long a request that is a
reasonable merge candidate can be queued on the request
queue. The resolution of this deadline is in
microseconds (ranging from 1 to 100000 usecs).
Setting this attribute to 0 (the default) will disable
request-based DM's merge heuristic and associated extra
accounting. This attribute is not applicable to
bio-based DM devices so it will only ever report 0 for
them.
What: /sys/block/dm-<num>/dm/use_blk_mq
Date: March 2015
KernelVersion: 4.1
Contact: dm-devel@redhat.com
Description: Request-based Device-mapper blk-mq I/O path mode.
Contains the value 1 if the device is using blk-mq.
Otherwise it contains 0. Read-only attribute.
Documentation/ABI/testing/sysfs-bus-pci-drivers-janz-cmodio 0 → 100644
View file @ 206c59d1
What: /sys/bus/pci/drivers/janz-cmodio/.../modulbus_number
Date: May 2010
KernelVersion: 2.6.35
Contact: Ira W. Snyder <ira.snyder@gmail.com>
Description:
Value representing the HEX switch S2 of the janz carrier board CMOD-IO or CAN-PCI2
Read-only: value of the configuration switch (0..15)
Documentation/ABI/testing/sysfs-class-mtd
View file @ 206c59d1
......@@ -222,3 +222,13 @@ Description:
The number of blocks that are marked as reserved, if any, in
this partition. These are typically used to store the in-flash
bad block table (BBT).
What: /sys/class/mtd/mtdX/offset
Date: March 2015
KernelVersion: 4.1
Contact: linux-mtd@lists.infradead.org
Description:
For a partition, the offset of that partition from the start
of the master device in bytes. This attribute is absent on
main devices, so it can be used to distinguish between
partitions and devices that aren't partitions.
Documentation/ABI/testing/sysfs-class-net
View file @ 206c59d1
......@@ -39,6 +39,25 @@ Description:
Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC
address.
What: /sys/class/net/<bridge iface>/bridge/group_fwd_mask
Date: January 2012
KernelVersion: 3.2
Contact: netdev@vger.kernel.org
Description:
Bitmask to allow forwarding of link local frames with address
01-80-C2-00-00-0X on a bridge device. Only values that set bits
not matching BR_GROUPFWD_RESTRICTED in net/bridge/br_private.h
allowed.
Default value 0 does not forward any link local frames.
Restricted bits:
0: 01-80-C2-00-00-00 Bridge Group Address used for STP
1: 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
2: 01-80-C2-00-00-02 (Link Aggregation) 802.3ad
Any values not setting these bits can be used. Take special
care when forwarding control frames e.g. 802.1X-PAE or LLDP.
What: /sys/class/net/<iface>/broadcast
Date: April 2005
KernelVersion: 2.6.12
......
Documentation/ABI/testing/sysfs-class-net-janz-ican3 0 → 100644
View file @ 206c59d1
What: /sys/class/net/<iface>/termination
Date: May 2010
KernelVersion: 2.6.35
Contact: Ira W. Snyder <ira.snyder@gmail.com>
Description:
Value representing the can bus termination
Default: 1 (termination active)
Reading: get actual termination state
Writing: set actual termination state (0=no termination, 1=termination active)
What: /sys/class/net/<iface>/fwinfo
Date: May 2015
KernelVersion: 3.19
Contact: Andreas Gröger <andreas24groeger@gmail.com>
Description:
Firmware stamp of ican3 module
Read-only: 32 byte string identification of the ICAN3 module
(known values: "JANZ-ICAN3 ICANOS 1.xx", "JANZ-ICAN3 CAL/CANopen 1.xx")
Documentation/ABI/testing/sysfs-devices-system-cpu
View file @ 206c59d1
......@@ -162,7 +162,7 @@ Description: Discover CPUs in the same CPU frequency coordination domain
What: /sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1}
Date: August 2008
KernelVersion: 2.6.27
Contact: discuss@x86-64.org
Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Description: Disable L3 cache indices
These files exist in every CPU's cache/index3 directory. Each
......
Documentation/ABI/testing/sysfs-driver-toshiba_acpi
View file @ 206c59d1
......@@ -8,9 +8,11 @@ Description: This file controls the keyboard backlight operation mode, valid
* 0x2 -> AUTO (also called TIMER)
* 0x8 -> ON
* 0x10 -> OFF
Note that the kernel 3.16 onwards this file accepts all listed
Note that from kernel 3.16 onwards this file accepts all listed
parameters, kernel 3.15 only accepts the first two (FN-Z and
AUTO).
Also note that toggling this value on type 1 devices, requires
a reboot for changes to take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
......@@ -67,15 +69,72 @@ Description: This file shows the current keyboard backlight type,
* 2 -> Type 2, supporting modes TIMER, ON and OFF
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Sleep & Charge charging mode, which
can be:
* 0 -> Disabled (0x00)
* 1 -> Alternate (0x09)
* 2 -> Auto (0x21)
* 3 -> Typical (0x11)
Note that from kernel 4.1 onwards this file accepts all listed
values, kernel 4.0 only supports the first three.
Note that this feature only works when connected to power, if
you want to use it under battery, see the entry named
"sleep_functions_on_battery"
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Sleep Functions under battery, and
set the level at which point they will be disabled, accepted
values can be:
* 0 -> Disabled
* 1-100 -> Battery level to disable sleep functions
Currently it prints two values, the first one indicates if the
feature is enabled or disabled, while the second one shows the
current battery level set.
Note that when the value is set to disabled, the sleep function
will only work when connected to power.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the USB Rapid Charge state, which can be:
* 0 -> Disabled
* 1 -> Enabled
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_music
Date: January 23, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the Sleep & Music state, which values can be:
* 0 -> Disabled
* 1 -> Enabled
Note that this feature only works when connected to power, if
you want to use it under battery, see the entry named
"sleep_functions_on_battery"
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file shows the current version of the driver
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the state of the internal fan, valid
values are:
......@@ -83,8 +142,8 @@ Description: This file controls the state of the internal fan, valid
* 1 -> ON
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_function_keys
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls the Special Functions (hotkeys) operation
mode, valid values are:
......@@ -94,21 +153,29 @@ Description: This file controls the Special Functions (hotkeys) operation
and the hotkeys are accessed via FN-F{1-12}.
In the "Special Functions" mode, the F{1-12} keys trigger the
hotkey and the F{1-12} keys are accessed via FN-F{1-12}.
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls whether the laptop should turn ON whenever
the LID is opened, valid values are:
* 0 -> Disabled
* 1 -> Enabled
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_three
Date: February, 2015
KernelVersion: 3.20
Date: February 12, 2015
KernelVersion: 4.0
Contact: Azael Avalos <coproscefalo@gmail.com>
Description: This file controls whether the USB 3 functionality, valid
values are:
Description: This file controls the USB 3 functionality, valid values are:
* 0 -> Disabled (Acts as a regular USB 2)
* 1 -> Enabled (Full USB 3 functionality)
Note that toggling this value requires a reboot for changes to
take effect.
Users: KToshiba
Documentation/ABI/testing/sysfs-platform-dell-laptop 0 → 100644
View file @ 206c59d1
What: /sys/class/leds/dell::kbd_backlight/als_enabled
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to control the automatic keyboard
illumination mode on some systems that have an ambient
light sensor. Write 1 to this file to enable the auto
mode, 0 to disable it.
What: /sys/class/leds/dell::kbd_backlight/als_setting
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to specifiy the on/off threshold value,
as reported by the ambient light sensor.
What: /sys/class/leds/dell::kbd_backlight/start_triggers
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to control the input triggers that
turn on the keyboard backlight illumination that is
disabled because of inactivity.
Read the file to see the triggers available. The ones
enabled are preceded by '+', those disabled by '-'.
To enable a trigger, write its name preceded by '+' to
this file. To disable a trigger, write its name preceded
by '-' instead.
For example, to enable the keyboard as trigger run:
echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
To disable it:
echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
Note that not all the available triggers can be configured.
What: /sys/class/leds/dell::kbd_backlight/stop_timeout
Date: December 2014
KernelVersion: 3.19
Contact: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Pali Rohár <pali.rohar@gmail.com>
Description:
This file allows to specify the interval after which the
keyboard illumination is disabled because of inactivity.
The timeouts are expressed in seconds, minutes, hours and
days, for which the symbols are 's', 'm', 'h' and 'd'
respectively.
To configure the timeout, write to this file a value along
with any the above units. If no unit is specified, the value
is assumed to be expressed in seconds.
For example, to set the timeout to 10 minutes run:
echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout
Note that when this file is read, the returned value might be
expressed in a different unit than the one used when the timeout
was set.
Also note that only some timeouts are supported and that
some systems might fall back to a specific timeout in case
an invalid timeout is written to this file.
Documentation/CodingStyle
View file @ 206c59d1
......@@ -13,7 +13,7 @@ and NOT read it. Burn them, it's a great symbolic gesture.
Anyway, here goes:
Chapter 1: Indentation
Chapter 1: Indentation
Tabs are 8 characters, and thus indentations are also 8 characters.
There are heretic movements that try to make indentations 4 (or even 2!)
......@@ -56,7 +56,6 @@ instead of "double-indenting" the "case" labels. E.g.:
break;
}
Don't put multiple statements on a single line unless you have
something to hide:
......@@ -156,25 +155,25 @@ comments on.
Do not unnecessarily use braces where a single statement will do.
if (condition)
action();
if (condition)
action();
and
if (condition)
do_this();
else
do_that();
if (condition)
do_this();
else
do_that();
This does not apply if only one branch of a conditional statement is a single
statement; in the latter case use braces in both branches:
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
3.1: Spaces
......@@ -186,8 +185,11 @@ although they are not required in the language, as in: "sizeof info" after
"struct fileinfo info;" is declared).
So use a space after these keywords:
if, switch, case, for, do, while
but not with sizeof, typeof, alignof, or __attribute__. E.g.,
s = sizeof(struct file);
Do not add spaces around (inside) parenthesized expressions. This example is
......@@ -209,12 +211,15 @@ such as any of these:
= + - < > * / % | & ^ <= >= == != ? :
but no space after unary operators:
& * + - ~ ! sizeof typeof alignof __attribute__ defined
no space before the postfix increment & decrement unary operators:
++ --
no space after the prefix increment & decrement unary operators:
++ --
and no space around the '.' and "->" structure member operators.
......@@ -268,13 +273,11 @@ See chapter 6 (Functions).
Chapter 5: Typedefs
Please don't use things like "vps_t".
It's a _mistake_ to use typedef for structures and pointers. When you see a
vps_t a;
in the source, what does it mean?
In contrast, if it says
struct virtual_container *a;
......@@ -372,11 +375,11 @@ In source files, separate functions with one blank line. If the function is
exported, the EXPORT* macro for it should follow immediately after the closing
function brace line. E.g.:
int system_is_up(void)
{
return system_state == SYSTEM_RUNNING;
}
EXPORT_SYMBOL(system_is_up);
int system_is_up(void)
{
return system_state == SYSTEM_RUNNING;
}
EXPORT_SYMBOL(system_is_up);
In function prototypes, include parameter names with their data types.
Although this is not required by the C language, it is preferred in Linux
......@@ -405,34 +408,34 @@ The rationale for using gotos is:
modifications are prevented
- saves the compiler work to optimize redundant code away ;)
int fun(int a)
{
int result = 0;
char *buffer;
buffer = kmalloc(SIZE, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
if (condition1) {
while (loop1) {
...
int fun(int a)
{
int result = 0;
char *buffer;
buffer = kmalloc(SIZE, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
if (condition1) {
while (loop1) {
...
}
result = 1;
goto out_buffer;
}
result = 1;
goto out_buffer;
...
out_buffer:
kfree(buffer);
return result;
}
...
out_buffer:
kfree(buffer);
return result;
}
A common type of bug to be aware of it "one err bugs" which look like this:
err:
kfree(foo->bar);
kfree(foo);
return ret;
err:
kfree(foo->bar);
kfree(foo);
return ret;
The bug in this code is that on some exit paths "foo" is NULL. Normally the
fix for this is to split it up into two error labels "err_bar:" and "err_foo:".
......@@ -503,9 +506,9 @@ values. To do the latter, you can stick the following in your .emacs file:
(defun c-lineup-arglist-tabs-only (ignored)
"Line up argument lists by tabs, not spaces"
(let* ((anchor (c-langelem-pos c-syntactic-element))
(column (c-langelem-2nd-pos c-syntactic-element))
(offset (- (1+ column) anchor))
(steps (floor offset c-basic-offset)))
(column (c-langelem-2nd-pos c-syntactic-element))
(offset (- (1+ column) anchor))
(steps (floor offset c-basic-offset)))
(* (max steps 1)
c-basic-offset)))
......@@ -612,7 +615,7 @@ have a reference count on it, you almost certainly have a bug.
Names of macros defining constants and labels in enums are capitalized.
#define CONSTANT 0x12345
#define CONSTANT 0x12345
Enums are preferred when defining several related constants.
......@@ -623,28 +626,28 @@ Generally, inline functions are preferable to macros resembling functions.
Macros with multiple statements should be enclosed in a do - while block:
#define macrofun(a, b, c) \
do { \
if (a == 5) \
do_this(b, c); \
} while (0)
#define macrofun(a, b, c) \
do { \
if (a == 5) \
do_this(b, c); \
} while (0)
Things to avoid when using macros:
1) macros that affect control flow:
#define FOO(x) \
do { \
if (blah(x) < 0) \
return -EBUGGERED; \
} while(0)
#define FOO(x) \
do { \
if (blah(x) < 0) \
return -EBUGGERED; \
} while(0)
is a _very_ bad idea. It looks like a function call but exits the "calling"
function; don't break the internal parsers of those who will read the code.
2) macros that depend on having a local variable with a magic name:
#define FOO(val) bar(index, val)
#define FOO(val) bar(index, val)
might look like a good thing, but it's confusing as hell when one reads the
code and it's prone to breakage from seemingly innocent changes.
......@@ -656,8 +659,8 @@ bite you if somebody e.g. turns FOO into an inline function.
must enclose the expression in parentheses. Beware of similar issues with
macros using parameters.
#define CONSTANT 0x4000
#define CONSTEXP (CONSTANT | 3)
#define CONSTANT 0x4000
#define CONSTEXP (CONSTANT | 3)
5) namespace collisions when defining local variables in macros resembling
functions:
......@@ -809,11 +812,11 @@ you should use, rather than explicitly coding some variant of them yourself.
For example, if you need to calculate the length of an array, take advantage
of the macro
#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
Similarly, if you need to calculate the size of some structure member, use
#define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
#define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
There are also min() and max() macros that do strict type checking if you
need them. Feel free to peruse that header file to see what else is already
......@@ -826,19 +829,19 @@ Some editors can interpret configuration information embedded in source files,
indicated with special markers. For example, emacs interprets lines marked
like this:
-*- mode: c -*-
-*- mode: c -*-
Or like this:
/*
Local Variables:
compile-command: "gcc -DMAGIC_DEBUG_FLAG foo.c"
End:
*/
/*
Local Variables:
compile-command: "gcc -DMAGIC_DEBUG_FLAG foo.c"
End:
*/
Vim interprets markers that look like this:
/* vim:set sw=8 noet */
/* vim:set sw=8 noet */
Do not include any of these in source files. People have their own personal
editor configurations, and your source files should not override them. This
......@@ -915,9 +918,9 @@ At the end of any non-trivial #if or #ifdef block (more than a few lines),
place a comment after the #endif on the same line, noting the conditional
expression used. For instance:
#ifdef CONFIG_SOMETHING
...
#endif /* CONFIG_SOMETHING */
#ifdef CONFIG_SOMETHING
...
#endif /* CONFIG_SOMETHING */
Appendix I: References
......
Documentation/DocBook/drm.tmpl
View file @ 206c59d1
......@@ -1293,7 +1293,7 @@ int max_width, max_height;</synopsis>
</para>
<para>
If a page flip can be successfully scheduled the driver must set the
<code>drm_crtc-&lt;fb</code> field to the new framebuffer pointed to
<code>drm_crtc-&gt;fb</code> field to the new framebuffer pointed to
by <code>fb</code>. This is important so that the reference counting
on framebuffers stays balanced.
</para>
......@@ -3979,6 +3979,11 @@ int num_ioctls;</synopsis>
!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_disable_interrupts
!Fdrivers/gpu/drm/i915/i915_irq.c intel_runtime_pm_enable_interrupts
</sect2>
<sect2>
<title>Intel GVT-g Guest Support(vGPU)</title>
!Pdrivers/gpu/drm/i915/i915_vgpu.c Intel GVT-g guest support
!Idrivers/gpu/drm/i915/i915_vgpu.c
</sect2>
</sect1>
<sect1>
<title>Display Hardware Handling</title>
......@@ -4046,6 +4051,17 @@ int num_ioctls;</synopsis>
<title>Frame Buffer Compression (FBC)</title>
!Pdrivers/gpu/drm/i915/intel_fbc.c Frame Buffer Compression (FBC)
!Idrivers/gpu/drm/i915/intel_fbc.c
</sect2>
<sect2>
<title>Display Refresh Rate Switching (DRRS)</title>
!Pdrivers/gpu/drm/i915/intel_dp.c Display Refresh Rate Switching (DRRS)
!Fdrivers/gpu/drm/i915/intel_dp.c intel_dp_set_drrs_state
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_enable
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_disable
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_invalidate
!Fdrivers/gpu/drm/i915/intel_dp.c intel_edp_drrs_flush
!Fdrivers/gpu/drm/i915/intel_dp.c intel_dp_drrs_init
</sect2>
<sect2>
<title>DPIO</title>
......@@ -4168,7 +4184,7 @@ int num_ioctls;</synopsis>
<sect2>
<title>Buffer Object Eviction</title>
<para>
This section documents the interface function for evicting buffer
This section documents the interface functions for evicting buffer
objects to make space available in the virtual gpu address spaces.
Note that this is mostly orthogonal to shrinking buffer objects
caches, which has the goal to make main memory (shared with the gpu
......@@ -4176,6 +4192,17 @@ int num_ioctls;</synopsis>
</para>
!Idrivers/gpu/drm/i915/i915_gem_evict.c
</sect2>
<sect2>
<title>Buffer Object Memory Shrinking</title>
<para>
This section documents the interface function for shrinking memory
usage of buffer object caches. Shrinking is used to make main memory
available. Note that this is mostly orthogonal to evicting buffer
objects, which has the goal to make space in gpu virtual address
spaces.
</para>
!Idrivers/gpu/drm/i915/i915_gem_shrinker.c
</sect2>
</sect1>
<sect1>
......
Documentation/DocBook/media/v4l/biblio.xml
View file @ 206c59d1
<bibliography>
<title>References</title>
<biblioentry id="eia608">
<abbrev>EIA&nbsp;608-B</abbrev>
<biblioentry id="cea608">
<abbrev>CEA&nbsp;608-E</abbrev>
<authorgroup>
<corpauthor>Electronic Industries Alliance (<ulink
url="http://www.eia.org">http://www.eia.org</ulink>)</corpauthor>
<corpauthor>Consumer Electronics Association (<ulink
url="http://www.ce.org">http://www.ce.org</ulink>)</corpauthor>
</authorgroup>
<title>EIA 608-B "Recommended Practice for Line 21 Data
Service"</title>
<title>CEA-608-E R-2014 "Line 21 Data Services"</title>
</biblioentry>
<biblioentry id="en300294">
......
Documentation/DocBook/media/v4l/compat.xml
View file @ 206c59d1
......@@ -2491,7 +2491,7 @@ that used it. It was originally scheduled for removal in 2.6.35.
</listitem>
<listitem>
<para>Added <constant>V4L2_EVENT_CTRL_CH_RANGE</constant> control event
changes flag. See <xref linkend="changes-flags"/>.</para>
changes flag. See <xref linkend="ctrl-changes-flags"/>.</para>
</listitem>
</orderedlist>
</section>
......
Documentation/DocBook/media/v4l/dev-sliced-vbi.xml
View file @ 206c59d1
......@@ -254,7 +254,7 @@ ETS&nbsp;300&nbsp;231, lsb first transmitted.</entry>
<row>
<entry><constant>V4L2_SLICED_CAPTION_525</constant></entry>
<entry>0x1000</entry>
<entry><xref linkend="eia608" /></entry>
<entry><xref linkend="cea608" /></entry>
<entry>NTSC line 21, 284 (second field 21)</entry>
<entry>Two bytes in transmission order, including parity
bit, lsb first transmitted.</entry>
......
Documentation/DocBook/media/v4l/media-ioc-enum-entities.xml
View file @ 206c59d1
......@@ -143,86 +143,28 @@
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>v4l</structfield></entry>
<entry><structfield>dev</structfield></entry>
<entry></entry>
<entry>Valid for V4L sub-devices and nodes only.</entry>
<entry>Valid for (sub-)devices that create a single device node.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>major</structfield></entry>
<entry>V4L device node major number. For V4L sub-devices with no
device node, set by the driver to 0.</entry>
<entry>Device node major number.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>minor</structfield></entry>
<entry>V4L device node minor number. For V4L sub-devices with no
device node, set by the driver to 0.</entry>
</row>
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>fb</structfield></entry>
<entry></entry>
<entry>Valid for frame buffer nodes only.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>major</structfield></entry>
<entry>Frame buffer device node major number.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>minor</structfield></entry>
<entry>Frame buffer device node minor number.</entry>
</row>
<row>
<entry></entry>
<entry>struct</entry>
<entry><structfield>alsa</structfield></entry>
<entry></entry>
<entry>Valid for ALSA devices only.</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>card</structfield></entry>
<entry>ALSA card number</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>device</structfield></entry>
<entry>ALSA device number</entry>
</row>
<row>
<entry></entry>
<entry></entry>
<entry>__u32</entry>
<entry><structfield>subdevice</structfield></entry>
<entry>ALSA sub-device number</entry>
</row>
<row>
<entry></entry>
<entry>int</entry>
<entry><structfield>dvb</structfield></entry>
<entry></entry>
<entry>DVB card number</entry>
<entry>Device node minor number.</entry>
</row>
<row>
<entry></entry>
<entry>__u8</entry>
<entry><structfield>raw</structfield>[180]</entry>
<entry><structfield>raw</structfield>[184]</entry>
<entry></entry>
<entry></entry>
</row>
......@@ -253,8 +195,24 @@
<entry>ALSA card</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB</constant></entry>
<entry>DVB card</entry>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_FE</constant></entry>
<entry>DVB frontend devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DEMUX</constant></entry>
<entry>DVB demux devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_DVR</constant></entry>
<entry>DVB DVR devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_CA</constant></entry>
<entry>DVB CAM devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_DEVNODE_DVB_NET</constant></entry>
<entry>DVB network devnode</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV</constant></entry>
......@@ -282,6 +240,10 @@
it in some digital video standard, with appropriate embedded timing
signals.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_T_V4L2_SUBDEV_TUNER</constant></entry>
<entry>TV and/or radio tuner</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/pixfmt-packed-rgb.xml
View file @ 206c59d1
......@@ -303,45 +303,6 @@ for a pixel lie next to each other in memory.</para>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
</row>
<row id="V4L2-PIX-FMT-BGR666">
<entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
<entry>'BGRH'</entry>
<entry></entry>
<entry>b<subscript>5</subscript></entry>
<entry>b<subscript>4</subscript></entry>
<entry>b<subscript>3</subscript></entry>
<entry>b<subscript>2</subscript></entry>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
<entry>g<subscript>5</subscript></entry>
<entry>g<subscript>4</subscript></entry>
<entry></entry>
<entry>g<subscript>3</subscript></entry>
<entry>g<subscript>2</subscript></entry>
<entry>g<subscript>1</subscript></entry>
<entry>g<subscript>0</subscript></entry>
<entry>r<subscript>5</subscript></entry>
<entry>r<subscript>4</subscript></entry>
<entry>r<subscript>3</subscript></entry>
<entry>r<subscript>2</subscript></entry>
<entry></entry>
<entry>r<subscript>1</subscript></entry>
<entry>r<subscript>0</subscript></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
<entry></entry>
</row>
<row id="V4L2-PIX-FMT-BGR24">
<entry><constant>V4L2_PIX_FMT_BGR24</constant></entry>
<entry>'BGR3'</entry>
......@@ -404,6 +365,46 @@ for a pixel lie next to each other in memory.</para>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
</row>
<row id="V4L2-PIX-FMT-BGR666">
<entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
<entry>'BGRH'</entry>
<entry></entry>
<entry>b<subscript>5</subscript></entry>
<entry>b<subscript>4</subscript></entry>
<entry>b<subscript>3</subscript></entry>
<entry>b<subscript>2</subscript></entry>
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
<entry>g<subscript>5</subscript></entry>
<entry>g<subscript>4</subscript></entry>
<entry></entry>
<entry>g<subscript>3</subscript></entry>
<entry>g<subscript>2</subscript></entry>
<entry>g<subscript>1</subscript></entry>
<entry>g<subscript>0</subscript></entry>
<entry>r<subscript>5</subscript></entry>
<entry>r<subscript>4</subscript></entry>
<entry>r<subscript>3</subscript></entry>
<entry>r<subscript>2</subscript></entry>
<entry></entry>
<entry>r<subscript>1</subscript></entry>
<entry>r<subscript>0</subscript></entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry></entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
</row>
<row id="V4L2-PIX-FMT-ABGR32">
<entry><constant>V4L2_PIX_FMT_ABGR32</constant></entry>
<entry>'AR24'</entry>
......
Documentation/DocBook/media/v4l/pixfmt-sgrbg8.xml
View file @ 206c59d1
......@@ -38,10 +38,10 @@ columns and rows.</para>
</row>
<row>
<entry>start&nbsp;+&nbsp;4:</entry>
<entry>R<subscript>10</subscript></entry>
<entry>B<subscript>11</subscript></entry>
<entry>R<subscript>12</subscript></entry>
<entry>B<subscript>13</subscript></entry>
<entry>B<subscript>10</subscript></entry>
<entry>G<subscript>11</subscript></entry>
<entry>B<subscript>12</subscript></entry>
<entry>G<subscript>13</subscript></entry>
</row>
<row>
<entry>start&nbsp;+&nbsp;8:</entry>
......@@ -52,10 +52,10 @@ columns and rows.</para>
</row>
<row>
<entry>start&nbsp;+&nbsp;12:</entry>
<entry>R<subscript>30</subscript></entry>
<entry>B<subscript>31</subscript></entry>
<entry>R<subscript>32</subscript></entry>
<entry>B<subscript>33</subscript></entry>
<entry>B<subscript>30</subscript></entry>
<entry>G<subscript>31</subscript></entry>
<entry>B<subscript>32</subscript></entry>
<entry>G<subscript>33</subscript></entry>
</row>
</tbody>
</tgroup>
......
Documentation/DocBook/media/v4l/pixfmt-srggb10p.xml
View file @ 206c59d1
......@@ -38,7 +38,7 @@
<title>Byte Order.</title>
<para>Each cell is one byte.
<informaltable frame="topbot" colsep="1" rowsep="1">
<tgroup cols="5" align="center" border="1">
<tgroup cols="5" align="center">
<colspec align="left" colwidth="2*" />
<tbody valign="top">
<row>
......
Documentation/DocBook/media/v4l/pixfmt-yuv420m.xml
View file @ 206c59d1
......@@ -29,12 +29,12 @@ and Cr planes have half as many pad bytes after their rows. In other
words, two Cx rows (including padding) is exactly as long as one Y row
(including padding).</para>
<para><constant>V4L2_PIX_FMT_NV12M</constant> is intended to be
<para><constant>V4L2_PIX_FMT_YUV420M</constant> is intended to be
used only in drivers and applications that support the multi-planar API,
described in <xref linkend="planar-apis"/>. </para>
<example>
<title><constant>V4L2_PIX_FMT_YVU420M</constant> 4 &times; 4
<title><constant>V4L2_PIX_FMT_YUV420M</constant> 4 &times; 4
pixel image</title>
<formalpara>
......
Documentation/DocBook/media/v4l/pixfmt.xml
View file @ 206c59d1
This diff is collapsed.
Documentation/DocBook/media/v4l/v4l2.xml
View file @ 206c59d1
......@@ -136,6 +136,7 @@ Remote Controller chapter.</contrib>
<year>2012</year>
<year>2013</year>
<year>2014</year>
<year>2015</year>
<holder>Bill Dirks, Michael H. Schimek, Hans Verkuil, Martin
Rubli, Andy Walls, Muralidharan Karicheri, Mauro Carvalho Chehab,
Pawel Osciak</holder>
......@@ -151,6 +152,14 @@ structs, ioctls) must be noted in more detail in the history chapter
(compat.xml), along with the possible impact on existing drivers and
applications. -->
<revision>
<revnumber>3.21</revnumber>
<date>2015-02-13</date>
<authorinitials>mcc</authorinitials>
<revremark>Fix documentation for media controller device nodes and add support for DVB device nodes.
Add support for Tuner sub-device.
</revremark>
</revision>
<revision>
<revnumber>3.19</revnumber>
<date>2014-12-05</date>
......
Documentation/DocBook/media/v4l/vidioc-cropcap.xml
View file @ 206c59d1
......@@ -59,6 +59,11 @@ constant except when switching the video standard. Remember this
switch can occur implicit when switching the video input or
output.</para>
<para>Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>
and use <constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>.</para>
<para>This ioctl must be implemented for video capture or output devices that
support cropping and/or scaling and/or have non-square pixels, and for overlay devices.</para>
......@@ -73,9 +78,7 @@ support cropping and/or scaling and/or have non-square pixels, and for overlay d
<entry>Type of the data stream, set by the application.
Only these types are valid here:
<constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant>,
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant> and
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> and
<constant>V4L2_BUF_TYPE_VIDEO_OVERLAY</constant>. See <xref linkend="v4l2-buf-type" />.</entry>
</row>
<row>
......
Documentation/DocBook/media/v4l/vidioc-dqevent.xml
View file @ 206c59d1
......@@ -64,7 +64,7 @@
<entry>__u32</entry>
<entry><structfield>type</structfield></entry>
<entry></entry>
<entry>Type of the event.</entry>
<entry>Type of the event, see <xref linkend="event-type" />.</entry>
</row>
<row>
<entry>union</entry>
......@@ -154,6 +154,113 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="event-type">
<title>Event Types</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_EVENT_ALL</constant></entry>
<entry>0</entry>
<entry>All events. V4L2_EVENT_ALL is valid only for
VIDIOC_UNSUBSCRIBE_EVENT for unsubscribing all events at once.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_VSYNC</constant></entry>
<entry>1</entry>
<entry>This event is triggered on the vertical sync.
This event has a &v4l2-event-vsync; associated with it.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_EOS</constant></entry>
<entry>2</entry>
<entry>This event is triggered when the end of a stream is reached.
This is typically used with MPEG decoders to report to the application
when the last of the MPEG stream has been decoded.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL</constant></entry>
<entry>3</entry>
<entry><para>This event requires that the <structfield>id</structfield>
matches the control ID from which you want to receive events.
This event is triggered if the control's value changes, if a
button control is pressed or if the control's flags change.
This event has a &v4l2-event-ctrl; associated with it. This struct
contains much of the same information as &v4l2-queryctrl; and
&v4l2-control;.</para>
<para>If the event is generated due to a call to &VIDIOC-S-CTRL; or
&VIDIOC-S-EXT-CTRLS;, then the event will <emphasis>not</emphasis> be sent to
the file handle that called the ioctl function. This prevents
nasty feedback loops. If you <emphasis>do</emphasis> want to get the
event, then set the <constant>V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK</constant>
flag.
</para>
<para>This event type will ensure that no information is lost when
more events are raised than there is room internally. In that
case the &v4l2-event-ctrl; of the second-oldest event is kept,
but the <structfield>changes</structfield> field of the
second-oldest event is ORed with the <structfield>changes</structfield>
field of the oldest event.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_FRAME_SYNC</constant></entry>
<entry>4</entry>
<entry>
<para>Triggered immediately when the reception of a
frame has begun. This event has a
&v4l2-event-frame-sync; associated with it.</para>
<para>If the hardware needs to be stopped in the case of a
buffer underrun it might not be able to generate this event.
In such cases the <structfield>frame_sequence</structfield>
field in &v4l2-event-frame-sync; will not be incremented. This
causes two consecutive frame sequence numbers to have n times
frame interval in between them.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_SOURCE_CHANGE</constant></entry>
<entry>5</entry>
<entry>
<para>This event is triggered when a source parameter change is
detected during runtime by the video device. It can be a
runtime resolution change triggered by a video decoder or the
format change happening on an input connector.
This event requires that the <structfield>id</structfield>
matches the input index (when used with a video device node)
or the pad index (when used with a subdevice node) from which
you want to receive events.</para>
<para>This event has a &v4l2-event-src-change; associated
with it. The <structfield>changes</structfield> bitfield denotes
what has changed for the subscribed pad. If multiple events
occurred before application could dequeue them, then the changes
will have the ORed value of all the events generated.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
<entry>6</entry>
<entry>
<para>Triggered whenever the motion detection state for one or more of the regions
changes. This event has a &v4l2-event-motion-det; associated with it.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_PRIVATE_START</constant></entry>
<entry>0x08000000</entry>
<entry>Base event number for driver-private events.</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="none" pgwide="1" id="v4l2-event-vsync">
<title>struct <structname>v4l2_event_vsync</structname></title>
<tgroup cols="3">
......@@ -177,7 +284,7 @@
<entry>__u32</entry>
<entry><structfield>changes</structfield></entry>
<entry></entry>
<entry>A bitmask that tells what has changed. See <xref linkend="changes-flags" />.</entry>
<entry>A bitmask that tells what has changed. See <xref linkend="ctrl-changes-flags" />.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -309,8 +416,8 @@
</tgroup>
</table>
<table pgwide="1" frame="none" id="changes-flags">
<title>Changes</title>
<table pgwide="1" frame="none" id="ctrl-changes-flags">
<title>Control Changes</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
......@@ -318,9 +425,9 @@
<entry><constant>V4L2_EVENT_CTRL_CH_VALUE</constant></entry>
<entry>0x0001</entry>
<entry>This control event was triggered because the value of the control
changed. Special case: if a button control is pressed, then this
event is sent as well, even though there is not explicit value
associated with a button control.</entry>
changed. Special cases: Volatile controls do no generate this event;
If a control has the <constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant>
flag set, then this event is sent as well, regardless its value.</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL_CH_FLAGS</constant></entry>
......
Documentation/DocBook/media/v4l/vidioc-g-crop.xml
View file @ 206c59d1
......@@ -70,6 +70,11 @@ structure or returns the &EINVAL; if cropping is not supported.</para>
<constant>VIDIOC_S_CROP</constant> ioctl with a pointer to this
structure.</para>
<para>Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>
and use <constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>.</para>
<para>The driver first adjusts the requested dimensions against
hardware limits, &ie; the bounds given by the capture/output window,
and it rounds to the closest possible values of horizontal and
......
Documentation/DocBook/media/v4l/vidioc-g-dv-timings.xml
View file @ 206c59d1
......@@ -318,10 +318,20 @@ can't generate such frequencies, then the flag will also be cleared.
</row>
<row>
<entry>V4L2_DV_FL_HALF_LINE</entry>
<entry>Specific to interlaced formats: if set, then field 1 (aka the odd field)
is really one half-line longer and field 2 (aka the even field) is really one half-line
shorter, so each field has exactly the same number of half-lines. Whether half-lines can be
detected or used depends on the hardware.
<entry>Specific to interlaced formats: if set, then the vertical frontporch
of field 1 (aka the odd field) is really one half-line longer and the vertical backporch
of field 2 (aka the even field) is really one half-line shorter, so each field has exactly
the same number of half-lines. Whether half-lines can be detected or used depends on
the hardware.
</entry>
</row>
<row>
<entry>V4L2_DV_FL_IS_CE_VIDEO</entry>
<entry>If set, then this is a Consumer Electronics (CE) video format.
Such formats differ from other formats (commonly called IT formats) in that if
R'G'B' encoding is used then by default the R'G'B' values use limited range
(i.e. 16-235) as opposed to full range (i.e. 0-255). All formats defined in CEA-861
except for the 640x480p59.94 format are CE formats.
</entry>
</row>
</tbody>
......
Documentation/DocBook/media/v4l/vidioc-g-fbuf.xml
View file @ 206c59d1
......@@ -240,9 +240,9 @@ where padding bytes after the last line of an image cross a system
page boundary. Capture devices may write padding bytes, the value is
undefined. Output devices ignore the contents of padding
bytes.</para><para>When the image format is planar the
<structfield>bytesperline</structfield> value applies to the largest
<structfield>bytesperline</structfield> value applies to the first
plane and is divided by the same factor as the
<structfield>width</structfield> field for any smaller planes. For
<structfield>width</structfield> field for the other planes. For
example the Cb and Cr planes of a YUV 4:2:0 image have half as many
padding bytes following each line as the Y plane. To avoid ambiguities
drivers must return a <structfield>bytesperline</structfield> value
......
Documentation/DocBook/media/v4l/vidioc-g-selection.xml
View file @ 206c59d1
......@@ -60,8 +60,8 @@
<para>To query the cropping (composing) rectangle set &v4l2-selection;
<structfield> type </structfield> field to the respective buffer type.
Do not use multiplanar buffers. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant>. Use
Do not use the multiplanar buffer types. Use <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE</constant>
instead of <constant>V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE</constant> and use
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT</constant> instead of
<constant>V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE</constant>. The next step is
setting the value of &v4l2-selection; <structfield>target</structfield> field
......
Documentation/DocBook/media/v4l/vidioc-g-sliced-vbi-cap.xml
View file @ 206c59d1
......@@ -205,7 +205,7 @@ ETS&nbsp;300&nbsp;231, lsb first transmitted.</entry>
<row>
<entry><constant>V4L2_SLICED_CAPTION_525</constant></entry>
<entry>0x1000</entry>
<entry><xref linkend="eia608" /></entry>
<entry><xref linkend="cea608" /></entry>
<entry>NTSC line 21, 284 (second field 21)</entry>
<entry>Two bytes in transmission order, including parity
bit, lsb first transmitted.</entry>
......
Documentation/DocBook/media/v4l/vidioc-querycap.xml
View file @ 206c59d1
......@@ -102,10 +102,10 @@ The bus_info must start with "PCI:" for PCI boards, "PCIe:" for PCI Express boar
<entry>__u32</entry>
<entry><structfield>version</structfield></entry>
<entry><para>Version number of the driver.</para>
<para>Starting on kernel 3.1, the version reported is provided per
V4L2 subsystem, following the same Kernel numberation scheme. However, it
should not always return the same version as the kernel, if, for example,
an stable or distribution-modified kernel uses the V4L2 stack from a
<para>Starting with kernel 3.1, the version reported is provided by the
V4L2 subsystem following the kernel numbering scheme. However, it
may not always return the same version as the kernel if, for example,
a stable or distribution-modified kernel uses the V4L2 stack from a
newer kernel.</para>
<para>The version number is formatted using the
<constant>KERNEL_VERSION()</constant> macro:</para></entry>
......
Documentation/DocBook/media/v4l/vidioc-queryctrl.xml
View file @ 206c59d1
......@@ -600,7 +600,9 @@ writing a value will cause the device to carry out a given action
changes continuously. A typical example would be the current gain value if the device
is in auto-gain mode. In such a case the hardware calculates the gain value based on
the lighting conditions which can change over time. Note that setting a new value for
a volatile control will have no effect. The new value will just be ignored.</entry>
a volatile control will have no effect and no <constant>V4L2_EVENT_CTRL_CH_VALUE</constant>
will be sent, unless the <constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant> flag
(see below) is also set. Otherwise the new value will just be ignored.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_FLAG_HAS_PAYLOAD</constant></entry>
......@@ -610,6 +612,14 @@ using one of the pointer fields of &v4l2-ext-control;. This flag is set for cont
that are an array, string, or have a compound type. In all cases you have to set a
pointer to memory containing the payload of the control.</entry>
</row>
<row>
<entry><constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant></entry>
<entry>0x0200</entry>
<entry>The value provided to the control will be propagated to the driver
even if remains constant. This is required when the control represents an action
on the hardware. For example: clearing an error flag or triggering the flash. All the
controls of the type <constant>V4L2_CTRL_TYPE_BUTTON</constant> have this flag set.</entry>
</row>
</tbody>
</tgroup>
</table>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-frame-interval.xml
View file @ 206c59d1
......@@ -67,9 +67,9 @@
<para>To enumerate frame intervals applications initialize the
<structfield>index</structfield>, <structfield>pad</structfield>,
<structfield>code</structfield>, <structfield>width</structfield> and
<structfield>height</structfield> fields of
&v4l2-subdev-frame-interval-enum; and call the
<structfield>which</structfield>, <structfield>code</structfield>,
<structfield>width</structfield> and <structfield>height</structfield>
fields of &v4l2-subdev-frame-interval-enum; and call the
<constant>VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL</constant> ioctl with a pointer
to this structure. Drivers fill the rest of the structure or return
an &EINVAL; if one of the input fields is invalid. All frame intervals are
......@@ -123,7 +123,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Frame intervals to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-frame-size.xml
View file @ 206c59d1
......@@ -61,9 +61,9 @@
ioctl.</para>
<para>To enumerate frame sizes applications initialize the
<structfield>pad</structfield>, <structfield>code</structfield> and
<structfield>index</structfield> fields of the
&v4l2-subdev-mbus-code-enum; and call the
<structfield>pad</structfield>, <structfield>which</structfield> ,
<structfield>code</structfield> and <structfield>index</structfield>
fields of the &v4l2-subdev-mbus-code-enum; and call the
<constant>VIDIOC_SUBDEV_ENUM_FRAME_SIZE</constant> ioctl with a pointer to
the structure. Drivers fill the minimum and maximum frame sizes or return
an &EINVAL; if one of the input parameters is invalid.</para>
......@@ -127,7 +127,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Frame sizes to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subdev-enum-mbus-code.xml
View file @ 206c59d1
......@@ -56,8 +56,8 @@
</note>
<para>To enumerate media bus formats available at a given sub-device pad
applications initialize the <structfield>pad</structfield> and
<structfield>index</structfield> fields of &v4l2-subdev-mbus-code-enum; and
applications initialize the <structfield>pad</structfield>, <structfield>which</structfield>
and <structfield>index</structfield> fields of &v4l2-subdev-mbus-code-enum; and
call the <constant>VIDIOC_SUBDEV_ENUM_MBUS_CODE</constant> ioctl with a
pointer to this structure. Drivers fill the rest of the structure or return
an &EINVAL; if either the <structfield>pad</structfield> or
......@@ -93,7 +93,12 @@
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[9]</entry>
<entry><structfield>which</structfield></entry>
<entry>Media bus format codes to be enumerated, from &v4l2-subdev-format-whence;.</entry>
</row>
<row>
<entry>__u32</entry>
<entry><structfield>reserved</structfield>[8]</entry>
<entry>Reserved for future extensions. Applications and drivers must
set the array to zero.</entry>
</row>
......
Documentation/DocBook/media/v4l/vidioc-subscribe-event.xml
View file @ 206c59d1
......@@ -60,7 +60,9 @@
<row>
<entry>__u32</entry>
<entry><structfield>type</structfield></entry>
<entry>Type of the event.</entry>
<entry>Type of the event, see <xref linkend="event-type" />. Note that
<constant>V4L2_EVENT_ALL</constant> can be used with VIDIOC_UNSUBSCRIBE_EVENT
for unsubscribing all events at once.</entry>
</row>
<row>
<entry>__u32</entry>
......@@ -84,113 +86,6 @@
</tgroup>
</table>
<table frame="none" pgwide="1" id="event-type">
<title>Event Types</title>
<tgroup cols="3">
&cs-def;
<tbody valign="top">
<row>
<entry><constant>V4L2_EVENT_ALL</constant></entry>
<entry>0</entry>
<entry>All events. V4L2_EVENT_ALL is valid only for
VIDIOC_UNSUBSCRIBE_EVENT for unsubscribing all events at once.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_VSYNC</constant></entry>
<entry>1</entry>
<entry>This event is triggered on the vertical sync.
This event has a &v4l2-event-vsync; associated with it.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_EOS</constant></entry>
<entry>2</entry>
<entry>This event is triggered when the end of a stream is reached.
This is typically used with MPEG decoders to report to the application
when the last of the MPEG stream has been decoded.
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_CTRL</constant></entry>
<entry>3</entry>
<entry><para>This event requires that the <structfield>id</structfield>
matches the control ID from which you want to receive events.
This event is triggered if the control's value changes, if a
button control is pressed or if the control's flags change.
This event has a &v4l2-event-ctrl; associated with it. This struct
contains much of the same information as &v4l2-queryctrl; and
&v4l2-control;.</para>
<para>If the event is generated due to a call to &VIDIOC-S-CTRL; or
&VIDIOC-S-EXT-CTRLS;, then the event will <emphasis>not</emphasis> be sent to
the file handle that called the ioctl function. This prevents
nasty feedback loops. If you <emphasis>do</emphasis> want to get the
event, then set the <constant>V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK</constant>
flag.
</para>
<para>This event type will ensure that no information is lost when
more events are raised than there is room internally. In that
case the &v4l2-event-ctrl; of the second-oldest event is kept,
but the <structfield>changes</structfield> field of the
second-oldest event is ORed with the <structfield>changes</structfield>
field of the oldest event.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_FRAME_SYNC</constant></entry>
<entry>4</entry>
<entry>
<para>Triggered immediately when the reception of a
frame has begun. This event has a
&v4l2-event-frame-sync; associated with it.</para>
<para>If the hardware needs to be stopped in the case of a
buffer underrun it might not be able to generate this event.
In such cases the <structfield>frame_sequence</structfield>
field in &v4l2-event-frame-sync; will not be incremented. This
causes two consecutive frame sequence numbers to have n times
frame interval in between them.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_SOURCE_CHANGE</constant></entry>
<entry>5</entry>
<entry>
<para>This event is triggered when a source parameter change is
detected during runtime by the video device. It can be a
runtime resolution change triggered by a video decoder or the
format change happening on an input connector.
This event requires that the <structfield>id</structfield>
matches the input index (when used with a video device node)
or the pad index (when used with a subdevice node) from which
you want to receive events.</para>
<para>This event has a &v4l2-event-src-change; associated
with it. The <structfield>changes</structfield> bitfield denotes
what has changed for the subscribed pad. If multiple events
occurred before application could dequeue them, then the changes
will have the ORed value of all the events generated.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
<entry>6</entry>
<entry>
<para>Triggered whenever the motion detection state for one or more of the regions
changes. This event has a &v4l2-event-motion-det; associated with it.</para>
</entry>
</row>
<row>
<entry><constant>V4L2_EVENT_PRIVATE_START</constant></entry>
<entry>0x08000000</entry>
<entry>Base event number for driver-private events.</entry>
</row>
</tbody>
</tgroup>
</table>
<table pgwide="1" frame="none" id="event-flags">
<title>Event Flags</title>
<tgroup cols="3">
......
Documentation/IPMI.txt
View file @ 206c59d1
......@@ -505,7 +505,10 @@ at module load time (for a module) with:
The addresses are normal I2C addresses. The adapter is the string
name of the adapter, as shown in /sys/class/i2c-adapter/i2c-<n>/name.
It is *NOT* i2c-<n> itself.
It is *NOT* i2c-<n> itself. Also, the comparison is done ignoring
spaces, so if the name is "This is an I2C chip" you can say
adapter_name=ThisisanI2cchip. This is because it's hard to pass in
spaces in kernel parameters.
The debug flags are bit flags for each BMC found, they are:
IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8
......
Documentation/Makefile
View file @ 206c59d1
subdir-y := accounting arm auxdisplay blackfin connector \
subdir-y := accounting auxdisplay blackfin connector \
filesystems filesystems ia64 laptops mic misc-devices \
networking pcmcia prctl ptp spi timers vDSO video4linux \
watchdog
Documentation/PCI/MSI-HOWTO.txt
View file @ 206c59d1
......@@ -353,7 +353,7 @@ retry:
rc = pci_enable_msix_range(adapter->pdev, adapter->msix_entries,
maxvec, maxvec);
/*
* -ENOSPC is the only error code allowed to be analized
* -ENOSPC is the only error code allowed to be analyzed
*/
if (rc == -ENOSPC) {
if (maxvec == 1)
......@@ -370,7 +370,7 @@ retry:
return rc;
}
Note how pci_enable_msix_range() return value is analized for a fallback -
Note how pci_enable_msix_range() return value is analyzed for a fallback -
any error code other than -ENOSPC indicates a fatal error and should not
be retried.
......@@ -486,7 +486,7 @@ during development.
If your device supports both MSI-X and MSI capabilities, you should use
the MSI-X facilities in preference to the MSI facilities. As mentioned
above, MSI-X supports any number of interrupts between 1 and 2048.
In constrast, MSI is restricted to a maximum of 32 interrupts (and
In contrast, MSI is restricted to a maximum of 32 interrupts (and
must be a power of two). In addition, the MSI interrupt vectors must
be allocated consecutively, so the system might not be able to allocate
as many vectors for MSI as it could for MSI-X. On some platforms, MSI
......@@ -501,18 +501,9 @@ necessary to disable interrupts (Linux guarantees the same interrupt will
not be re-entered). If a device uses multiple interrupts, the driver
must disable interrupts while the lock is held. If the device sends
a different interrupt, the driver will deadlock trying to recursively
acquire the spinlock.
There are two solutions. The first is to take the lock with
spin_lock_irqsave() or spin_lock_irq() (see
Documentation/DocBook/kernel-locking). The second is to specify
IRQF_DISABLED to request_irq() so that the kernel runs the entire
interrupt routine with interrupts disabled.
If your MSI interrupt routine does not hold the lock for the whole time
it is running, the first solution may be best. The second solution is
normally preferred as it avoids making two transitions from interrupt
disabled to enabled and back again.
acquire the spinlock. Such deadlocks can be avoided by using
spin_lock_irqsave() or spin_lock_irq() which disable local interrupts
and acquire the lock (see Documentation/DocBook/kernel-locking).
4.6 How to tell whether MSI/MSI-X is enabled on a device
......
Documentation/PCI/pci-error-recovery.txt
View file @ 206c59d1
......@@ -256,7 +256,7 @@ STEP 4: Slot Reset
------------------
In response to a return value of PCI_ERS_RESULT_NEED_RESET, the
the platform will peform a slot reset on the requesting PCI device(s).
the platform will perform a slot reset on the requesting PCI device(s).
The actual steps taken by a platform to perform a slot reset
will be platform-dependent. Upon completion of slot reset, the
platform will call the device slot_reset() callback.
......
Documentation/PCI/pcieaer-howto.txt
View file @ 206c59d1
......@@ -66,8 +66,8 @@ hardware (mostly chipsets) has root ports that cannot obtain the reporting
source ID. nosourceid=n by default.
2.3 AER error output
When a PCI-E AER error is captured, an error message will be outputed to
console. If it's a correctable error, it is outputed as a warning.
When a PCI-E AER error is captured, an error message will be outputted to
console. If it's a correctable error, it is outputted as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
......
Documentation/acpi/enumeration.txt
View file @ 206c59d1
......@@ -253,7 +253,7 @@ input driver:
GPIO support
~~~~~~~~~~~~
ACPI 5 introduced two new resources to describe GPIO connections: GpioIo
and GpioInt. These resources are used be used to pass GPIO numbers used by
and GpioInt. These resources can be used to pass GPIO numbers used by
the device to the driver. ACPI 5.1 extended this with _DSD (Device
Specific Data) which made it possible to name the GPIOs among other things.
......
Documentation/acpi/gpio-properties.txt
View file @ 206c59d1
_DSD Device Properties Related to GPIO
--------------------------------------
With the release of ACPI 5.1 and the _DSD configuration objecte names
can finally be given to GPIOs (and other things as well) returned by
_CRS. Previously, we were only able to use an integer index to find
With the release of ACPI 5.1, the _DSD configuration object finally
allows names to be given to GPIOs (and other things as well) returned
by _CRS. Previously, we were only able to use an integer index to find
the corresponding GPIO, which is pretty error prone (it depends on
the _CRS output ordering, for example).
......
Documentation/arm/00-INDEX
View file @ 206c59d1
......@@ -10,8 +10,6 @@ IXP4xx
- Intel IXP4xx Network processor.
Makefile
- Build sourcefiles as part of the Documentation-build for arm
msm/
- MSM specific documentation
Netwinder
- Netwinder specific documentation
Porting
......
Documentation/arm/Booting
View file @ 206c59d1
......@@ -58,13 +58,18 @@ serial format options as described in
--------------------------
Existing boot loaders: OPTIONAL
New boot loaders: MANDATORY
New boot loaders: MANDATORY except for DT-only platforms
The boot loader should detect the machine type its running on by some
method. Whether this is a hard coded value or some algorithm that
looks at the connected hardware is beyond the scope of this document.
The boot loader must ultimately be able to provide a MACH_TYPE_xxx
value to the kernel. (see linux/arch/arm/tools/mach-types).
value to the kernel. (see linux/arch/arm/tools/mach-types). This
should be passed to the kernel in register r1.
For DT-only platforms, the machine type will be determined by device
tree. set the machine type to all ones (~0). This is not strictly
necessary, but assures that it will not match any existing types.
4. Setup boot data
------------------
......
Documentation/arm/Makefile deleted 100644 → 0
View file @ 5ec596c4
subdir-y := SH-Mobile
Documentation/arm/Marvell/README
View file @ 206c59d1
......@@ -96,6 +96,11 @@ EBU Armada family
88F6820
88F6828
Armada 390/398 Flavors:
88F6920
88F6928
Product infos: http://www.marvell.com/embedded-processors/armada-39x/
Armada XP Flavors:
MV78230
MV78260
......
Documentation/arm/README
View file @ 206c59d1
......@@ -185,13 +185,20 @@ Kernel entry (head.S)
board devices are used, or the device is setup, and provides that
machine specific "personality."
This fine-grained machine specific selection is controlled by the machine
type ID, which acts both as a run-time and a compile-time code selection
method.
For platforms that support device tree (DT), the machine selection is
controlled at runtime by passing the device tree blob to the kernel. At
compile-time, support for the machine type must be selected. This allows for
a single multiplatform kernel build to be used for several machine types.
You can register a new machine via the web site at:
For platforms that do not use device tree, this machine selection is
controlled by the machine type ID, which acts both as a run-time and a
compile-time code selection method. You can register a new machine via the
web site at:
<http://www.arm.linux.org.uk/developer/machines/>
Note: Please do not register a machine type for DT-only platforms. If your
platform is DT-only, you do not need a registered machine type.
---
Russell King (15/03/2004)
Documentation/arm/SH-Mobile/Makefile deleted 100644 → 0
View file @ 5ec596c4
# List of programs to build
hostprogs-y := vrl4
# Tell kbuild to always build the programs
always := $(hostprogs-y)
HOSTCFLAGS_vrl4.o += -I$(objtree)/usr/include -I$(srctree)/tools/include
Documentation/arm/SH-Mobile/vrl4.c deleted 100644 → 0
View file @ 5ec596c4
/*
* vrl4 format generator
*
* Copyright (C) 2010 Simon Horman
*
* This file is subject to the terms and conditions of the GNU General Public
* License. See the file "COPYING" in the main directory of this archive
* for more details.
*/
/*
* usage: vrl4 < zImage > out
* dd if=out of=/dev/sdx bs=512 seek=1 # Write the image to sector 1
*
* Reads a zImage from stdin and writes a vrl4 image to stdout.
* In practice this means writing a padded vrl4 header to stdout followed
* by the zImage.
*
* The padding places the zImage at ALIGN bytes into the output.
* The vrl4 uses ALIGN + START_BASE as the start_address.
* This is where the mask ROM will jump to after verifying the header.
*
* The header sets copy_size to min(sizeof(zImage), MAX_BOOT_PROG_LEN) + ALIGN.
* That is, the mask ROM will load the padded header (ALIGN bytes)
* And then MAX_BOOT_PROG_LEN bytes of the image, or the entire image,
* whichever is smaller.
*
* The zImage is not modified in any way.
*/
#define _BSD_SOURCE
#include <endian.h>
#include <unistd.h>
#include <stdint.h>
#include <stdio.h>
#include <errno.h>
#include <tools/endian.h>
struct hdr {
uint32_t magic1;
uint32_t reserved1;
uint32_t magic2;
uint32_t reserved2;
uint16_t copy_size;
uint16_t boot_options;
uint32_t reserved3;
uint32_t start_address;
uint32_t reserved4;
uint32_t reserved5;
char reserved6[308];
};
#define DECLARE_HDR(h) \
struct hdr (h) = { \
.magic1 = htole32(0xea000000), \
.reserved1 = htole32(0x56), \
.magic2 = htole32(0xe59ff008), \
.reserved3 = htole16(0x1) }
/* Align to 512 bytes, the MMCIF sector size */
#define ALIGN_BITS 9
#define ALIGN (1 << ALIGN_BITS)
#define START_BASE 0xe55b0000
/*
* With an alignment of 512 the header uses the first sector.
* There is a 128 sector (64kbyte) limit on the data loaded by the mask ROM.
* So there are 127 sectors left for the boot programme. But in practice
* Only a small portion of a zImage is needed, 16 sectors should be more
* than enough.
*
* Note that this sets how much of the zImage is copied by the mask ROM.
* The entire zImage is present after the header and is loaded
* by the code in the boot program (which is the first portion of the zImage).
*/
#define MAX_BOOT_PROG_LEN (16 * 512)
#define ROUND_UP(x) ((x + ALIGN - 1) & ~(ALIGN - 1))
static ssize_t do_read(int fd, void *buf, size_t count)
{
size_t offset = 0;
ssize_t l;
while (offset < count) {
l = read(fd, buf + offset, count - offset);
if (!l)
break;
if (l < 0) {
if (errno == EAGAIN || errno == EWOULDBLOCK)
continue;
perror("read");
return -1;
}
offset += l;
}
return offset;
}
static ssize_t do_write(int fd, const void *buf, size_t count)
{
size_t offset = 0;
ssize_t l;
while (offset < count) {
l = write(fd, buf + offset, count - offset);
if (l < 0) {
if (errno == EAGAIN || errno == EWOULDBLOCK)
continue;
perror("write");
return -1;
}
offset += l;
}
return offset;
}
static ssize_t write_zero(int fd, size_t len)
{
size_t i = len;
while (i--) {
const char x = 0;
if (do_write(fd, &x, 1) < 0)
return -1;
}
return len;
}
int main(void)
{
DECLARE_HDR(hdr);
char boot_program[MAX_BOOT_PROG_LEN];
size_t aligned_hdr_len, alligned_prog_len;
ssize_t prog_len;
prog_len = do_read(0, boot_program, sizeof(boot_program));
if (prog_len <= 0)
return -1;
aligned_hdr_len = ROUND_UP(sizeof(hdr));
hdr.start_address = htole32(START_BASE + aligned_hdr_len);
alligned_prog_len = ROUND_UP(prog_len);
hdr.copy_size = htole16(aligned_hdr_len + alligned_prog_len);
if (do_write(1, &hdr, sizeof(hdr)) < 0)
return -1;
if (write_zero(1, aligned_hdr_len - sizeof(hdr)) < 0)
return -1;
if (do_write(1, boot_program, prog_len) < 0)
return 1;
/* Write out the rest of the kernel */
while (1) {
prog_len = do_read(0, boot_program, sizeof(boot_program));
if (prog_len < 0)
return 1;
if (prog_len == 0)
break;
if (do_write(1, boot_program, prog_len) < 0)
return 1;
}
return 0;
}
Documentation/arm/SH-Mobile/zboot-rom-mmcif.txt deleted 100644 → 0
View file @ 5ec596c4
ROM-able zImage boot from MMC
-----------------------------
An ROM-able zImage compiled with ZBOOT_ROM_MMCIF may be written to MMC and
SuperH Mobile ARM will to boot directly from the MMCIF hardware block.
This is achieved by the mask ROM loading the first portion of the image into
MERAM and then jumping to it. This portion contains loader code which
copies the entire image to SDRAM and jumps to it. From there the zImage
boot code proceeds as normal, uncompressing the image into its final
location and then jumping to it.
This code has been tested on an AP4EB board using the developer 1A eMMC
boot mode which is configured using the following jumper settings.
The board used for testing required a patched mask ROM in order for
this mode to function.
8 7 6 5 4 3 2 1
x|x|x|x|x| |x|
S4 -+-+-+-+-+-+-+-
| | | | |x| |x on
The zImage must be written to the MMC card at sector 1 (512 bytes) in
vrl4 format. A utility vrl4 is supplied to accomplish this.
e.g.
vrl4 < zImage | dd of=/dev/sdX bs=512 seek=1
A dual-voltage MMC 4.0 card was used for testing.
Documentation/arm/SH-Mobile/zboot-rom-sdhi.txt deleted 100644 → 0
View file @ 5ec596c4
ROM-able zImage boot from eSD
-----------------------------
An ROM-able zImage compiled with ZBOOT_ROM_SDHI may be written to eSD and
SuperH Mobile ARM will to boot directly from the SDHI hardware block.
This is achieved by the mask ROM loading the first portion of the image into
MERAM and then jumping to it. This portion contains loader code which
copies the entire image to SDRAM and jumps to it. From there the zImage
boot code proceeds as normal, uncompressing the image into its final
location and then jumping to it.
This code has been tested on an mackerel board using the developer 1A eSD
boot mode which is configured using the following jumper settings.
8 7 6 5 4 3 2 1
x|x|x|x| |x|x|
S4 -+-+-+-+-+-+-+-
| | | |x| | |x on
The eSD card needs to be present in SDHI slot 1 (CN7).
As such S1 and S33 also need to be configured as per
the notes in arch/arm/mach-shmobile/board-mackerel.c.
A partial zImage must be written to physical partition #1 (boot)
of the eSD at sector 0 in vrl4 format. A utility vrl4 is supplied to
accomplish this.
e.g.
vrl4 < zImage | dd of=/dev/sdX bs=512 count=17
A full copy of _the same_ zImage should be written to physical partition #1
(boot) of the eSD at sector 0. This should _not_ be in vrl4 format.
vrl4 < zImage | dd of=/dev/sdX bs=512
Note: The commands above assume that the physical partition has been
switched. No such facility currently exists in the Linux Kernel.
Physical partitions are described in the eSD specification. At the time of
writing they are not the same as partitions that are typically configured
using fdisk and visible through /proc/partitions
Documentation/arm/msm/gpiomux.txt deleted 100644 → 0
View file @ 5ec596c4
This document provides an overview of the msm_gpiomux interface, which
is used to provide gpio pin multiplexing and configuration on mach-msm
targets.
History
=======
The first-generation API for gpio configuration & multiplexing on msm
is the function gpio_tlmm_config(). This function has a few notable
shortcomings, which led to its deprecation and replacement by gpiomux:
The 'disable' parameter: Setting the second parameter to
gpio_tlmm_config to GPIO_CFG_DISABLE tells the peripheral
processor in charge of the subsystem to perform a look-up into a
low-power table and apply the low-power/sleep setting for the pin.
As the msm family evolved this became problematic. Not all pins
have sleep settings, not all peripheral processors will accept requests
to apply said sleep settings, and not all msm targets have their gpio
subsystems managed by a peripheral processor. In order to get consistent
behavior on all targets, drivers are forced to ignore this parameter,
rendering it useless.
The 'direction' flag: for all mux-settings other than raw-gpio (0),
the output-enable bit of a gpio is hard-wired to a known
input (usually VDD or ground). For those settings, the direction flag
is meaningless at best, and deceptive at worst. In addition, using the
direction flag to change output-enable (OE) directly can cause trouble in
gpiolib, which has no visibility into gpio direction changes made
in this way. Direction control in gpio mode should be made through gpiolib.
Key Features of gpiomux
=======================
- A consistent interface across all generations of msm. Drivers can expect
the same results on every target.
- gpiomux plays nicely with gpiolib. Functions that should belong to gpiolib
are left to gpiolib and not duplicated here. gpiomux is written with the
intent that gpio_chips will call gpiomux reference-counting methods
from their request() and free() hooks, providing full integration.
- Tabular configuration. Instead of having to call gpio_tlmm_config
hundreds of times, gpio configuration is placed in a single table.
- Per-gpio sleep. Each gpio is individually reference counted, allowing only
those lines which are in use to be put in high-power states.
- 0 means 'do nothing': all flags are designed so that the default memset-zero
equates to a sensible default of 'no configuration', preventing users
from having to provide hundreds of 'no-op' configs for unused or
unwanted lines.
Usage
=====
To use gpiomux, provide configuration information for relevant gpio lines
in the msm_gpiomux_configs table. Since a 0 equates to "unconfigured",
only those lines to be managed by gpiomux need to be specified. Here
is a completely fictional example:
struct msm_gpiomux_config msm_gpiomux_configs[GPIOMUX_NGPIOS] = {
[12] = {
.active = GPIOMUX_VALID | GPIOMUX_DRV_8MA | GPIOMUX_FUNC_1,
.suspended = GPIOMUX_VALID | GPIOMUX_PULL_DOWN,
},
[34] = {
.suspended = GPIOMUX_VALID | GPIOMUX_PULL_DOWN,
},
};
To indicate that a gpio is in use, call msm_gpiomux_get() to increase
its reference count. To decrease the reference count, call msm_gpiomux_put().
The effect of this configuration is as follows:
When the system boots, gpios 12 and 34 will be initialized with their
'suspended' configurations. All other gpios, which were left unconfigured,
will not be touched.
When msm_gpiomux_get() is called on gpio 12 to raise its reference count
above 0, its active configuration will be applied. Since no other gpio
line has a valid active configuration, msm_gpiomux_get() will have no
effect on any other line.
When msm_gpiomux_put() is called on gpio 12 or 34 to drop their reference
count to 0, their suspended configurations will be applied.
Since no other gpio line has a valid suspended configuration, no other
gpio line will be effected by msm_gpiomux_put(). Since gpio 34 has no valid
active configuration, this is effectively a no-op for gpio 34 as well,
with one small caveat, see the section "About Output-Enable Settings".
All of the GPIOMUX_VALID flags may seem like unnecessary overhead, but
they address some important issues. As unused entries (all those
except 12 and 34) are zero-filled, gpiomux needs a way to distinguish
the used fields from the unused. In addition, the all-zero pattern
is a valid configuration! Therefore, gpiomux defines an additional bit
which is used to indicate when a field is used. This has the pleasant
side-effect of allowing calls to msm_gpiomux_write to use '0' to indicate
that a value should not be changed:
msm_gpiomux_write(0, GPIOMUX_VALID, 0);
replaces the active configuration of gpio 0 with an all-zero configuration,
but leaves the suspended configuration as it was.
Static Configurations
=====================
To install a static configuration, which is applied at boot and does
not change after that, install a configuration with a suspended component
but no active component, as in the previous example:
[34] = {
.suspended = GPIOMUX_VALID | GPIOMUX_PULL_DOWN,
},
The suspended setting is applied during boot, and the lack of any valid
active setting prevents any other setting from being applied at runtime.
If other subsystems attempting to access the line is a concern, one could
*really* anchor the configuration down by calling msm_gpiomux_get on the
line at initialization to move the line into active mode. With the line
held, it will never be re-suspended, and with no valid active configuration,
no new configurations will be applied.
But then, if having other subsystems grabbing for the line is truly a concern,
it should be reserved with gpio_request instead, which carries an implicit
msm_gpiomux_get.
gpiomux and gpiolib
===================
It is expected that msm gpio_chips will call msm_gpiomux_get() and
msm_gpiomux_put() from their request and free hooks, like this fictional
example:
static int request(struct gpio_chip *chip, unsigned offset)
{
return msm_gpiomux_get(chip->base + offset);
}
static void free(struct gpio_chip *chip, unsigned offset)
{
msm_gpiomux_put(chip->base + offset);
}
...somewhere in a gpio_chip declaration...
.request = request,
.free = free,
This provides important functionality:
- It guarantees that a gpio line will have its 'active' config applied
when the line is requested, and will not be suspended while the line
remains requested; and
- It guarantees that gpio-direction settings from gpiolib behave sensibly.
See "About Output-Enable Settings."
This mechanism allows for "auto-request" of gpiomux lines via gpiolib
when it is suitable. Drivers wishing more exact control are, of course,
free to also use msm_gpiomux_set and msm_gpiomux_get.
About Output-Enable Settings
============================
Some msm targets do not have the ability to query the current gpio
configuration setting. This means that changes made to the output-enable
(OE) bit by gpiolib cannot be consistently detected and preserved by gpiomux.
Therefore, when gpiomux applies a configuration setting, any direction
settings which may have been applied by gpiolib are lost and the default
input settings are re-applied.
For this reason, drivers should not assume that gpio direction settings
continue to hold if they free and then re-request a gpio. This seems like
common sense - after all, anybody could have obtained the line in the
meantime - but it needs saying.
This also means that calls to msm_gpiomux_write will reset the OE bit,
which means that if the gpio line is held by a client of gpiolib and
msm_gpiomux_write is called, the direction setting has been lost and
gpiolib's internal state has been broken.
Release gpio lines before reconfiguring them.
Documentation/arm64/acpi_object_usage.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/arm64/arm-acpi.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/blackfin/Makefile
View file @ 206c59d1
ifneq ($(CONFIG_BLACKFIN),)
ifneq ($(CONFIG_BFIN_GPTIMERS,)
ifneq ($(CONFIG_BFIN_GPTIMERS),)
obj-m := gptimers-example.o
endif
endif
Documentation/block/biodoc.txt
View file @ 206c59d1
......@@ -48,8 +48,7 @@ Description of Contents:
- Highmem I/O support
- I/O scheduler modularization
1.2 Tuning based on high level requirements/capabilities
1.2.1 I/O Barriers
1.2.2 Request Priority/Latency
1.2.1 Request Priority/Latency
1.3 Direct access/bypass to lower layers for diagnostics and special
device operations
1.3.1 Pre-built commands
......@@ -255,29 +254,12 @@ some control over i/o ordering.
What kind of support exists at the generic block layer for this ?
The flags and rw fields in the bio structure can be used for some tuning
from above e.g indicating that an i/o is just a readahead request, or for
marking barrier requests (discussed next), or priority settings (currently
unused). As far as user applications are concerned they would need an
additional mechanism either via open flags or ioctls, or some other upper
level mechanism to communicate such settings to block.
1.2.1 I/O Barriers
There is a way to enforce strict ordering for i/os through barriers.
All requests before a barrier point must be serviced before the barrier
request and any other requests arriving after the barrier will not be
serviced until after the barrier has completed. This is useful for higher
level control on write ordering, e.g flushing a log of committed updates
to disk before the corresponding updates themselves.
A flag in the bio structure, BIO_BARRIER is used to identify a barrier i/o.
The generic i/o scheduler would make sure that it places the barrier request and
all other requests coming after it after all the previous requests in the
queue. Barriers may be implemented in different ways depending on the
driver. For more details regarding I/O barriers, please read barrier.txt
in this directory.
1.2.2 Request Priority/Latency
from above e.g indicating that an i/o is just a readahead request, or priority
settings (currently unused). As far as user applications are concerned they
would need an additional mechanism either via open flags or ioctls, or some
other upper level mechanism to communicate such settings to block.
1.2.1 Request Priority/Latency
Todo/Under discussion:
Arjan's proposed request priority scheme allows higher levels some broad
......@@ -906,8 +888,8 @@ queue and specific I/O schedulers. Unless stated otherwise, elevator is used
to refer to both parts and I/O scheduler to specific I/O schedulers.
Block layer implements generic dispatch queue in block/*.c.
The generic dispatch queue is responsible for properly ordering barrier
requests, requeueing, handling non-fs requests and all other subtleties.
The generic dispatch queue is responsible for requeueing, handling non-fs
requests and all other subtleties.
Specific I/O schedulers are responsible for ordering normal filesystem
requests. They can also choose to delay certain requests to improve
......
Documentation/cgroups/memory.txt
View file @ 206c59d1
......@@ -275,11 +275,6 @@ When oom event notifier is registered, event will be delivered.
2.7 Kernel Memory Extension (CONFIG_MEMCG_KMEM)
WARNING: Current implementation lacks reclaim support. That means allocation
attempts will fail when close to the limit even if there are plenty of
kmem available for reclaim. That makes this option unusable in real
life so DO NOT SELECT IT unless for development purposes.
With the Kernel memory extension, the Memory Controller is able to limit
the amount of kernel memory used by the system. Kernel memory is fundamentally
different than user memory, since it can't be swapped out, which makes it
......@@ -345,6 +340,9 @@ set:
In this case, the admin could set up K so that the sum of all groups is
never greater than the total memory, and freely set U at the cost of his
QoS.
WARNING: In the current implementation, memory reclaim will NOT be
triggered for a cgroup when it hits K while staying below U, which makes
this setup impractical.
U != 0, K >= U:
Since kmem charges will also be fed to the user counter and reclaim will be
......
Documentation/cpu-hotplug.txt
View file @ 206c59d1
......@@ -108,7 +108,7 @@ Never use anything other than cpumask_t to represent bitmap of CPUs.
for_each_possible_cpu - Iterate over cpu_possible_mask
for_each_online_cpu - Iterate over cpu_online_mask
for_each_present_cpu - Iterate over cpu_present_mask
for_each_cpu_mask(x,mask) - Iterate over some random collection of cpu mask.
for_each_cpu(x,mask) - Iterate over some random collection of cpu mask.
#include <linux/cpu.h>
get_online_cpus() and put_online_cpus():
......
Documentation/device-mapper/dm-crypt.txt
View file @ 206c59d1
......@@ -5,7 +5,7 @@ Device-Mapper's "crypt" target provides transparent encryption of block devices
using the kernel crypto API.
For a more detailed description of supported parameters see:
http://code.google.com/p/cryptsetup/wiki/DMCrypt
https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt
Parameters: <cipher> <key> <iv_offset> <device path> \
<offset> [<#opt_params> <opt_params>]
......@@ -80,7 +80,7 @@ Example scripts
===============
LUKS (Linux Unified Key Setup) is now the preferred way to set up disk
encryption with dm-crypt using the 'cryptsetup' utility, see
http://code.google.com/p/cryptsetup/
https://gitlab.com/cryptsetup/cryptsetup
[[
#!/bin/sh
......
Documentation/device-mapper/log-writes.txt 0 → 100644
View file @ 206c59d1
dm-log-writes
=============
This target takes 2 devices, one to pass all IO to normally, and one to log all
of the write operations to. This is intended for file system developers wishing
to verify the integrity of metadata or data as the file system is written to.
There is a log_write_entry written for every WRITE request and the target is
able to take arbitrary data from userspace to insert into the log. The data
that is in the WRITE requests is copied into the log to make the replay happen
exactly as it happened originally.
Log Ordering
============
We log things in order of completion once we are sure the write is no longer in
cache. This means that normal WRITE requests are not actually logged until the
next REQ_FLUSH request. This is to make it easier for userspace to replay the
log in a way that correlates to what is on disk and not what is in cache, to
make it easier to detect improper waiting/flushing.
This works by attaching all WRITE requests to a list once the write completes.
Once we see a REQ_FLUSH request we splice this list onto the request and once
the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only
completed WRITEs, at the time the REQ_FLUSH is issued, are added in order to
simulate the worst case scenario with regard to power failures. Consider the
following example (W means write, C means complete):
W1,W2,W3,C3,C2,Wflush,C1,Cflush
The log would show the following
W3,W2,flush,W1....
Again this is to simulate what is actually on disk, this allows us to detect
cases where a power failure at a particular point in time would create an
inconsistent file system.
Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
they complete as those requests will obviously bypass the device cache.
Any REQ_DISCARD requests are treated like WRITE requests. Otherwise we would
have all the DISCARD requests, and then the WRITE requests and then the FLUSH
request. Consider the following example:
WRITE block 1, DISCARD block 1, FLUSH
If we logged DISCARD when it completed, the replay would look like this
DISCARD 1, WRITE 1, FLUSH
which isn't quite what happened and wouldn't be caught during the log replay.
Target interface
================
i) Constructor
log-writes <dev_path> <log_dev_path>
dev_path : Device that all of the IO will go to normally.
log_dev_path : Device where the log entries are written to.
ii) Status
<#logged entries> <highest allocated sector>
#logged entries : Number of logged entries
highest allocated sector : Highest allocated sector
iii) Messages
mark <description>
You can use a dmsetup message to set an arbitrary mark in a log.
For example say you want to fsck a file system after every
write, but first you need to replay up to the mkfs to make sure
we're fsck'ing something reasonable, you would do something like
this:
mkfs.btrfs -f /dev/mapper/log
dmsetup message log 0 mark mkfs
<run test>
This would allow you to replay the log up to the mkfs mark and
then replay from that point on doing the fsck check in the
interval that you want.
Every log has a mark at the end labeled "dm-log-writes-end".
Userspace component
===================
There is a userspace tool that will replay the log for you in various ways.
It can be found here: https://github.com/josefbacik/log-writes
Example usage
=============
Say you want to test fsync on your file system. You would do something like
this:
TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
dmsetup create log --table "$TABLE"
mkfs.btrfs -f /dev/mapper/log
dmsetup message log 0 mark mkfs
mount /dev/mapper/log /mnt/btrfs-test
<some test that does fsync at the end>
dmsetup message log 0 mark fsync
md5sum /mnt/btrfs-test/foo
umount /mnt/btrfs-test
dmsetup remove log
replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync
mount /dev/sdb /mnt/btrfs-test
md5sum /mnt/btrfs-test/foo
<verify md5sum's are correct>
Another option is to do a complicated file system operation and verify the file
system is consistent during the entire operation. You could do this with:
TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
dmsetup create log --table "$TABLE"
mkfs.btrfs -f /dev/mapper/log
dmsetup message log 0 mark mkfs
mount /dev/mapper/log /mnt/btrfs-test
<fsstress to dirty the fs>
btrfs filesystem balance /mnt/btrfs-test
umount /mnt/btrfs-test
dmsetup remove log
replay-log --log /dev/sdc --replay /dev/sdb --end-mark mkfs
btrfsck /dev/sdb
replay-log --log /dev/sdc --replay /dev/sdb --start-mark mkfs \
--fsck "btrfsck /dev/sdb" --check fua
And that will replay the log until it sees a FUA request, run the fsck command
and if the fsck passes it will replay to the next FUA, until it is completed or
the fsck command exists abnormally.
Documentation/device-mapper/switch.txt
View file @ 206c59d1
......@@ -47,8 +47,8 @@ consume far too much memory.
Using this device-mapper switch target we can now build a two-layer
device hierarchy:
Upper Tier – Determine which array member the I/O should be sent to.
Lower Tier – Load balance amongst paths to a particular member.
Upper Tier - Determine which array member the I/O should be sent to.
Lower Tier - Load balance amongst paths to a particular member.
The lower tier consists of a single dm multipath device for each member.
Each of these multipath devices contains the set of paths directly to
......
Documentation/device-mapper/thin-provisioning.txt
View file @ 206c59d1
......@@ -380,9 +380,6 @@ then you'll have no access to blocks mapped beyond the end. If you
load a target that is bigger than before, then extra blocks will be
provisioned as and when needed.
If you wish to reduce the size of your thin device and potentially
regain some space then send the 'trim' message to the pool.
ii) Status
<nr mapped sectors> <highest mapped sector>
......
Documentation/device-mapper/verity.txt
View file @ 206c59d1
......@@ -11,6 +11,7 @@ Construction Parameters
<data_block_size> <hash_block_size>
<num_data_blocks> <hash_start_block>
<algorithm> <digest> <salt>
[<#opt_params> <opt_params>]
<version>
This is the type of the on-disk hash format.
......@@ -62,6 +63,22 @@ Construction Parameters
<salt>
The hexadecimal encoding of the salt value.
<#opt_params>
Number of optional parameters. If there are no optional parameters,
the optional paramaters section can be skipped or #opt_params can be zero.
Otherwise #opt_params is the number of following arguments.
Example of optional parameters section:
1 ignore_corruption
ignore_corruption
Log corrupted blocks, but allow read operations to proceed normally.
restart_on_corruption
Restart the system when a corrupted block is discovered. This option is
not compatible with ignore_corruption and requires user space support to
avoid restart loops.
Theory of operation
===================
......@@ -125,7 +142,7 @@ block boundary) are the hash blocks which are stored a depth at a time
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
https://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity
Status
======
......@@ -142,7 +159,7 @@ Set up a device:
A command line tool veritysetup is available to compute or verify
the hash tree or activate the kernel device. This is available from
the cryptsetup upstream repository http://code.google.com/p/cryptsetup/
the cryptsetup upstream repository https://gitlab.com/cryptsetup/cryptsetup/
(as a libcryptsetup extension).
Create hash on the device:
......
Documentation/devicetree/bindings/arc/pct.txt 0 → 100644
View file @ 206c59d1
* ARC Performance Counters
The ARC700 can be configured with a pipeline performance monitor for counting
CPU and cache events like cache misses and hits. Like conventional PCT there
are 100+ hardware conditions dynamically mapped to upto 32 counters
Note that:
* The ARC 700 PCT does not support interrupts; although HW events may be
counted, the HW events themselves cannot serve as a trigger for a sample.
Required properties:
- compatible : should contain
"snps,arc700-pct"
Example:
pmu {
compatible = "snps,arc700-pct";
};
Documentation/devicetree/bindings/arc/pmu.txt deleted 100644 → 0
View file @ 5ec596c4
* ARC Performance Monitor Unit
The ARC 700 can be configured with a pipeline performance monitor for counting
CPU and cache events like cache misses and hits.
Note that:
* ARC 700 refers to a family of ARC processor cores;
- There is only one type of PMU available for the whole family;
- The PMU may support different sets of events; supported events are probed
at boot time, as required by the reference manual.
* The ARC 700 PMU does not support interrupts; although HW events may be
counted, the HW events themselves cannot serve as a trigger for a sample.
Required properties:
- compatible : should contain
"snps,arc700-pmu"
Example:
pmu {
compatible = "snps,arc700-pmu";
};
Documentation/devicetree/bindings/arm/al,alpine.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/arm/altera.txt 0 → 100644
View file @ 206c59d1
Altera's SoCFPGA platform device tree bindings
---------------------------------------------
Boards with Cyclone 5 SoC:
Required root node properties:
compatible = "altr,socfpga-cyclone5", "altr,socfpga";
Boards with Arria 5 SoC:
Required root node properties:
compatible = "altr,socfpga-arria5", "altr,socfpga";
Boards with Arria 10 SoC:
Required root node properties:
compatible = "altr,socfpga-arria10", "altr,socfpga";
Documentation/devicetree/bindings/arm/amlogic.txt
View file @ 206c59d1
......@@ -8,3 +8,7 @@ Boards with the Amlogic Meson6 SoC shall have the following properties:
Boards with the Amlogic Meson8 SoC shall have the following properties:
Required root node property:
compatible: "amlogic,meson8";
Board compatible values:
- "geniatech,atv1200"
- "minix,neo-x8"
Documentation/devicetree/bindings/arm/arch_timer.txt
View file @ 206c59d1
......@@ -17,7 +17,10 @@ to deliver its interrupts via SPIs.
- interrupts : Interrupt list for secure, non-secure, virtual and
hypervisor timers, in that order.
- clock-frequency : The frequency of the main counter, in Hz. Optional.
- clock-frequency : The frequency of the main counter, in Hz. Should be present
only where necessary to work around broken firmware which does not configure
CNTFRQ on all CPUs to a uniform correct value. Use of this property is
strongly discouraged; fix your firmware unless absolutely impossible.
- always-on : a boolean property. If present, the timer is powered through an
always-on power domain, therefore it never loses context.
......@@ -46,7 +49,8 @@ Example:
- compatible : Should at least contain "arm,armv7-timer-mem".
- clock-frequency : The frequency of the main counter, in Hz. Optional.
- clock-frequency : The frequency of the main counter, in Hz. Should be present
only when firmware has not configured the MMIO CNTFRQ registers.
- reg : The control frame base address.
......
Documentation/devicetree/bindings/arm/armada-39x.txt 0 → 100644
View file @ 206c59d1
Marvell Armada 39x Platforms Device Tree Bindings
-------------------------------------------------
Boards with a SoC of the Marvell Armada 39x family shall have the
following property:
Required root node property:
- compatible: must contain "marvell,armada390"
In addition, boards using the Marvell Armada 398 SoC shall have the
following property before the previous one:
Required root node property:
compatible: must contain "marvell,armada398"
Example:
compatible = "marvell,a398-db", "marvell,armada398", "marvell,armada390";
Documentation/devicetree/bindings/arm/coresight.txt
View file @ 206c59d1
......@@ -61,7 +61,6 @@ Example:
compatible = "arm,coresight-etb10", "arm,primecell";
reg = <0 0x20010000 0 0x1000>;
coresight-default-sink;
clocks = <&oscclk6a>;
clock-names = "apb_pclk";
port {
......
Documentation/devicetree/bindings/arm/geniatech.txt deleted 100644 → 0
View file @ 5ec596c4
Geniatech platforms device tree bindings
-------------------------------------------
Geniatech ATV1200
- compatible = "geniatech,atv1200"
Documentation/devicetree/bindings/arm/msm/qcom,idle-state.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/arm/omap/ctrl.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/arm/omap/l4.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/bus/renesas,bsc.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/bus/simple-pm-bus.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/clock/exynos5433-clock.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/clock/pwm-clock.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/common-properties.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/cris/axis.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/cris/boards.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/cris/interrupts.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/dma/apm-xgene-dma.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/dma/jz4780-dma.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/dma/rcar-audmapp.txt deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
Documentation/devicetree/bindings/dma/renesas,usb-dmac.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/gpio/gpio-altera.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/i2c/mt9v032.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/i2c/ov2640.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/i2c/ov2659.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/ti,omap3isp.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/xilinx/video.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/xilinx/xlnx,v-tc.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/xilinx/xlnx,v-tpg.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/media/xilinx/xlnx,video.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/mfd/qcom,tcsr.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/net/amd-xgbe-phy.txt deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
Documentation/devicetree/bindings/net/ipq806x-dwmac.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/net/nxp,lpc1850-dwmac.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/net/ti,dp83867.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/net/wireless/ti,wlcore.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/panel/auo,b101ean01.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/panel/innolux,at043tn24.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/power/fsl,imx-gpc.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/rtc/abracon,abx80x.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/devicetree/bindings/soc/mediatek/pwrap.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/dma-buf-sharing.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/driver-model/devres.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/email-clients.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/filesystems/f2fs.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/filesystems/nfs/nfs-rdma.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/filesystems/proc.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/filesystems/xfs.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/gpio/board.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/gpio/consumer.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/hwmon/tmp401
View file @ 206c59d1
This diff is collapsed.
Documentation/i2o/README deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
Documentation/i2o/ioctl deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
Documentation/input/alps.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/input/event-codes.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/input/gpio-tilt.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/input/iforce-protocol.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/input/walkera0701.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/input/yealink.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/ioctl/ioctl-number.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/kasan.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/kernel-parameters.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/kmemcheck.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/kprobes.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/laptops/thinkpad-acpi.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/md-cluster.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/memory-barriers.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/memory-hotplug.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/module-signing.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/bonding.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/can.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/dctcp.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/ieee802154.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/ip-sysctl.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/mpls-sysctl.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/pktgen.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/scaling.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/networking/switchdev.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/printk-formats.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/s390/qeth.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/scheduler/completion.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/serial/tty.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/target/tcm_mod_builder.py
View file @ 206c59d1
This diff is collapsed.
Documentation/target/tcmu-design.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/trace/coresight.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/video4linux/v4l2-controls.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/video4linux/vivid.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/virtual/kvm/api.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/virtual/kvm/mmu.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/vm/pagemap.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/vm/transhuge.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/zh_CN/arm64/booting.txt
View file @ 206c59d1
This diff is collapsed.
Documentation/zh_CN/arm64/legacy_instructions.txt 0 → 100644
View file @ 206c59d1
This diff is collapsed.
Documentation/zh_CN/arm64/memory.txt
View file @ 206c59d1
This diff is collapsed.
MAINTAINERS
View file @ 206c59d1
This diff is collapsed.
Makefile
View file @ 206c59d1
This diff is collapsed.
README
View file @ 206c59d1
This diff is collapsed.
arch/alpha/boot/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/alpha/boot/main.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/boot/stdio.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/alpha/boot/tools/objstrip.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/include/asm/types.h
View file @ 206c59d1
This diff is collapsed.
arch/alpha/include/asm/unistd.h
View file @ 206c59d1
This diff is collapsed.
arch/alpha/include/uapi/asm/unistd.h
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/err_ev6.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/irq.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/osf_sys.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/process.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/smp.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/srmcons.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/sys_marvel.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/systbls.S
View file @ 206c59d1
This diff is collapsed.
arch/alpha/kernel/traps.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/oprofile/op_model_ev4.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/oprofile/op_model_ev5.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/oprofile/op_model_ev6.c
View file @ 206c59d1
This diff is collapsed.
arch/alpha/oprofile/op_model_ev67.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/Kconfig.debug
View file @ 206c59d1
This diff is collapsed.
arch/arc/boot/dts/angel4.dts
View file @ 206c59d1
This diff is collapsed.
arch/arc/configs/nsimosci_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arc/include/asm/arcregs.h
View file @ 206c59d1
This diff is collapsed.
arch/arc/include/asm/atomic.h
View file @ 206c59d1
This diff is collapsed.
arch/arc/include/asm/bitops.h
View file @ 206c59d1
This diff is collapsed.
arch/arc/include/asm/perf_event.h
View file @ 206c59d1
This diff is collapsed.
arch/arc/kernel/perf_event.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/kernel/process.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/kernel/setup.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/kernel/traps.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/mm/cache_arc700.c
View file @ 206c59d1
This diff is collapsed.
arch/arc/mm/init.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/Kconfig.debug
View file @ 206c59d1
This diff is collapsed.
arch/arm/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/compressed/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/compressed/head-shmobile.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/compressed/mmcif-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/compressed/sdhi-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/compressed/sdhi-shmobile.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/compressed/sdhi-shmobile.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/alpine-db.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/alpine.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-bone-common.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-boneblack.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-chiliboard.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-chilisom.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-evmsk.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am335x-nano.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am33xx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am33xx.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am3517.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am35xx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am4372.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am437x-idk-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am437x-sk-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am43x-epos-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am43xx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/am57xx-beagle-x15.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-370-db.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-370-mirabox.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-370-rd.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-370-xp.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-370.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-375-db.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-375.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-385-db-ap.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-388-db.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-388-gp.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-388-rd.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-38x.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-390.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-398-db.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-398.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-39x.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-axpwifiap.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-db.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-gp.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-linksys-mamba.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-matrix.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-mv78260.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp-mv78460.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/armada-xp.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91-sama5d3_xplained.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91-sama5d4_xplained.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91-sama5d4ek.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91rm9200.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9260.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9261.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9263.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9g25.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9g25ek.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9g45.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9n12.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9n12ek.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9rl.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9x5.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9x5_isi.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9x5cm.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/at91sam9x5ek.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm-cygnus.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm4708-netgear-r6250.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm4709-netgear-r8000.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm7445.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm911360_entphn.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm958300k.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/bcm958305k.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dm8168-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dm816x.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dove-cubox.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dove.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra7-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra7.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra72-evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra72x.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra74x.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/dra7xx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/emev2-kzm9d.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/emev2.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos3250.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos4412-trats2.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5250-snow.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5250-spring.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5250.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5420-peach-pit.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5420-pinctrl.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5420-smdk5420.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5420.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5422-odroidxu3.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/exynos5800-peach-pi.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/hip04.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx23-olinuxino.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx25-pdk.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx25-pinfunc.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx25.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx27.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx28-apf28.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx28-apf28dev.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx28.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx35.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx50.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx51.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx53.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6dl-aristainetos_4.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6dl-aristainetos_7.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6dl-cubox-i.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6dl-hummingboard.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6q-cubox-i.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6q-hummingboard.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6q.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6qdl-cubox-i.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6qdl-hummingboard.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6qdl-microsom.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6qdl-sabreauto.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6qdl.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sl-warp.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sl.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sx-sdb-reva.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sx-sdb.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sx-sdb.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/imx6sx.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/kirkwood-nas2big.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/kirkwood-net2big.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/meson.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/meson6-atv1200.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/meson8-minix-neo-x8.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/meson8.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/mt6589.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/nspire-classic.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/nspire-cx.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/nspire.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap2420.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap2430-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap2430.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap24xx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-beagle-xm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-beagle.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-cm-t3517.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-cm-t3730.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-cm-t3x30.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-devkit8000.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-evm-common.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-gta04.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-igep.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-igep0020-rev-f.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-igep0030-rev-g.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-lilly-a83x.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-n9.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-n900.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-n950-n9.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-n950.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-overo-base.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-pandora-1ghz.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-pandora-600mhz.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-pandora-common.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-tao3530.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3-zoom3.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap34xx-hs.dtsi deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/omap34xx.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap36xx-hs.dtsi deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/omap36xx.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap3xxx-clocks.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap4-cpu-thermal.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap4-panda-common.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap4-sdp.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap4.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/omap5.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-apq8064.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-apq8084-ifc6540.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-apq8084-mtp.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-apq8084.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-ipq8064.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-msm8660.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-msm8960.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-msm8974.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-pm8841.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-pm8941.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/qcom-pma8084.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a73a4-ape6evm-reference.dts deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/r8a73a4-ape6evm.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a73a4.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7740.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7778-bockw.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7778.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7779-marzen.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7790-lager.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7790.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7791-henninger.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7791-koelsch.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7791.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7794-alt.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/r8a7794.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3188-radxarock.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288-evb-act8846.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288-evb-rk808.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288-evb.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288-firefly.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288-popmetal.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/rk3288.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d35ek.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_can.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_emac.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_gmac.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_lcd.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_mci2.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_tcb1.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d3_uart.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sama5d4.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sh7372-mackerel.dts deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/sh7372.dtsi deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/sh73a0-kzm9g-reference.dts deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/boot/dts/sh73a0-kzm9g.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/sh73a0.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/ste-dbx5x0.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/ste-href.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/ste-snowball.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-jetson-tk1-emc.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-jetson-tk1.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-nyan-big-emc.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-nyan-big.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-nyan-blaze-emc.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-nyan-blaze.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124-nyan.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra124.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/tegra30-beaver.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vexpress-v2p-ca9.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vf-colibri.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vf500.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/vfxxx.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/boot/dts/zynq-7000.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm/common/mcpm_entry.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/ape6evm_defconfig deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/configs/at91_dt_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/exynos_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/imx_v4_v5_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/imx_v6_v7_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/mackerel_defconfig deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/configs/msm_defconfig deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/configs/multi_v5_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/multi_v7_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/mvebu_v7_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/mxs_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/omap1_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/omap2plus_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/qcom_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/shmobile_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/configs/sunxi_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/include/asm/dma-iommu.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/include/asm/mcpm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/include/asm/xen/page.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/include/debug/msm.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/include/uapi/asm/kvm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/kernel/entry-common.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/kernel/head-nommu.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/kernel/perf_event_cpu.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/kvm/arm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/Kconfig 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/Makefile 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/alpine_cpu_pm.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/alpine_cpu_resume.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/alpine_machine.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-alpine/platsmp.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/at91rm9200.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/at91sam9.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/generic.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91_dbgu.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91_ramc.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91_st.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91rm9200.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9260.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9260_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9261.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9261_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9263.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9263_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9g45.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9g45_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9n12.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9n12_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9rl.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9rl_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9x5.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/at91sam9x5_matrix.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/cpu.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/hardware.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/sama5d3.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/sama5d4.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/include/mach/uncompress.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/pm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/sama5.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/setup.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-at91/soc.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-at91/soc.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-bcm/bcm_cygnus.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-cns3xxx/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/asp.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/board-da850-evm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/devices-da8xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/dm646x.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-davinci/include/mach/irqs.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/exynos.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/firmware.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/mcpm-exynos.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/platsmp.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/pm_domains.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/regs-pmu.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/smc.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-exynos/suspend.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-gemini/common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-gemini/reset.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/clk-imx25.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/clk-imx6q.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/cpu-imx25.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/devices-imx25.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/devices/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/devices/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/devices/platform-fec.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/devices/platform-imx-fb.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/devices/platform-imxdi_rtc.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/ehci-imx25.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/eukrea_mbimxsd25-baseboard.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/gpc.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/hardware.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/iomux-mx25.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/iomux-mx3.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/iomux-v3.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/iomux-v3.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-cpuimx35.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-eukrea_cpuimx25.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/mach-imx6q.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-imx6sl.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-imx6sx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-mx25_3ds.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/mach-mx35_3ds.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-pcm043.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mach-vpr200.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-imx/mm-imx25.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/mx25.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-imx/pm-imx6.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mediatek/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-meson/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-msm/Kconfig deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/Makefile deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/Makefile.boot deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-halibut.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-msm7x30.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-qsd8x50.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-sapphire.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-trout-gpio.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-trout-mmc.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-trout-panel.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-trout.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/board-trout.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/clock-pcom.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/clock-pcom.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/clock.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/clock.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/common.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/devices-msm7x00.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/devices-msm7x30.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/devices-qsd8x50.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/devices.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/dma.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/gpiomux-8x50.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/gpiomux-v1.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/gpiomux.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/gpiomux.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/dma.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/entry-macro.S deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/irqs-7x00.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/irqs-7x30.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/irqs-8x50.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/irqs.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/msm_iomap-7x00.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/msm_iomap-7x30.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/msm_iomap-8x50.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/msm_iomap.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/msm_smd.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/sirc.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/include/mach/vreg.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/io.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/irq-vic.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/irq.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/last_radio_log.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/proc_comm.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/proc_comm.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/sirc.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/smd.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/smd_debug.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/smd_private.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-msm/vreg.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-mvebu/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mvebu/board-v7.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mvebu/dove.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mvebu/kirkwood.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mvebu/platsmp-a9.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-mvebu/pmsu.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap1/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/board-cm-t35.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/board-devkit8000.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-omap2/board-omap3stalker.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-omap2/board-omap3touchbook.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-omap2/clock.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/clock.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm2xxx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm2xxx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm33xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm33xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm3xxx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm3xxx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm44xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cm_common.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/cminst44xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/common.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/control.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/control.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/devices.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/display.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/gpmc-nand.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/gpmc-onenand.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/id.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/io.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/mux.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap-secure.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap34xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap4-common.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap_device.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap_hwmod.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap_hwmod_43xx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/omap_hwmod_7xx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/pdata-quirks.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/pm24xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/pm34xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prcm-common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prcm43xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm-regbits-34xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm-regbits-44xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm2xxx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm2xxx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm33xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm33xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm3xxx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm3xxx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm44xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm44xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm44xx_54xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm54xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm7xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prm_common.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prminst44xx.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/prminst44xx.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/sleep34xx.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/sleep44xx.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/timer.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/usb-tusb6010.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vc.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vc.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vc3xxx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vc44xx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vp.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vp3xxx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-omap2/vp44xx_data.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/include/mach/lubbock.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/include/mach/mainstone.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/lubbock.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/mainstone.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-pxa/pxa_cplds_irqs.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-qcom/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-qcom/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-qcom/platsmp.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-rockchip/platsmp.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-rockchip/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-rockchip/pm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-rockchip/rockchip.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/pm-s3c2416.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c2410.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c2412.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c2416.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c2440.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c2442.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c24xx/s3c244x.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/crag6410.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/mach-crag6410.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/mach-smdk6410.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-s3c64xx/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/Makefile.boot
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/board-ape6evm-reference.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/board-ape6evm.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/board-bockw.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/board-kzm9g-reference.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/board-kzm9g.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/board-mackerel.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/board-marzen.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/clock-r8a73a4.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/clock-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/clock.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/common.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/cpuidle.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/entry-intc.S deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/clkdev.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/head-mackerel.txt deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/mmc-mackerel.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/mmc.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/sdhi-sh7372.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/sdhi.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/system.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/uncompress.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/include/mach/zboot.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/intc-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/pm-r8a7790.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/pm-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/r8a73a4.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/r8a7790.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/r8a7791.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/rcar-gen2.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/regulator-quirk-rcar-gen2.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/setup-r8a73a4.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/setup-r8a7740.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/setup-r8a7778.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/setup-rcar-gen2.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/setup-sh7372.c deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/setup-sh73a0.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/sh7372.h deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/sh73a0.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/sleep-sh7372.S deleted 100644 → 0
View file @ 5ec596c4
This diff is collapsed.
arch/arm/mach-shmobile/smp-r8a7779.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/smp-r8a7790.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/smp-r8a7791.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-shmobile/smp-sh73a0.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-vexpress/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-vexpress/dcscb.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mach-vexpress/tc2_pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/dma-mapping.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/mmu.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/proc-arm1020.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/proc-arm1020e.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/proc-arm925.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/mm/proc-feroceon.S
View file @ 206c59d1
This diff is collapsed.
arch/arm/net/bpf_jit_32.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/plat-samsung/include/plat/pm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm/plat-samsung/pm-debug.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/plat-samsung/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/tools/mach-types
View file @ 206c59d1
This diff is collapsed.
arch/arm/vdso/.gitignore
View file @ 206c59d1
This diff is collapsed.
arch/arm/vdso/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm/xen/enlighten.c
View file @ 206c59d1
This diff is collapsed.
arch/arm/xen/mm.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/Kconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm64/Kconfig.debug
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/apm/apm-storm.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/arm/juno.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/mediatek/mt8173-evb.dts
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/mediatek/mt8173-pinfunc.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/mediatek/mt8173.dtsi
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/qcom/Makefile 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/qcom/msm8916-mtp.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/qcom/msm8916.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/sprd/Makefile 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/sprd/sc9836-openphone.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/sprd/sc9836.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/sprd/sharkl64.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/xilinx/Makefile 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/boot/dts/xilinx/zynqmp.dtsi 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/configs/defconfig
View file @ 206c59d1
This diff is collapsed.
arch/arm64/crypto/crc32-arm64.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/crypto/sha1-ce-glue.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/crypto/sha2-ce-glue.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/acenv.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/acpi.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/arm-cci.h 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/barrier.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/cpu_ops.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/fixmap.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/irq.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/pci.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/psci.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/asm/smp.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/include/uapi/asm/kvm.h
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/Makefile
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/acpi.c 0 → 100644
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/alternative.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/cpu_ops.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/pci.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/perf_event.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/psci.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/setup.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/smp.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/kernel/time.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/mm/dma-mapping.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/mm/dump.c
View file @ 206c59d1
This diff is collapsed.
arch/arm64/net/bpf_jit_comp.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF533-EZKIT_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF533-STAMP_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF537-STAMP_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF538-EZKIT_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF561-EZKIT_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/BF609-EZKIT_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF527_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF533_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF537E_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF537U_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF548_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/CM-BF561_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/DNP5370_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/IP0X_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/PNAV-10_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/SRV1_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/TCM-BF518_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/configs/TCM-BF537_defconfig
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/include/asm/io.h
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/include/uapi/asm/unistd.h
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/kernel/debug-mmrs.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/kernel/kgdb.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/kernel/setup.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/mach-bf561/smp.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/mach-bf609/boards/ezkit.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/mach-bf609/clock.c
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/mach-common/entry.S
View file @ 206c59d1
This diff is collapsed.
arch/blackfin/mach-common/pm.c
View file @ 206c59d1
This diff is collapsed.
arch/cris/Kconfig
View file @ 206c59d1
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7