Skip to content

K
Kernel

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

通知 8
Star 0
Fork 0
K
Kernel
提交 5a84d159 编写于 作者: R Russell King 提交者： Russell King
浏览文件
操作

Merge ARM fixes

上级 e80a0e6e 7d477a04
展开全部 隐藏空白更改
内联 并排
Showing with 56829 addition and 20553 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.mailmap 0 → 100644
浏览文件 @ 5a84d159
#
# This list is used by git-shortlog to fix a few botched name translations
# in the git archive, either because the author's full name was messed up
# and/or not always written the same way, making contributions from the
# same person appearing not to be so or badly displayed.
#
# repo-abbrev: /pub/scm/linux/kernel/git/
#
Aaron Durbin <adurbin@google.com>
Adam Oldham <oldhamca@gmail.com>
Adam Radford <aradford@gmail.com>
Adrian Bunk <bunk@stusta.de>
Alan Cox <alan@lxorguk.ukuu.org.uk>
Alan Cox <root@hraefn.swansea.linux.org.uk>
Aleksey Gorelov <aleksey_gorelov@phoenix.com>
Al Viro <viro@ftp.linux.org.uk>
Al Viro <viro@zenIV.linux.org.uk>
Andreas Herrmann <aherrman@de.ibm.com>
Andrew Morton <akpm@osdl.org>
Andrew Vasquez <andrew.vasquez@qlogic.com>
Andy Adamson <andros@citi.umich.edu>
Arnaud Patard <arnaud.patard@rtp-net.org>
Arnd Bergmann <arnd@arndb.de>
Axel Dyks <xl@xlsigned.net>
Ben Gardner <bgardner@wabtec.com>
Ben M Cahill <ben.m.cahill@intel.com>
Björn Steinbrink <B.Steinbrink@gmx.de>
Brian Avery <b.avery@hp.com>
Brian King <brking@us.ibm.com>
Christoph Hellwig <hch@lst.de>
Corey Minyard <minyard@acm.org>
David Brownell <david-b@pacbell.net>
David Woodhouse <dwmw2@shinybook.infradead.org>
Domen Puncer <domen@coderock.org>
Douglas Gilbert <dougg@torque.net>
Ed L. Cashin <ecashin@coraid.com>
Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Felipe W Damasio <felipewd@terra.com.br>
Felix Kuhling <fxkuehl@gmx.de>
Felix Moeller <felix@derklecks.de>
Filipe Lautert <filipe@icewall.org>
Franck Bui-Huu <vagabon.xyz@gmail.com>
Frank Zago <fzago@systemfabricworks.com>
Greg Kroah-Hartman <greg@echidna.(none)>
Greg Kroah-Hartman <gregkh@suse.de>
Greg Kroah-Hartman <greg@kroah.com>
Henk Vergonet <Henk.Vergonet@gmail.com>
Henrik Kretzschmar <henne@nachtwindheim.de>
Herbert Xu <herbert@gondor.apana.org.au>
Jacob Shin <Jacob.Shin@amd.com>
James Bottomley <jejb@mulgrave.(none)>
James Bottomley <jejb@titanic.il.steeleye.com>
James E Wilson <wilson@specifix.com>
James Ketrenos <jketreno@io.(none)>
Jean Tourrilhes <jt@hpl.hp.com>
Jeff Garzik <jgarzik@pretzel.yyz.us>
Jens Axboe <axboe@suse.de>
Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
John Stultz <johnstul@us.ibm.com>
Juha Yrjola <at solidboot.com>
Juha Yrjola <juha.yrjola@nokia.com>
Juha Yrjola <juha.yrjola@solidboot.com>
Kay Sievers <kay.sievers@vrfy.org>
Kenneth W Chen <kenneth.w.chen@intel.com>
Koushik <raghavendra.koushik@neterion.com>
Leonid I Ananiev <leonid.i.ananiev@intel.com>
Linas Vepstas <linas@austin.ibm.com>
Matthieu CASTET <castet.matthieu@free.fr>
Michel Dänzer <michel@tungstengraphics.com>
Mitesh shah <mshah@teja.com>
Morten Welinder <terra@gnome.org>
Morten Welinder <welinder@anemone.rentec.com>
Morten Welinder <welinder@darter.rentec.com>
Morten Welinder <welinder@troll.com>
Nguyen Anh Quynh <aquynh@gmail.com>
Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Patrick Mochel <mochel@digitalimplant.org>
Peter A Jonsson <pj@ludd.ltu.se>
Praveen BP <praveenbp@ti.com>
Rajesh Shah <rajesh.shah@intel.com>
Ralf Baechle <ralf@linux-mips.org>
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Rémi Denis-Courmont <rdenis@simphalempin.com>
Rudolf Marek <R.Marek@sh.cvut.cz>
Rui Saraiva <rmps@joel.ist.utl.pt>
Sachin P Sant <ssant@in.ibm.com>
Sam Ravnborg <sam@mars.ravnborg.org>
Simon Kelley <simon@thekelleys.org.uk>
Stéphane Witzmann <stephane.witzmann@ubpmes.univ-bpclermont.fr>
Stephen Hemminger <shemminger@osdl.org>
Tejun Heo <htejun@gmail.com>
Thomas Graf <tgraf@suug.ch>
Tony Luck <tony.luck@intel.com>
Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
CREDITS
浏览文件 @ 5a84d159
......@@ -2571,6 +2571,16 @@ S: Subiaco, 6008
S: Perth, Western Australia
S: Australia
N: Miguel Ojeda Sandonis
E: maxextreme@gmail.com
D: Author: Auxiliary LCD Controller driver (ks0108)
D: Author: Auxiliary LCD driver (cfag12864b)
D: Author: Auxiliary LCD framebuffer driver (cfag12864bfb)
D: Maintainer: Auxiliary display drivers tree (drivers/auxdisplay/*)
S: C/ Mieses 20, 9-B
S: Valladolid 47009
S: Spain
N: Greg Page
E: gpage@sovereign.org
D: IPX development and support
......
Documentation/ABI/testing/debugfs-pktcdvd
浏览文件 @ 5a84d159
What: /debug/pktcdvd/pktcdvd[0-7]
Date: Oct. 2006
KernelVersion: 2.6.19
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
......@@ -11,8 +11,7 @@ The pktcdvd module (packet writing driver) creates
these files in debugfs:
/debug/pktcdvd/pktcdvd[0-7]/
info (0444) Lots of human readable driver
statistics and infos. Multiple lines!
info (0444) Lots of driver statistics and infos.
Example:
-------
......
Documentation/ABI/testing/sysfs-class-pktcdvd
浏览文件 @ 5a84d159
What: /sys/class/pktcdvd/
Date: Oct. 2006
KernelVersion: 2.6.19
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
......
Documentation/DocBook/gadget.tmpl
浏览文件 @ 5a84d159
......@@ -482,13 +482,13 @@ slightly.
<para>Gadget drivers
rely on common USB structures and constants
defined in the
<filename>&lt;linux/usb_ch9.h&gt;</filename>
<filename>&lt;linux/usb/ch9.h&gt;</filename>
header file, which is standard in Linux 2.6 kernels.
These are the same types and constants used by host
side drivers (and usbcore).
</para>
!Iinclude/linux/usb_ch9.h
!Iinclude/linux/usb/ch9.h
</sect1>
<sect1 id="core"><title>Core Objects and Methods</title>
......
Documentation/DocBook/kernel-api.tmpl
浏览文件 @ 5a84d159
......@@ -316,6 +316,9 @@ X!Earch/i386/kernel/mca.c
<sect1><title>DMI Interfaces</title>
!Edrivers/firmware/dmi_scan.c
</sect1>
<sect1><title>EDD Interfaces</title>
!Idrivers/firmware/edd.c
</sect1>
</chapter>
<chapter id="security">
......
Documentation/DocBook/stylesheet.xsl
浏览文件 @ 5a84d159
......@@ -4,4 +4,5 @@
<param name="funcsynopsis.style">ansi</param>
<param name="funcsynopsis.tabular.threshold">80</param>
<!-- <param name="paper.type">A4</param> -->
<param name="generate.section.toc.level">2</param>
</stylesheet>
Documentation/DocBook/usb.tmpl
浏览文件 @ 5a84d159
......@@ -187,13 +187,13 @@
<chapter><title>USB-Standard Types</title>
<para>In <filename>&lt;linux/usb_ch9.h&gt;</filename> you will find
<para>In <filename>&lt;linux/usb/ch9.h&gt;</filename> you will find
the USB data types defined in chapter 9 of the USB specification.
These data types are used throughout USB, and in APIs including
this host side API, gadget APIs, and usbfs.
</para>
!Iinclude/linux/usb_ch9.h
!Iinclude/linux/usb/ch9.h
</chapter>
......@@ -574,7 +574,7 @@ for (;;) {
#include &lt;asm/byteorder.h&gt;</programlisting>
The standard USB device model requests, from "Chapter 9" of
the USB 2.0 specification, are automatically included from
the <filename>&lt;linux/usb_ch9.h&gt;</filename> header.
the <filename>&lt;linux/usb/ch9.h&gt;</filename> header.
</para>
<para>Unless noted otherwise, the ioctl requests
......
Documentation/HOWTO
浏览文件 @ 5a84d159
......@@ -30,6 +30,7 @@ are not a good substitute for a solid C education and/or years of
experience, the following books are good for, if anything, reference:
- "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
- "Practical C Programming" by Steve Oualline [O'Reilly]
- "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
The kernel is written using GNU C and the GNU toolchain. While it
adheres to the ISO C89 standard, it uses a number of extensions that are
......
Documentation/acpi-hotkey.txt 已删除 100644 → 0
浏览文件 @ e80a0e6e
driver/acpi/hotkey.c implement:
1. /proc/acpi/hotkey/event_config
(event based hotkey or event config interface):
a. add a event based hotkey(event) :
echo "0:bus::action:method:num:num" > event_config
b. delete a event based hotkey(event):
echo "1:::::num:num" > event_config
c. modify a event based hotkey(event):
echo "2:bus::action:method:num:num" > event_config
2. /proc/acpi/hotkey/poll_config
(polling based hotkey or event config interface):
a.add a polling based hotkey(event) :
echo "0:bus:method:action:method:num" > poll_config
this adding command will create a proc file
/proc/acpi/hotkey/method, which is used to get
result of polling.
b.delete a polling based hotkey(event):
echo "1:::::num" > event_config
c.modify a polling based hotkey(event):
echo "2:bus:method:action:method:num" > poll_config
3./proc/acpi/hotkey/action
(interface to call aml method associated with a
specific hotkey(event))
echo "event_num:event_type:event_argument" >
/proc/acpi/hotkey/action.
The result of the execution of this aml method is
attached to /proc/acpi/hotkey/poll_method, which is dynamically
created. Please use command "cat /proc/acpi/hotkey/polling_method"
to retrieve it.
Note: Use cmdline "acpi_generic_hotkey" to over-ride
platform-specific with generic driver.
Documentation/auxdisplay/cfag12864b 0 → 100644
浏览文件 @ 5a84d159
===================================
cfag12864b LCD Driver Documentation
===================================
License: GPLv2
Author & Maintainer: Miguel Ojeda Sandonis <maxextreme@gmail.com>
Date: 2006-10-27
--------
0. INDEX
--------
1. DRIVER INFORMATION
2. DEVICE INFORMATION
3. WIRING
4. USERSPACE PROGRAMMING
---------------------
1. DRIVER INFORMATION
---------------------
This driver support one cfag12864b display at time.
---------------------
2. DEVICE INFORMATION
---------------------
Manufacturer: Crystalfontz
Device Name: Crystalfontz 12864b LCD Series
Device Code: cfag12864b
Webpage: http://www.crystalfontz.com
Device Webpage: http://www.crystalfontz.com/products/12864b/
Type: LCD (Liquid Crystal Display)
Width: 128
Height: 64
Colors: 2 (B/N)
Controller: ks0108
Controllers: 2
Pages: 8 each controller
Addresses: 64 each page
Data size: 1 byte each address
Memory size: 2 * 8 * 64 * 1 = 1024 bytes = 1 Kbyte
---------
3. WIRING
---------
The cfag12864b LCD Series don't have official wiring.
The common wiring is done to the parallel port as shown:
Parallel Port cfag12864b
Name Pin# Pin# Name
Strobe ( 1)------------------------------(17) Enable
Data 0 ( 2)------------------------------( 4) Data 0
Data 1 ( 3)------------------------------( 5) Data 1
Data 2 ( 4)------------------------------( 6) Data 2
Data 3 ( 5)------------------------------( 7) Data 3
Data 4 ( 6)------------------------------( 8) Data 4
Data 5 ( 7)------------------------------( 9) Data 5
Data 6 ( 8)------------------------------(10) Data 6
Data 7 ( 9)------------------------------(11) Data 7
(10) [+5v]---( 1) Vdd
(11) [GND]---( 2) Ground
(12) [+5v]---(14) Reset
(13) [GND]---(15) Read / Write
Line (14)------------------------------(13) Controller Select 1
(15)
Init (16)------------------------------(12) Controller Select 2
Select (17)------------------------------(16) Data / Instruction
Ground (18)---[GND] [+5v]---(19) LED +
Ground (19)---[GND]
Ground (20)---[GND] E A Values:
Ground (21)---[GND] [GND]---[P1]---(18) Vee R = Resistor = 22 ohm
Ground (22)---[GND] | P1 = Preset = 10 Kohm
Ground (23)---[GND] ---- S ------( 3) V0 P2 = Preset = 1 Kohm
Ground (24)---[GND] | |
Ground (25)---[GND] [GND]---[P2]---[R]---(20) LED -
------------------------
4. USERSPACE PROGRAMMING
------------------------
The cfag12864bfb describes a framebuffer device (/dev/fbX).
It has a size of 1024 bytes = 1 Kbyte.
Each bit represents one pixel. If the bit is high, the pixel will
turn on. If the pixel is low, the pixel will turn off.
You can use the framebuffer as a file: fopen, fwrite, fclose...
Although the LCD won't get updated until the next refresh time arrives.
Also, you can mmap the framebuffer: open & mmap, munmap & close...
which is the best option for most uses.
Check Documentation/auxdisplay/cfag12864b-example.c
for a real working userspace complete program with usage examples.
Documentation/auxdisplay/cfag12864b-example.c 0 → 100644
浏览文件 @ 5a84d159
/*
* Filename: cfag12864b-example.c
* Version: 0.1.0
* Description: cfag12864b LCD userspace example program
* License: GPLv2
*
* Author: Copyright (C) Miguel Ojeda Sandonis <maxextreme@gmail.com>
* Date: 2006-10-31
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
*/
/*
* ------------------------
* start of cfag12864b code
* ------------------------
*/
#include <string.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/mman.h>
#define CFAG12864B_WIDTH (128)
#define CFAG12864B_HEIGHT (64)
#define CFAG12864B_SIZE (128 * 64 / 8)
#define CFAG12864B_BPB (8)
#define CFAG12864B_ADDRESS(x, y) ((y) * CFAG12864B_WIDTH / \
CFAG12864B_BPB + (x) / CFAG12864B_BPB)
#define CFAG12864B_BIT(n) (((unsigned char) 1) << (n))
#undef CFAG12864B_DOCHECK
#ifdef CFAG12864B_DOCHECK
#define CFAG12864B_CHECK(x, y) ((x) < CFAG12864B_WIDTH && \
(y) < CFAG12864B_HEIGHT)
#else
#define CFAG12864B_CHECK(x, y) (1)
#endif
int cfag12864b_fd;
unsigned char * cfag12864b_mem;
unsigned char cfag12864b_buffer[CFAG12864B_SIZE];
/*
* init a cfag12864b framebuffer device
*
* No error: return = 0
* Unable to open: return = -1
* Unable to mmap: return = -2
*/
int cfag12864b_init(char *path)
{
cfag12864b_fd = open(path, O_RDWR);
if (cfag12864b_fd == -1)
return -1;
cfag12864b_mem = mmap(0, CFAG12864B_SIZE, PROT_READ | PROT_WRITE,
MAP_SHARED, cfag12864b_fd, 0);
if (cfag12864b_mem == MAP_FAILED) {
close(cfag12864b_fd);
return -2;
}
return 0;
}
/*
* exit a cfag12864b framebuffer device
*/
void cfag12864b_exit(void)
{
munmap(cfag12864b_mem, CFAG12864B_SIZE);
close(cfag12864b_fd);
}
/*
* set (x, y) pixel
*/
void cfag12864b_set(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] |=
CFAG12864B_BIT(x % CFAG12864B_BPB);
}
/*
* unset (x, y) pixel
*/
void cfag12864b_unset(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] &=
~CFAG12864B_BIT(x % CFAG12864B_BPB);
}
/*
* is set (x, y) pixel?
*
* Pixel off: return = 0
* Pixel on: return = 1
*/
unsigned char cfag12864b_isset(unsigned char x, unsigned char y)
{
if (CFAG12864B_CHECK(x, y))
if (cfag12864b_buffer[CFAG12864B_ADDRESS(x, y)] &
CFAG12864B_BIT(x % CFAG12864B_BPB))
return 1;
return 0;
}
/*
* not (x, y) pixel
*/
void cfag12864b_not(unsigned char x, unsigned char y)
{
if (cfag12864b_isset(x, y))
cfag12864b_unset(x, y);
else
cfag12864b_set(x, y);
}
/*
* fill (set all pixels)
*/
void cfag12864b_fill(void)
{
unsigned short i;
for (i = 0; i < CFAG12864B_SIZE; i++)
cfag12864b_buffer[i] = 0xFF;
}
/*
* clear (unset all pixels)
*/
void cfag12864b_clear(void)
{
unsigned short i;
for (i = 0; i < CFAG12864B_SIZE; i++)
cfag12864b_buffer[i] = 0;
}
/*
* format a [128*64] matrix
*
* Pixel off: src[i] = 0
* Pixel on: src[i] > 0
*/
void cfag12864b_format(unsigned char * matrix)
{
unsigned char i, j, n;
for (i = 0; i < CFAG12864B_HEIGHT; i++)
for (j = 0; j < CFAG12864B_WIDTH / CFAG12864B_BPB; j++) {
cfag12864b_buffer[i * CFAG12864B_WIDTH / CFAG12864B_BPB +
j] = 0;
for (n = 0; n < CFAG12864B_BPB; n++)
if (matrix[i * CFAG12864B_WIDTH +
j * CFAG12864B_BPB + n])
cfag12864b_buffer[i * CFAG12864B_WIDTH /
CFAG12864B_BPB + j] |=
CFAG12864B_BIT(n);
}
}
/*
* blit buffer to lcd
*/
void cfag12864b_blit(void)
{
memcpy(cfag12864b_mem, cfag12864b_buffer, CFAG12864B_SIZE);
}
/*
* ----------------------
* end of cfag12864b code
* ----------------------
*/
#include <stdio.h>
#include <string.h>
#define EXAMPLES 6
void example(unsigned char n)
{
unsigned short i, j;
unsigned char matrix[CFAG12864B_WIDTH * CFAG12864B_HEIGHT];
if (n > EXAMPLES)
return;
printf("Example %i/%i - ", n, EXAMPLES);
switch (n) {
case 1:
printf("Draw points setting bits");
cfag12864b_clear();
for (i = 0; i < CFAG12864B_WIDTH; i += 2)
for (j = 0; j < CFAG12864B_HEIGHT; j += 2)
cfag12864b_set(i, j);
break;
case 2:
printf("Clear the LCD");
cfag12864b_clear();
break;
case 3:
printf("Draw rows formatting a [128*64] matrix");
memset(matrix, 0, CFAG12864B_WIDTH * CFAG12864B_HEIGHT);
for (i = 0; i < CFAG12864B_WIDTH; i++)
for (j = 0; j < CFAG12864B_HEIGHT; j += 2)
matrix[j * CFAG12864B_WIDTH + i] = 1;
cfag12864b_format(matrix);
break;
case 4:
printf("Fill the lcd");
cfag12864b_fill();
break;
case 5:
printf("Draw columns unsetting bits");
for (i = 0; i < CFAG12864B_WIDTH; i += 2)
for (j = 0; j < CFAG12864B_HEIGHT; j++)
cfag12864b_unset(i, j);
break;
case 6:
printf("Do negative not-ing all bits");
for (i = 0; i < CFAG12864B_WIDTH; i++)
for (j = 0; j < CFAG12864B_HEIGHT; j ++)
cfag12864b_not(i, j);
break;
}
puts(" - [Press Enter]");
}
int main(int argc, char *argv[])
{
unsigned char n;
if (argc != 2) {
printf(
"Sintax: %s fbdev\n"
"Usually: /dev/fb0, /dev/fb1...\n", argv[0]);
return -1;
}
if (cfag12864b_init(argv[1])) {
printf("Can't init %s fbdev\n", argv[1]);
return -2;
}
for (n = 1; n <= EXAMPLES; n++) {
example(n);
cfag12864b_blit();
while (getchar() != '\n');
}
cfag12864b_exit();
return 0;
}
Documentation/auxdisplay/ks0108 0 → 100644
浏览文件 @ 5a84d159
==========================================
ks0108 LCD Controller Driver Documentation
==========================================
License: GPLv2
Author & Maintainer: Miguel Ojeda Sandonis <maxextreme@gmail.com>
Date: 2006-10-27
--------
0. INDEX
--------
1. DRIVER INFORMATION
2. DEVICE INFORMATION
3. WIRING
---------------------
1. DRIVER INFORMATION
---------------------
This driver support the ks0108 LCD controller.
---------------------
2. DEVICE INFORMATION
---------------------
Manufacturer: Samsung
Device Name: KS0108 LCD Controller
Device Code: ks0108
Webpage: -
Device Webpage: -
Type: LCD Controller (Liquid Crystal Display Controller)
Width: 64
Height: 64
Colors: 2 (B/N)
Pages: 8
Addresses: 64 each page
Data size: 1 byte each address
Memory size: 8 * 64 * 1 = 512 bytes
---------
3. WIRING
---------
The driver supports data parallel port wiring.
If you aren't building LCD related hardware, you should check
your LCD specific wiring information in the same folder.
For example, check Documentation/auxdisplay/cfag12864b.
Documentation/cdrom/packet-writing.txt
浏览文件 @ 5a84d159
......@@ -93,7 +93,7 @@ Notes
Using the pktcdvd sysfs interface
---------------------------------
Since Linux 2.6.19, the pktcdvd module has a sysfs interface
Since Linux 2.6.20, the pktcdvd module has a sysfs interface
and can be controlled by it. For example the "pktcdvd" tool uses
this interface. (see http://people.freenet.de/BalaGi#pktcdvd )
......
Documentation/crypto/api-intro.txt
浏览文件 @ 5a84d159
......@@ -193,6 +193,7 @@ Original developers of the crypto algorithms:
Kartikey Mahendra Bhatt (CAST6)
Jon Oberheide (ARC4)
Jouni Malinen (Michael MIC)
NTT(Nippon Telegraph and Telephone Corporation) (Camellia)
SHA1 algorithm contributors:
Jean-Francois Dive
......@@ -246,6 +247,9 @@ Tiger algorithm contributors:
VIA PadLock contributors:
Michal Ludvig
Camellia algorithm contributors:
NTT(Nippon Telegraph and Telephone Corporation) (Camellia)
Generic scatterwalk code by Adam J. Richter <adam@yggdrasil.com>
Please send any credits updates or corrections to:
......
Documentation/driver-model/devres.txt 0 → 100644
浏览文件 @ 5a84d159
Devres - Managed Device Resource
================================
Tejun Heo <teheo@suse.de>
First draft 10 January 2007
1. Intro : Huh? Devres?
2. Devres : Devres in a nutshell
3. Devres Group : Group devres'es and release them together
4. Details : Life time rules, calling context, ...
5. Overhead : How much do we have to pay for this?
6. List of managed interfaces : Currently implemented managed interfaces
1. Intro
--------
devres came up while trying to convert libata to use iomap. Each
iomapped address should be kept and unmapped on driver detach. For
example, a plain SFF ATA controller (that is, good old PCI IDE) in
native mode makes use of 5 PCI BARs and all of them should be
maintained.
As with many other device drivers, libata low level drivers have
sufficient bugs in ->remove and ->probe failure path. Well, yes,
that's probably because libata low level driver developers are lazy
bunch, but aren't all low level driver developers? After spending a
day fiddling with braindamaged hardware with no document or
braindamaged document, if it's finally working, well, it's working.
For one reason or another, low level drivers don't receive as much
attention or testing as core code, and bugs on driver detach or
initilaization failure doesn't happen often enough to be noticeable.
Init failure path is worse because it's much less travelled while
needs to handle multiple entry points.
So, many low level drivers end up leaking resources on driver detach
and having half broken failure path implementation in ->probe() which
would leak resources or even cause oops when failure occurs. iomap
adds more to this mix. So do msi and msix.
2. Devres
---------
devres is basically linked list of arbitrarily sized memory areas
associated with a struct device. Each devres entry is associated with
a release function. A devres can be released in several ways. No
matter what, all devres entries are released on driver detach. On
release, the associated release function is invoked and then the
devres entry is freed.
Managed interface is created for resources commonly used by device
drivers using devres. For example, coherent DMA memory is acquired
using dma_alloc_coherent(). The managed version is called
dmam_alloc_coherent(). It is identical to dma_alloc_coherent() except
for the DMA memory allocated using it is managed and will be
automatically released on driver detach. Implementation looks like
the following.
struct dma_devres {
size_t size;
void *vaddr;
dma_addr_t dma_handle;
};
static void dmam_coherent_release(struct device *dev, void *res)
{
struct dma_devres *this = res;
dma_free_coherent(dev, this->size, this->vaddr, this->dma_handle);
}
dmam_alloc_coherent(dev, size, dma_handle, gfp)
{
struct dma_devres *dr;
void *vaddr;
dr = devres_alloc(dmam_coherent_release, sizeof(*dr), gfp);
...
/* alloc DMA memory as usual */
vaddr = dma_alloc_coherent(...);
...
/* record size, vaddr, dma_handle in dr */
dr->vaddr = vaddr;
...
devres_add(dev, dr);
return vaddr;
}
If a driver uses dmam_alloc_coherent(), the area is guaranteed to be
freed whether initialization fails half-way or the device gets
detached. If most resources are acquired using managed interface, a
driver can have much simpler init and exit code. Init path basically
looks like the following.
my_init_one()
{
struct mydev *d;
d = devm_kzalloc(dev, sizeof(*d), GFP_KERNEL);
if (!d)
return -ENOMEM;
d->ring = dmam_alloc_coherent(...);
if (!d->ring)
return -ENOMEM;
if (check something)
return -EINVAL;
...
return register_to_upper_layer(d);
}
And exit path,
my_remove_one()
{
unregister_from_upper_layer(d);
shutdown_my_hardware();
}
As shown above, low level drivers can be simplified a lot by using
devres. Complexity is shifted from less maintained low level drivers
to better maintained higher layer. Also, as init failure path is
shared with exit path, both can get more testing.
3. Devres group
---------------
Devres entries can be grouped using devres group. When a group is
released, all contained normal devres entries and properly nested
groups are released. One usage is to rollback series of acquired
resources on failure. For example,
if (!devres_open_group(dev, NULL, GFP_KERNEL))
return -ENOMEM;
acquire A;
if (failed)
goto err;
acquire B;
if (failed)
goto err;
...
devres_remove_group(dev, NULL);
return 0;
err:
devres_release_group(dev, NULL);
return err_code;
As resource acquision failure usually means probe failure, constructs
like above are usually useful in midlayer driver (e.g. libata core
layer) where interface function shouldn't have side effect on failure.
For LLDs, just returning error code suffices in most cases.
Each group is identified by void *id. It can either be explicitly
specified by @id argument to devres_open_group() or automatically
created by passing NULL as @id as in the above example. In both
cases, devres_open_group() returns the group's id. The returned id
can be passed to other devres functions to select the target group.
If NULL is given to those functions, the latest open group is
selected.
For example, you can do something like the following.
int my_midlayer_create_something()
{
if (!devres_open_group(dev, my_midlayer_create_something, GFP_KERNEL))
return -ENOMEM;
...
devres_close_group(dev, my_midlayer_something);
return 0;
}
void my_midlayer_destroy_something()
{
devres_release_group(dev, my_midlayer_create_soemthing);
}
4. Details
----------
Lifetime of a devres entry begins on devres allocation and finishes
when it is released or destroyed (removed and freed) - no reference
counting.
devres core guarantees atomicity to all basic devres operations and
has support for single-instance devres types (atomic
lookup-and-add-if-not-found). Other than that, synchronizing
concurrent accesses to allocated devres data is caller's
responsibility. This is usually non-issue because bus ops and
resource allocations already do the job.
For an example of single-instance devres type, read pcim_iomap_table()
in lib/iomap.c.
All devres interface functions can be called without context if the
right gfp mask is given.
5. Overhead
-----------
Each devres bookkeeping info is allocated together with requested data
area. With debug option turned off, bookkeeping info occupies 16
bytes on 32bit machines and 24 bytes on 64bit (three pointers rounded
up to ull alignment). If singly linked list is used, it can be
reduced to two pointers (8 bytes on 32bit, 16 bytes on 64bit).
Each devres group occupies 8 pointers. It can be reduced to 6 if
singly linked list is used.
Memory space overhead on ahci controller with two ports is between 300
and 400 bytes on 32bit machine after naive conversion (we can
certainly invest a bit more effort into libata core layer).
6. List of managed interfaces
-----------------------------
IO region
devm_request_region()
devm_request_mem_region()
devm_release_region()
devm_release_mem_region()
IRQ
devm_request_irq()
devm_free_irq()
DMA
dmam_alloc_coherent()
dmam_free_coherent()
dmam_alloc_noncoherent()
dmam_free_noncoherent()
dmam_declare_coherent_memory()
dmam_pool_create()
dmam_pool_destroy()
PCI
pcim_enable_device() : after success, all PCI ops become managed
pcim_pin_device() : keep PCI device enabled after release
IOMAP
devm_ioport_map()
devm_ioport_unmap()
devm_ioremap()
devm_ioremap_nocache()
devm_iounmap()
pcim_iomap()
pcim_iounmap()
pcim_iomap_table() : array of mapped addresses indexed by BAR
pcim_iomap_regions() : do request_region() and iomap() on multiple BARs
Documentation/driver-model/platform.txt
浏览文件 @ 5a84d159
......@@ -66,7 +66,7 @@ runtime memory footprint:
Device Enumeration
~~~~~~~~~~~~~~~~~~
As a rule, platform specific (and often board-specific) setup code wil
As a rule, platform specific (and often board-specific) setup code will
register platform devices:
int platform_device_register(struct platform_device *pdev);
......@@ -106,7 +106,7 @@ It's built from two components:
* platform_device.id ... the device instance number, or else "-1"
to indicate there's only one.
These are catenated, so name/id "serial"/0 indicates bus_id "serial.0", and
These are concatenated, so name/id "serial"/0 indicates bus_id "serial.0", and
"serial/3" indicates bus_id "serial.3"; both would use the platform_driver
named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id)
and use the platform_driver called "my_rtc".
......
Documentation/drivers/edac/edac.txt
浏览文件 @ 5a84d159
......@@ -339,7 +339,21 @@ Device Symlink:
'device'
Symlink to the memory controller device
Symlink to the memory controller device.
Sdram memory scrubbing rate:
'sdram_scrub_rate'
Read/Write attribute file that controls memory scrubbing. The scrubbing
rate is set by writing a minimum bandwith in bytes/sec to the attribute
file. The rate will be translated to an internal value that gives at
least the specified rate.
Reading the file will return the actual scrubbing rate employed.
If configuration fails or memory scrubbing is not implemented, the value
of the attribute file will be -1.
......
Documentation/fb/s3fb.txt 0 → 100644
浏览文件 @ 5a84d159
s3fb - fbdev driver for S3 Trio/Virge chips
===========================================
Supported Hardware
==================
S3 Trio32
S3 Trio64 (and variants V+, UV+, V2/DX, V2/GX)
S3 Virge (and variants VX, DX, GX and GX2+)
S3 Plato/PX (completely untested)
S3 Aurora64V+ (completely untested)
- only PCI bus supported
- only BIOS initialized VGA devices supported
- probably not working on big endian
I tested s3fb on Trio64 (plain, V+ and V2/DX) and Virge (plain, VX, DX),
all on i386.
Supported Features
==================
* 4 bpp pseudocolor modes (with 18bit palette, two variants)
* 8 bpp pseudocolor mode (with 18bit palette)
* 16 bpp truecolor modes (RGB 555 and RGB 565)
* 24 bpp truecolor mode (RGB 888) on (only on Virge VX)
* 32 bpp truecolor mode (RGB 888) on (not on Virge VX)
* text mode (activated by bpp = 0)
* interlaced mode variant (not available in text mode)
* doublescan mode variant (not available in text mode)
* panning in both directions
* suspend/resume support
* DPMS support
Text mode is supported even in higher resolutions, but there is limitation
to lower pixclocks (maximum between 50-60 MHz, depending on specific hardware).
This limitation is not enforced by driver. Text mode supports 8bit wide fonts
only (hardware limitation) and 16bit tall fonts (driver limitation).
There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
packed pixels, high nibble first. Second mode (selected if nonstd == 1) is mode
with interleaved planes (1 byte interleave), MSB first. Both modes support
8bit wide fonts only (driver limitation).
Suspend/resume works on systems that initialize video card during resume and
if device is active (for example used by fbcon).
Missing Features
================
(alias TODO list)
* secondary (not initialized by BIOS) device support
* big endian support
* Zorro bus support
* MMIO support
* 24 bpp mode support on more cards
* support for fontwidths != 8 in 4 bpp modes
* support for fontheight != 16 in text mode
* composite and external sync (is anyone able to test this?)
* hardware cursor
* video overlay support
* vsync synchronization
* feature connector support
* acceleration support (8514-like 2D, Virge 3D, busmaster transfers)
* better values for some magic registers (performance issues)
Known bugs
==========
* cursor disable in text mode doesn't work
--
Ondrej Zajicek <santiago@crfreenet.org>
Documentation/feature-removal-schedule.txt
浏览文件 @ 5a84d159
......@@ -50,22 +50,6 @@ Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: ieee1394 core's unused exports (CONFIG_IEEE1394_EXPORT_FULL_API)
When: January 2007
Why: There are no projects known to use these exported symbols, except
dfg1394 (uses one symbol whose functionality is core-internal now).
Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: ieee1394's *_oui sysfs attributes (CONFIG_IEEE1394_OUI_DB)
When: January 2007
Files: drivers/ieee1394/: oui.db, oui2c.sh
Why: big size, little value
Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
---------------------------
What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
When: December 2006
Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
......@@ -186,18 +170,6 @@ Who: Greg Kroah-Hartman <gregkh@suse.de>
---------------------------
What: find_trylock_page
When: January 2007
Why: The interface no longer has any callers left in the kernel. It
is an odd interface (compared with other find_*_page functions), in
that it does not take a refcount to the page, only the page lock.
It should be replaced with find_get_page or find_lock_page if possible.
This feature removal can be reevaluated if users of the interface
cannot cleanly use something else.
Who: Nick Piggin <npiggin@suse.de>
---------------------------
What: Interrupt only SA_* flags
When: Januar 2007
Why: The interrupt related SA_* flags are replaced by IRQF_* to move them
......@@ -243,6 +215,13 @@ Who: Jean Delvare <khali@linux-fr.org>,
---------------------------
What: drivers depending on OBSOLETE_OSS
When: options in 2.6.22, code in 2.6.24
Why: OSS drivers with ALSA replacements
Who: Adrian Bunk <bunk@stusta.de>
---------------------------
What: IPv4 only connection tracking/NAT/helpers
When: 2.6.22
Why: The new layer 3 independant connection tracking replaces the old
......@@ -274,28 +253,6 @@ Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
---------------------------
What: ACPI hotkey driver (CONFIG_ACPI_HOTKEY)
When: 2.6.21
Why: hotkey.c was an attempt to consolidate multiple drivers that use
ACPI to implement hotkeys. However, hotkeys are not documented
in the ACPI specification, so the drivers used undocumented
vendor-specific hooks and turned out to be more different than
the same.
Further, the keys and the features supplied by each platform
are different, so there will always be a need for
platform-specific drivers.
So the new plan is to delete hotkey.c and instead, work on the
platform specific drivers to try to make them look the same
to the user when they supply the same features.
hotkey.c has always depended on CONFIG_EXPERIMENTAL
Who: Len Brown <len.brown@intel.com>
---------------------------
What: /sys/firmware/acpi/namespace
When: 2.6.21
Why: The ACPI namespace is effectively the symbol list for
......@@ -306,11 +263,18 @@ Why: The ACPI namespace is effectively the symbol list for
the BIOS can be extracted and disassembled with acpidump
and iasl as documented in the pmtools package here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils
Who: Len Brown <len.brown@intel.com>
---------------------------
What: ACPI procfs interface
When: July 2007
Why: After ACPI sysfs conversion, ACPI attributes will be duplicated
in sysfs and the ACPI procfs interface should be removed.
Who: Zhang Rui <rui.zhang@intel.com>
---------------------------
What: /proc/acpi/button
When: August 2007
Why: /proc/acpi/button has been replaced by events to the input layer
......@@ -319,9 +283,24 @@ Who: Len Brown <len.brown@intel.com>
---------------------------
What: JFFS (version 1)
When: 2.6.21
Why: Unmaintained for years, superceded by JFFS2 for years.
Who: Jeff Garzik <jeff@garzik.org>
What: sk98lin network driver
When: July 2007
Why: In kernel tree version of driver is unmaintained. Sk98lin driver
replaced by the skge driver.
Who: Stephen Hemminger <shemminger@osdl.org>
---------------------------
What: Compaq touchscreen device emulation
When: Oct 2007
Files: drivers/input/tsdev.c
Why: The code says it was obsolete when it was written in 2001.
tslib is a userspace library which does anything tsdev can do and
much more besides in userspace where this code belongs. There is no
longer any need for tsdev and applications should have converted to
use tslib by now.
The name "tsdev" is also extremely confusing and lots of people have
it loaded when they don't need/use it.
Who: Richard Purdie <rpurdie@rpsys.net>
---------------------------
Documentation/filesystems/00-INDEX
浏览文件 @ 5a84d159
......@@ -4,6 +4,8 @@ Exporting
- explanation of how to make filesystems exportable.
Locking
- info on locking rules as they pertain to Linux VFS.
9p.txt
- 9p (v9fs) is an implementation of the Plan 9 remote fs protocol.
adfs.txt
- info and mount options for the Acorn Advanced Disc Filing System.
afs.txt
......@@ -82,8 +84,6 @@ udf.txt
- info and mount options for the UDF filesystem.
ufs.txt
- info on the ufs filesystem.
v9fs.txt
- v9fs is a Unix implementation of the Plan 9 9p remote fs protocol.
vfat.txt
- info on using the VFAT filesystem used in Windows NT and Windows 95
vfs.txt
......
Documentation/filesystems/9p.txt
浏览文件 @ 5a84d159
......@@ -40,6 +40,10 @@ OPTIONS
aname=name aname specifies the file tree to access when the server is
offering several exported file systems.
cache=mode specifies a cacheing policy. By default, no caches are used.
loose = no attempts are made at consistency,
intended for exclusive, read-only mounts
debug=n specifies debug level. The debug level is a bitmask.
0x01 = display verbose error messages
0x02 = developer debug (DEBUG_CURRENT)
......
Documentation/filesystems/relay.txt
浏览文件 @ 5a84d159
......@@ -157,7 +157,7 @@ TBD(curr. line MT:/API/)
channel management functions:
relay_open(base_filename, parent, subbuf_size, n_subbufs,
callbacks)
callbacks, private_data)
relay_close(chan)
relay_flush(chan)
relay_reset(chan)
......@@ -251,7 +251,7 @@ static struct rchan_callbacks relay_callbacks =
And an example relay_open() invocation using them:
chan = relay_open("cpu", NULL, SUBBUF_SIZE, N_SUBBUFS, &relay_callbacks);
chan = relay_open("cpu", NULL, SUBBUF_SIZE, N_SUBBUFS, &relay_callbacks, NULL);
If the create_buf_file() callback fails, or isn't defined, channel
creation and thus relay_open() will fail.
......@@ -289,6 +289,11 @@ they use the proper locking for such a buffer, either by wrapping
writes in a spinlock, or by copying a write function from relay.h and
creating a local version that internally does the proper locking.
The private_data passed into relay_open() allows clients to associate
user-defined data with a channel, and is immediately available
(including in create_buf_file()) via chan->private_data or
buf->chan->private_data.
Channel 'modes'
---------------
......
Documentation/filesystems/sysfs-pci.txt
浏览文件 @ 5a84d159
......@@ -65,7 +65,7 @@ Accessing legacy resources through sysfs
----------------------------------------
Legacy I/O port and ISA memory resources are also provided in sysfs if the
underlying platform supports them. They're located in the PCI class heirarchy,
underlying platform supports them. They're located in the PCI class hierarchy,
e.g.
/sys/class/pci_bus/0000:17/
......
Documentation/filesystems/ufs.txt
浏览文件 @ 5a84d159
......@@ -21,7 +21,7 @@ ufstype=type_of_ufs
supported as read-write
ufs2 used in FreeBSD 5.x
supported as read-only
supported as read-write
5xbsd synonym for ufs2
......@@ -50,12 +50,11 @@ ufstype=type_of_ufs
POSSIBLE PROBLEMS
=================
There is still bug in reallocation of fragment, in file fs/ufs/balloc.c,
line 364. But it seems working on current buffer cache configuration.
See next section, if you have any.
BUG REPORTS
===========
Any ufs bug report you can send to daniel.pirkl@email.cz (do not send
partition tables bug reports.)
Any ufs bug report you can send to daniel.pirkl@email.cz or
to dushistov@mail.ru (do not send partition tables bug reports).
Documentation/gpio.txt 0 → 100644
浏览文件 @ 5a84d159
GPIO Interfaces
This provides an overview of GPIO access conventions on Linux.
What is a GPIO?
===============
A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
digital signal. They are provided from many kinds of chip, and are familiar
to Linux developers working with embedded and custom hardware. Each GPIO
represents a bit connected to a particular pin, or "ball" on Ball Grid Array
(BGA) packages. Board schematics show which external hardware connects to
which GPIOs. Drivers can be written generically, so that board setup code
passes such pin configuration data to drivers.
System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
non-dedicated pin can be configured as a GPIO; and most chips have at least
several dozen of them. Programmable logic devices (like FPGAs) can easily
provide GPIOs; multifunction chips like power managers, and audio codecs
often have a few such pins to help with pin scarcity on SOCs; and there are
also "GPIO Expander" chips that connect using the I2C or SPI serial busses.
Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
firmware knowing how they're used).
The exact capabilities of GPIOs vary between systems. Common options:
- Output values are writable (high=1, low=0). Some chips also have
options about how that value is driven, so that for example only one
value might be driven ... supporting "wire-OR" and similar schemes
for the other value.
- Input values are likewise readable (1, 0). Some chips support readback
of pins configured as "output", which is very useful in such "wire-OR"
cases (to support bidirectional signaling). GPIO controllers may have
input de-glitch logic, sometimes with software controls.
- Inputs can often be used as IRQ signals, often edge triggered but
sometimes level triggered. Such IRQs may be configurable as system
wakeup events, to wake the system from a low power state.
- Usually a GPIO will be configurable as either input or output, as needed
by different product boards; single direction ones exist too.
- Most GPIOs can be accessed while holding spinlocks, but those accessed
through a serial bus normally can't. Some systems support both types.
On a given board each GPIO is used for one specific purpose like monitoring
MMC/SD card insertion/removal, detecting card writeprotect status, driving
a LED, configuring a transceiver, bitbanging a serial bus, poking a hardware
watchdog, sensing a switch, and so on.
GPIO conventions
================
Note that this is called a "convention" because you don't need to do it this
way, and it's no crime if you don't. There **are** cases where portability
is not the main issue; GPIOs are often used for the kind of board-specific
glue logic that may even change between board revisions, and can't ever be
used on a board that's wired differently. Only least-common-denominator
functionality can be very portable. Other features are platform-specific,
and that can be critical for glue logic.
Plus, this doesn't define an implementation framework, just an interface.
One platform might implement it as simple inline functions accessing chip
registers; another might implement it by delegating through abstractions
used for several very different kinds of GPIO controller.
That said, if the convention is supported on their platform, drivers should
use it when possible:
#include <asm/gpio.h>
If you stick to this convention then it'll be easier for other developers to
see what your code is doing, and help maintain it.
Identifying GPIOs
-----------------
GPIOs are identified by unsigned integers in the range 0..MAX_INT. That
reserves "negative" numbers for other purposes like marking signals as
"not available on this board", or indicating faults. Code that doesn't
touch the underlying hardware treats these integers as opaque cookies.
Platforms define how they use those integers, and usually #define symbols
for the GPIO lines so that board-specific setup code directly corresponds
to the relevant schematics. In contrast, drivers should only use GPIO
numbers passed to them from that setup code, using platform_data to hold
board-specific pin configuration data (along with other board specific
data they need). That avoids portability problems.
So for example one platform uses numbers 32-159 for GPIOs; while another
uses numbers 0..63 with one set of GPIO controllers, 64-79 with another
type of GPIO controller, and on one particular board 80-95 with an FPGA.
The numbers need not be contiguous; either of those platforms could also
use numbers 2000-2063 to identify GPIOs in a bank of I2C GPIO expanders.
Whether a platform supports multiple GPIO controllers is currently a
platform-specific implementation issue.
Using GPIOs
-----------
One of the first things to do with a GPIO, often in board setup code when
setting up a platform_device using the GPIO, is mark its direction:
/* set as input or output, returning 0 or negative errno */
int gpio_direction_input(unsigned gpio);
int gpio_direction_output(unsigned gpio);
The return value is zero for success, else a negative errno. It should
be checked, since the get/set calls don't have error returns and since
misconfiguration is possible. (These calls could sleep.)
Setting the direction can fail if the GPIO number is invalid, or when
that particular GPIO can't be used in that mode. It's generally a bad
idea to rely on boot firmware to have set the direction correctly, since
it probably wasn't validated to do more than boot Linux. (Similarly,
that board setup code probably needs to multiplex that pin as a GPIO,
and configure pullups/pulldowns appropriately.)
Spinlock-Safe GPIO access
-------------------------
Most GPIO controllers can be accessed with memory read/write instructions.
That doesn't need to sleep, and can safely be done from inside IRQ handlers.
Use these calls to access such GPIOs:
/* GPIO INPUT: return zero or nonzero */
int gpio_get_value(unsigned gpio);
/* GPIO OUTPUT */
void gpio_set_value(unsigned gpio, int value);
The values are boolean, zero for low, nonzero for high. When reading the
value of an output pin, the value returned should be what's seen on the
pin ... that won't always match the specified output value, because of
issues including wire-OR and output latencies.
The get/set calls have no error returns because "invalid GPIO" should have
been reported earlier in gpio_set_direction(). However, note that not all
platforms can read the value of output pins; those that can't should always
return zero. Also, using these calls for GPIOs that can't safely be accessed
without sleeping (see below) is an error.
Platform-specific implementations are encouraged to optimize the two
calls to access the GPIO value in cases where the GPIO number (and for
output, value) are constant. It's normal for them to need only a couple
of instructions in such cases (reading or writing a hardware register),
and not to need spinlocks. Such optimized calls can make bitbanging
applications a lot more efficient (in both space and time) than spending
dozens of instructions on subroutine calls.
GPIO access that may sleep
--------------------------
Some GPIO controllers must be accessed using message based busses like I2C
or SPI. Commands to read or write those GPIO values require waiting to
get to the head of a queue to transmit a command and get its response.
This requires sleeping, which can't be done from inside IRQ handlers.
Platforms that support this type of GPIO distinguish them from other GPIOs
by returning nonzero from this call:
int gpio_cansleep(unsigned gpio);
To access such GPIOs, a different set of accessors is defined:
/* GPIO INPUT: return zero or nonzero, might sleep */
int gpio_get_value_cansleep(unsigned gpio);
/* GPIO OUTPUT, might sleep */
void gpio_set_value_cansleep(unsigned gpio, int value);
Other than the fact that these calls might sleep, and will not be ignored
for GPIOs that can't be accessed from IRQ handlers, these calls act the
same as the spinlock-safe calls.
Claiming and Releasing GPIOs (OPTIONAL)
---------------------------------------
To help catch system configuration errors, two calls are defined.
However, many platforms don't currently support this mechanism.
/* request GPIO, returning 0 or negative errno.
* non-null labels may be useful for diagnostics.
*/
int gpio_request(unsigned gpio, const char *label);
/* release previously-claimed GPIO */
void gpio_free(unsigned gpio);
Passing invalid GPIO numbers to gpio_request() will fail, as will requesting
GPIOs that have already been claimed with that call. The return value of
gpio_request() must be checked. (These calls could sleep.)
These calls serve two basic purposes. One is marking the signals which
are actually in use as GPIOs, for better diagnostics; systems may have
several hundred potential GPIOs, but often only a dozen are used on any
given board. Another is to catch conflicts between drivers, reporting
errors when drivers wrongly think they have exclusive use of that signal.
These two calls are optional because not not all current Linux platforms
offer such functionality in their GPIO support; a valid implementation
could return success for all gpio_request() calls. Unlike the other calls,
the state they represent doesn't normally match anything from a hardware
register; it's just a software bitmap which clearly is not necessary for
correct operation of hardware or (bug free) drivers.
Note that requesting a GPIO does NOT cause it to be configured in any
way; it just marks that GPIO as in use. Separate code must handle any
pin setup (e.g. controlling which pin the GPIO uses, pullup/pulldown).
GPIOs mapped to IRQs
--------------------
GPIO numbers are unsigned integers; so are IRQ numbers. These make up
two logically distinct namespaces (GPIO 0 need not use IRQ 0). You can
map between them using calls like:
/* map GPIO numbers to IRQ numbers */
int gpio_to_irq(unsigned gpio);
/* map IRQ numbers to GPIO numbers */
int irq_to_gpio(unsigned irq);
Those return either the corresponding number in the other namespace, or
else a negative errno code if the mapping can't be done. (For example,
some GPIOs can't used as IRQs.) It is an unchecked error to use a GPIO
number that hasn't been marked as an input using gpio_set_direction(), or
to use an IRQ number that didn't originally come from gpio_to_irq().
These two mapping calls are expected to cost on the order of a single
addition or subtraction. They're not allowed to sleep.
Non-error values returned from gpio_to_irq() can be passed to request_irq()
or free_irq(). They will often be stored into IRQ resources for platform
devices, by the board-specific initialization code. Note that IRQ trigger
options are part of the IRQ interface, e.g. IRQF_TRIGGER_FALLING, as are
system wakeup capabilities.
Non-error values returned from irq_to_gpio() would most commonly be used
with gpio_get_value(), for example to initialize or update driver state
when the IRQ is edge-triggered.
What do these conventions omit?
===============================
One of the biggest things these conventions omit is pin multiplexing, since
this is highly chip-specific and nonportable. One platform might not need
explicit multiplexing; another might have just two options for use of any
given pin; another might have eight options per pin; another might be able
to route a given GPIO to any one of several pins. (Yes, those examples all
come from systems that run Linux today.)
Related to multiplexing is configuration and enabling of the pullups or
pulldowns integrated on some platforms. Not all platforms support them,
or support them in the same way; and any given board might use external
pullups (or pulldowns) so that the on-chip ones should not be used.
There are other system-specific mechanisms that are not specified here,
like the aforementioned options for input de-glitching and wire-OR output.
Hardware may support reading or writing GPIOs in gangs, but that's usually
configuration dependent: for GPIOs sharing the same bank. (GPIOs are
commonly grouped in banks of 16 or 32, with a given SOC having several such
banks.) Some systems can trigger IRQs from output GPIOs. Code relying on
such mechanisms will necessarily be nonportable.
Dynamic definition of GPIOs is not currently supported; for example, as
a side effect of configuring an add-on board with some GPIO expanders.
These calls are purely for kernel space, but a userspace API could be built
on top of it.
Documentation/hrtimer/timer_stats.txt 0 → 100644
浏览文件 @ 5a84d159
timer_stats - timer usage statistics
------------------------------------
timer_stats is a debugging facility to make the timer (ab)usage in a Linux
system visible to kernel and userspace developers. It is not intended for
production usage as it adds significant overhead to the (hr)timer code and the
(hr)timer data structures.
timer_stats should be used by kernel and userspace developers to verify that
their code does not make unduly use of timers. This helps to avoid unnecessary
wakeups, which should be avoided to optimize power consumption.
It can be enabled by CONFIG_TIMER_STATS in the "Kernel hacking" configuration
section.
timer_stats collects information about the timer events which are fired in a
Linux system over a sample period:
- the pid of the task(process) which initialized the timer
- the name of the process which initialized the timer
- the function where the timer was intialized
- the callback function which is associated to the timer
- the number of events (callbacks)
timer_stats adds an entry to /proc: /proc/timer_stats
This entry is used to control the statistics functionality and to read out the
sampled information.
The timer_stats functionality is inactive on bootup.
To activate a sample period issue:
# echo 1 >/proc/timer_stats
To stop a sample period issue:
# echo 0 >/proc/timer_stats
The statistics can be retrieved by:
# cat /proc/timer_stats
The readout of /proc/timer_stats automatically disables sampling. The sampled
information is kept until a new sample period is started. This allows multiple
readouts.
Sample output of /proc/timer_stats:
Timerstats sample period: 3.888770 s
12, 0 swapper hrtimer_stop_sched_tick (hrtimer_sched_tick)
15, 1 swapper hcd_submit_urb (rh_timer_func)
4, 959 kedac schedule_timeout (process_timeout)
1, 0 swapper page_writeback_init (wb_timer_fn)
28, 0 swapper hrtimer_stop_sched_tick (hrtimer_sched_tick)
22, 2948 IRQ 4 tty_flip_buffer_push (delayed_work_timer_fn)
3, 3100 bash schedule_timeout (process_timeout)
1, 1 swapper queue_delayed_work_on (delayed_work_timer_fn)
1, 1 swapper queue_delayed_work_on (delayed_work_timer_fn)
1, 1 swapper neigh_table_init_no_netlink (neigh_periodic_timer)
1, 2292 ip __netdev_watchdog_up (dev_watchdog)
1, 23 events/1 do_cache_clean (delayed_work_timer_fn)
90 total events, 30.0 events/sec
The first column is the number of events, the second column the pid, the third
column is the name of the process. The forth column shows the function which
initialized the timer and in parantheses the callback function which was
executed on expiry.
Thomas, Ingo
Documentation/hrtimers/highres.txt 0 → 100644
浏览文件 @ 5a84d159
High resolution timers and dynamic ticks design notes
-----------------------------------------------------
Further information can be found in the paper of the OLS 2006 talk "hrtimers
and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
be found on the OLS website:
http://www.linuxsymposium.org/2006/linuxsymposium_procv1.pdf
The slides to this talk are available from:
http://tglx.de/projects/hrtimers/ols2006-hrtimers.pdf
The slides contain five figures (pages 2, 15, 18, 20, 22), which illustrate the
changes in the time(r) related Linux subsystems. Figure #1 (p. 2) shows the
design of the Linux time(r) system before hrtimers and other building blocks
got merged into mainline.
Note: the paper and the slides are talking about "clock event source", while we
switched to the name "clock event devices" in meantime.
The design contains the following basic building blocks:
- hrtimer base infrastructure
- timeofday and clock source management
- clock event management
- high resolution timer functionality
- dynamic ticks
hrtimer base infrastructure
---------------------------
The hrtimer base infrastructure was merged into the 2.6.16 kernel. Details of
the base implementation are covered in Documentation/hrtimers/hrtimer.txt. See
also figure #2 (OLS slides p. 15)
The main differences to the timer wheel, which holds the armed timer_list type
timers are:
- time ordered enqueueing into a rb-tree
- independent of ticks (the processing is based on nanoseconds)
timeofday and clock source management
-------------------------------------
John Stultz's Generic Time Of Day (GTOD) framework moves a large portion of
code out of the architecture-specific areas into a generic management
framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
specific portion is reduced to the low level hardware details of the clock
sources, which are registered in the framework and selected on a quality based
decision. The low level code provides hardware setup and readout routines and
initializes data structures, which are used by the generic time keeping code to
convert the clock ticks to nanosecond based time values. All other time keeping
related functionality is moved into the generic code. The GTOD base patch got
merged into the 2.6.18 kernel.
Further information about the Generic Time Of Day framework is available in the
OLS 2005 Proceedings Volume 1:
http://www.linuxsymposium.org/2005/linuxsymposium_procv1.pdf
The paper "We Are Not Getting Any Younger: A New Approach to Time and
Timers" was written by J. Stultz, D.V. Hart, & N. Aravamudan.
Figure #3 (OLS slides p.18) illustrates the transformation.
clock event management
----------------------
While clock sources provide read access to the monotonically increasing time
value, clock event devices are used to schedule the next event
interrupt(s). The next event is currently defined to be periodic, with its
period defined at compile time. The setup and selection of the event device
for various event driven functionalities is hardwired into the architecture
dependent code. This results in duplicated code across all architectures and
makes it extremely difficult to change the configuration of the system to use
event interrupt devices other than those already built into the
architecture. Another implication of the current design is that it is necessary
to touch all the architecture-specific implementations in order to provide new
functionality like high resolution timers or dynamic ticks.
The clock events subsystem tries to address this problem by providing a generic
solution to manage clock event devices and their usage for the various clock
event driven kernel functionalities. The goal of the clock event subsystem is
to minimize the clock event related architecture dependent code to the pure
hardware related handling and to allow easy addition and utilization of new
clock event devices. It also minimizes the duplicated code across the
architectures as it provides generic functionality down to the interrupt
service handler, which is almost inherently hardware dependent.
Clock event devices are registered either by the architecture dependent boot
code or at module insertion time. Each clock event device fills a data
structure with clock-specific property parameters and callback functions. The
clock event management decides, by using the specified property parameters, the
set of system functions a clock event device will be used to support. This
includes the distinction of per-CPU and per-system global event devices.
System-level global event devices are used for the Linux periodic tick. Per-CPU
event devices are used to provide local CPU functionality such as process
accounting, profiling, and high resolution timers.
The management layer assignes one or more of the folliwing functions to a clock
event device:
- system global periodic tick (jiffies update)
- cpu local update_process_times
- cpu local profiling
- cpu local next event interrupt (non periodic mode)
The clock event device delegates the selection of those timer interrupt related
functions completely to the management layer. The clock management layer stores
a function pointer in the device description structure, which has to be called
from the hardware level handler. This removes a lot of duplicated code from the
architecture specific timer interrupt handlers and hands the control over the
clock event devices and the assignment of timer interrupt related functionality
to the core code.
The clock event layer API is rather small. Aside from the clock event device
registration interface it provides functions to schedule the next event
interrupt, clock event device notification service and support for suspend and
resume.
The framework adds about 700 lines of code which results in a 2KB increase of
the kernel binary size. The conversion of i386 removes about 100 lines of
code. The binary size decrease is in the range of 400 byte. We believe that the
increase of flexibility and the avoidance of duplicated code across
architectures justifies the slight increase of the binary size.
The conversion of an architecture has no functional impact, but allows to
utilize the high resolution and dynamic tick functionalites without any change
to the clock event device and timer interrupt code. After the conversion the
enabling of high resolution timers and dynamic ticks is simply provided by
adding the kernel/time/Kconfig file to the architecture specific Kconfig and
adding the dynamic tick specific calls to the idle routine (a total of 3 lines
added to the idle function and the Kconfig file)
Figure #4 (OLS slides p.20) illustrates the transformation.
high resolution timer functionality
-----------------------------------
During system boot it is not possible to use the high resolution timer
functionality, while making it possible would be difficult and would serve no
useful function. The initialization of the clock event device framework, the
clock source framework (GTOD) and hrtimers itself has to be done and
appropriate clock sources and clock event devices have to be registered before
the high resolution functionality can work. Up to the point where hrtimers are
initialized, the system works in the usual low resolution periodic mode. The
clock source and the clock event device layers provide notification functions
which inform hrtimers about availability of new hardware. hrtimers validates
the usability of the registered clock sources and clock event devices before
switching to high resolution mode. This ensures also that a kernel which is
configured for high resolution timers can run on a system which lacks the
necessary hardware support.
The high resolution timer code does not support SMP machines which have only
global clock event devices. The support of such hardware would involve IPI
calls when an interrupt happens. The overhead would be much larger than the
benefit. This is the reason why we currently disable high resolution and
dynamic ticks on i386 SMP systems which stop the local APIC in C3 power
state. A workaround is available as an idea, but the problem has not been
tackled yet.
The time ordered insertion of timers provides all the infrastructure to decide
whether the event device has to be reprogrammed when a timer is added. The
decision is made per timer base and synchronized across per-cpu timer bases in
a support function. The design allows the system to utilize separate per-CPU
clock event devices for the per-CPU timer bases, but currently only one
reprogrammable clock event device per-CPU is utilized.
When the timer interrupt happens, the next event interrupt handler is called
from the clock event distribution code and moves expired timers from the
red-black tree to a separate double linked list and invokes the softirq
handler. An additional mode field in the hrtimer structure allows the system to
execute callback functions directly from the next event interrupt handler. This
is restricted to code which can safely be executed in the hard interrupt
context. This applies, for example, to the common case of a wakeup function as
used by nanosleep. The advantage of executing the handler in the interrupt
context is the avoidance of up to two context switches - from the interrupted
context to the softirq and to the task which is woken up by the expired
timer.
Once a system has switched to high resolution mode, the periodic tick is
switched off. This disables the per system global periodic clock event device -
e.g. the PIT on i386 SMP systems.
The periodic tick functionality is provided by an per-cpu hrtimer. The callback
function is executed in the next event interrupt context and updates jiffies
and calls update_process_times and profiling. The implementation of the hrtimer
based periodic tick is designed to be extended with dynamic tick functionality.
This allows to use a single clock event device to schedule high resolution
timer and periodic events (jiffies tick, profiling, process accounting) on UP
systems. This has been proved to work with the PIT on i386 and the Incrementer
on PPC.
The softirq for running the hrtimer queues and executing the callbacks has been
separated from the tick bound timer softirq to allow accurate delivery of high
resolution timer signals which are used by itimer and POSIX interval
timers. The execution of this softirq can still be delayed by other softirqs,
but the overall latencies have been significantly improved by this separation.
Figure #5 (OLS slides p.22) illustrates the transformation.
dynamic ticks
-------------
Dynamic ticks are the logical consequence of the hrtimer based periodic tick
replacement (sched_tick). The functionality of the sched_tick hrtimer is
extended by three functions:
- hrtimer_stop_sched_tick
- hrtimer_restart_sched_tick
- hrtimer_update_jiffies
hrtimer_stop_sched_tick() is called when a CPU goes into idle state. The code
evaluates the next scheduled timer event (from both hrtimers and the timer
wheel) and in case that the next event is further away than the next tick it
reprograms the sched_tick to this future event, to allow longer idle sleeps
without worthless interruption by the periodic tick. The function is also
called when an interrupt happens during the idle period, which does not cause a
reschedule. The call is necessary as the interrupt handler might have armed a
new timer whose expiry time is before the time which was identified as the
nearest event in the previous call to hrtimer_stop_sched_tick.
hrtimer_restart_sched_tick() is called when the CPU leaves the idle state before
it calls schedule(). hrtimer_restart_sched_tick() resumes the periodic tick,
which is kept active until the next call to hrtimer_stop_sched_tick().
hrtimer_update_jiffies() is called from irq_enter() when an interrupt happens
in the idle period to make sure that jiffies are up to date and the interrupt
handler has not to deal with an eventually stale jiffy value.
The dynamic tick feature provides statistical values which are exported to
userspace via /proc/stats and can be made available for enhanced power
management control.
The implementation leaves room for further development like full tickless
systems, where the time slice is controlled by the scheduler, variable
frequency profiling, and a complete removal of jiffies in the future.
Aside the current initial submission of i386 support, the patchset has been
extended to x86_64 and ARM already. Initial (work in progress) support is also
available for MIPS and PowerPC.
Thomas, Ingo
Documentation/hwmon/it87
浏览文件 @ 5a84d159
......@@ -135,6 +135,16 @@ Give 0 for unused sensor. Any other value is invalid. To configure this at
startup, consult lm_sensors's /etc/sensors.conf. (2 = thermistor;
3 = thermal diode)
Fan speed control
-----------------
The fan speed control features are limited to manual PWM mode. Automatic
"Smart Guardian" mode control handling is not implemented. However
if you want to go for "manual mode" just write 1 to pwmN_enable.
If you are only able to control the fan speed with very small PWM values,
try lowering the PWM base frequency (pwm1_freq). Depending on the fan,
it may give you a somewhat greater control range. The same frequency is
used to drive all fan outputs, which is why pwm2_freq and pwm3_freq are
read-only.
Documentation/hwmon/sysfs-interface
浏览文件 @ 5a84d159
......@@ -166,16 +166,21 @@ pwm[1-*] Pulse width modulation fan control.
pwm[1-*]_enable
Switch PWM on and off.
Not always present even if fan*_pwm is.
Not always present even if pwmN is.
0: turn off
1: turn on in manual mode
2+: turn on in automatic mode
Check individual chip documentation files for automatic mode details.
Check individual chip documentation files for automatic mode
details.
RW
pwm[1-*]_mode
0: DC mode
1: PWM mode
pwm[1-*]_mode 0: DC mode (direct current)
1: PWM mode (pulse-width modulation)
RW
pwm[1-*]_freq Base PWM frequency in Hz.
Only possibly available when pwmN_mode is PWM, but not always
present even then.
RW
pwm[1-*]_auto_channels_temp
......
Documentation/hwmon/w83627ehf
浏览文件 @ 5a84d159
......@@ -2,26 +2,29 @@ Kernel driver w83627ehf
=======================
Supported chips:
* Winbond W83627EHF/EHG (ISA access ONLY)
* Winbond W83627EHF/EHG/DHG (ISA access ONLY)
Prefix: 'w83627ehf'
Addresses scanned: ISA address retrieved from Super I/O registers
Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83627EHF_%20W83627EHGb.pdf
Datasheet:
http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/W83627EHF_%20W83627EHGb.pdf
DHG datasheet confidential.
Authors:
Jean Delvare <khali@linux-fr.org>
Yuan Mu (Winbond)
Rudolf Marek <r.marek@assembler.cz>
David Hubbard <david.c.hubbard@gmail.com>
Description
-----------
This driver implements support for the Winbond W83627EHF and W83627EHG
super I/O chips. We will refer to them collectively as Winbond chips.
This driver implements support for the Winbond W83627EHF, W83627EHG, and
W83627DHG super I/O chips. We will refer to them collectively as Winbond chips.
The chips implement three temperature sensors, five fan rotation
speed sensors, ten analog voltage sensors, alarms with beep warnings (control
unimplemented), and some automatic fan regulation strategies (plus manual
fan control mode).
speed sensors, ten analog voltage sensors (only nine for the 627DHG), alarms
with beep warnings (control unimplemented), and some automatic fan regulation
strategies (plus manual fan control mode).
Temperatures are measured in degrees Celsius and measurement resolution is 1
degC for temp1 and 0.5 degC for temp2 and temp3. An alarm is triggered when
......@@ -55,6 +58,9 @@ prog -> pwm4 (the programmable setting is not supported by the driver)
/sys files
----------
name - this is a standard hwmon device entry. For the W83627EHF and W83627EHG,
it is set to "w83627ehf" and for the W83627DHG it is set to "w83627dhg"
pwm[1-4] - this file stores PWM duty cycle or DC value (fan speed) in range:
0 (stop) to 255 (full)
......@@ -83,3 +89,37 @@ pwm[1-4]_stop_time - how many milliseconds [ms] must elapse to switch
Note: last two functions are influenced by other control bits, not yet exported
by the driver, so a change might not have any effect.
Implementation Details
----------------------
Future driver development should bear in mind that the following registers have
different functions on the 627EHF and the 627DHG. Some registers also have
different power-on default values, but BIOS should already be loading
appropriate defaults. Note that bank selection must be performed as is currently
done in the driver for all register addresses.
0x49: only on DHG, selects temperature source for AUX fan, CPU fan0
0x4a: not completely documented for the EHF and the DHG documentation assigns
different behavior to bits 7 and 6, including extending the temperature
input selection to SmartFan I, not just SmartFan III. Testing on the EHF
will reveal whether they are compatible or not.
0x58: Chip ID: 0xa1=EHF 0xc1=DHG
0x5e: only on DHG, has bits to enable "current mode" temperature detection and
critical temperature protection
0x45b: only on EHF, bit 3, vin4 alarm (EHF supports 10 inputs, only 9 on DHG)
0x552: only on EHF, vin4
0x558: only on EHF, vin4 high limit
0x559: only on EHF, vin4 low limit
0x6b: only on DHG, SYS fan critical temperature
0x6c: only on DHG, CPU fan0 critical temperature
0x6d: only on DHG, AUX fan critical temperature
0x6e: only on DHG, CPU fan1 critical temperature
0x50-0x55 and 0x650-0x657 are marked "Test Register" for the EHF, but "Reserved
Register" for the DHG
The DHG also supports PECI, where the DHG queries Intel CPU temperatures, and
the ICH8 southbridge gets that data via PECI from the DHG, so that the
southbridge drives the fans. And the DHG supports SST, a one-wire serial bus.
Documentation/i2c/busses/i2c-i801
浏览文件 @ 5a84d159
......@@ -48,14 +48,9 @@ following:
The SMBus controller is function 3 in device 1f. Class 0c05 is SMBus Serial
Controller.
If you do NOT see the 24x3 device at function 3, and you can't figure out
any way in the BIOS to enable it,
The ICH chips are quite similar to Intel's PIIX4 chip, at least in the
SMBus controller.
See the file i2c-piix4 for some additional information.
Process Call Support
--------------------
......@@ -74,6 +69,61 @@ SMBus 2.0 Support
The 82801DB (ICH4) and later chips support several SMBus 2.0 features.
Hidden ICH SMBus
----------------
If your system has an Intel ICH south bridge, but you do NOT see the
SMBus device at 00:1f.3 in lspci, and you can't figure out any way in the
BIOS to enable it, it means it has been hidden by the BIOS code. Asus is
well known for first doing this on their P4B motherboard, and many other
boards after that. Some vendor machines are affected as well.
The first thing to try is the "i2c_ec" ACPI driver. It could be that the
SMBus was hidden on purpose because it'll be driven by ACPI. If the
i2c_ec driver works for you, just forget about the i2c-i801 driver and
don't try to unhide the ICH SMBus. Even if i2c_ec doesn't work, you
better make sure that the SMBus isn't used by the ACPI code. Try loading
the "fan" and "thermal" drivers, and check in /proc/acpi/fan and
/proc/acpi/thermal_zone. If you find anything there, it's likely that
the ACPI is accessing the SMBus and it's safer not to unhide it. Only
once you are certain that ACPI isn't using the SMBus, you can attempt
to unhide it.
In order to unhide the SMBus, we need to change the value of a PCI
register before the kernel enumerates the PCI devices. This is done in
drivers/pci/quirks.c, where all affected boards must be listed (see
function asus_hides_smbus_hostbridge.) If the SMBus device is missing,
and you think there's something interesting on the SMBus (e.g. a
hardware monitoring chip), you need to add your board to the list.
The motherboard is identified using the subvendor and subdevice IDs of the
host bridge PCI device. Get yours with "lspci -n -v -s 00:00.0":
00:00.0 Class 0600: 8086:2570 (rev 02)
Subsystem: 1043:80f2
Flags: bus master, fast devsel, latency 0
Memory at fc000000 (32-bit, prefetchable) [size=32M]
Capabilities: [e4] #09 [2106]
Capabilities: [a0] AGP version 3.0
Here the host bridge ID is 2570 (82865G/PE/P), the subvendor ID is 1043
(Asus) and the subdevice ID is 80f2 (P4P800-X). You can find the symbolic
names for the bridge ID and the subvendor ID in include/linux/pci_ids.h,
and then add a case for your subdevice ID at the right place in
drivers/pci/quirks.c. Then please give it very good testing, to make sure
that the unhidden SMBus doesn't conflict with e.g. ACPI.
If it works, proves useful (i.e. there are usable chips on the SMBus)
and seems safe, please submit a patch for inclusion into the kernel.
Note: There's a useful script in lm_sensors 2.10.2 and later, named
unhide_ICH_SMBus (in prog/hotplug), which uses the fakephp driver to
temporarily unhide the SMBus without having to patch and recompile your
kernel. It's very convenient if you just want to check if there's
anything interesting on your hidden ICH SMBus.
**********************
The lm_sensors project gratefully acknowledges the support of Texas
Instruments in the initial development of this driver.
......
Documentation/i2c/busses/i2c-parport
浏览文件 @ 5a84d159
......@@ -19,6 +19,7 @@ It currently supports the following devices:
* (type=4) Analog Devices ADM1032 evaluation board
* (type=5) Analog Devices evaluation boards: ADM1025, ADM1030, ADM1031
* (type=6) Barco LPT->DVI (K5800236) adapter
* (type=7) One For All JP1 parallel port adapter
These devices use different pinout configurations, so you have to tell
the driver what you have, using the type module parameter. There is no
......@@ -157,3 +158,17 @@ many more, using /dev/velleman.
http://home.wanadoo.nl/hihihi/libk8005.htm
http://struyve.mine.nu:8080/index.php?block=k8000
http://sourceforge.net/projects/libk8005/
One For All JP1 parallel port adapter
-------------------------------------
The JP1 project revolves around a set of remote controls which expose
the I2C bus their internal configuration EEPROM lives on via a 6 pin
jumper in the battery compartment. More details can be found at:
http://www.hifi-remote.com/jp1/
Details of the simple parallel port hardware can be found at:
http://www.hifi-remote.com/jp1/hardware.shtml
Documentation/i2c/busses/i2c-piix4
浏览文件 @ 5a84d159
......@@ -6,7 +6,7 @@ Supported adapters:
Datasheet: Publicly available at the Intel website
* ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges
Datasheet: Only available via NDA from ServerWorks
* ATI IXP southbridges IXP200, IXP300, IXP400
* ATI IXP200, IXP300, IXP400 and SB600 southbridges
Datasheet: Not publicly available
* Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
Datasheet: Publicly available at the SMSC website http://www.smsc.com
......
Documentation/i2c/busses/i2c-viapro
浏览文件 @ 5a84d159
......@@ -13,6 +13,9 @@ Supported adapters:
* VIA Technologies, Inc. VT8235, VT8237R, VT8237A, VT8251
Datasheet: available on request and under NDA from VIA
* VIA Technologies, Inc. CX700
Datasheet: available on request and under NDA from VIA
Authors:
Kysti Mlkki <kmalkki@cc.hut.fi>,
Mark D. Studebaker <mdsxyz123@yahoo.com>,
......@@ -44,6 +47,7 @@ Your lspci -n listing must show one of these :
device 1106:3227 (VT8237R)
device 1106:3337 (VT8237A)
device 1106:3287 (VT8251)
device 1106:8324 (CX700)
If none of these show up, you should look in the BIOS for settings like
enable ACPI / SMBus or even USB.
......@@ -51,3 +55,6 @@ enable ACPI / SMBus or even USB.
Except for the oldest chips (VT82C596A/B, VT82C686A and most probably
VT8231), this driver supports I2C block transactions. Such transactions
are mainly useful to read from and write to EEPROMs.
The CX700 additionally appears to support SMBus PEC, although this driver
doesn't implement it yet.
Documentation/i2c/porting-clients
浏览文件 @ 5a84d159
......@@ -129,6 +129,12 @@ Technical changes:
structure, those name member should be initialized to a driver name
string. i2c_driver itself has no name member anymore.
* [Driver model] Instead of shutdown or reboot notifiers, provide a
shutdown() method in your driver.
* [Power management] Use the driver model suspend() and resume()
callbacks instead of the obsolete pm_register() calls.
Coding policy:
* [Copyright] Use (C), not (c), for copyright.
......
Documentation/i2c/smbus-protocol
浏览文件 @ 5a84d159
......@@ -97,7 +97,7 @@ SMBus Write Word Data
=====================
This is the opposite operation of the Read Word Data command. 16 bits
of data is read from a device, from a designated register that is
of data is written to a device, to the designated register that is
specified through the Comm byte.
S Addr Wr [A] Comm [A] DataLow [A] DataHigh [A] P
......
Documentation/i2c/writing-clients
浏览文件 @ 5a84d159
......@@ -21,20 +21,26 @@ The driver structure
Usually, you will implement a single driver structure, and instantiate
all clients from it. Remember, a driver structure contains general access
routines, a client structure specific information like the actual I2C
address.
routines, and should be zero-initialized except for fields with data you
provide. A client structure holds device-specific information like the
driver model device node, and its I2C address.
static struct i2c_driver foo_driver = {
.driver = {
.name = "foo",
},
.attach_adapter = &foo_attach_adapter,
.detach_client = &foo_detach_client,
.command = &foo_command /* may be NULL */
.attach_adapter = foo_attach_adapter,
.detach_client = foo_detach_client,
.shutdown = foo_shutdown, /* optional */
.suspend = foo_suspend, /* optional */
.resume = foo_resume, /* optional */
.command = foo_command, /* optional */
}
The name field must match the driver name, including the case. It must not
contain spaces, and may be up to 31 characters long.
The name field is the driver name, and must not contain spaces. It
should match the module name (if the driver can be compiled as a module),
although you can use MODULE_ALIAS (passing "foo" in this example) to add
another name for the module.
All other fields are for call-back functions which will be explained
below.
......@@ -43,11 +49,18 @@ below.
Extra client data
=================
The client structure has a special `data' field that can point to any
structure at all. You can use this to keep client-specific data. You
Each client structure has a special `data' field that can point to any
structure at all. You should use this to keep device-specific data,
especially in drivers that handle multiple I2C or SMBUS devices. You
do not always need this, but especially for `sensors' drivers, it can
be very useful.
/* store the value */
void i2c_set_clientdata(struct i2c_client *client, void *data);
/* retrieve the value */
void *i2c_get_clientdata(struct i2c_client *client);
An example structure is below.
struct foo_data {
......@@ -493,6 +506,33 @@ by `__init_data'. Hose functions and structures can be removed after
kernel booting (or module loading) is completed.
Power Management
================
If your I2C device needs special handling when entering a system low
power state -- like putting a transceiver into a low power mode, or
activating a system wakeup mechanism -- do that in the suspend() method.
The resume() method should reverse what the suspend() method does.
These are standard driver model calls, and they work just like they
would for any other driver stack. The calls can sleep, and can use
I2C messaging to the device being suspended or resumed (since their
parent I2C adapter is active when these calls are issued, and IRQs
are still enabled).
System Shutdown
===============
If your I2C device needs special handling when the system shuts down
or reboots (including kexec) -- like turning something off -- use a
shutdown() method.
Again, this is a standard driver model call, working just like it
would for any other driver stack: the calls can sleep, and can use
I2C messaging.
Command function
================
......
Documentation/ioctl-number.txt
浏览文件 @ 5a84d159
......@@ -94,8 +94,7 @@ Code Seq# Include File Comments
'L' 00-1F linux/loop.h
'L' E0-FF linux/ppdd.h encrypted disk device driver
<http://linux01.gwdg.de/~alatham/ppdd.html>
'M' all linux/soundcard.h conflict!
'M' 00-1F linux/isicom.h conflict!
'M' all linux/soundcard.h
'N' 00-1F drivers/usb/scanner.h
'P' all linux/soundcard.h
'Q' all linux/soundcard.h
......
Documentation/isdn/README.gigaset
浏览文件 @ 5a84d159
......@@ -8,29 +8,33 @@ GigaSet 307x Device Driver
This release supports the connection of the Gigaset 307x/417x family of
ISDN DECT bases via Gigaset M101 Data, Gigaset M105 Data or direct USB
connection. The following devices are reported to be compatible:
307x/417x:
Gigaset SX255isdn
Gigaset SX353isdn
Sinus 45 [AB] isdn (Deutsche Telekom)
Sinus 721X/XA
Bases:
Siemens Gigaset 3070/3075 isdn
Siemens Gigaset 4170/4175 isdn
Siemens Gigaset SX205/255
Siemens Gigaset SX353
T-Com Sinus 45 [AB] isdn
T-Com Sinus 721X[A] [SE]
Vox Chicago 390 ISDN (KPN Telecom)
M101:
Sinus 45 Data 1 (Telekom)
M105:
Gigaset USB Adapter DECT
Sinus 45 Data 2 (Telekom)
Sinus 721 data
RS232 data boxes:
Siemens Gigaset M101 Data
T-Com Sinus 45 Data 1
USB data boxes:
Siemens Gigaset M105 Data
Siemens Gigaset USB Adapter DECT
T-Com Sinus 45 Data 2
T-Com Sinus 721 data
Chicago 390 USB (KPN)
See also http://www.erbze.info/sinus_gigaset.htm and
http://gigaset307x.sourceforge.net/
We had also reports from users of Gigaset M105 who could use the drivers
with SX 100 and CX 100 ISDN bases (only in unimodem mode, see section 2.4.)
If you have another device that works with our driver, please let us know.
For example, Gigaset SX205isdn/Sinus 721 X SE and Gigaset SX303isdn bases
are just versions without answering machine of models known to work, so
they should work just as well; but so far we are lacking positive reports
on these.
Chances of getting an USB device to work are good if the output of
lsusb
......@@ -60,14 +64,28 @@ GigaSet 307x Device Driver
To get the device working, you have to load the proper kernel module. You
can do this using
modprobe modulename
where modulename is usb_gigaset (M105) or bas_gigaset (direct USB
connection to the base).
where modulename is ser_gigaset (M101), usb_gigaset (M105), or
bas_gigaset (direct USB connection to the base).
The module ser_gigaset provides a serial line discipline N_GIGASET_M101
which drives the device through the regular serial line driver. To use it,
run the Gigaset M101 daemon "gigasetm101d" (also available from
http://sourceforge.net/projects/gigaset307x/) with the device file of the
RS232 port to the M101 as an argument, for example:
gigasetm101d /dev/ttyS1
This will open the device file, set its line discipline to N_GIGASET_M101,
and then sleep in the background, keeping the device open so that the
line discipline remains active. To deactivate it, kill the daemon, for
example with
killall gigasetm101d
before disconnecting the device.
2.2. Device nodes for user space programs
------------------------------------
The device can be accessed from user space (eg. by the user space tools
mentioned in 1.2.) through the device nodes:
- /dev/ttyGS0 for M101 (RS232 data boxes)
- /dev/ttyGU0 for M105 (USB data boxes)
- /dev/ttyGB0 for the base driver (direct USB connection)
......@@ -168,6 +186,19 @@ GigaSet 307x Device Driver
You can also use /sys/class/tty/ttyGxy/cidmode for changing the CID mode
setting (ttyGxy is ttyGU0 or ttyGB0).
2.6. M105 Undocumented USB Requests
------------------------------
The Gigaset M105 USB data box understands a couple of useful, but
undocumented USB commands. These requests are not used in normal
operation (for wireless access to the base), but are needed for access
to the M105's own configuration mode (registration to the base, baudrate
and line format settings, device status queries) via the gigacontr
utility. Their use is disabled in the driver by default for safety
reasons but can be enabled by setting the kernel configuration option
"Support for undocumented USB requests" (GIGASET_UNDOCREQ) to "Y" and
recompiling.
3. Troubleshooting
---------------
......
Documentation/kbuild/makefiles.txt
浏览文件 @ 5a84d159
......@@ -34,7 +34,7 @@ This document describes the Linux kernel Makefiles.
--- 6.1 Set variables to tweak the build to the architecture
--- 6.2 Add prerequisites to archprepare:
--- 6.3 List directories to visit when descending
--- 6.4 Architecture specific boot images
--- 6.4 Architecture-specific boot images
--- 6.5 Building non-kbuild targets
--- 6.6 Commands useful for building a boot image
--- 6.7 Custom kbuild commands
......@@ -124,7 +124,7 @@ more details, with real examples.
Example:
obj-y += foo.o
This tell kbuild that there is one object in that directory, named
This tells kbuild that there is one object in that directory, named
foo.o. foo.o will be built from foo.c or foo.S.
If foo.o shall be built as a module, the variable obj-m is used.
......@@ -353,7 +353,7 @@ more details, with real examples.
Special rules are used when the kbuild infrastructure does
not provide the required support. A typical example is
header files generated during the build process.
Another example are the architecture specific Makefiles which
Another example are the architecture-specific Makefiles which
need special rules to prepare boot images etc.
Special rules are written as normal Make rules.
......@@ -416,7 +416,7 @@ more details, with real examples.
#arch/i386/kernel/Makefile
vsyscall-flags += $(call ld-option, -Wl$(comma)--hash-style=sysv)
In the above example vsyscall-flags will be assigned the option
In the above example, vsyscall-flags will be assigned the option
-Wl$(comma)--hash-style=sysv if it is supported by $(CC).
The second argument is optional, and if supplied will be used
if first argument is not supported.
......@@ -434,7 +434,7 @@ more details, with real examples.
#arch/i386/Makefile
cflags-y += $(call cc-option,-march=pentium-mmx,-march=i586)
In the above example cflags-y will be assigned the option
In the above example, cflags-y will be assigned the option
-march=pentium-mmx if supported by $(CC), otherwise -march=i586.
The second argument to cc-option is optional, and if omitted,
cflags-y will be assigned no value if first option is not supported.
......@@ -750,10 +750,10 @@ When kbuild executes, the following steps are followed (roughly):
located at the root of the obj tree.
The very first objects linked are listed in head-y, assigned by
arch/$(ARCH)/Makefile.
7) Finally, the architecture specific part does any required post processing
7) Finally, the architecture-specific part does any required post processing
and builds the final bootimage.
- This includes building boot records
- Preparing initrd images and thelike
- Preparing initrd images and the like
--- 6.1 Set variables to tweak the build to the architecture
......@@ -880,7 +880,7 @@ When kbuild executes, the following steps are followed (roughly):
$(head-y) lists objects to be linked first in vmlinux.
$(libs-y) lists directories where a lib.a archive can be located.
The rest lists directories where a built-in.o object file can be
The rest list directories where a built-in.o object file can be
located.
$(init-y) objects will be located after $(head-y).
......@@ -888,7 +888,7 @@ When kbuild executes, the following steps are followed (roughly):
$(core-y), $(libs-y), $(drivers-y) and $(net-y).
The top level Makefile defines values for all generic directories,
and arch/$(ARCH)/Makefile only adds architecture specific directories.
and arch/$(ARCH)/Makefile only adds architecture-specific directories.
Example:
#arch/sparc64/Makefile
......@@ -897,7 +897,7 @@ When kbuild executes, the following steps are followed (roughly):
drivers-$(CONFIG_OPROFILE) += arch/sparc64/oprofile/
--- 6.4 Architecture specific boot images
--- 6.4 Architecture-specific boot images
An arch Makefile specifies goals that take the vmlinux file, compress
it, wrap it in bootstrapping code, and copy the resulting files
......@@ -924,7 +924,7 @@ When kbuild executes, the following steps are followed (roughly):
"$(Q)$(MAKE) $(build)=<dir>" is the recommended way to invoke
make in a subdirectory.
There are no rules for naming architecture specific targets,
There are no rules for naming architecture-specific targets,
but executing "make help" will list all relevant targets.
To support this, $(archhelp) must be defined.
......@@ -982,7 +982,7 @@ When kbuild executes, the following steps are followed (roughly):
$(call if_changed,ld/objcopy/gzip)
When the rule is evaluated, it is checked to see if any files
needs an update, or the command line has changed since the last
need an update, or the command line has changed since the last
invocation. The latter will force a rebuild if any options
to the executable have changed.
Any target that utilises if_changed must be listed in $(targets),
......@@ -1089,7 +1089,7 @@ When kbuild executes, the following steps are followed (roughly):
assignment.
The kbuild infrastructure for *lds file are used in several
architecture specific files.
architecture-specific files.
=== 7 Kbuild Variables
......@@ -1133,7 +1133,7 @@ The top Makefile exports the following variables:
This variable defines a place for the arch Makefiles to install
the resident kernel image and System.map file.
Use this for architecture specific install targets.
Use this for architecture-specific install targets.
INSTALL_MOD_PATH, MODLIB
......
Documentation/kdump/kdump.txt
浏览文件 @ 5a84d159
......@@ -311,10 +311,10 @@ Following are the arch specific command line options to be used while
loading dump-capture kernel.
For i386, x86_64 and ia64:
"init 1 irqpoll maxcpus=1"
"1 irqpoll maxcpus=1"
For ppc64:
"init 1 maxcpus=1 noirqdistrib"
"1 maxcpus=1 noirqdistrib"
Notes on loading the dump-capture kernel:
......@@ -332,8 +332,8 @@ Notes on loading the dump-capture kernel:
* You must specify <root-dev> in the format corresponding to the root
device name in the output of mount command.
* "init 1" boots the dump-capture kernel into single-user mode without
networking. If you want networking, use "init 3."
* Boot parameter "1" boots the dump-capture kernel into single-user
mode without networking. If you want networking, use "3".
* We generally don' have to bring up a SMP kernel just to capture the
dump. Hence generally it is useful either to build a UP dump-capture
......
Documentation/kernel-doc-nano-HOWTO.txt
浏览文件 @ 5a84d159
......@@ -101,16 +101,20 @@ The format of the block comment is like this:
/**
* function_name(:)? (- short description)?
(* @parameterx: (description of parameter x)?)*
(* @parameterx(space)*: (description of parameter x)?)*
(* a blank line)?
* (Description:)? (Description of function)?
* (section header: (section description)? )*
(*)?*/
The short function description cannot be multiline, but the other
descriptions can be (and they can contain blank lines). Avoid putting a
spurious blank line after the function name, or else the description will
be repeated!
The short function description ***cannot be multiline***, but the other
descriptions can be (and they can contain blank lines). If you continue
that initial short description onto a second line, that second line will
appear further down at the beginning of the description section, which is
almost certainly not what you had in mind.
Avoid putting a spurious blank line after the function name, or else the
description will be repeated!
All descriptive text is further processed, scanning for the following special
patterns, which are highlighted appropriately.
......@@ -121,6 +125,31 @@ patterns, which are highlighted appropriately.
'@parameter' - name of a parameter
'%CONST' - name of a constant.
NOTE 1: The multi-line descriptive text you provide does *not* recognize
line breaks, so if you try to format some text nicely, as in:
Return codes
0 - cool
1 - invalid arg
2 - out of memory
this will all run together and produce:
Return codes 0 - cool 1 - invalid arg 2 - out of memory
NOTE 2: If the descriptive text you provide has lines that begin with
some phrase followed by a colon, each of those phrases will be taken as
a new section heading, which means you should similarly try to avoid text
like:
Return codes:
0: cool
1: invalid arg
2: out of memory
every line of which would start a new section. Again, probably not
what you were after.
Take a look around the source tree for examples.
......
Documentation/kernel-docs.txt
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 5a84d159
......@@ -48,6 +48,7 @@ parameter is applicable:
ISAPNP ISA PnP code is enabled.
ISDN Appropriate ISDN support is enabled.
JOY Appropriate joystick support is enabled.
LIBATA Libata driver is enabled
LP Printer support is enabled.
LOOP Loopback device support is enabled.
M68k M68k architecture is enabled.
......@@ -104,6 +105,9 @@ loader, and have no meaning to the kernel directly.
Do not modify the syntax of boot loader parameters without extreme
need or coordination with <Documentation/i386/boot.txt>.
There are also arch-specific kernel-parameters not documented here.
See for example <Documentation/x86_64/boot-options.txt>.
Note that ALL kernel parameters listed below are CASE SENSITIVE, and that
a trailing = on the name of any parameter states that that parameter will
be entered as an environment variable, whereas its absence indicates that
......@@ -361,6 +365,11 @@ and is between 256 and 4096 characters. It is defined in the file
clocksource is not available, it defaults to PIT.
Format: { pit | tsc | cyclone | pmtmr }
code_bytes [IA32] How many bytes of object code to print in an
oops report.
Range: 0 - 8192
Default: 64
disable_8254_timer
enable_8254_timer
[IA32/X86_64] Disable/Enable interrupt 0 timer routing
......@@ -601,6 +610,10 @@ and is between 256 and 4096 characters. It is defined in the file
highmem otherwise. This also works to reduce highmem
size on bigger boxes.
highres= [KNL] Enable/disable high resolution timer mode.
Valid parameters: "on", "off"
Default: "on"
hisax= [HW,ISDN]
See Documentation/isdn/README.HiSax.
......@@ -851,7 +864,14 @@ and is between 256 and 4096 characters. It is defined in the file
Format: <1-256>
maxcpus= [SMP] Maximum number of processors that an SMP kernel
should make use of
should make use of.
Using "nosmp" or "maxcpus=0" will disable SMP
entirely (the MPS table probe still happens, though).
A command-line option of "maxcpus=<NUM>", where <NUM>
is an integer greater than 0, limits the maximum number
of CPUs activated in SMP mode to <NUM>.
Using "maxcpus=1" on an SMP kernel is the trivial
case of an SMP kernel with only one CPU.
max_addr=[KMG] [KNL,BOOT,ia64] All physical memory greater than or
equal to this physical address is ignored.
......@@ -1026,6 +1046,10 @@ and is between 256 and 4096 characters. It is defined in the file
emulation library even if a 387 maths coprocessor
is present.
noacpi [LIBATA] Disables use of ACPI in libata suspend/resume
when set.
Format: <int>
noaliencache [MM, NUMA] Disables the allcoation of alien caches in
the slab allocator. Saves per-node memory, but will
impact performance on real NUMA hardware.
......@@ -1070,6 +1094,10 @@ and is between 256 and 4096 characters. It is defined in the file
in certain environments such as networked servers or
real-time systems.
nohz= [KNL] Boottime enable/disable dynamic ticks
Valid arguments: on, off
Default: on
noirqbalance [IA-32,SMP,KNL] Disable kernel irq balancing
noirqdebug [IA-32] Disables the code which attempts to detect and
......@@ -1259,6 +1287,12 @@ and is between 256 and 4096 characters. It is defined in the file
This sorting is done to get a device
order compatible with older (<= 2.4) kernels.
nobfsort Don't sort PCI devices into breadth-first order.
cbiosize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's IO window.
The default value is 256 bytes.
cbmemsize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's memory
window. The default value is 64 megabytes.
pcmv= [HW,PCMCIA] BadgePAD 4
......@@ -1396,6 +1430,8 @@ and is between 256 and 4096 characters. It is defined in the file
in <PAGE_SIZE> units (needed only for swap files).
See Documentation/power/swsusp-and-swap-files.txt
retain_initrd [RAM] Keep initrd memory after extraction
rhash_entries= [KNL,NET]
Set number of hash buckets for route cache
......
Documentation/local_ops.txt 0 → 100644
浏览文件 @ 5a84d159
Semantics and Behavior of Local Atomic Operations
Mathieu Desnoyers
This document explains the purpose of the local atomic operations, how
to implement them for any given architecture and shows how they can be used
properly. It also stresses on the precautions that must be taken when reading
those local variables across CPUs when the order of memory writes matters.
* Purpose of local atomic operations
Local atomic operations are meant to provide fast and highly reentrant per CPU
counters. They minimize the performance cost of standard atomic operations by
removing the LOCK prefix and memory barriers normally required to synchronize
across CPUs.
Having fast per CPU atomic counters is interesting in many cases : it does not
require disabling interrupts to protect from interrupt handlers and it permits
coherent counters in NMI handlers. It is especially useful for tracing purposes
and for various performance monitoring counters.
Local atomic operations only guarantee variable modification atomicity wrt the
CPU which owns the data. Therefore, care must taken to make sure that only one
CPU writes to the local_t data. This is done by using per cpu data and making
sure that we modify it from within a preemption safe context. It is however
permitted to read local_t data from any CPU : it will then appear to be written
out of order wrt other memory writes on the owner CPU.
* Implementation for a given architecture
It can be done by slightly modifying the standard atomic operations : only
their UP variant must be kept. It typically means removing LOCK prefix (on
i386 and x86_64) and any SMP sychronization barrier. If the architecture does
not have a different behavior between SMP and UP, including asm-generic/local.h
in your archtecture's local.h is sufficient.
The local_t type is defined as an opaque signed long by embedding an
atomic_long_t inside a structure. This is made so a cast from this type to a
long fails. The definition looks like :
typedef struct { atomic_long_t a; } local_t;
* How to use local atomic operations
#include <linux/percpu.h>
#include <asm/local.h>
static DEFINE_PER_CPU(local_t, counters) = LOCAL_INIT(0);
* Counting
Counting is done on all the bits of a signed long.
In preemptible context, use get_cpu_var() and put_cpu_var() around local atomic
operations : it makes sure that preemption is disabled around write access to
the per cpu variable. For instance :
local_inc(&get_cpu_var(counters));
put_cpu_var(counters);
If you are already in a preemption-safe context, you can directly use
__get_cpu_var() instead.
local_inc(&__get_cpu_var(counters));
* Reading the counters
Those local counters can be read from foreign CPUs to sum the count. Note that
the data seen by local_read across CPUs must be considered to be out of order
relatively to other memory writes happening on the CPU that owns the data.
long sum = 0;
for_each_online_cpu(cpu)
sum += local_read(&per_cpu(counters, cpu));
If you want to use a remote local_read to synchronize access to a resource
between CPUs, explicit smp_wmb() and smp_rmb() memory barriers must be used
respectively on the writer and the reader CPUs. It would be the case if you use
the local_t variable as a counter of bytes written in a buffer : there should
be a smp_wmb() between the buffer write and the counter increment and also a
smp_rmb() between the counter read and the buffer read.
Here is a sample module which implements a basic per cpu counter using local.h.
--- BEGIN ---
/* test-local.c
*
* Sample module for local.h usage.
*/
#include <asm/local.h>
#include <linux/module.h>
#include <linux/timer.h>
static DEFINE_PER_CPU(local_t, counters) = LOCAL_INIT(0);
static struct timer_list test_timer;
/* IPI called on each CPU. */
static void test_each(void *info)
{
/* Increment the counter from a non preemptible context */
printk("Increment on cpu %d\n", smp_processor_id());
local_inc(&__get_cpu_var(counters));
/* This is what incrementing the variable would look like within a
* preemptible context (it disables preemption) :
*
* local_inc(&get_cpu_var(counters));
* put_cpu_var(counters);
*/
}
static void do_test_timer(unsigned long data)
{
int cpu;
/* Increment the counters */
on_each_cpu(test_each, NULL, 0, 1);
/* Read all the counters */
printk("Counters read from CPU %d\n", smp_processor_id());
for_each_online_cpu(cpu) {
printk("Read : CPU %d, count %ld\n", cpu,
local_read(&per_cpu(counters, cpu)));
}
del_timer(&test_timer);
test_timer.expires = jiffies + 1000;
add_timer(&test_timer);
}
static int __init test_init(void)
{
/* initialize the timer that will increment the counter */
init_timer(&test_timer);
test_timer.function = do_test_timer;
test_timer.expires = jiffies + 1;
add_timer(&test_timer);
return 0;
}
static void __exit test_exit(void)
{
del_timer_sync(&test_timer);
}
module_init(test_init);
module_exit(test_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Mathieu Desnoyers");
MODULE_DESCRIPTION("Local Atomic Ops");
--- END ---
Documentation/nfsroot.txt
浏览文件 @ 5a84d159
......@@ -67,8 +67,8 @@ nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
<nfs-options> Standard NFS options. All options are separated by commas.
The following defaults are used:
port = as given by server portmap daemon
rsize = 1024
wsize = 1024
rsize = 4096
wsize = 4096
timeo = 7
retrans = 3
acregmin = 3
......
Documentation/pci.txt
浏览文件 @ 5a84d159
......@@ -205,8 +205,8 @@ Tips on when/where to use the above attributes:
exclusively called by the probe() routine, can be marked __devinit.
Ditto for remove() and __devexit.
o If mydriver_probe() is marked with __devinit(), then all address
references to mydriver_probe must use __devexit_p(mydriver_probe)
o If mydriver_remove() is marked with __devexit(), then all address
references to mydriver_remove must use __devexit_p(mydriver_remove)
(in the struct pci_driver declaration for example).
__devexit_p() will generate the function name _or_ NULL if the
function will be discarded. For an example, see drivers/net/tg3.c.
......
Documentation/powerpc/booting-without-of.txt
浏览文件 @ 5a84d159
......@@ -497,7 +497,7 @@ looks like in practice.
| |- device_type = "cpu"
| |- reg = <0>
| |- clock-frequency = <5f5e1000>
| |- linux,boot-cpu
| |- 64-bit
| |- linux,phandle = <2>
|
o memory@0
......@@ -509,7 +509,6 @@ looks like in practice.
o chosen
|- name = "chosen"
|- bootargs = "root=/dev/sda2"
|- linux,platform = <00000600>
|- linux,phandle = <4>
This tree is almost a minimal tree. It pretty much contains the
......@@ -519,7 +518,7 @@ physical memory layout. It also includes misc information passed
through /chosen, like in this example, the platform type (mandatory)
and the kernel command line arguments (optional).
The /cpus/PowerPC,970@0/linux,boot-cpu property is an example of a
The /cpus/PowerPC,970@0/64-bit property is an example of a
property without a value. All other properties have a value. The
significance of the #address-cells and #size-cells properties will be
explained in chapter IV which defines precisely the required nodes and
......@@ -733,8 +732,7 @@ address which can extend beyond that limit.
that typically get driven by the same platform code in the
kernel, you would use a different "model" property but put a
value in "compatible". The kernel doesn't directly use that
value (see /chosen/linux,platform for how the kernel chooses a
platform type) but it is generally useful.
value but it is generally useful.
The root node is also generally where you add additional properties
specific to your board like the serial number if any, that sort of
......@@ -778,7 +776,6 @@ address which can extend beyond that limit.
bytes
- d-cache-size : one cell, size of L1 data cache in bytes
- i-cache-size : one cell, size of L1 instruction cache in bytes
- linux, boot-cpu : Should be defined if this cpu is the boot cpu.
Recommended properties:
......@@ -843,11 +840,6 @@ address which can extend beyond that limit.
the prom_init() trampoline when booting with an OF client interface,
but that you have to provide yourself when using the flattened format.
Required properties:
- linux,platform : This is your platform number as assigned by the
architecture maintainers
Recommended properties:
- bootargs : This zero-terminated string is passed as the kernel
......@@ -1334,6 +1326,9 @@ platforms are moved over to use the flattened-device-tree model.
fsl-usb2-mph compatible controllers. Either this property or
"port0" (or both) must be defined for "fsl-usb2-mph" compatible
controllers.
- dr_mode : indicates the working mode for "fsl-usb2-dr" compatible
controllers. Can be "host", "peripheral", or "otg". Default to
"host" if not defined for backward compatibility.
Recommended properties :
- interrupts : <a b> where a is the interrupt number and b is a
......@@ -1367,6 +1362,7 @@ platforms are moved over to use the flattened-device-tree model.
#size-cells = <0>;
interrupt-parent = <700>;
interrupts = <26 1>;
dr_mode = "otg";
phy = "ulpi";
};
......
Documentation/powerpc/mpc52xx-device-tree-bindings.txt
浏览文件 @ 5a84d159
MPC52xx Device Tree Bindings
MPC5200 Device Tree Bindings
----------------------------
(c) 2006 Secret Lab Technologies Ltd
(c) 2006-2007 Secret Lab Technologies Ltd
Grant Likely <grant.likely at secretlab.ca>
********** DRAFT ***********
......@@ -20,11 +20,11 @@ described in Documentation/powerpc/booting-without-of.txt), or passed
by Open Firmare (IEEE 1275) compatible firmware using an OF compatible
client interface API.
This document specifies the requirements on the device-tree for mpc52xx
This document specifies the requirements on the device-tree for mpc5200
based boards. These requirements are above and beyond the details
specified in either the OpenFirmware spec or booting-without-of.txt
All new mpc52xx-based boards are expected to match this document. In
All new mpc5200-based boards are expected to match this document. In
cases where this document is not sufficient to support a new board port,
this document should be updated as part of adding the new board support.
......@@ -32,26 +32,26 @@ II - Philosophy
===============
The core of this document is naming convention. The whole point of
defining this convention is to reduce or eliminate the number of
special cases required to support a 52xx board. If all 52xx boards
follow the same convention, then generic 52xx support code will work
special cases required to support a 5200 board. If all 5200 boards
follow the same convention, then generic 5200 support code will work
rather than coding special cases for each new board.
This section tries to capture the thought process behind why the naming
convention is what it is.
1. Node names
-------------
1. names
---------
There is strong convention/requirements already established for children
of the root node. 'cpus' describes the processor cores, 'memory'
describes memory, and 'chosen' provides boot configuration. Other nodes
are added to describe devices attached to the processor local bus.
Following convention already established with other system-on-chip
processors, MPC52xx boards must have an 'soc5200' node as a child of the
root node.
processors, 5200 device trees should use the name 'soc5200' for the
parent node of on chip devices, and the root node should be its parent.
The soc5200 node holds child nodes for all on chip devices. Child nodes
are typically named after the configured function. ie. the FEC node is
named 'ethernet', and a PSC in uart mode is named 'serial'.
Child nodes are typically named after the configured function. ie.
the FEC node is named 'ethernet', and a PSC in uart mode is named 'serial'.
2. device_type property
-----------------------
......@@ -66,28 +66,47 @@ exactly.
Since device_type isn't enough to match devices to drivers, there also
needs to be a naming convention for the compatible property. Compatible
is an list of device descriptions sorted from specific to generic. For
the mpc52xx, the required format for each compatible value is
<chip>-<device>[-<mode>]. At the minimum, the list shall contain two
items; the first specifying the exact chip, and the second specifying
mpc52xx for the chip.
ie. ethernet on mpc5200b: compatible = "mpc5200b-ethernet\0mpc52xx-ethernet"
The idea here is that most drivers will match to the most generic field
in the compatible list (mpc52xx-*), but can also test the more specific
field for enabling bug fixes or extra features.
the mpc5200, the required format for each compatible value is
<chip>-<device>[-<mode>]. The OS should be able to match a device driver
to the device based solely on the compatible value. If two drivers
match on the compatible list; the 'most compatible' driver should be
selected.
The split between the MPC5200 and the MPC5200B leaves a bit of a
connundrum. How should the compatible property be set up to provide
maximum compatability information; but still acurately describe the
chip? For the MPC5200; the answer is easy. Most of the SoC devices
originally appeared on the MPC5200. Since they didn't exist anywhere
else; the 5200 compatible properties will contain only one item;
"mpc5200-<device>".
The 5200B is almost the same as the 5200, but not quite. It fixes
silicon bugs and it adds a small number of enhancements. Most of the
devices either provide exactly the same interface as on the 5200. A few
devices have extra functions but still have a backwards compatible mode.
To express this infomation as completely as possible, 5200B device trees
should have two items in the compatible list;
"mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended
that 5200B device trees follow this convention (instead of only listing
the base mpc5200 item).
If another chip appear on the market with one of the mpc5200 SoC
devices, then the compatible list should include mpc5200-<device>.
ie. ethernet on mpc5200: compatible = "mpc5200-ethernet"
ethernet on mpc5200b: compatible = "mpc5200b-ethernet\0mpc5200-ethernet"
Modal devices, like PSCs, also append the configured function to the
end of the compatible field. ie. A PSC in i2s mode would specify
"mpc52xx-psc-i2s", not "mpc52xx-i2s". This convention is chosen to
"mpc5200-psc-i2s", not "mpc5200-i2s". This convention is chosen to
avoid naming conflicts with non-psc devices providing the same
function. For example, "mpc52xx-spi" and "mpc52xx-psc-spi" describe
function. For example, "mpc5200-spi" and "mpc5200-psc-spi" describe
the mpc5200 simple spi device and a PSC spi mode respectively.
If the soc device is more generic and present on other SOCs, the
compatible property can specify the more generic device type also.
ie. mscan: compatible = "mpc5200-mscan\0mpc52xx-mscan\0fsl,mscan";
ie. mscan: compatible = "mpc5200-mscan\0fsl,mscan";
At the time of writing, exact chip may be either 'mpc5200' or
'mpc5200b'.
......@@ -96,7 +115,7 @@ Device drivers should always try to match as generically as possible.
III - Structure
===============
The device tree for an mpc52xx board follows the structure defined in
The device tree for an mpc5200 board follows the structure defined in
booting-without-of.txt with the following additional notes:
0) the root node
......@@ -115,7 +134,7 @@ Typical memory description node; see booting-without-of.
3) The soc5200 node
-------------------
This node describes the on chip SOC peripherals. Every mpc52xx based
This node describes the on chip SOC peripherals. Every mpc5200 based
board will have this node, and as such there is a common naming
convention for SOC devices.
......@@ -125,71 +144,111 @@ name type description
device_type string must be "soc"
ranges int should be <0 baseaddr baseaddr+10000>
reg int must be <baseaddr 10000>
compatible string mpc5200: "mpc5200-soc"
mpc5200b: "mpc5200b-soc\0mpc5200-soc"
system-frequency int Fsystem frequency; source of all
other clocks.
bus-frequency int IPB bus frequency in HZ. Clock rate
used by most of the soc devices.
#interrupt-cells int must be <3>.
Recommended properties:
name type description
---- ---- -----------
compatible string should be "<chip>-soc\0mpc52xx-soc"
ie. "mpc5200b-soc\0mpc52xx-soc"
#interrupt-cells int must be <3>. If it is not defined
here then it must be defined in every
soc device node.
bus-frequency int IPB bus frequency in HZ. Clock rate
used by most of the soc devices.
Defining it here avoids needing it
added to every device node.
model string Exact model of the chip;
ie: model="fsl,mpc5200"
revision string Silicon revision of chip
ie: revision="M08A"
The 'model' and 'revision' properties are *strongly* recommended. Having
them presence acts as a bit of a safety net for working around as yet
undiscovered bugs on one version of silicon. For example, device drivers
can use the model and revision properties to decide if a bug fix should
be turned on.
4) soc5200 child nodes
----------------------
Any on chip SOC devices available to Linux must appear as soc5200 child nodes.
Note: in the tables below, '*' matches all <chip> values. ie.
*-pic would translate to "mpc5200-pic\0mpc52xx-pic"
Note: The tables below show the value for the mpc5200. A mpc5200b device
tree should use the "mpc5200b-<device>\0mpc5200-<device> form.
Required soc5200 child nodes:
name device_type compatible Description
---- ----------- ---------- -----------
cdm@<addr> cdm *-cmd Clock Distribution
pic@<addr> interrupt-controller *-pic need an interrupt
cdm@<addr> cdm mpc5200-cmd Clock Distribution
pic@<addr> interrupt-controller mpc5200-pic need an interrupt
controller to boot
bestcomm@<addr> dma-controller *-bestcomm 52xx pic also requires
the bestcomm device
bestcomm@<addr> dma-controller mpc5200-bestcomm 5200 pic also requires
the bestcomm device
Recommended soc5200 child nodes; populate as needed for your board
name device_type compatible Description
---- ----------- ---------- -----------
gpt@<addr> gpt *-gpt General purpose timers
rtc@<addr> rtc *-rtc Real time clock
mscan@<addr> mscan *-mscan CAN bus controller
pci@<addr> pci *-pci PCI bridge
serial@<addr> serial *-psc-uart PSC in serial mode
i2s@<addr> sound *-psc-i2s PSC in i2s mode
ac97@<addr> sound *-psc-ac97 PSC in ac97 mode
spi@<addr> spi *-psc-spi PSC in spi mode
irda@<addr> irda *-psc-irda PSC in IrDA mode
spi@<addr> spi *-spi MPC52xx spi device
ethernet@<addr> network *-fec MPC52xx ethernet device
ata@<addr> ata *-ata IDE ATA interface
i2c@<addr> i2c *-i2c I2C controller
usb@<addr> usb-ohci-be *-ohci,ohci-be USB controller
xlb@<addr> xlb *-xlb XLB arbritrator
name device_type compatible Description
---- ----------- ---------- -----------
gpt@<addr> gpt mpc5200-gpt General purpose timers
rtc@<addr> rtc mpc5200-rtc Real time clock
mscan@<addr> mscan mpc5200-mscan CAN bus controller
pci@<addr> pci mpc5200-pci PCI bridge
serial@<addr> serial mpc5200-psc-uart PSC in serial mode
i2s@<addr> sound mpc5200-psc-i2s PSC in i2s mode
ac97@<addr> sound mpc5200-psc-ac97 PSC in ac97 mode
spi@<addr> spi mpc5200-psc-spi PSC in spi mode
irda@<addr> irda mpc5200-psc-irda PSC in IrDA mode
spi@<addr> spi mpc5200-spi MPC5200 spi device
ethernet@<addr> network mpc5200-fec MPC5200 ethernet device
ata@<addr> ata mpc5200-ata IDE ATA interface
i2c@<addr> i2c mpc5200-i2c I2C controller
usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller
xlb@<addr> xlb mpc5200-xlb XLB arbritrator
Important child node properties
name type description
---- ---- -----------
cell-index int When multiple devices are present, is the
index of the device in the hardware (ie. There
are 6 PSC on the 5200 numbered PSC1 to PSC6)
PSC1 has 'cell-index = <0>'
PSC4 has 'cell-index = <3>'
5) General Purpose Timer nodes (child of soc5200 node)
On the mpc5200 and 5200b, GPT0 has a watchdog timer function. If the board
design supports the internal wdt, then the device node for GPT0 should
include the empty property 'has-wdt'.
6) PSC nodes (child of soc5200 node)
PSC nodes can define the optional 'port-number' property to force assignment
order of serial ports. For example, PSC5 might be physically connected to
the port labeled 'COM1' and PSC1 wired to 'COM1'. In this case, PSC5 would
have a "port-number = <0>" property, and PSC1 would have "port-number = <1>".
PSC in i2s mode: The mpc5200 and mpc5200b PSCs are not compatible when in
i2s mode. An 'mpc5200b-psc-i2s' node cannot include 'mpc5200-psc-i2s' in the
compatible field.
IV - Extra Notes
================
1. Interrupt mapping
--------------------
The mpc52xx pic driver splits hardware IRQ numbers into two levels. The
The mpc5200 pic driver splits hardware IRQ numbers into two levels. The
split reflects the layout of the PIC hardware itself, which groups
interrupts into one of three groups; CRIT, MAIN or PERP. Also, the
Bestcomm dma engine has it's own set of interrupt sources which are
cascaded off of peripheral interrupt 0, which the driver interprets as a
fourth group, SDMA.
The interrupts property for device nodes using the mpc52xx pic consists
The interrupts property for device nodes using the mpc5200 pic consists
of three cells; <L1 L2 level>
L1 := [CRIT=0, MAIN=1, PERP=2, SDMA=3]
L2 := interrupt number; directly mapped from the value in the
"ICTL PerStat, MainStat, CritStat Encoded Register"
level := [LEVEL_HIGH=0, EDGE_RISING=1, EDGE_FALLING=2, LEVEL_LOW=3]
2. Shared registers
-------------------
Some SoC devices share registers between them. ie. the i2c devices use
a single clock control register, and almost all device are affected by
the port_config register. Devices which need to manipulate shared regs
should look to the parent SoC node. The soc node is responsible
for arbitrating all shared register access.
Documentation/rbtree.txt 0 → 100644
浏览文件 @ 5a84d159
Red-black Trees (rbtree) in Linux
January 18, 2007
Rob Landley <rob@landley.net>
=============================
What are red-black trees, and what are they for?
------------------------------------------------
Red-black trees are a type of self-balancing binary search tree, used for
storing sortable key/value data pairs. This differs from radix trees (which
are used to efficiently store sparse arrays and thus use long integer indexes
to insert/access/delete nodes) and hash tables (which are not kept sorted to
be easily traversed in order, and must be tuned for a specific size and
hash function where rbtrees scale gracefully storing arbitrary keys).
Red-black trees are similar to AVL trees, but provide faster real-time bounded
worst case performance for insertion and deletion (at most two rotations and
three rotations, respectively, to balance the tree), with slightly slower
(but still O(log n)) lookup time.
To quote Linux Weekly News:
There are a number of red-black trees in use in the kernel.
The anticipatory, deadline, and CFQ I/O schedulers all employ
rbtrees to track requests; the packet CD/DVD driver does the same.
The high-resolution timer code uses an rbtree to organize outstanding
timer requests. The ext3 filesystem tracks directory entries in a
red-black tree. Virtual memory areas (VMAs) are tracked with red-black
trees, as are epoll file descriptors, cryptographic keys, and network
packets in the "hierarchical token bucket" scheduler.
This document covers use of the Linux rbtree implementation. For more
information on the nature and implementation of Red Black Trees, see:
Linux Weekly News article on red-black trees
http://lwn.net/Articles/184495/
Wikipedia entry on red-black trees
http://en.wikipedia.org/wiki/Red-black_tree
Linux implementation of red-black trees
---------------------------------------
Linux's rbtree implementation lives in the file "lib/rbtree.c". To use it,
"#include <linux/rbtree.h>".
The Linux rbtree implementation is optimized for speed, and thus has one
less layer of indirection (and better cache locality) than more traditional
tree implementations. Instead of using pointers to separate rb_node and data
structures, each instance of struct rb_node is embedded in the data structure
it organizes. And instead of using a comparison callback function pointer,
users are expected to write their own tree search and insert functions
which call the provided rbtree functions. Locking is also left up to the
user of the rbtree code.
Creating a new rbtree
---------------------
Data nodes in an rbtree tree are structures containing a struct rb_node member:
struct mytype {
struct rb_node node;
char *keystring;
};
When dealing with a pointer to the embedded struct rb_node, the containing data
structure may be accessed with the standard container_of() macro. In addition,
individual members may be accessed directly via rb_entry(node, type, member).
At the root of each rbtree is an rb_root structure, which is initialized to be
empty via:
struct rb_root mytree = RB_ROOT;
Searching for a value in an rbtree
----------------------------------
Writing a search function for your tree is fairly straightforward: start at the
root, compare each value, and follow the left or right branch as necessary.
Example:
struct mytype *my_search(struct rb_root *root, char *string)
{
struct rb_node *node = root->rb_node;
while (node) {
struct mytype *data = container_of(node, struct mytype, node);
int result;
result = strcmp(string, data->keystring);
if (result < 0)
node = node->rb_left;
else if (result > 0)
node = node->rb_right;
else
return data;
}
return NULL;
}
Inserting data into an rbtree
-----------------------------
Inserting data in the tree involves first searching for the place to insert the
new node, then inserting the node and rebalancing ("recoloring") the tree.
The search for insertion differs from the previous search by finding the
location of the pointer on which to graft the new node. The new node also
needs a link to its parent node for rebalancing purposes.
Example:
int my_insert(struct rb_root *root, struct mytype *data)
{
struct rb_node **new = &(root->rb_node), *parent = NULL;
/* Figure out where to put new node */
while (*new) {
struct mytype *this = container_of(*new, struct mytype, node);
int result = strcmp(data->keystring, this->keystring);
parent = *new;
if (result < 0)
new = &((*new)->rb_left);
else if (result > 0)
new = &((*new)->rb_right);
else
return FALSE;
}
/* Add new node and rebalance tree. */
rb_link_node(data->node, parent, new);
rb_insert_color(data->node, root);
return TRUE;
}
Removing or replacing existing data in an rbtree
------------------------------------------------
To remove an existing node from a tree, call:
void rb_erase(struct rb_node *victim, struct rb_root *tree);
Example:
struct mytype *data = mysearch(mytree, "walrus");
if (data) {
rb_erase(data->node, mytree);
myfree(data);
}
To replace an existing node in a tree with a new one with the same key, call:
void rb_replace_node(struct rb_node *old, struct rb_node *new,
struct rb_root *tree);
Replacing a node this way does not re-sort the tree: If the new node doesn't
have the same key as the old node, the rbtree will probably become corrupted.
Iterating through the elements stored in an rbtree (in sort order)
------------------------------------------------------------------
Four functions are provided for iterating through an rbtree's contents in
sorted order. These work on arbitrary trees, and should not need to be
modified or wrapped (except for locking purposes):
struct rb_node *rb_first(struct rb_root *tree);
struct rb_node *rb_last(struct rb_root *tree);
struct rb_node *rb_next(struct rb_node *node);
struct rb_node *rb_prev(struct rb_node *node);
To start iterating, call rb_first() or rb_last() with a pointer to the root
of the tree, which will return a pointer to the node structure contained in
the first or last element in the tree. To continue, fetch the next or previous
node by calling rb_next() or rb_prev() on the current node. This will return
NULL when there are no more nodes left.
The iterator functions return a pointer to the embedded struct rb_node, from
which the containing data structure may be accessed with the container_of()
macro, and individual members may be accessed directly via
rb_entry(node, type, member).
Example:
struct rb_node *node;
for (node = rb_first(&mytree); node; node = rb_next(node))
printk("key=%s\n", rb_entry(node, int, keystring));
Documentation/rtc.txt
浏览文件 @ 5a84d159
......@@ -149,7 +149,7 @@ RTC class framework, but can't be supported by the older driver.
is connected to an IRQ line, it can often issue an alarm IRQ up to
24 hours in the future.
* RTC_WKALM_SET, RTC_WKALM_READ ... RTCs that can issue alarms beyond
* RTC_WKALM_SET, RTC_WKALM_RD ... RTCs that can issue alarms beyond
the next 24 hours use a slightly more powerful API, which supports
setting the longer alarm time and enabling its IRQ using a single
request (using the same model as EFI firmware).
......@@ -167,6 +167,28 @@ Linux out of a low power sleep state (or hibernation) back to a fully
operational state. For example, a system could enter a deep power saving
state until it's time to execute some scheduled tasks.
Note that many of these ioctls need not actually be implemented by your
driver. The common rtc-dev interface handles many of these nicely if your
driver returns ENOIOCTLCMD. Some common examples:
* RTC_RD_TIME, RTC_SET_TIME: the read_time/set_time functions will be
called with appropriate values.
* RTC_ALM_SET, RTC_ALM_READ, RTC_WKALM_SET, RTC_WKALM_RD: the
set_alarm/read_alarm functions will be called. To differentiate
between the ALM and WKALM, check the larger fields of the rtc_wkalrm
struct (like tm_year). These will be set to -1 when using ALM and
will be set to proper values when using WKALM.
* RTC_IRQP_SET, RTC_IRQP_READ: the irq_set_freq function will be called
to set the frequency while the framework will handle the read for you
since the frequency is stored in the irq_freq member of the rtc_device
structure. Also make sure you set the max_user_freq member in your
initialization routines so the framework can sanity check the user
input for you.
If all else fails, check out the rtc-test.c driver!
-------------------- 8< ---------------- 8< -----------------------------
......@@ -237,7 +259,7 @@ int main(int argc, char **argv)
"\n...Update IRQs not supported.\n");
goto test_READ;
}
perror("ioctl");
perror("RTC_UIE_ON ioctl");
exit(errno);
}
......@@ -284,7 +306,7 @@ int main(int argc, char **argv)
/* Turn off update interrupts */
retval = ioctl(fd, RTC_UIE_OFF, 0);
if (retval == -1) {
perror("ioctl");
perror("RTC_UIE_OFF ioctl");
exit(errno);
}
......@@ -292,7 +314,7 @@ test_READ:
/* Read the RTC time/date */
retval = ioctl(fd, RTC_RD_TIME, &rtc_tm);
if (retval == -1) {
perror("ioctl");
perror("RTC_RD_TIME ioctl");
exit(errno);
}
......@@ -320,14 +342,14 @@ test_READ:
"\n...Alarm IRQs not supported.\n");
goto test_PIE;
}
perror("ioctl");
perror("RTC_ALM_SET ioctl");
exit(errno);
}
/* Read the current alarm settings */
retval = ioctl(fd, RTC_ALM_READ, &rtc_tm);
if (retval == -1) {
perror("ioctl");
perror("RTC_ALM_READ ioctl");
exit(errno);
}
......@@ -337,7 +359,7 @@ test_READ:
/* Enable alarm interrupts */
retval = ioctl(fd, RTC_AIE_ON, 0);
if (retval == -1) {
perror("ioctl");
perror("RTC_AIE_ON ioctl");
exit(errno);
}
......@@ -355,7 +377,7 @@ test_READ:
/* Disable alarm interrupts */
retval = ioctl(fd, RTC_AIE_OFF, 0);
if (retval == -1) {
perror("ioctl");
perror("RTC_AIE_OFF ioctl");
exit(errno);
}
......@@ -368,7 +390,7 @@ test_PIE:
fprintf(stderr, "\nNo periodic IRQ support\n");
return 0;
}
perror("ioctl");
perror("RTC_IRQP_READ ioctl");
exit(errno);
}
fprintf(stderr, "\nPeriodic IRQ rate is %ldHz.\n", tmp);
......@@ -387,7 +409,7 @@ test_PIE:
"\n...Periodic IRQ rate is fixed\n");
goto done;
}
perror("ioctl");
perror("RTC_IRQP_SET ioctl");
exit(errno);
}
......@@ -397,7 +419,7 @@ test_PIE:
/* Enable periodic interrupts */
retval = ioctl(fd, RTC_PIE_ON, 0);
if (retval == -1) {
perror("ioctl");
perror("RTC_PIE_ON ioctl");
exit(errno);
}
......@@ -416,7 +438,7 @@ test_PIE:
/* Disable periodic interrupts */
retval = ioctl(fd, RTC_PIE_OFF, 0);
if (retval == -1) {
perror("ioctl");
perror("RTC_PIE_OFF ioctl");
exit(errno);
}
}
......
Documentation/s390/Debugging390.txt
浏览文件 @ 5a84d159
......@@ -480,7 +480,7 @@ r2 argument 0 / return value 0 call-clobbered
r3 argument 1 / return value 1 (if long long) call-clobbered
r4 argument 2 call-clobbered
r5 argument 3 call-clobbered
r6 argument 5 saved
r6 argument 4 saved
r7 pointer-to arguments 5 to ... saved
r8 this & that saved
r9 this & that saved
......
Documentation/scsi/ChangeLog.megaraid
浏览文件 @ 5a84d159
Release Date : Thu Nov 16 15:32:35 EST 2006 -
Sumant Patro <sumant.patro@lsi.com>
Current Version : 2.20.5.1 (scsi module), 2.20.2.6 (cmm module)
Older Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
1. Changes in Initialization to fix kdump failure.
Send SYNC command on loading.
This command clears the pending commands in the adapter
and re-initialize its internal RAID structure.
Without this change, megaraid driver either panics or fails to
initialize the adapter during kdump's second kernel boot
if there are pending commands or interrupts from other devices
sharing the same IRQ.
2. Authors email-id domain name changed from lsil.com to lsi.com.
Also modified the MODULE_AUTHOR to megaraidlinux@lsi.com
Release Date : Fri May 19 09:31:45 EST 2006 - Seokmann Ju <sju@lsil.com>
Current Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
Older Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
......
Documentation/sh/new-machine.txt
浏览文件 @ 5a84d159
......@@ -17,7 +17,7 @@ of the board-specific code (with the exception of stboards) ended up
in arch/sh/kernel/ directly, with board-specific headers ending up in
include/asm-sh/. For the new kernel, things are broken out by board type,
companion chip type, and CPU type. Looking at a tree view of this directory
heirarchy looks like the following:
hierarchy looks like the following:
Board-specific code:
......@@ -108,7 +108,7 @@ overloading), and you can feel free to name the directory after the family
member itself.
There are a few things that each board is required to have, both in the
arch/sh/boards and the include/asm-sh/ heirarchy. In order to better
arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
explain this, we use some examples for adding an imaginary board. For
setup code, we're required at the very least to provide definitions for
get_system_type() and platform_setup(). For our imaginary board, this
......
Documentation/sony-laptop.txt 0 → 100644
浏览文件 @ 5a84d159
Sony Notebook Control Driver (SNC) Readme
-----------------------------------------
Copyright (C) 2004- 2005 Stelian Pop <stelian@popies.net>
Copyright (C) 2007 Mattia Dongili <malattia@linux.it>
This mini-driver drives the SNC device present in the ACPI BIOS of
the Sony Vaio laptops.
It gives access to some extra laptop functionalities. In its current
form, this driver let the user set or query the screen brightness
through the backlight subsystem and remove/apply power to some devices.
Backlight control:
------------------
If your laptop model supports it, you will find sysfs files in the
/sys/class/backlight/sony/
directory. You will be able to query and set the current screen
brightness:
brightness get/set screen brightness (an iteger
between 0 and 7)
actual_brightness reading from this file will query the HW
to get real brightness value
max_brightness the maximum brightness value
Platform specific:
------------------
Loading the sony-laptop module will create a
/sys/devices/platform/sony-laptop/
directory populated with some files.
You then read/write integer values from/to those files by using
standard UNIX tools.
The files are:
brightness_default screen brightness which will be set
when the laptop will be rebooted
cdpower power on/off the internal CD drive
audiopower power on/off the internal sound card
lanpower power on/off the internal ethernet card
(only in debug mode)
Note that some files may be missing if they are not supported
by your particular laptop model.
Example usage:
# echo "1" > /sys/devices/platform/sony-laptop/brightness_default
sets the lowest screen brightness for the next and later reboots,
# echo "8" > /sys/devices/platform/sony-laptop/brightness_default
sets the highest screen brightness for the next and later reboots,
# cat /sys/devices/platform/sony-laptop/brightness_default
retrieves the value.
# echo "0" > /sys/devices/platform/sony-laptop/audiopower
powers off the sound card,
# echo "1" > /sys/devices/platform/sony-laptop/audiopower
powers on the sound card.
Development:
------------
If you want to help with the development of this driver (and
you are not afraid of any side effects doing strange things with
your ACPI BIOS could have on your laptop), load the driver and
pass the option 'debug=1'.
REPEAT: DON'T DO THIS IF YOU DON'T LIKE RISKY BUSINESS.
In your kernel logs you will find the list of all ACPI methods
the SNC device has on your laptop. You can see the GCDP/GCDP methods
used to pwer on/off the CD drive, but there are others.
I HAVE NO IDEA WHAT THOSE METHODS DO.
The sony-laptop driver creates, for some of those methods (the most
current ones found on several Vaio models), an entry under
/sys/devices/platform/sony-laptop, just like the 'cdpower' one.
You can create other entries corresponding to your own laptop methods by
further editing the source (see the 'sony_acpi_values' table, and add a new
entry to this table with your get/set method names using the
HANDLE_NAMES macro).
Your mission, should you accept it, is to try finding out what
those entries are for, by reading/writing random values from/to those
files and find out what is the impact on your laptop.
Should you find anything interesting, please report it back to me,
I will not disavow all knowledge of your actions :)
Bugs/Limitations:
-----------------
* This driver is not based on official documentation from Sony
(because there is none), so there is no guarantee this driver
will work at all, or do the right thing. Although this hasn't
happened to me, this driver could do very bad things to your
laptop, including permanent damage.
* The sony-laptop and sonypi drivers do not interact at all. In the
future, sonypi could use sony-laptop to do (part of) its business.
* spicctrl, which is the userspace tool used to communicate with the
sonypi driver (through /dev/sonypi) does not try to use the
sony-laptop driver. In the future, spicctrl could try sonypi first,
and if it isn't present, try sony-laptop instead.
Documentation/sound/alsa/ALSA-Configuration.txt
浏览文件 @ 5a84d159
......@@ -242,6 +242,12 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
ac97_clock - AC'97 clock (default = 48000)
ac97_quirk - AC'97 workaround for strange hardware
See "AC97 Quirk Option" section below.
ac97_codec - Workaround to specify which AC'97 codec
instead of probing. If this works for you
file a bug with your `lspci -vn` output.
-2 -- Force probing.
-1 -- Default behavior.
0-2 -- Use the specified codec.
spdif_aclink - S/PDIF transfer over AC-link (default = 1)
This module supports one card and autoprobe.
......@@ -779,6 +785,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
asus-dig ASUS with SPDIF out
asus-dig2 ASUS with SPDIF out (using GPIO2)
uniwill 3-jack
fujitsu Fujitsu Laptops (Pi1536)
F1734 2-jack
lg LG laptop (m1 express dual)
lg-lw LG LW20/LW25 laptop
......@@ -800,14 +807,18 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
ALC262
fujitsu Fujitsu Laptop
hp-bpc HP xw4400/6400/8400/9400 laptops
hp-bpc-d7000 HP BPC D7000
benq Benq ED8
hippo Hippo (ATI) with jack detection, Sony UX-90s
hippo_1 Hippo (Benq) with jack detection
basic fixed pin assignment w/o SPDIF
auto auto-config reading BIOS (default)
ALC882/885
3stack-dig 3-jack with SPDIF I/O
6stck-dig 6-jack digital with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
arima Arima W820Di1
macpro MacPro support
auto auto-config reading BIOS (default)
ALC883/888
......@@ -817,6 +828,10 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
medion Medion Laptops
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
auto auto-config reading BIOS (default)
ALC861/660
......@@ -825,6 +840,16 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
6stack-dig 6-jack with SPDIF I/O
3stack-660 3-jack (for ALC660)
uniwill-m31 Uniwill M31 laptop
toshiba Toshiba laptop support
asus Asus laptop support
asus-laptop ASUS F2/F3 laptops
auto auto-config reading BIOS (default)
ALC861VD/660VD
3stack 3-jack
3stack-dig 3-jack with SPDIF OUT
6stack-dig 6-jack with SPDIF OUT
3stack-660 3-jack (for ALC660VD)
auto auto-config reading BIOS (default)
CMI9880
......@@ -845,6 +870,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
3stack 3-stack, shared surrounds
laptop 2-channel only (FSC V2060, Samsung M50)
laptop-eapd 2-channel with EAPD (Samsung R65, ASUS A6J)
ultra 2-channel with EAPD (Samsung Ultra tablet PC)
AD1988
6stack 6-jack
......@@ -854,12 +880,31 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
laptop 3-jack with hp-jack automute
laptop-dig ditto with SPDIF
auto auto-config reading BIOS (default)
Conexant 5045
laptop Laptop config
test for testing/debugging purpose, almost all controls
can be adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
Conexant 5047
laptop Basic Laptop config
laptop-hp Laptop config for some HP models (subdevice 30A5)
laptop-eapd Laptop config with EAPD support
test for testing/debugging purpose, almost all controls
can be adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
STAC9200/9205/9220/9221/9254
ref Reference board
3stack D945 3stack
5stack D945 5stack + SPDIF
STAC9202/9250/9251
ref Reference board, base config
m2-2 Some Gateway MX series laptops
m6 Some Gateway NX series laptops
STAC9227/9228/9229/927x
ref Reference board
3stack D965 3stack
......@@ -974,6 +1019,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
Module for Envy24HT (VT/ICE1724), Envy24PT (VT1720) based PCI sound cards.
* MidiMan M Audio Revolution 5.1
* MidiMan M Audio Revolution 7.1
* MidiMan M Audio Audiophile 192
* AMP Ltd AUDIO2000
* TerraTec Aureon 5.1 Sky
* TerraTec Aureon 7.1 Space
......@@ -993,7 +1039,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
model - Use the given board model, one of the following:
revo51, revo71, amp2000, prodigy71, prodigy71lt,
prodigy192, aureon51, aureon71, universe,
prodigy192, aureon51, aureon71, universe, ap192,
k8x800, phase22, phase28, ms300, av710
This module supports multiple cards and autoprobe.
......@@ -1049,6 +1095,9 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
buggy_semaphore - Enable workaround for hardwares with buggy
semaphores (e.g. on some ASUS laptops)
(default off)
spdif_aclink - Use S/PDIF over AC-link instead of direct connection
from the controller chip
(0 = off, 1 = on, -1 = default)
This module supports one chip and autoprobe.
......@@ -1371,6 +1420,13 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
This module supports multiple cards.
Module snd-portman2x4
---------------------
Module for Midiman Portman 2x4 parallel port MIDI interface
This module supports multiple cards.
Module snd-powermac (on ppc only)
---------------------------------
......
Documentation/sound/alsa/DocBook/alsa-driver-api.tmpl
浏览文件 @ 5a84d159
......@@ -36,7 +36,7 @@
</bookinfo>
<chapter><title>Management of Cards and Devices</title>
<sect1><title>Card Managment</title>
<sect1><title>Card Management</title>
!Esound/core/init.c
</sect1>
<sect1><title>Device Components</title>
......@@ -59,7 +59,7 @@
<sect1><title>PCM Format Helpers</title>
!Esound/core/pcm_misc.c
</sect1>
<sect1><title>PCM Memory Managment</title>
<sect1><title>PCM Memory Management</title>
!Esound/core/pcm_memory.c
</sect1>
</chapter>
......
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 5a84d159
......@@ -1360,8 +1360,7 @@
<informalexample>
<programlisting>
<![CDATA[
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id,
struct pt_regs *regs)
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id)
{
struct mychip *chip = dev_id;
....
......@@ -2127,7 +2126,7 @@
accessible via <constant>substream-&gt;runtime</constant>.
This runtime pointer holds the various information; it holds
the copy of hw_params and sw_params configurations, the buffer
pointers, mmap records, spinlocks, etc. Almost everyhing you
pointers, mmap records, spinlocks, etc. Almost everything you
need for controlling the PCM can be found there.
</para>
......@@ -2340,7 +2339,7 @@ struct _snd_pcm_runtime {
<para>
When the PCM substreams can be synchronized (typically,
synchorinized start/stop of a playback and a capture streams),
synchronized start/stop of a playback and a capture streams),
you can give <constant>SNDRV_PCM_INFO_SYNC_START</constant>,
too. In this case, you'll need to check the linked-list of
PCM substreams in the trigger callback. This will be
......@@ -3062,8 +3061,7 @@ struct _snd_pcm_runtime {
<title>Interrupt Handler Case #1</title>
<programlisting>
<![CDATA[
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id,
struct pt_regs *regs)
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id)
{
struct mychip *chip = dev_id;
spin_lock(&chip->lock);
......@@ -3106,8 +3104,7 @@ struct _snd_pcm_runtime {
<title>Interrupt Handler Case #2</title>
<programlisting>
<![CDATA[
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id,
struct pt_regs *regs)
static irqreturn_t snd_mychip_interrupt(int irq, void *dev_id)
{
struct mychip *chip = dev_id;
spin_lock(&chip->lock);
......@@ -3247,7 +3244,7 @@ struct _snd_pcm_runtime {
You can even define your own constraint rules.
For example, let's suppose my_chip can manage a substream of 1 channel
if and only if the format is S16_LE, otherwise it supports any format
specified in the <structname>snd_pcm_hardware</structname> stucture (or in any
specified in the <structname>snd_pcm_hardware</structname> structure (or in any
other constraint_list). You can build a rule like this:
<example>
......@@ -3690,16 +3687,6 @@ struct _snd_pcm_runtime {
</example>
</para>
<para>
Here, the chip instance is retrieved via
<function>snd_kcontrol_chip()</function> macro. This macro
just accesses to kcontrol-&gt;private_data. The
kcontrol-&gt;private_data field is
given as the argument of <function>snd_ctl_new()</function>
(see the later subsection
<link linkend="control-interface-constructor"><citetitle>Constructor</citetitle></link>).
</para>
<para>
The <structfield>value</structfield> field is depending on
the type of control as well as on info callback. For example,
......@@ -3780,7 +3767,7 @@ struct _snd_pcm_runtime {
<para>
Like <structfield>get</structfield> callback,
when the control has more than one elements,
all elemehts must be evaluated in this callback, too.
all elements must be evaluated in this callback, too.
</para>
</section>
......@@ -5541,12 +5528,12 @@ struct _snd_pcm_runtime {
#ifdef CONFIG_PM
static int snd_my_suspend(struct pci_dev *pci, pm_message_t state)
{
.... /* do things for suspsend */
.... /* do things for suspend */
return 0;
}
static int snd_my_resume(struct pci_dev *pci)
{
.... /* do things for suspsend */
.... /* do things for suspend */
return 0;
}
#endif
......@@ -6111,7 +6098,7 @@ struct _snd_pcm_runtime {
<!-- ****************************************************** -->
<!-- Acknowledgments -->
<!-- ****************************************************** -->
<chapter id="acknowledments">
<chapter id="acknowledgments">
<title>Acknowledgments</title>
<para>
I would like to thank Phil Kerr for his help for improvement and
......
Documentation/sound/alsa/hda_codec.txt
浏览文件 @ 5a84d159
......@@ -277,11 +277,11 @@ Helper Functions
snd_hda_get_codec_name() stores the codec name on the given string.
snd_hda_check_board_config() can be used to obtain the configuration
information matching with the device. Define the table with struct
hda_board_config entries (zero-terminated), and pass it to the
function. The function checks the modelname given as a module
parameter, and PCI subsystem IDs. If the matching entry is found, it
returns the config field value.
information matching with the device. Define the model string table
and the table with struct snd_pci_quirk entries (zero-terminated),
and pass it to the function. The function checks the modelname given
as a module parameter, and PCI subsystem IDs. If the matching entry
is found, it returns the config field value.
snd_hda_add_new_ctls() can be used to create and add control entries.
Pass the zero-terminated array of struct snd_kcontrol_new. The same array
......
Documentation/sound/alsa/soc/DAI.txt 0 → 100644
浏览文件 @ 5a84d159
ASoC currently supports the three main Digital Audio Interfaces (DAI) found on
SoC controllers and portable audio CODECS today, namely AC97, I2S and PCM.
AC97
====
AC97 is a five wire interface commonly found on many PC sound cards. It is
now also popular in many portable devices. This DAI has a reset line and time
multiplexes its data on its SDATA_OUT (playback) and SDATA_IN (capture) lines.
The bit clock (BCLK) is always driven by the CODEC (usually 12.288MHz) and the
frame (FRAME) (usually 48kHz) is always driven by the controller. Each AC97
frame is 21uS long and is divided into 13 time slots.
The AC97 specification can be found at :-
http://www.intel.com/design/chipsets/audio/ac97_r23.pdf
I2S
===
I2S is a common 4 wire DAI used in HiFi, STB and portable devices. The Tx and
Rx lines are used for audio transmision, whilst the bit clock (BCLK) and
left/right clock (LRC) synchronise the link. I2S is flexible in that either the
controller or CODEC can drive (master) the BCLK and LRC clock lines. Bit clock
usually varies depending on the sample rate and the master system clock
(SYSCLK). LRCLK is the same as the sample rate. A few devices support separate
ADC and DAC LRCLK's, this allows for similtanious capture and playback at
different sample rates.
I2S has several different operating modes:-
o I2S - MSB is transmitted on the falling edge of the first BCLK after LRC
transition.
o Left Justified - MSB is transmitted on transition of LRC.
o Right Justified - MSB is transmitted sample size BCLK's before LRC
transition.
PCM
===
PCM is another 4 wire interface, very similar to I2S, that can support a more
flexible protocol. It has bit clock (BCLK) and sync (SYNC) lines that are used
to synchronise the link whilst the Tx and Rx lines are used to transmit and
receive the audio data. Bit clock usually varies depending on sample rate
whilst sync runs at the sample rate. PCM also supports Time Division
Multiplexing (TDM) in that several devices can use the bus similtaniuosly (This
is sometimes referred to as network mode).
Common PCM operating modes:-
o Mode A - MSB is transmitted on falling edge of first BCLK after FRAME/SYNC.
o Mode B - MSB is transmitted on rising edge of FRAME/SYNC.
Documentation/sound/alsa/soc/clocking.txt 0 → 100644
浏览文件 @ 5a84d159
Audio Clocking
==============
This text describes the audio clocking terms in ASoC and digital audio in
general. Note: Audio clocking can be complex !
Master Clock
------------
Every audio subsystem is driven by a master clock (sometimes refered to as MCLK
or SYSCLK). This audio master clock can be derived from a number of sources
(e.g. crystal, PLL, CPU clock) and is responsible for producing the correct
audio playback and capture sample rates.
Some master clocks (e.g. PLL's and CPU based clocks) are configuarble in that
their speed can be altered by software (depending on the system use and to save
power). Other master clocks are fixed at at set frequency (i.e. crystals).
DAI Clocks
----------
The Digital Audio Interface is usually driven by a Bit Clock (often referred to
as BCLK). This clock is used to drive the digital audio data across the link
between the codec and CPU.
The DAI also has a frame clock to signal the start of each audio frame. This
clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
runs at exactly the sample rate (LRC = Rate).
Bit Clock can be generated as follows:-
BCLK = MCLK / x
or
BCLK = LRC * x
or
BCLK = LRC * Channels * Word Size
This relationship depends on the codec or SoC CPU in particular. In general
it's best to configure BCLK to the lowest possible speed (depending on your
rate, number of channels and wordsize) to save on power.
It's also desireable to use the codec (if possible) to drive (or master) the
audio clocks as it's usually gives more accurate sample rates than the CPU.
Documentation/sound/alsa/soc/codec.txt 0 → 100644
浏览文件 @ 5a84d159
ASoC Codec Driver
=================
The codec driver is generic and hardware independent code that configures the
codec to provide audio capture and playback. It should contain no code that is
specific to the target platform or machine. All platform and machine specific
code should be added to the platform and machine drivers respectively.
Each codec driver *must* provide the following features:-
1) Codec DAI and PCM configuration
2) Codec control IO - using I2C, 3 Wire(SPI) or both API's
3) Mixers and audio controls
4) Codec audio operations
Optionally, codec drivers can also provide:-
5) DAPM description.
6) DAPM event handler.
7) DAC Digital mute control.
It's probably best to use this guide in conjuction with the existing codec
driver code in sound/soc/codecs/
ASoC Codec driver breakdown
===========================
1 - Codec DAI and PCM configuration
-----------------------------------
Each codec driver must have a struct snd_soc_codec_dai to define it's DAI and
PCM's capablities and operations. This struct is exported so that it can be
registered with the core by your machine driver.
e.g.
struct snd_soc_codec_dai wm8731_dai = {
.name = "WM8731",
/* playback capabilities */
.playback = {
.stream_name = "Playback",
.channels_min = 1,
.channels_max = 2,
.rates = WM8731_RATES,
.formats = WM8731_FORMATS,},
/* capture capabilities */
.capture = {
.stream_name = "Capture",
.channels_min = 1,
.channels_max = 2,
.rates = WM8731_RATES,
.formats = WM8731_FORMATS,},
/* pcm operations - see section 4 below */
.ops = {
.prepare = wm8731_pcm_prepare,
.hw_params = wm8731_hw_params,
.shutdown = wm8731_shutdown,
},
/* DAI operations - see DAI.txt */
.dai_ops = {
.digital_mute = wm8731_mute,
.set_sysclk = wm8731_set_dai_sysclk,
.set_fmt = wm8731_set_dai_fmt,
}
};
EXPORT_SYMBOL_GPL(wm8731_dai);
2 - Codec control IO
--------------------
The codec can ususally be controlled via an I2C or SPI style interface (AC97
combines control with data in the DAI). The codec drivers will have to provide
functions to read and write the codec registers along with supplying a register
cache:-
/* IO control data and register cache */
void *control_data; /* codec control (i2c/3wire) data */
void *reg_cache;
Codec read/write should do any data formatting and call the hardware read write
below to perform the IO. These functions are called by the core and alsa when
performing DAPM or changing the mixer:-
unsigned int (*read)(struct snd_soc_codec *, unsigned int);
int (*write)(struct snd_soc_codec *, unsigned int, unsigned int);
Codec hardware IO functions - usually points to either the I2C, SPI or AC97
read/write:-
hw_write_t hw_write;
hw_read_t hw_read;
3 - Mixers and audio controls
-----------------------------
All the codec mixers and audio controls can be defined using the convenience
macros defined in soc.h.
#define SOC_SINGLE(xname, reg, shift, mask, invert)
Defines a single control as follows:-
xname = Control name e.g. "Playback Volume"
reg = codec register
shift = control bit(s) offset in register
mask = control bit size(s) e.g. mask of 7 = 3 bits
invert = the control is inverted
Other macros include:-
#define SOC_DOUBLE(xname, reg, shift_left, shift_right, mask, invert)
A stereo control
#define SOC_DOUBLE_R(xname, reg_left, reg_right, shift, mask, invert)
A stereo control spanning 2 registers
#define SOC_ENUM_SINGLE(xreg, xshift, xmask, xtexts)
Defines an single enumerated control as follows:-
xreg = register
xshift = control bit(s) offset in register
xmask = control bit(s) size
xtexts = pointer to array of strings that describe each setting
#define SOC_ENUM_DOUBLE(xreg, xshift_l, xshift_r, xmask, xtexts)
Defines a stereo enumerated control
4 - Codec Audio Operations
--------------------------
The codec driver also supports the following alsa operations:-
/* SoC audio ops */
struct snd_soc_ops {
int (*startup)(struct snd_pcm_substream *);
void (*shutdown)(struct snd_pcm_substream *);
int (*hw_params)(struct snd_pcm_substream *, struct snd_pcm_hw_params *);
int (*hw_free)(struct snd_pcm_substream *);
int (*prepare)(struct snd_pcm_substream *);
};
Please refer to the alsa driver PCM documentation for details.
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/c436.htm
5 - DAPM description.
---------------------
The Dynamic Audio Power Management description describes the codec's power
components, their relationships and registers to the ASoC core. Please read
dapm.txt for details of building the description.
Please also see the examples in other codec drivers.
6 - DAPM event handler
----------------------
This function is a callback that handles codec domain PM calls and system
domain PM calls (e.g. suspend and resume). It's used to put the codec to sleep
when not in use.
Power states:-
SNDRV_CTL_POWER_D0: /* full On */
/* vref/mid, clk and osc on, active */
SNDRV_CTL_POWER_D1: /* partial On */
SNDRV_CTL_POWER_D2: /* partial On */
SNDRV_CTL_POWER_D3hot: /* Off, with power */
/* everything off except vref/vmid, inactive */
SNDRV_CTL_POWER_D3cold: /* Everything Off, without power */
7 - Codec DAC digital mute control.
------------------------------------
Most codecs have a digital mute before the DAC's that can be used to minimise
any system noise. The mute stops any digital data from entering the DAC.
A callback can be created that is called by the core for each codec DAI when the
mute is applied or freed.
i.e.
static int wm8974_mute(struct snd_soc_codec *codec,
struct snd_soc_codec_dai *dai, int mute)
{
u16 mute_reg = wm8974_read_reg_cache(codec, WM8974_DAC) & 0xffbf;
if(mute)
wm8974_write(codec, WM8974_DAC, mute_reg | 0x40);
else
wm8974_write(codec, WM8974_DAC, mute_reg);
return 0;
}
Documentation/sound/alsa/soc/dapm.txt 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/sound/alsa/soc/machine.txt 0 → 100644
浏览文件 @ 5a84d159
ASoC Machine Driver
===================
The ASoC machine (or board) driver is the code that glues together the platform
and codec drivers.
The machine driver can contain codec and platform specific code. It registers
the audio subsystem with the kernel as a platform device and is represented by
the following struct:-
/* SoC machine */
struct snd_soc_machine {
char *name;
int (*probe)(struct platform_device *pdev);
int (*remove)(struct platform_device *pdev);
/* the pre and post PM functions are used to do any PM work before and
* after the codec and DAI's do any PM work. */
int (*suspend_pre)(struct platform_device *pdev, pm_message_t state);
int (*suspend_post)(struct platform_device *pdev, pm_message_t state);
int (*resume_pre)(struct platform_device *pdev);
int (*resume_post)(struct platform_device *pdev);
/* machine stream operations */
struct snd_soc_ops *ops;
/* CPU <--> Codec DAI links */
struct snd_soc_dai_link *dai_link;
int num_links;
};
probe()/remove()
----------------
probe/remove are optional. Do any machine specific probe here.
suspend()/resume()
------------------
The machine driver has pre and post versions of suspend and resume to take care
of any machine audio tasks that have to be done before or after the codec, DAI's
and DMA is suspended and resumed. Optional.
Machine operations
------------------
The machine specific audio operations can be set here. Again this is optional.
Machine DAI Configuration
-------------------------
The machine DAI configuration glues all the codec and CPU DAI's together. It can
also be used to set up the DAI system clock and for any machine related DAI
initialisation e.g. the machine audio map can be connected to the codec audio
map, unconnnected codec pins can be set as such. Please see corgi.c, spitz.c
for examples.
struct snd_soc_dai_link is used to set up each DAI in your machine. e.g.
/* corgi digital audio interface glue - connects codec <--> CPU */
static struct snd_soc_dai_link corgi_dai = {
.name = "WM8731",
.stream_name = "WM8731",
.cpu_dai = &pxa_i2s_dai,
.codec_dai = &wm8731_dai,
.init = corgi_wm8731_init,
.ops = &corgi_ops,
};
struct snd_soc_machine then sets up the machine with it's DAI's. e.g.
/* corgi audio machine driver */
static struct snd_soc_machine snd_soc_machine_corgi = {
.name = "Corgi",
.dai_link = &corgi_dai,
.num_links = 1,
};
Machine Audio Subsystem
-----------------------
The machine soc device glues the platform, machine and codec driver together.
Private data can also be set here. e.g.
/* corgi audio private data */
static struct wm8731_setup_data corgi_wm8731_setup = {
.i2c_address = 0x1b,
};
/* corgi audio subsystem */
static struct snd_soc_device corgi_snd_devdata = {
.machine = &snd_soc_machine_corgi,
.platform = &pxa2xx_soc_platform,
.codec_dev = &soc_codec_dev_wm8731,
.codec_data = &corgi_wm8731_setup,
};
Machine Power Map
-----------------
The machine driver can optionally extend the codec power map and to become an
audio power map of the audio subsystem. This allows for automatic power up/down
of speaker/HP amplifiers, etc. Codec pins can be connected to the machines jack
sockets in the machine init function. See soc/pxa/spitz.c and dapm.txt for
details.
Machine Controls
----------------
Machine specific audio mixer controls can be added in the dai init function.
\ No newline at end of file
Documentation/sound/alsa/soc/overview.txt 0 → 100644
浏览文件 @ 5a84d159
ALSA SoC Layer
==============
The overall project goal of the ALSA System on Chip (ASoC) layer is to provide
better ALSA support for embedded system on chip procesors (e.g. pxa2xx, au1x00,
iMX, etc) and portable audio codecs. Currently there is some support in the
kernel for SoC audio, however it has some limitations:-
* Currently, codec drivers are often tightly coupled to the underlying SoC
cpu. This is not ideal and leads to code duplication i.e. Linux now has 4
different wm8731 drivers for 4 different SoC platforms.
* There is no standard method to signal user initiated audio events.
e.g. Headphone/Mic insertion, Headphone/Mic detection after an insertion
event. These are quite common events on portable devices and ofter require
machine specific code to re route audio, enable amps etc after such an event.
* Current drivers tend to power up the entire codec when playing
(or recording) audio. This is fine for a PC, but tends to waste a lot of
power on portable devices. There is also no support for saving power via
changing codec oversampling rates, bias currents, etc.
ASoC Design
===========
The ASoC layer is designed to address these issues and provide the following
features :-
* Codec independence. Allows reuse of codec drivers on other platforms
and machines.
* Easy I2S/PCM audio interface setup between codec and SoC. Each SoC interface
and codec registers it's audio interface capabilities with the core and are
subsequently matched and configured when the application hw params are known.
* Dynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
it's minimum power state at all times. This includes powering up/down
internal power blocks depending on the internal codec audio routing and any
active streams.
* Pop and click reduction. Pops and clicks can be reduced by powering the
codec up/down in the correct sequence (including using digital mute). ASoC
signals the codec when to change power states.
* Machine specific controls: Allow machines to add controls to the sound card
e.g. volume control for speaker amp.
To achieve all this, ASoC basically splits an embedded audio system into 3
components :-
* Codec driver: The codec driver is platform independent and contains audio
controls, audio interface capabilities, codec dapm definition and codec IO
functions.
* Platform driver: The platform driver contains the audio dma engine and audio
interface drivers (e.g. I2S, AC97, PCM) for that platform.
* Machine driver: The machine driver handles any machine specific controls and
audio events. i.e. turing on an amp at start of playback.
Documentation
=============
The documentation is spilt into the following sections:-
overview.txt: This file.
codec.txt: Codec driver internals.
DAI.txt: Description of Digital Audio Interface standards and how to configure
a DAI within your codec and CPU DAI drivers.
dapm.txt: Dynamic Audio Power Management
platform.txt: Platform audio DMA and DAI.
machine.txt: Machine driver internals.
pop_clicks.txt: How to minimise audio artifacts.
clocking.txt: ASoC clocking for best power performance.
\ No newline at end of file
Documentation/sound/alsa/soc/platform.txt 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/sound/alsa/soc/pops_clicks.txt 0 → 100644
浏览文件 @ 5a84d159
Audio Pops and Clicks
=====================
Pops and clicks are unwanted audio artifacts caused by the powering up and down
of components within the audio subsystem. This is noticable on PC's when an
audio module is either loaded or unloaded (at module load time the sound card is
powered up and causes a popping noise on the speakers).
Pops and clicks can be more frequent on portable systems with DAPM. This is
because the components within the subsystem are being dynamically powered
depending on the audio usage and this can subsequently cause a small pop or
click every time a component power state is changed.
Minimising Playback Pops and Clicks
===================================
Playback pops in portable audio subsystems cannot be completely eliminated atm,
however future audio codec hardware will have better pop and click supression.
Pops can be reduced within playback by powering the audio components in a
specific order. This order is different for startup and shutdown and follows
some basic rules:-
Startup Order :- DAC --> Mixers --> Output PGA --> Digital Unmute
Shutdown Order :- Digital Mute --> Output PGA --> Mixers --> DAC
This assumes that the codec PCM output path from the DAC is via a mixer and then
a PGA (programmable gain amplifier) before being output to the speakers.
Minimising Capture Pops and Clicks
==================================
Capture artifacts are somewhat easier to get rid as we can delay activating the
ADC until all the pops have occured. This follows similar power rules to
playback in that components are powered in a sequence depending upon stream
startup or shutdown.
Startup Order - Input PGA --> Mixers --> ADC
Shutdown Order - ADC --> Mixers --> Input PGA
Zipper Noise
============
An unwanted zipper noise can occur within the audio playback or capture stream
when a volume control is changed near its maximum gain value. The zipper noise
is heard when the gain increase or decrease changes the mean audio signal
amplitude too quickly. It can be minimised by enabling the zero cross setting
for each volume control. The ZC forces the gain change to occur when the signal
crosses the zero amplitude line.
Documentation/spi/spi-summary
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/sysrq.txt
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/usb/proc_usb_info.txt
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/usb/usbmon.txt
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/video-output.txt 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/x86_64/kernel-stacks
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/x86_64/machinecheck 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
Documentation/x86_64/mm.txt
浏览文件 @ 5a84d159
此差异已折叠。
MAINTAINERS
浏览文件 @ 5a84d159
此差异已折叠。
Makefile
浏览文件 @ 5a84d159
此差异已折叠。
README
浏览文件 @ 5a84d159
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/alpha/kernel/pci.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/alpha/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/alpha/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/alpha/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/common/rtctime.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/common/sharpsl_pm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/isa.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-at91/clock.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-at91/gpio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-iop13xx/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-netx/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-pxa/corgi_pm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-pxa/sharpsl_pm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-pxa/spitz_pm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-pxa/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mach-sa1100/jornada720.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm26/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm26/kernel/ecard.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm26/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/arm26/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/cpu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/syscall_table.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/kernel/vmlinux.lds.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/lib/libgcc.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/avr32/lib/longlong.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/avr32/mach-at32ap/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mach-at32ap/at32ap7000.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mach-at32ap/clock.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mach-at32ap/extint.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mach-at32ap/pio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mm/cache.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/avr32/mm/tlb.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/drivers/ds1302.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/drivers/eeprom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/drivers/gpio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/drivers/i2c.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/mm/tlb.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v10/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v32/drivers/gpio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v32/drivers/i2c.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v32/mm/tlb.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/arch-v32/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/kernel/profile.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/cris/mm/tlb.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/frv/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/frv/kernel/pm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/frv/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/frv/kernel/sysctl.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/frv/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/kernel/ints.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/h8300/platform/h8s/ints.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/Kconfig.cpu
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/Kconfig.debug
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/boot/compressed/relocs.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/acpi/boot.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/acpi/earlyquirk.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/apic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/apm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/asm-offsets.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/common.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/cpufreq/e_powersaver.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/cyrix.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mcheck/mce.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mcheck/mce.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mcheck/p4.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mtrr/if.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mtrr/main.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/mtrr/mtrr.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/proc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpu/transmeta.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/cpuid.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/e820.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/head.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/hpet.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/i8253.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/i8259.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/io_apic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/kprobes.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/microcode.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/mpparse.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/msr.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/nmi.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/paravirt.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/pcspeaker.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/smpboot.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/srat.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/sysenter.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/topology.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/tsc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/tsc_sync.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/vm86.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/vmi.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/vmitime.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mach-default/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mach-es7000/es7000.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mach-es7000/es7000plat.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/math-emu/get_address.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/math-emu/status_w.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/discontig.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/fault.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/highmem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/pageattr.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/mm/pgtable.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/oprofile/nmi_int.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/oprofile/op_model_ppro.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/pci/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/pci/common.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/pci/mmconfig-shared.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/pci/mmconfig.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/i386/pci/pci.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/hp/common/hwsw_iommu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/hp/common/sba_iommu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/ia32/binfmt_elf32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/ia32/ia32_entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/ia32/sys_ia32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/acpi.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/crash.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/crash_dump.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/efi.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/iosapic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/irq_ia64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/machine_kexec.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/msi_ia64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/perfmon.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/sal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/salinfo.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/mm/contig.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/mm/discontig.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/mm/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/huberror.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/io_acpi_init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/io_common.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/io_init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/iomv.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/msi_sn.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn2_smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/sn2/sn_hwperf.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ia64/sn/kernel/xpc_main.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/head.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/ashxdi3.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/checksum.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/delay.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/memcpy.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/memset.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/strlen.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/lib/usercopy.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi/defconfig.nommu
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi/defconfig.smp
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi/defconfig.up
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi2/defconfig.opsp 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi2/defconfig.vdec2
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mappi3/defconfig.smp
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mm/fault-nommu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mm/fault.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/mm/mmu.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/oaks32r/defconfig.nommu
浏览文件 @ 5a84d159
此差异已折叠。
arch/m32r/opsput/defconfig.opsput
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/atari/stdma.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/bvme6000/rtc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/ints.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/vmlinux-std.lds
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/kernel/vmlinux-sun3.lds
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68k/mvme16x/rtc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/platform/5307/ints.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/m68knommu/platform/5307/pit.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/Kconfig.debug
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/arc/identify.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/arc/memory.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/common/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/common/pci.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/common/power.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/common/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/common/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/au1000/pb1200/irqmap.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/cobalt/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/cobalt/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/atlas_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/bigsur_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/cobalt_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/db1000_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/db1100_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/db1200_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/db1500_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/db1550_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ddb5477_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/e55_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/emma2rh_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ev64120_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/excite_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ip22_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ip27_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ip32_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/jazz_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/jmr3927_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/malta_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/mipssim_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/mpc30x_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/ocelot_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/pb1100_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/pb1500_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/pb1550_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/qemu_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/rm200_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/sead_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/tb0226_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/tb0229_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/tb0287_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/workpad_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/configs/wrppmc_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/ddb5xxx/common/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/ddb5xxx/ddb5477/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/int-handler.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/ioasic-irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/kn02-irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/prom/identify.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/prom/memory.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/dec/tc.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/emma2rh/markeins/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/gt64120/ev64120/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/gt64120/ev64120/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/gt64120/wrppmc/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/gt64120/wrppmc/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/jazz/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/jmr3927/common/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/jmr3927/rbhma3100/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/jmr3927/rbhma3100/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/apm.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/mips/kernel/asm-offsets.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/cpu-probe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/gdb-stub.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/head.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/i8259.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irixelf.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irq-msc01.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irq-mv6434x.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irq-rm7000.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irq-rm9000.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/irq_cpu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/linux32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/machine_kexec.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/mips-mt.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/proc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/r4k_fpu.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/rtlx.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/scall64-64.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/scall64-n32.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/scall64-o32.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/signal-common.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/signal32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/signal_n32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/smp-mt.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/smtc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/sysirix.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/kernel/vpe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lasat/interrupt.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lasat/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lasat/sysctl.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib-32/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib-64/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib-64/memset.S 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/mips/lib/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib/iomap-pci.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib/iomap.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib/memcpy-inatomic.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/lib/uncached.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mips-boards/sim/sim_int.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mips-boards/sim/sim_mem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/c-sb1.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/cache.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/dma-coherent.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/mips/mm/dma-ip27.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/mips/mm/dma-ip32.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/mips/mm/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/pgtable-32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/mm/pgtable-64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/jaguar_atx/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/jaguar_atx/platform.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_3/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_3/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_c/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_c/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_g/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/momentum/ocelot_g/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/oprofile/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/fixup-sni.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/fixup-vr4133.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/ops-sni.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/pci-dac.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pci/pci.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/pmc-sierra/yosemite/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/qemu/q-mem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip22/ip22-eisa.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip22/ip22-int.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip22/ip22-mc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip27/ip27-irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip27/ip27-memory.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip27/ip27-timer.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip32/ip32-irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sgi-ip32/ip32-memory.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sibyte/bcm1480/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sibyte/cfe/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sibyte/sb1250/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sibyte/sb1250/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/a20r.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/ds1216.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/pcimt.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/pcit.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/reset.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/rm200.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/sniprom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/sni/time.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/tx4938/common/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/vr41xx/common/icu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/vr41xx/common/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/mips/vr41xx/common/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/perf.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/sys_parisc32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/syscall_table.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/topology.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/parisc/mm/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/Kconfig.debug
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/kuroboxHD.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/kuroboxHG.dts
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/lite5200.dts
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/lite5200b.dts
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc8313erdb.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc832x_mds.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc8349emitxgp.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc8568mds.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc866ads.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/boot/dts/mpc885ads.dts 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/cell_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/celleb_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc8272_ads_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc8313_rdb_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc834x_itxgp_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc836x_mds_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc8568mds_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/mpc866_ads_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/pasemi_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/configs/ps3_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/btext.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/cpu_setup_pa6t.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/cputable.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/entry_64.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/head_32.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/head_44x.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/head_64.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/idle.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/iomap.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/kprobes.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/legacy_serial.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/lparcfg.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/misc_64.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/module_32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/nvram_64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/pci_32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/pci_64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/pmc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/ppc_ksyms.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/proc_ppc64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/prom.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/prom_init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/prom_parse.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/rtas-proc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/rtas.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/rtas_flash.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/setup_32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/sys_ppc32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/sysfs.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/udbg.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/udbg_16550.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/vdso.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/vio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/lib/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/lib/rheap.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/mm/hugetlbpage.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/mm/mem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/mm/numa.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/mm/pgtable_32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/mm/pgtable_64.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/oprofile/common.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/52xx/efika-setup.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/powerpc/platforms/52xx/efika.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/powerpc/platforms/52xx/mpc52xx_pci.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/83xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/83xx/misc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/83xx/mpc8313_rdb.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/83xx/mpc834x_sys.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/powerpc/platforms/85xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/85xx/mpc85xx_mds.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/86xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/Makefile 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/m8xx_setup.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/mpc86xads.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/mpc86xads_setup.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/mpc885ads.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/8xx/mpc885ads_setup.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/cell/iommu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/cell/pmu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/cell/spu_manage.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/Makefile 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/beat.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/beat.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/beat_syscall.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/beat_wrapper.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/htab.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/hvCall.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/interrupt.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/interrupt.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/iommu.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/pci.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/pci.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/scc.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/scc_epci.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/scc_sio.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/scc_uhc.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/setup.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/smp.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/spu_priv1.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/celleb/udbg_beat.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/chrp/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/iseries/mf.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/maple/pci.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pasemi/Kconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pasemi/idle.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pasemi/iommu.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pasemi/pci.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pasemi/powersave.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/htab.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/mm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/ps3/spu.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pseries/firmware.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/powerpc/platforms/pseries/kexec.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pseries/power.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pseries/pseries.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/platforms/pseries/ras.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/powerpc/sysdev/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/commproc.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/cpm2_pic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/cpm2_pic.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/fsl_soc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/grackle.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/ipic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/micropatch.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/mpc8xx_pic.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/mpc8xx_pic.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/pmi.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/sysdev/qe_lib/qe_ic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/xmon/ppc-opc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/xmon/spu-dis.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/xmon/spu-opc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/powerpc/xmon/xmon.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/8xx_io/cs4218_tdm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/boot/simple/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/boot/simple/misc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/configs/taishan_defconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/head.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/head_fsl_booke.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/ppc_htab.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/ppc_ksyms.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/lib/rheap.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/mm/pgtable.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/4xx/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/4xx/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/4xx/taishan.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/4xx/taishan.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/gemini.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/ppc/platforms/gemini_pci.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/ppc/platforms/gemini_prom.S 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/ppc/platforms/gemini_serial.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/ppc/platforms/gemini_setup.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/ppc/platforms/lopec.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/pplus.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/platforms/prep_setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/syslib/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/syslib/i8259.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/syslib/m8xx_setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/syslib/ppc85xx_rio.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/xmon/ppc-opc.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/ppc/xmon/start.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/appldata/appldata.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/appldata/appldata_base.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/appldata/appldata_mem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/Kconfig 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/aes_s390.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/crypt_s390.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/crypt_s390_query.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/s390/crypto/des_check_key.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/des_s390.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/prng.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/sha1_s390.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/crypto/sha256_s390.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/hypfs/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/hypfs/hypfs.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/hypfs/hypfs_diag.h 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/s390/hypfs/hypfs_vm.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/hypfs/inode.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/binfmt_elf32.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/compat_linux.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/compat_linux.h
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/compat_signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/compat_wrapper.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/cpcmd.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/crash.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/debug.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/early.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/ebcdic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/head31.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/head64.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/ipl.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/kprobes.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/machine_kexec.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/module.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/profile.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/s390/kernel/ptrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/s390_ext.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/stacktrace.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/syscalls.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/kernel/vtime.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/delay.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/qrnnd.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/uaccess.h 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/uaccess_mvcos.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/uaccess_pt.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/lib/uaccess_std.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/math-emu/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/math-emu/math.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/math-emu/qrnnd.S 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/s390/mm/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/mm/cmm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/mm/extmem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/mm/fault.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/mm/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/s390/mm/ioremap.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/s390/mm/vmem.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/bigsur/Makefile 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/bigsur/io.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/bigsur/irq.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/bigsur/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/bigsur/setup.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/ec3104/Makefile 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/ec3104/io.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/ec3104/irq.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/ec3104/setup.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/hp6xx/hp6xx_apm.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/mpc1211/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/mpc1211/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/mpc1211/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/renesas/r7780rp/io.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/renesas/r7780rp/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/renesas/rts7751r2d/io.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/renesas/rts7751r2d/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/7206/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7206/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/7206/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7300/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7300/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/7300/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/73180/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/73180/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/73180/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7343/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7343/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/7343/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/770x/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/770x/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/770x/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/770x/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7751/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/se/7751/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/se/7751/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/sh03/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/sh03/led.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/boards/sh03/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/boards/shmin/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/cchips/voyagergx/irq.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/cchips/voyagergx/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/configs/se7750_defconfig
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/drivers/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/drivers/dma/dma-sh.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/drivers/heartbeat.c 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/drivers/pci/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/drivers/pci/ops-bigsur.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/drivers/pci/pci-sh7751.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/Makefile
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/apm.c 已删除 100644 → 0
浏览文件 @ e80a0e6e
此差异已折叠。
arch/sh/kernel/cpu/init.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/irq/ipr.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh2/entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh2/probe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh2a/probe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh3/entry.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh3/probe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/cpu/sh4/probe.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/debugtraps.S 0 → 100644
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/early_printk.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/entry-common.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/io_generic.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/kgdb_stub.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/process.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/setup.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/sh_ksyms.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/signal.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/syscalls.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/time.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/traps.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/vmlinux.lds.S
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/kernel/vsyscall/vsyscall.c
浏览文件 @ 5a84d159
此差异已折叠。
arch/sh/mm/Kconfig
浏览文件 @ 5a84d159
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或